GitLab

Closes extranet #14593198

In later cset, we'll want to retrieve the inherited rule from the management
rule UI. This UI is generated from SEDAArchiveTransfer and
SEDASeqAltArchiveUnitArchiveUnitRefIdManagement entities, so we want this method
on those entity types.

[entities] Make _climb_rule_holders working on SEDASeqAltArchiveUnitArchiveUnitRefIdManagement entities

This will be useful in later cset to add inherited_rule method on this entity
type.

and add it as a method of archive unit entities.

Related to extranet #14593198

This makes the UX better by adding constraint on what is allowed or not.

as we may find there information about location of the entity within the result
set.

it's already in parent's selector.

It doesn't add any value other the link's title, while it's costly to maintain
translation (and a lot of them are missing).

* 'value' is better than 'type' which is the whole section's title
* we use lower case everywhere

to make it clearer they depend on values previously selected.

Related to extranet #12351787

* Display type before term, because its value will modify possible term's
  vocabularies, so it makes sense to display it before

* Force display of type as well as term, it make things (js) simpler and user
  still have the cardinality if he doesn't want to force a type to be set

* Hide the 'add new' link in any cases, else it ends up appearing unwillingly
  while we don't need it at all.

Related to extranet #12351787

as specified in extranet #12351787.

Some UI tweaks will be done later to make it more robust (removing the
possibility to add/remove the type inlined form).

'cause I find it clearer that way.

Related to extranet #12351787

Also update its title and concept's language because it's not a SEDA 2 specific vocabulary.

so user can clone entities.

this causes an error during automatic tests, and we don't want that anyway.

breaking test with a fresh database.

to consider that its container may be None (in case of a component archive
unit).

This is a bit tough since in SEDA 0.2, Integrity element are defined as children
of the root transfer node, hence we have to reuse the kind of reference trick we
have in SEDA 0.2 export: document export a seda:profid attribute whose value is
the referenced by default value on the UnitIdentifier element associated to the
digest (and algorithm) definition.

Related to #16687452

Using Integrity element of the document (data object).

Related to #16687452

So we'll be able in later cset to override xsd_transfer in SEDA 0.2 export
without having to much duplicated code.

This will be used by latter cset to support Integrity (digest algorithm)
elements in SEDA 0.2.

so it's much easier to read.

using yet another custom afs.

whatever its role.

by copying the clone_of relation.

Closes #16684622

concret subclasses are built in registration_callback.

of archive transfers and units.

and fix a typo in a comment