feat(db): add persistent identifier (pids) table #65

Open
opened 2025-08-14 08:48:42 +00:00 by chartgerink · 0 comments
Owner

In v1, the Digital Object Identifiers (DOIs) were embedded in a lot of tables directly. However, in v2 it looks like there will be ongoing Persistent Identifier (PID) support that goes beyond any single one.

A table that links any output to many PIDs will be more scalable. It will allow a DOI to be linked and an ARK, without needing to adjust the outputs/versions table. If we add support for other PIDs in the future, that would then also be more scalable.

In v1, the Digital Object Identifiers (DOIs) were embedded in a lot of tables directly. However, in v2 it looks like there will be ongoing Persistent Identifier (PID) support that goes beyond any single one. A table that links any output to many PIDs will be more scalable. It will allow a DOI to be linked and an ARK, without needing to adjust the outputs/versions table. If we add support for other PIDs in the future, that would then also be more scalable.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: libscie/researchequals-api#65
No description provided.