Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change hasPid cardinality to 0-1 #40

Closed
zozlak opened this issue Feb 13, 2025 · 2 comments
Closed

Change hasPid cardinality to 0-1 #40

zozlak opened this issue Feb 13, 2025 · 2 comments
Assignees

Comments

@zozlak
Copy link
Member

zozlak commented Feb 13, 2025

Currently the cardinality of acdh:hasPid is 0-n but having multiple would break all the services which depend on the acdh:hasPid being a primary resource identifier (most importantly the OAI-PMH service), therefore the cardinality should be set to 0-1

@zozlak zozlak self-assigned this Feb 13, 2025
@bellerophons-pegasus bellerophons-pegasus changed the title Change hasPid cardibality to 0-1 Change hasPid cardinality to 0-1 Feb 14, 2025
@bellerophons-pegasus
Copy link
Member

The cardinality 0-n has the background that when creating the ontology, we thought that there might be cases where we end up with two identifiers, e.g. a Handle and some DOI, which should both be prominently presented.
But I think now with a few years in use it might be safe to say acdh:hasPid can only have one value and all others go into acdh:hasIdentifier.

Before doing that: please check if there is any entity in ARCHE that would violate the new cardinality constraint

@zozlak
Copy link
Member Author

zozlak commented Feb 14, 2025

I confirm all existing resources have 0-1.

@zozlak zozlak closed this as completed in 904eefe Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants