GitLab

I.e. instead of having two (clickable) buttons, one with the action text
(e.g. "add") and one with the caret and only the latter with the effect
of toggling the menu, we now only produce one button with both the
action text and the caret as content. This way, the user won't get
confused when clicking on the text as the menu will toggle.

it's an implementation specific attribute, we don't want to see it in the UI.

Introduce a bootstrap tooltip whose presence is indicated through a question
mark on hover.

Notice the comment change above aliasing cw's uicfg: this have to be there
because of the relative import from our own uicfg module, though it's still
unclear to me why this screw up the module's local namespace.

Closes #17106808

This allows to keep only specific rules in derived rtags and to look for other
in the "parent" rtag, so that rules which are set there after the derived rtag
have been constructed are still considered (if not overriden).

This will avoid some rules duplication in at least the saem_ref cube. There may
be a few ones that may be removed from this cube but this is not done by this
commit.

Using this feature requires backporting fixes done in unreleased cubicweb
3.25.3.

Related to #17106806

and drop monkey-patches which are hence no more necessary.

Closes #17106806

consistently with the primary view.

This is used for internals and is not yet ready to be exposed to admin.

It doesn't add any value other the link's title, while it's costly to maintain
translation (and a lot of them are missing).

Related to extranet #12351787

Depend on cubicweb >= 3.24

and add a test to avoid this in the future.

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

Related to #16684053

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.

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

Closes #16684239

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.

So underlying things such as deepcopy are hidden a bit. Along the way, rename dor_afs to
do_ref_afs which is easier to read.

We'll need that here soon!

There is now a pop-up allowing to edit the annotation.  If some annotation
exists, pop-up is displayed open from the start.

Disable this functionnality for first level content types, because for them it
feels better to see the annotation as a first level attribute.

Existing views already display the annotation properly when it exists.

Closes #14157055

Validation is done in a custom hook due to cw'schema limitation: all constraints
must be checked and we need several one in our case (one for each possible
parent type).

A custom vocabulary function is introduced and reused for the 'seda_rule'
relation. There is still some limitation in case where the parent entity has not
yet been created, as we're missing information to go back to the container
holding the scheme definition.

Closes #13562327

and move the XSDM_MAPPING singleton to the xsd module.

On our demo where this cube is in a CW_CUBES_PATH directory, I had to add a
__init__.py file in this directory and to put it in PYTHONPATH to avoid a crash
on start, because of the attempt to find __module__ of registrable instances.

This problem hasn't been reported to cubicweb nor lgc because the proper fix
would be to have cubes as standard python packages. Until then we'll live with
those monkey-patches.

Since this element is optional, it needs special handling at XSD generation time
to compute its cardinality: if one of its subelement has mandatory card, its
cardinality should be 1, else 0..1 is fine.

Extract a (rtype, role) iterator on the XSD mapping out of
rtags_from_xsd_element function, to be reused by XSD generation.

Related to #11447483

for later usage from other modules

and start configuring the creation/edition form for them.

All the "add button" related code in __init__ has been backported from the
saem_ref cube.

Related to #11447483