Page History
...
Configuration properties involved:
coar-notify.enabled = true|false | show/hide the COAR Notify logo in the footer linked to the informative page; used also in the authorization feature at java class org.dspace.app.rest.authorization.impl.CoarNotifyEnabled |
ldn.enabled = true|false | true => message is received and managed false => message is refuced and the server respond with an HTTP 404 |
ldn.notify.inbox = DSpace\url\address\ | where the ldn inbox rest service is mapped. IE: ${dspace.server.url}/ldn/inbox |
coar-notify.ip-range.enabled = true|false | enables the filter on the IP of the sender (external) for received ldn message (into the DSpace ldn inbox) |
Relation with the Quality Assurance Correction Service
The LDN system, as a message exchanging i/o system, has an inbox and an outbox. Every LDN message refers to a Notify Service: all the Notify Services are configured manually from the admin application form. A Notify Service is just like an authority labelled on LDN messages.
The Quality Assurance system is the implementation of item metadata updates operations. A Quality Assurance Event contains informations for item metadata updates: QAEvent are stored into QAEvent solr collection. All of the QAEvent are shown on an administration form. Every QAEvent can be accepted, ignored or removed: if accepted some metadata of the referred item are modified, if ignored or removed nothing about the item is modified. Every QAEvent has a property named source : qaevents qa events created by processing an LDNMessage has source="coar-notify".
To process an LDN message means to create a QAEvents; as soon as the QAEvent is accepted the referred item is updated. We do it by routing LDN Messages from the queue to the LDN Router. The LDN Router is designed into the spring file /dspace/config/spring/api/ldn-coar-notify.xml on the bean ldnRouter.
The match between LDN message type and the QAEvent topic is configured onto ldn-coar-notify.xml spring file. Every LDN message type has an action related, which owns a list of actions. An action is often an email to be sent and an LDNProcessor to call. The LDN processor receives the QAEvent topic as a parameter and creates the relative QAEvent.
...
Third party system can retrieve the location of the repository LDN InBox via the LDN autodiscovery mechanism, nevertheless to be able to interact with DSpace they need to be approved by a Repository Administrators and listed in the LDN Services Directory (see next paragraph); otherwise their messages will be flagged as untrusted and not processed at all.
LDN Services Directory
| Anchor | ||||
|---|---|---|---|---|
|
You need to register the external services to trust incoming LDN messages / send LDN messages to:
...
Administrators can do that using the menu LDN Services. New/Edit Notify Service with this form:
|
| Name: a label for the Notify Service used on the UI |
| Description: the description of the Notify Service - add details here |
| Service URL: the url of the remote Notify Service used when DSpace sends out LDN Messages |
Level of Trust: floaing point number value accepted between 0 and 1. This value is passed into every QA Event created by every LDN Message associated with this Notify Service: it goes to evaluate the "score" attribute of the QA Event. Score attribute is used for rejection/acceptance qa event automation. See the project file dspace/config/spring/api/qaevents.xml on the bean qaAutomaticProcessingMap/qaScoreEvaluation |
| Service IP Range |
Name: a label for the Notify Service ; Description: the description of the Notify Service ; Service URL: the url of the remote Notify Service used when DSpace sends out LDN messages ; Level of Trust: 0 < possible values <=1 : passed into every QAEvent created by every ldnmessage having this Notify Service. this |
|---|
All fields, except 'Description', are required, and at least one Inbound pattern must be defined.
...
When Offer message has been followed by a related Announce incoming message, there are no boxes of this kind shown, because it’s expected for the boxes about suggestions qa to be shown!
Automatic meaning
...
Overview
Content Tools