GitLab

and drop related monkey-patch.

And not globally.

Related to #13830428.

Since this is mandatory in data model.

In that case, we shouldn't check for existence of an entity under the choice

A content has no more than one title and description. In the same way, an
ArchiveTransfer has no more than one comment.

Handle this as hardcoded special cases, waiting for a better solution.

Closes #13750725.

Iterate over all etypes and rdefs constituting the compound graph of a
`SEDAArchiveTransfer` and set the same permissions than the
`SEDAArchiveTransfer`.

Instead of displaying the DataObjectReference entity. And put this information
in the `relations` section.

Related to #13751449.

Closes #13830646, #13853099.

Closes #13813234.

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.

As I can't make it appear on the inlined form title, make the overall message
look better by omitting obscur relation name.

Also, change translation to use alternative instead of xsd:choice, as in the UI.

This code wasn't tested and nothing was relying upon it (those elements are in
inlined form in the UI).

And hide them from the default tab

Also more consistent between main form and inlined form, and drop display of
counter.

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.

Handle case where size is 2.

Closes #13562322

* drop buggy call to afs
* use lower case for labels, for consistency
* consistent use of "ajouter" in "add a ..." messages (only for element with
  multiple cardinality)
* reledit configuration

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