Skip to content

DM-51479: Create a preliminary design document for the bibliographic API #187

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

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

jonathansick
Copy link
Member

This document explores what the database schema and REST API may look like for a bibliographic API in Ook.

With the help of Copilot :)
DataCite uses relationship types to handle citations/relationships in
addition to other types of relationships, so we'll do the same thing.
This means that all resource-to-resource relationships, even versioning,
are now handled the same way.
This includes how resources can be integrated with the existing authors
API.
We can onsider a release and products of the release as citeable
resources as well.
These are better than UUIDs for APIs (see the book *API Design
Patterns*).
This idea comes from the *API Design Patterns* book (ch 6, resource
identification). The idea we can have consistent sort order between the
database and the public IDs is very appealing.
Have the endpoints discussion at the end.
This was changed in the previous PR.
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

Successfully merging this pull request may close these issues.

1 participant