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.

Sign up for GitHub

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

Jump to bottom

Pass all DOI API data to Backend #138

Open
alexandermichels opened this issue Sep 13, 2024 · 1 comment
Open

Pass all DOI API data to Backend #138

alexandermichels opened this issue Sep 13, 2024 · 1 comment
Labels
frontend-backend Changes that involve both frontend and backend
Milestone
The Empire Strike...

Comments

@alexandermichels
Copy link
Collaborator

Describe the solution you'd like

Currently, we only store a select amount of data from the DOI API when submitting a publication. It would be useful to store that data anyways in case we decide to use it in the future and/or if the API starts charging or limiting.
@erickzli
Copy link
Collaborator

@fbaig For this issue, do you think it would be easier if the backend fetches the information direct from CrossRef, rather than passing information from the frontend?

@erickzli erickzli added the frontend-backend Changes that involve both frontend and backend label Nov 24, 2024
@erickzli erickzli added this to the The Empire Strikes Back milestone Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
frontend-backend Changes that involve both frontend and backend
Projects
None yet
Milestone
The Empire Strikes Back
Development

No branches or pull requests
2 participants
@erickzli @alexandermichels