...

When Offer message has been followed by a related Announce incoming message, the box shown is blue! It is blue because receiving an Announce means - then the message is extracted - we produce a new QA Event. As every QA Event it is shown on Item Page and myDSpace page.

Configuring automatic QA evaluation using the Level of Trust

It’s Score is a number 0 < # < 1. Triggers
If the proper configuration is enabled an automatic check for approval of QAEvent QAEvents is run once the LDN message is extracted.
On qaevents.xml spring configuration files   file the bean qaScoreEvaluation describes we can configure three different boundaries defaults to manage to automatically approve/reject/ignore the level of trust:

<property name="scoreToReject" value="0.3" />
<property name="scoreToIgnore" value="0.5" />
<property name="scoreToApprove" value="0.8" />

• if score <= rejection deletes the QAEvent;

...

• if score <= ignore discards the QAEvent;

...

• if score >= approval accepts the QAEvent automatically

...

• if score respects the following:  scoreToIgnore < score < scoreToApprove
  no automatic action is performed and the user must check manually the QA event

This feature must not be confused with the automatic triggering for LDN Inbound pattern

Sending LDN Notifications during the submission of an item

...

In the example below it is shown the submission of an Item with a new section named for COAR-Notify. 
In this section we can manually choose manually specific ldn-services which cover the request on Review (which were not marked as automatic) in order to ask for Review, Endorsement and ReviewIngest to external services.
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. 

...

(non-automatic) pattern has been configured for the LDN Service this service will not be displayed in any of the dropdown. 

Image Added

Automatic Inbound pattern triggering

When adding new LDN Inbound pattern to a LDN Service we can select if a pattern has to be automatic or not.

Flagging a pattern as automatic means that the request described by the current pattern is sent automatically to the external service:

• No action is required during the submission to select the LDN Service for a specific pattern
• The service in not even listed in the COAR notify step of the submission 

Item filters for Inbound pattern

When adding inbound pattern to a service we have the possibility to add an item-filter for each described pattern

An item filter allows to filter items according to specified criteria.

• If the pattern is flagged as automatic the item filter is evaluated automatically
  • if the item filter is respected the LDN Notification is stored and queued for sending
  • if the item filter is not respected the LDN Notification is not even generated an nothing will be sent to the external service
• If the pattern is not flagged as automatic the item filter is evaluated when choosing the service from the dropdown for Notify in the submission
  • if the pattern is not respected an error message will be displayed saying the selected LDN service cannot be used for the current item
  • if the pattern is respected no error message is displayed 

The LDN Consumer

The LDN Consumer is the consume responsible for generating the outgoing LDN Notification.

This consumer is triggered any time an Item is successfully installed and a check against the registerd LDN Services/patterns is done to generate the appropriate LDN Notification

This consumer is responsible for the handling of both automatic a non-automatic patterns

event.consumer.ldnmessage.class = org.dspace.app.ldn.LDNMessageConsumer
event.consumer.ldnmessage.filters = Item+Install

Test calls: Request Endorsement (LDN Message on item submission)

...