GitLab

Depend on cubicweb >= 3.24

Leading to untranslated string. Fix xsd2uicfg and regenerate uicfg file.

Related to #16684053

In SEDA 2.1, only one Content node is permitted per archive unit (2.0 allow
multiple ones). This allows to skip the SEDAContent entity in our model and to
attach all its children to its parent
(SEDASeqAltArchiveUnitArchiveUnitRefIdManagement).

This patch replaces occurences of SEDAContent/seda_content and should have test
to green but there is still some work to do on the UI side.

Related to #16684017

They have been introduced at a first glance to handle references during profile
generation as well as display of 'first class' element in the UI. The main problem is
that they clash when using the 'import archive unit' feature, since one may not
import the same unit twice without changing the id first. Another problem is
that their purpose is not clear to end-user.

This changeset remove the attribute, use eid instead during profile generation
and fix tests. UI and proper migration will be handled in later csets.

Related #16070476

We've to distinguish the case of generic reference from other kind of references
available through SEDAContent (IsPartOf, VersionOf, etc).

There is now a pop-up allowing to edit the annotation.  If some annotation
exists, pop-up is displayed open from the start.

Disable this functionnality for first level content types, because for them it
feels better to see the annotation as a first level attribute.

Existing views already display the annotation properly when it exists.

Closes #14157055

For UX reason, don't add it when there is no user_cardinality as well (so we can
consistently edit annotation).

Related to #14157055

Related to #14157219

As there may be multiple ones.

Closes #13750862

Closes #13853501

Related to #13751449.

On archive unit form, hiding the choice field was handled wrongly by editing
xsd2uicfg.py The real problem is we need to load uicfg rules before the views.

It makes no sense to specify it at profile definition time.

We must export it manually when generating an XSD profile, since this is a
required element.

Closes #13562322

for seda relationship that may appears in the 'attributes' section (ie
cardinality '1' or '?').

and use rtags_from_xsd_element function for Gps subelements.

Deactivating it for all relations.

Those configure the ORM (pre-retrieved attribute and sort order) and provide a
'value_attr' attribute, to be used in the UI  to determine if the entity has
some business attribute or only some cardinality.

and use it for uicfg generation.

so they use a simple TextInput rather than a TextArea.

rather then adding them and skipping them later. That made later use of the same
data structure easier.

Related to #11447483