Page History
...
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: floating 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: two IP numbers expected as minimum and maximum. This range can be used to add a filter to entrust the identified Notify Service of every incoming LDN Messages. If IP Range is enabled, the sender Notify Service is identified but the current LDN Message is coming from an IP out of this range - the LDN Message is set as untrusted. |
LDN Inbox URL: every incoming LDN Message must have an identifiable Notify Service. This is the URL of that external system's LDN Inbox. We match this field to the "origin.inbox" attribute of the incoming LDN Message. Despite the ip range - this This field is mandatory. Every incoming LDN Message with a non-identifiable Notify Service associated is setas set as untrusted and won't be enrouted to the Ldn Router. |
Inbound Pattern: stored into the database table notifyservice_inbound_pattern - we can add at least 1 of them for each Notify Service. Every inbound pattern is the triple of [ pattern, item filter, automatic flag ] :
|
...
In the example below it is shown the submission of an Item with a new section named COAR-Notify. In this section we can choose manually specific ldn-services which cover the request on Review, Endorsement and Review. If No LDN-Services have been configured with these Inbound Patterns, combos on the COAR-Notify section are going to be empty! Example: by flagging automatic to the Inbound Pattern Request Review of LDN Service named "X" , it means that the LDN Service X will not be visible on the Request Review combo of the COAR-Notify submission section. This is the meaning of automatic: a Request Review is going to be sent out to X every time an Item is submitted. All items? No, the items filtered by the Item Filter configured on that Inbound Pattern.
Test calls: Request Endorsement (LDN Message on item submission)
...