GitLab

we want to use them for seda 1.0 / 0.2 export.

Now that we've proper vocabularies for them.

with some code cleanups and refactor it that we may ensure data files validity
from tests.

To do so we will handle seda-2, seda-1, seda-02, seda (default) language to
specify value that should be used in export. When multiple languages are
specified, also add explicitly a french or english label.

This cset adds some new data files from the saem_ref cube, or complete existing ones.

Related to #12759207, #15045341

It should be in the application cube.

Not updating debian/changelog and cubicweb-seda.spec because this release is
still for demo only, not an actually packaged release (installed from source on
our demo server).

Reintroduce code list version for simplified profiles, but restrict elements to those making sense in that case

similarly as for archive units.

So hide the former and add a tab for the later on archive unit in simplified
profiles.

filename is a bit specific since it's a BinaryDataObject attribute retrieved
from its jumped FileInfo element.

As an attribute, it's displayed in the BDO main tab.

As a FileInfo element, it was also catched by rtags_from_xsd_element to be
displayed in the tab display FileInfo subelements. This was also screwing up
its reledit view.

Skipping such attributes in underlying `rtags_from_rtype_role_targets` function
fixes both problems.

unclear why it wasn't displayed by default while it is for Compressed entities.

Add clearer translation along the way.

There should be no need for etype specific rules, default rules will be
overriden.

Move entity_call method in parent abc for tabs displaying objects below archive unit's content sequence

We don't have to handle the case of "reference" archive unit. Refactor a bit the
original tab class to ease this overriding, by introducing a 'sub_unit_types'
class property.

Instead of displaying content subobjects, display directly the properties we're
interested in. An archive unit may only have one content entity in the case of
simplified profiles.

so that on creation, we don't get every archive unit in the database but only
those in the parent's container.

And rename it consistently with other simplified profile specific tabs.

not the transfer entity.