nva-nvi is designed to manage and process publication data for nvi (Norsk vitenskapsindeks) reporting.
The project enables evaluation, point calculation and curator management of publications that qualify as nvi candidates.
The application template uses AWS Serverless Application Model (AWS SAM) to define application resources. AWS SAM is an extension of AWS CloudFormation with a simpler syntax for configuring common serverless application resources such as functions, triggers, and APIs. For resources not included in the SAM specification, you can use standard AWS CloudFormation resource types.
When building a new environment or the search indexes are deleted and needs to
be rebuilt, make sure to run the InitHandler.
- Trigger
DeleteNviCandidateIndexHandler(skip if mappings unchanged) - Trigger
InitHandler(skip if mappings unchanged) - Run batch job with
REFRESH_CANDIDATES- see batch jobs docs
To start a batch re-evaluation of existing publications for a given year as NVI candidates, trigger BatchReEvaluateNviCandidatesHandler with the following input:
{
"detail": {
"pageSize": 500,
"year": "2024"
}
}The IndexDLQ is a shared DLQ for all handlers related to indexing.
NviRequeueDlqHandler consumes messages from the IndexDLQ, and updates the
candidate in the DB with a new version. This will trigger the indexing flow
for the candidates.
Default count (number of messages consumed from DLQ) is 10. To specify
another count, provide it as input:
{
"count": 100
}See template for which DLQs are available for redrive (configured with
RedrivePolicy). To start a DLQ redrive, locate the DLQ in the AWS console
(SQS) and press Start DLQ Redrive.
