GitLab

Those special attribute / content values should be explicitly typed using xsd's
ID and IDREF respectivly.

Closes #16070553

undetected by flake8 because of later assignment to the same name.

Every SEDA version allow several top level archive units or equivalent.

Closes #16070768

Move all (?) rtags customization for the case of simplified profiles to the
``simplified`` module. This:

* avoid rtags proliferation, hence errors,
* provide a single entry point for client module (eg saem_ref).

The situation could be a bit improved by using implementation for cubicweb's
#16164880.

.format on encoded string will attempt to encode its parameters, unlike the %
operator which will unicode the format string.

The scheme may contains generic 'seda' values. This function properly deal with
every possible language.

else it may causes problem with during tests.

instead of a simple uicfg rule which isn't enough because of the ambivalent usage of SEDAStartDate: it was also currently hiding it from archive unit's start date which is undesirable.

since it doesn't handle that.

else a ValidationError is raised when a value is set, since constraint can't be
verified.

To do so, introduce a new "component_unit" selector.

If this is validated, we will have handle this on import in a profile (check
vocabulary consistency).

Proper fix has to be discussed, in the mean time don't crash.

We still rely on the referenced_by trick, simply removing __linkto information.
This is the quickest way to make it work, because customizing data reference to
inline the binary data object for is painful (among other, this is an ambiguous
relation which isn't supported by inlined forms).

The main known drawback is that the form's title is contextless.

With some adjustments in hooks:

* in SetContainerOp, avoid inserting container relation when it's already
  being set (by node motion);
* prevent EnsureChoiceNotEmptyOp from being run with the relation is not
  targetting a choice.

Closes #15047080.

Just keep ITreeBase instead of ITree and added a compatibility method
`iterparents` to IContainedToITreeBase adapter to minimize changes in
views/jqtree.py.

Motions in tree are not handled yet.

Related to #15047080.

At some point, we'll probably have to:

* ensure action doesn't appear in case it shouldn't (eg reference archive units)

* move it to the archive unit tab rather than in the actions box

But this is a almost direct backport, enhancements will come later.

because I feel good that way. For better argumentation, see
http://stackoverflow.com/questions/32543608/deque-popleft-and-list-pop0-is-there-performance-difference#32543726

Before one had to pick a value...

Else it's built for each imported file, and this is very costly since when the
massive store is in use, table indexes have been dropped.

This will be done properly in next skos release which will accept extid2eid map
as optional argument.

For instance in SAEM, we need a store with custom metadata generator that will
generate ark for imported concepts.

This prepare the 'seda components' functionality from SAEM. For now, we don't
support data object as component, since most metadata moved to its related
archive unit with SEDA2.

We also have to change data object parent relation's cardinality since in case
of an archive unit as  component, we can't have this relation to the transfer
entity.