Design website namespace #1

Open
opened 2025-12-18 07:08:59 +00:00 by mih · 0 comments
Owner

This is relevant, because the website will function as a poor-man's PID resolver. IOW PIDs on entities that are reflected on the website will resolve to the respective pages on the website.

Presently, the metadata pool uses a custom namespace with random PIDs

  • persons/ (not calling it contributors to avoid making implications)
  • datasets/
  • instruments/
  • projects/ (problematic insofar as ./ is also a project (psyinf itself)
  • publications/
  • objectives/

The following are likely to be generated, but maybe not promoted as a top-level category

  • topics/ (problematic when we would be aiming for a PID reuse from a proper vocabulary, would point elsewhere)
  • grants/ (same as with topics, if we aim to use "official" PIDs)
This is relevant, because the website will function as a poor-man's PID resolver. IOW PIDs on entities that are reflected on the website will resolve to the respective pages on the website. Presently, the metadata pool uses a custom namespace with random PIDs - `persons/` (not calling it contributors to avoid making implications) - `datasets/` - `instruments/` - `projects/` (problematic insofar as `./` is also a project (psyinf itself) - `publications/` - `objectives/` The following are likely to be generated, but maybe not promoted as a top-level category - `topics/` (problematic when we would be aiming for a PID reuse from a proper vocabulary, would point elsewhere) - `grants/` (same as with topics, if we aim to use "official" PIDs)
Sign in to join this conversation.
No labels
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
www/www-from-model#1
No description provided.