Is your feature request related to a problem? Please describe.
We were struggling with the problem, that our projectinvestigators have the right to edit their projects via the editmodes, but were not allowed to associate related (archived) publications to the project. The relation to the project is hold in the Publications dc.relation.project authority field and the rights to edit the Publication are only given to our controller group / collection administrators.
Describe the solution you'd like
We would like some additional mode where other entities can be assigned to existing entities. We suggest the terminus associate / associationmode (interlinking/linking and relations are ambiguous in the dspace world). The solution could be some mixture of the edit-itemmode and the edit-relation-mode. Users with the rights to edit the project see some context-menu-button, come to some new page with some related entity search configuration and can select/ or deselect specific entries. When they select/deselect the entries, then the Publications are updated.
Describe alternatives or workarounds you've considered
workaround: some implementation of some ItemEnhancer on the project, which fills some fakeitem field to the Publication and which is than deleted and the authority value is created on the referenced Publication.
Additional context
The logic is similar to the edit-relationship module; it displays some search configuration with additional action buttons to associate/disassociate items. Some additional endpoint triggers the action. The access to the page/endpoint and the specific context-menu entry is evaluated by some implementation of the AccessItemMode and so configured in some way similar to the edit-item-mode
Components / workflow:
context-menu entry: As an user with associateitemmode-rights to the item (e.g. based on some metadatafield), i see some entry in the context-menu entry.
When i click the context-entry i come to some protected page displaying the search of the configured discovery index. Some own list representation of the search results offers me the action buttons_
to connect/associate items
disconnect/disasccociate items if some connection exists.
The user get's some basic notification about the operation success.
As an user i can filter already connected items by calling some query based on the metadatafield..
with some little delay (despite to frontend caching and the solr indexing) the changes are reflected to the item
Is your feature request related to a problem? Please describe. We were struggling with the problem, that our projectinvestigators have the right to edit their projects via the editmodes, but were not allowed to associate related (archived) publications to the project. The relation to the project is hold in the Publications
dc.relation.projectauthority field and the rights to edit the Publication are only given to our controller group / collection administrators.Describe the solution you'd like We would like some additional mode where other entities can be assigned to existing entities. We suggest the terminus associate / associationmode (interlinking/linking and relations are ambiguous in the dspace world). The solution could be some mixture of the edit-itemmode and the edit-relation-mode. Users with the rights to edit the project see some context-menu-button, come to some new page with some related entity search configuration and can select/ or deselect specific entries. When they select/deselect the entries, then the Publications are updated.
Describe alternatives or workarounds you've considered
Additional context The logic is similar to the edit-relationship module; it displays some search configuration with additional action buttons to associate/disassociate items. Some additional endpoint triggers the action. The access to the page/endpoint and the specific context-menu entry is evaluated by some implementation of the AccessItemMode and so configured in some way similar to the edit-item-mode
Components / workflow: