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

Ensure we have a working API #121

Open
richard-jones opened this issue Jan 28, 2025 · 3 comments
Open

Ensure we have a working API #121

richard-jones opened this issue Jan 28, 2025 · 3 comments
Assignees

Comments

@richard-jones
Copy link
Collaborator

richard-jones commented Jan 28, 2025

Ensure the API is in sync with the user interface and deposit requirements

@richard-jones richard-jones converted this from a draft issue Jan 28, 2025
@richard-jones richard-jones moved this from Ready to In progress in Fair Data Repository Jan 28, 2025
@J4bbi
Copy link
Collaborator

J4bbi commented Feb 11, 2025

@cc-a I am unclear on what needs to be done.

Is it to bring the REST API in sync with the customizations done on submission form?

That is to say:

  • for the REST API not to recognise a creator having a role?
  • for the default values of publisher and resource type to be the only acceptable ones (this could be achieved by making resource type a vocabulary of one item)?
  • for the acceptable values for rights just to from the fixed list?

@cc-a
Copy link
Collaborator

cc-a commented Feb 12, 2025

Hey @J4bbi, yep. In addition to the items you list above we should also prevent setting references or publication_date metadata via API.

@richard-jones
Copy link
Collaborator Author

PR can be merged and testing added

@richard-jones richard-jones moved this from In progress to In review in Fair Data Repository Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

No branches or pull requests

4 participants