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

IMPROVEMENT: missing relation between datlink entries and releases #210

Open
agy-why opened this issue Aug 30, 2023 · 2 comments
Open

IMPROVEMENT: missing relation between datlink entries and releases #210

agy-why opened this issue Aug 30, 2023 · 2 comments

Comments

@agy-why
Copy link
Member

agy-why commented Aug 30, 2023

There is no clear way to relate a datalink entry with a given release.

However this relation does exists. Each datalink table (non-generated ones) leaves in a schema (representing the release).

A solution would be to propagate the schema information down to OAI via the oai datalink adapter:
https://github.com/django-daiquiri/daiquiri/blob/master/daiquiri/oai/adapter.py#L206

The schema information is stored in the table name. From this one could extract the published and updated dates but also the IsPartOf entry without the necessity of a specific semantic from datalink.

This would only require to put the datalink table in the proper schema (representing the release).

@agy-why
Copy link
Member Author

agy-why commented Aug 30, 2023

related to #209

@agy-why
Copy link
Member Author

agy-why commented Sep 13, 2023

To get updated and published date for an object with DOI, read published and updated date from metadata of the corresponding datalink table (the one holding the doi).

@agy-why agy-why modified the milestones: Next version, MiniRelease Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant