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

ods:entityRelationshipOrder: question about usecase #165

Open
DavidFichtmueller opened this issue Sep 11, 2024 · 1 comment
Open

ods:entityRelationshipOrder: question about usecase #165

DavidFichtmueller opened this issue Sep 11, 2024 · 1 comment
Assignees
Labels

Comments

@DavidFichtmueller
Copy link
Contributor

Term Name

ods:entityRelationshipOrder

Digital Object Name

DigitalSpecimen: EntityRelationship

Feedback

This is more of a question than a feedback on this term: what is the use case for this term? It seems like there is must be cases, where the order of multiple entityRelationships would be relevant, but we couldn't come up with any that couldn't also be covered with dwc:relationshipEstablishedDate .

@samleeflang
Copy link
Contributor

The idea was that if you have multiple relationships of the same type, you could indicate an order. Haven't seen specific issues with this yet, but you could think of a situation where there are multiple serialisations (as we have in the FDO Handle) and you want to indicate a preference/order. The use case is a bit thin, I have to admit. We could also remove it for now and read it when there is an actual need for this term. Maybe that is better, I will remove this term for now until we have a use case. Adding terms shouldn't be an issue in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants