GitLab

Depend on cubicweb >= 3.24

As specified by extranet #14592456

instead of 'mot-clé', as specified in extranet #14592456.

and so avoid deprecation warning.

leading to archive units which are not in a profile.

There were concurrency between simplified_afs and do_ref_afs and the latter was
unexpectedly selected, leading to erroneous interface proposing to link to an
existing data objects, which makes no sense in the case of simplified profile or
component archive units.

This was because of an `is_typed_reference` unexpectedly return 1 in this case,
while this is not possible because component archive unit are considered
"simplified", and there may be no typed reference in a simplified profile.

Fix it by extracting a `is_full_seda2_profile` function from the
`full_seda2_profile` predicated. Along the way, renamed `is_typed_reference`
into `typed_reference` for consistency with `full_seda2_profile` and
`simplified_profile`.

similar to the one added for do_ref_vocabulary in parent cset.

and add a test to avoid this in the future.

Along the way "properly" handle monkey-patching necessary to import some seda
views modules.

else when there is no value field, it has a tiny space allocated and you've to go
to the right side of the table to see the '+' allowing to add a value.

Closes extranet #16687517

Closes extranet #16687524

it should only be displayed for full seda2 profiles.

Leading to untranslated string. Fix xsd2uicfg and regenerate uicfg file.

As a right box (the default location) it takes some precious horizontal space
for low-benefit information.

On the saemref demo with a few thousands of authority records, it's necessary
to have such 'lazy' widget.

closes #16687425

else its cardinality will be considered while we want the attribute's cardinality
defined in the schema.

Fix test broken since f54a06d45f49

Closes #16684053

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.