GitLab

causing error at import time :'(

which will occurs when the profile has some data object linked to several mime
types or format ids. Tests setup is shared with profile generation, so modify it
there, it won't hurt the original functional case to cover this as well.

Closes #36331831

since this may now occurs with values deducted from file category. In such case,
generates proper rng:choices / xsd:enumeration.

Related to #36331831

Upon modification of file_category relation, synchronize mime_type / format_id
values for the binary data-object, through intermediary SEDAMimeType /
SEDAFormatId entities which are kept for now but could be removed if the
automatic user cardinality system is validated by business people.

Synchronization is implemented to consider textual values of concept in the
category vocabulary, and to keep only those which have a match in the
vocabularies that are set on the transfer (code list version).

Because of that, don't attempt to synchronize values on archive unit component,
that should be done when it is imported into a transfer.

Related to #36331831

on a binary data object. This is done to prepare automatic synchronization of
these entities'values (concept) according to file_category. At some point we may
want to remove them in favor of direct relations to the binary data object,
since these are there to handle a cardinality which will be automatically
handled, provided the implemented behaviour fine with business people.

Related to #36331831

rather than later, so one may still use the `import_seda_schemes` high-level
function to import files which are not in the migration/data directory (but
rather in test/data).

Related to #36331831

Do it minimal with no js involved but a simple multiple select. This still have
to be coupled to format_id / mime_type but this will be done in later csets.

Related to #36331831

So they may link to several mime types / formats deducted from the file
category. This was actually not very usable before, since one could not expect
a single pronom format (e.g. for a specific PDF version).

Related to #36331831

provided by the SAEM team. Link it to the file_category relation.

Related to #36331831

This relation will be used in later csets to link the file to a high-level file
format, that will be used to control low-level mime  type and format id fields.

Related to extranet #36331831

not  format_litteral

in case the profile is a simplified profile. This is because this relation is
there because of the SEDA 2 underlying model, where all data objects are below
the transfer node, but it is not used in SEDA 0.2 and 1.0, where data
objects are dispatched under the archive units tree. So we don't want to prevent
having several data objects with cardinality != 1 at different level of the
tree.

Closes extranet #37372358

Introduce a bootstrap tooltip whose presence is indicated through a question
mark on hover.

Notice the comment change above aliasing cw's uicfg: this have to be there
because of the relative import from our own uicfg module, though it's still
unclear to me why this screw up the module's local namespace.

Closes #17106808

Introduce in views/uicfg.py a new data structure providing XSD element name and
documentation indexed by entity type, relation type and role.

Related to #17106808

so that they may be used later to generate tooltips in the UI.

This requires using yet unreleased pyxst to get support for documentation
elements.

Related to #17106808

0.10.7 changed default cardinality but missed this migration step.

to keep existing migration in sync with change introduced in ba6a36fa1ce7.


Closes #17106805

because this is related to simplified view of those object and unrelated to
archive unit, so one would rather expect to find them there.

This allows to keep only specific rules in derived rtags and to look for other
in the "parent" rtag, so that rules which are set there after the derived rtag
have been constructed are still considered (if not overriden).

This will avoid some rules duplication in at least the saem_ref cube. There may
be a few ones that may be removed from this cube but this is not done by this
commit.

Using this feature requires backporting fixes done in unreleased cubicweb
3.25.3.

Related to #17106806

and drop monkey-patches which are hence no more necessary.

Closes #17106806

to only contains languages whose 2-letters code is in the SEDA 0.2 languages list.

Closes #17106805

Closes #17098388

As explained in the previous commit, we want items with cardinality = 1 first
then the one with cardinality != 1 if any. See previous commit for detailed
explanation.

Closes #17098404

By trying to validate several profiles using Jing (in Asalae), it appears that
it isn't possible to validate a profile where there are several elements with
the same name with optional or/and multiple cardinality, e.g. with a profile
telling we expect  1..n Document followed by 1 Document, a transfer with two
documents won't be accepted, telling a required document is missing. This is
much probably because the validator "eats" the two documents for the first rule,
then it misses one to satisfy the second rule.

In order to avoid generating such insatisfyable profiles, while not changing
much the UI for now, we decided to add hook preventing usage of several sibling
children with a cardinality != 1 during edition, and then at RNG profile
generation time to put the one with cardinality != 1 as last children. That way
profiles should always be validable.

This patch introduces the hooks preventing insatisfyable profiles to be created.
The next one will ensure the order of RNG export.

Two hooks are added to check for unhandled case one for new watched relations
and the other for update cardinalities.

Added test cases for the 3 most prominent cases: archive unit, document and
keywords, with more coverage in the first one and only simple check for the two
others. Also, some test have to be updated to follow this change. Notice diff of
exported RNG isn't nice to read but is actually only removal of a surrounding
"oneOrMore" element.

Related to #17098404

Those structures will be used as bases for hooks necessary to check for
unhandled cardinalities, that will be introduced by the following change set.

We have to watch composite relation that may lead to several children, and for
the entity types that are possible as children.

Related to #17098404

This has several advantages:
* it's consistent with xsd/rng defaults
* it simplifies code
* it may avoid undesired validation error once #17098404 will be fixed

This requires several test update, fixed by a mix of test case update or
expected data update to minimize the changes.

Related to #17098404