GitLab

Take care msgid are not the saem for archive transfer vs archive unit.

Related to extranet #12349917

in case of simplified profile. This requires adding afs rules and adding/updating
some translations.

Closes extranet #16385548

It should simply be skipped by adding it to GRAPH_SKIP_RTYPES.

giving client cube a consistent way to control graph traversal and so to avoid
considering undesired special relations such as container.

this is not part of the seda cube API.

* scheme_relation_type / scheme_entity_type (reserved to managers)
* code_keyword_type (users friendly)

Having a standard user available in a security test makes sense.

We prefer a succeding migration then detecting weirdness in the database.
Error encountered while migrating the seda demo.

using global sets instead of through partial .keyword attribute.

This is useful for saem to insert its naa without redefining the whole function.

similarly to assertUnauthorized.

so it's importable and reusable from client libs.

add avoid a lot of confirmation.

This is an enum in the original xsd while we don't output possible values
currently, so in the mean time make it mandatory, it's still a bit better than
relying on the original schema for that, and it makes sense from a business POV
to force specification of description level of an archive unit.

A lot of tests have to be updated, some of them because output value is now
different, others because we've to introduce a scheme+concept to handle the
validation, but they were not expecting that.

Closes #16687907

not text. Consistently with SEDA 1/0.2 export.

as this was already done for SEDA 1/0.2 export.

Move method from SEDA 1 export to the common base class with SEDA 2 export to
make it available there and avoid duplication. Also SEDA 2 test needs update
since this method return cwuri instead of absolute_url.

Related to extranet #15934739

Export used to chose concept value by searching for label with the following
language code:

1. version specific (seda-2, seda-1 or seda-02)
2. seda
3. en

and crash if no matching label was found. But it seems we don't want it to crash
because we use some concept which has e.g. only a concept in 'fr' language code.
At some point we may want to improve this, depending on the relation (internal
seda vocabulary vs open vocabulary such as keyword reference), but for now,
let's add 'fr' to the expected language list and fallback to any language if
none has been found so the export doesn't fail.

Related to extranet #15934212

useful for e.g. the saem_ref cube that introduces some entity types (Activity)
which would be shared by different compound graph while we want it to be
skipped.

Added a test checking that we've a consistent number of separators in each line
of lcsv files. This led to fix some some headers as well as some definitions
containing the separator in text, leading to no error but unconsidered text.

Along the way, uniformize column labels.

We do not mind fixing definitions in existing database for now, since there are
now production databases in the wild yet.

Related to #17066564

one was erroneous due to a bad copy/paste, the other was not correctly
translated in the SEDA 1.0 specification at
https://redirect.francearchives.fr/seda/api/seda_v1-0_descriptionlevel_code_xsd_Element_LevelDescriptionCode.htm#LevelDescriptionCode

This first point also fixes concept's definition, but we do not mind fixing it
in existing database for now, since there are now production databases in the
wild yet.

Related to #17066564

We never run into this part of the  code, so let's drop it.

Before this cset, data objects were inserted one after another in some random
order, but in the RNG semantics this was forcing their order. To avoid this,
we've to put them in a rng:group node.

Several strategies have been considered to achieve this:

* change the underlying XSD representation, but this would require either
  changing the data model or handling a difference between the representation
  used to generate the schema and the one used to generate the RNG profile,

* add some special case when a data object node is generated, but this would
  require handling some state to see if the rng:group has already been inserted,

* add a postprocessing step doing the job all at once using lxml's API.

It appeared to me that the two first strategies where too much tricky and less
readable than the third one.

Related to #17066567

XSD isn't able to properly export SEDA 2.0, stop supporting it all together.

Some of them being in .pot, others in persistent vocabularies requiring some
migration.

Closes #17066620

when in a simplified profile, because the ui only display bdo's cardinality.

Closes #17066567

Its tests are fine under the ValidationHooksTC umbrella.

will be easier to use another function from this module.

Cardinality and permissions defined on the relation type wasn't considered as
expected because the relation is added dynamically in post_build_callback. We
have to set them explicitly there.

This added to a bug in the cloning code led to entities with several containers.
To fix this, migration script pick the container with the greatest eid since it
should be the one which is not unexpectedly copied. Anyway, even if that's wrong
that's no big deal because there are only demo instances for now which don't
really care of data loss.

This patch also set properly cardinality on container relation for
SEDAArchiveUnit, which is expected to be optional while mandatory for others.
This has not been detected before since it wasn't actually mandatory by default
before this patch.

I don't like it and it doesn't work well.

Closes #17066566

The previous implementation was yielding rdefs which were not in the compound
graph, because of the blind loop on every rdef of an rtype.

To fix this, we can't use structure_def whose data structure isn't adapted to
this use-case, rather iterate top-down from the root (this 'child_structure'
method is unfortunatly not in compound.Graph, we might add it there at some
point).

those went unnoticed because in saem they are added by some global widget, but
they are actually necessary. Along the way, declare them using standard
needs_css / needs_js widget class attributes.

Closes #17066562