Skip to content

Which DOI to accept as context.id #59

@J4bbi

Description

@J4bbi
Image

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):

  1. 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.
  2. The context.id is resovled (changed!) to the most recent, versioned DOI (this feels messy)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions