Page History
Quality Assurance Event
A QA event is an entity stored on the qaevent solr collection.
...
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:
...
Every QA Event must have a recognized source: this means that at time of writing we recognize 3 possible sources.
Quality Assurance Topic
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 |
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.
Quality Assurance Message
the message of a qa event is a json-formatted string that contains all the new values related to the item.
Quality Assurance Management
A qa events lands on the repository according to its source. for example: Openaire has an import batch for qaevents in json format to be loaded, Coar-Notify creates new qa event solr document when certain ldn messages are received.
...
When discarded or rejected the solr document of the qa event is deleted.
Processing the decision
Every decision been made from this panel (about qa events) is reported on the outside through an http post call. It is directed to all the receivers configured at the configuration key: qaevents. + source + .acknowledge-url
...
<!-- This action bind the publication to the project, otherwise if the project has not been specified,
create a new project with the available data and then bind it to the publication -->
<bean id="ProjectLinkedEntityAction" class="org.dspace.qaevent.action.QAEntityOpenaireMetadataAction">
<!-- which metadata will hold the relation between the publication and the project -->
<property name="relation" value="isPublicationOfProject" />
<!-- the type of local entity used to store the project details -->
<property name="entityType" value="Project" />
<property name="entityMetadata">
<map>
<!--The key are the json path of qa message, the value is the metadata in
the linked entity where the information should be stored -->
<!-- <entry key="acronym" value="" /> -->
<entry key="code" value="dc.identifier" />
<!-- <entry key="funder" value="oairecerif.funder" /> -->
<entry key="title" value="dc.title" />
<!-- <entry key="fundingProgram" value="oairecerif.fundingProgram" /> -->
<!-- <entry key="openaireId" value="oairecerif.funding.identifier" /> -->
</map>
</property>
</bean>
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.
...
Overview
Content Tools