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

Add to database the new relations from Datacite 4.5 #2032

Open
14 tasks
rija opened this issue Sep 17, 2024 · 2 comments
Open
14 tasks

Add to database the new relations from Datacite 4.5 #2032

rija opened this issue Sep 17, 2024 · 2 comments

Comments

@rija
Copy link
Contributor

rija commented Sep 17, 2024

User story

As a curator
I want to make use of the new types of relations between dataset introduced in the newer version of Datacite schema
So that I can create semantically richer relationships between datasets

Acceptance criteria

Given I have two datasets that I want to relate
When I go the admin page for dataset relations
Then I can choose a relation to connect to the dataset
And the list of relations includes those from the DataCite schema version 4.5

Additional Info

this is a followup to #1959
because the main codebase is still using an old version of Datacite schema,
we cannot yet add vocabulary from a newer version, otherwise the process triggered by Mint DOI
will throw a validation error

list of relationships:
https://datacite-metadata-schema.readthedocs.io/en/4.5/appendices/appendix-1/relationType/

This is dependent on the following tasks to be done:

Product Backlog Item Ready Checklist

  • Business value is clearly articulated
  • Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
  • Dependencies are identified and no external dependencies would block this item from being completed
  • At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
  • This item is estimated and small enough to comfortably be completed in one sprint
  • Acceptance criteria are clear and testable
  • Performance criteria, if any, are defined and testable
  • The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

  • Item(s) in increment pass all Acceptance Criteria
  • Code is refactored to best practices and coding standards
  • Documentation is updated as needed
  • Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
  • No deviation from the team technology stack and software architecture has been introduced
  • The product is in a releasable state (i.e. the increment has not broken anything)
@alli83
Copy link
Collaborator

alli83 commented Oct 18, 2024

Is this ticket regarding the creation of a distinct form to be able to create, modify, delete relationships in database?

@only1chunts
Copy link
Member

@alli83 the intension of this ticket is to get the terms in the database to be able to be used in the Dataset:Relationship form. I dont know how much extra work it is to create a form to administer the relationship terms, if its simple & quick, then yes why not, but I suspect thats fair amount of additional work and its not a priority right now (the list of relationship terms will not change very often so the need for a curator to be able to change them is very low)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To Estimate
Development

No branches or pull requests

3 participants