Draft: AssociateItem Backend

[floriangantner]

References

• Fixes Associate some project to some publication #365
• Related to Draft: AssociateItem RestContract Rest7Contract#3
• Counterpart Frontend/Angular: Draft: Associate Item Frontend dspace-angular#50

Description

• see issue . when all issues are created and draft status has ended
• new Feature of associate item

Instructions for Reviewers

• deploy default configuration and check the configured associateitem-service.xml
• the configation is similar to the edititem modes. Additional properties can be defined which are essential for the associateitem actions: discovery, metadatafield, itemSourcetype, itemTypeTarget, disableAuthSource and the optional parameter conditionSource and conditionTarget

  <bean class="org.dspace.content.edit.AssociateItemMode">
      <property name="name" value="PROJECTPUBLICATION" />
      <property name="security">
          <value type="org.dspace.content.security.CrisSecurity">
              CUSTOM
          </value>
      </property>
      <property name="items">
          <list>
              <value>crispj.investigator</value>
          </list>
      </property>
      <!-- discovery index configuration that is shown on the associate-item-page -->
      <property name="discovery" value="researchoutputs" />
      <!-- metadatafield where the metadata is being created . It must be authority controlled -->
      <property name="metadatafield" value="dc.relation.project" />
      <!-- additional check for entity types. discovery indexes might display multiple types and the authority might only support one type -->
      <property name="itemTypeSource" value="Publication" />
      <property name="itemTypeTarget" value="Project" />
      <!-- disable the authorization at the item where the metadata is being created. -->
      <property name="disableAuthSource" value="true" />
      <!-- additional conditions can be specified which must be fulfilled on the source and/or target item, when some associateitem request is made -->
      <!--
      <property name="conditionSource" value-ref="" />
      <property name="conditionTarget" value-ref="" />
      -->
  </bean>

List of changes in this PR:

• AssociateItemMode
  • in adoption to EditItemMode Implementation
• AssociateItem Rest Endpoint and Services
• example configuration provided:
• tbd: Tests will be provided

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
• My PR passes Checkstyle validation based on the Code Style Guide.
• My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
• My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
• If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[github-actions]

This pull request has been automatically marked as stale because it has not had
activity in one year. It will be closed in 14 days if no further activity occurs.

Allowing pull requests to close as stale helps us filter out old work that is no longer
relevant and helps developers focus on reviewing current work.

All pull requests closed by this bot act like normal pull requests;
they can be searched for, commented on or reopened at any point.

If these changes are still relevant then please comment and/or rebase your PR based on the
latest DSpace code. This will remove the stale status and notify us to assign a reviewer
for your PR.

[github-actions]

This pull request has been closed automatically. If these changes are still relevant
then please re-open this pull request with a comment and rebase your PR based on the latest
DSpace code. This will notify us to assign a reviewer to your PR.