-
Notifications
You must be signed in to change notification settings - Fork 1
Which DOI to accept as context.id #59
Copy link
Copy link
Open
Description
Invenio has the concept of a parent record that always resolves to the most recent record.
This makes it ambiguous, or at best time context specific, which version of a record an incoming endorsement or review refers to.
There is a possibility for instance, that a notification is created in an external system but only delivered after a time lag and that during this time, an updated version of a record is published.
There are two possible solutions for when receiving a notification with a parent record as it's context id (this is obviously not a problem if it's a version specific DOI):
- It is rejected as an ambiguous request, given a 422 response. The reasoning being that the server needs to make inferences that might be incorrect in order to process the notification.
- The context.id is resovled (changed!) to the most recent, versioned DOI (this feels messy)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels