GitLab

Related to #16684053

Now that we have a different ui for simple vs reference keyword, cardinality on
keyword reference is no more meaningful and hidden in the UI, since we would
like to always have cardinality=1 for reference keyword when generating profiles.

The easiest way to do so is to set proper default value, else by removing the
attribute we would have to do extra customization to the SEDA 2 profile
generator to consider that it shouldn't use the cardinality in the SEDA 2 XSD
(0..1).

Closes #16070921

This is done using a 'keyword_type' parameters at creation time, then detecting
if the keyword has a reference or not. In the case of simple keyword, only
display cardinality and keyword's content (the string). For concept, hide
keyword's content but force creation of a reference.

Reference's cardinality may be hidden, though a bit of work will be needed to
generate '1' cardinality on profile export.

Related to #16070921

This is a mandatory and unique children of Keyword, so it may be skipped while
this ease thing to get a different UI for 'simple keyword' vs 'concept keyword'
that still has to be done.

Related to #16070921

Hard-coded changeset has been rebased and integrated.

This allows to factorize url parameters generation and to have consistent
separation of concerns.

from the archive unit's archive units tab (to add sub archive unit parametrized
by an extra URL parameter).

it had two responsability: computing links to put in the dropdown and actually
generating the HTML. This makes it unusable when one want to generate link in
another fashion.

Rather extract a new `add_links_from_rtypes_roles` to generate links and inline
the HTML generation in client code.

Though this requires yet unpublished patch of cw 3.24 to not crash on addition
of Activity (as prov is a dependancy of the eac cube).

Test if Agent is still in the schema before dropping it, since saem_ref use the
seda cube but also have its own definition of Agent, which we don't want to
drop.

This requires a bit more work than expected due to monolitic implementation of
render_attributes in cubicweb, as explained in the inline comment.

Closes #16684017

Everything has been moved to the views.archiveunit module.

Closes #16684017

i.e. the tab displaying content information which is not yet displayed by other
tab (mainly controlled by uicfg rules).

Move there pre-existing code in the same module, for the case of simplified
profiles.

Related to #16684017

The only one remaining being the default one. Along the way, rename some
identifier and classes to be more consistent.

The views.content module isn't modified yet, it will be dropped all at once when
this work will be completed.

Related to #16684017

Update rql query and use .dc_title entity method to generate label from
annotation (prefetched).

This relation is explicitly marked as composite in shema/__init__.py to ease the
case of simplified profiles, where we want data objects to appear as children of
archive unit instead of references as expected by SEDA 2. Doing this, we
introduced a bug in SEDA 2 profile generation where the target value (hence the
referenced data object) was also considered as the 'cardinality entity' (the one
defining the cardinality / annotation) for the associated XML element. This led
to using the data object's cardinality / annotation for the *reference* element.

this is necessary to setup a new instance (import of lcsv data).

This is not anymore necessary for the web UI which may now inline this into the
archive unit creation form.

else one see 'type OAIS' in primary tab and "type d'information" in edit form.

else extra \n get inserted.

This was done only for simplified profile, but since we folded SEDAContent
entity we want this for the generic case.

Along the way, introduce base classes that will be used to do more tabs like
those (all the content's tab will be moved up to the archive unit).

Related to #16684017

instead of 'SEDASeqAltArchiveUnitArchiveUnitRefIdManagement' which is boring to
read and remember.

Related to #16684017

This should have been done for a while, but was not causing problem until we
jumped the Content element. This is now necessary to avoid test failure.

Related to #16684017

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

This has been missed while backporting from the saem_ref cube. Use a more
specific class name along the way.

As this is currenly the actual meaning. If it has been properly named, I would
probably have returned the proper value for data object (false, not true).

* make it mandatory ;

* update migration script removing id to copy existing value to annotation
  before removal ;

* regenerate test data file since this change adds exported annotations.

Along the way, add missing escaping when displaying user_annotation, by using
printable_value.

Related to #16070476

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

Closes #16688021

for instance in case of restrictionEndDate, it was returning

  [(content entity, restriction end date entity)]

instead of

  [(restriction end date entity, None)]


This was only causing cardinality error (eg you get the content entity's
cardinality instead of the restriction end date's one) which have been unnoticed
until a cardinality uncompatible with attribute was used on a content node.

Closes #16688086