Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By default the Announce Relationship pattern retrieves the dc.relation metadata, which is currently not configured in any of the standard submissions submission forms and must be added manually.

This metadata can be overridden by setting the java property ldn.notify.relation.metadata so that any custom metadata can could be used.

Real use case

After making sure all the above configurations are properly set proceed with the following:

  1. Start a submission on DSpace 1 for an item and set the dc.relation metadata (or any other metadata, in case it is overridden by the property ldn.notify.relation.metadata)
  2. Once the submission is completed on DSpace 1, wait for the notification to be processed and sent (Check access the LDN Dashboard to know about the notifications statusescheck the notification status)
  3. Once the LDN Message is delivered to DSpace 2, move to the DSpace 2 system and check that the notification is correctly received (and processed)
  4. Check the Quality Assurance page on DSpace 2 for the processed notifications and approve them (Approval is not requested if a configuration for automatic approval has been provided, check the documentation page COAR Notify - LDN Services#ConfiguringautomaticQAevaluationusingtheLevelofTrust)
  5. Once the notification is approved on DSpace 2, a new metadata is added to the item. This metadata is the reference to the DSpace 1 related item (i.e. the item involved in the relationship)

...