Flis Metadata Client
====================
Client for FLIS applications that require common metadata
Quick start
-----------
#. Add ``flis_metadata.common`` and ``flis_metadata.client``
to your ``INSTALLED_APPS`` setting like this::
INSTALLED_APPS = (
...
'flis_metadata.common',
'flis_metadata.client',
)
#. Add ``METADATA_REMOTE_HOST`` and ``METADATA_REMOTE_PATH`` into your settings file::
METADATA_REMOTE_HOST = 'http://localhost:8000'
METADATA_REMOTE_PATH = ''
#. Run ``python manage.py migrate`` to migrate the common app.
#. Run ``python manage.py sync_remote_models`` to sync the metadata models with
the remote ones.
How to add a new model
----------------------
We want to move model ``Foo`` from ``flis.someapp`` to be
replicated in all FLIS apps
In this app:
1. Add the model in ``common/models.py``. Make sure it extends
``ReplicatedModel``.
2. Add ``urls``, ``views`` and ``templates`` to edit it.
3. Add a fixture having all instances of ``Foo`` for every FLIS app.
Note:
This data will be replicated and migrated in every app that uses
this package, so make sure that the migration includes everything
4. Update the pip package using ``setup.py``.
In ``flis.someapp`` and other apps using this model
#. Update ``eaa.flis.metadata`` package in ``requirements.txt`` and
install it.
#. For every relation to the ``Foo`` model::
# add a new fake foreign key field
x = models.ForeingKey(Foo)
fake_x = models.ForeingKey('common.Foo')
# or add a new fake many to many field
y = models.ManyToManyField(Foo)
fake_y = models.ManyToManyField('common.Foo')
#. Add a migration to add the new fields
#. Create a datamigration that
a) Calls ``load_metadata_fixtures`` management command
b) For every ``x`` copies the same information in ``fake_x``
using the instance found in ``common.Foo``::
obj.fake_x = orm['common.Foo'].objects.get(title=obj.x.title)
# or
for y in obj.y.all():
obj.fake_y.add(orm['common.Foo'].objects.get(title=y.title)
#. Remove the ``Foo`` model and ``x`` fields from
``flis.someapp``.
#. Create an automatic schemamigration to reflect the removals.
#. Rename ``fake_x`` fields to ``x`` in ``models.py``.
#. In the migration generated at step 5 rename the fields and M2M tables from
``fake_x`` to ``x``.
#. Run the migration in different corner cases.
Note:
You can browse through ``flis.flip``, ``flis.horizon-scanning-tool`` or
``flis.live_catalogue`` to see an example of such migrations.
Metadata
Release files for eea.flis.metadata 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| eea.flis.metadata-0.6.2.tar.gz | 8.0 kB | Without provenance | Details |
Release files / eea.flis.metadata-0.6.2.tar.gz
| Download URL | eea.flis.metadata-0.6.2.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa7e5eff3fa5b367bd485a1f228045912ccf6eebcfddc482881e37779cfffa11
|
|
BLAKE2b-256 checksum How to use checksums |
00f6926a11c042b1670e05e69da4822475308b71ea3fde2f81cbce2ed9260189
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for eea.flis.metadata 0.6.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.