...

A QA event is an entity stored on the qaevent solr collection.

A QA Event owns data related to an item archived in the repository: into it's message property it may have values for new metadata to be added to the Item.

...

All the system described here is turned off and on with the configuration property: qaevents.enabled. It is defaulted as false: 

qaevents.enabled = false

Quality Assurance Source

A QA Source is the recognized authority through which the qa event has landed on the repository. Source names are stored into the configuration key:  qaevents.source . It is defaulted as:

qaevents.sources = openaire, DSpaceUsers, coar-notify

Every QA Event must have a recognized source: this means that at time of writing we recognize 3 possible sources.

...

The QA Topic describes the type of event. As the topic is known - it is expected for the message content to have a certain format. All the topic managed by the openaire source are stored into the configuration key: qaevents.openaire.import.topic. it is defaulted as:

qaevents.openaire.import.topic = ENRICH/MISSING/ABSTRACT
# add missing publication id suggestion
qaevents.openaire.import.topic = ENRICH/MISSING/PID
# add more publication id suggestion
qaevents.openaire.import.topic = ENRICH/MORE/PID
# add missing project suggestion
qaevents.openaire.import.topic = ENRICH/MISSING/PROJECT
# add more project suggestion
qaevents.openaire.import.topic = ENRICH/MORE/PROJECT
# add more review
qaevents.openaire.import.topic = ENRICH/MORE/REVIEW
# add more endorsement
qaevents.openaire.import.topic = ENRICH/MORE/ENDORSEMENT
# add more release/relationship
qaevents.openaire.import.topic = ENRICH/MORE/LINK

Quality Assurance Target

the target of a qa event is an item archived into the repository. The qa event solr document owns the item system uuid into the resource_uuid property.

...

QA Events are visible at Menu -< Notifications → Quality Assurance

...

...

This is the main page of the Quality Assurance.

The first column shows the Sources the user can see.
The last

...

column shows the counter of the events the user can see.

...

Image Added

By clicking at the counter the source page is shown.

...

Here there's the list of all the qa events the user can see,

grouped by their topic

Image Removed

Image Added

Every qa event can be accepted, discarded or rejected.

When accepted an action is triggered. There's a configured correspondence between the topic of the event and an action to be performed. 

When discarded or rejected the solr document of the qa event is deleted.

Image Added

Every decision been made from this panel (about qa events) is reported on the outside through an hhtp http post call. It is directed to all the receivers configured at the configuration key: qaevents. + source + .acknowledge-url

it contains a simple json as payload as:

Quality Assurance Security

QA Events are filtered by a security system. The system is defined on the spring context (see qaevents.xml in specific)  on the QAEVentSecurityService bean. The default security system is set as only DSpace administrators can see and manage all sources. A security system can be assigned to none,  one or more qa sources. The default one is used for Openaire source. Two more security system are defined at time of writing: one for each managed source: DSpaceUsers and coar-notify. Security filters help to hide qa events to the logged user. IE coar-notify security filter allow users to see qa events only to administrators and to targeted-item submitters.