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

parent-doi: add configuration #1740

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

utnapischtim
Copy link
Contributor

@utnapischtim utnapischtim commented May 2, 2024

should fix #1652

QUESTIONS:

  • is this a valid approach?
  • should the default be:
    • yes create parent dois
    • no parent doi should be created
  • the PR implements it as DATACITE_ENABLE, where it has to be explicitly turned on
    the problem with that is, that it is not backwards compatible to the actual code, BUT it would be backwards compatible to v11
  • i added a check to the migration script, to only create parent DOI's if datacite is enabled (PR). if the PARENT_DOI_ENABLE config will be merged this should be added to the migration script too

Copy link
Member

@slint slint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the solution, and decoupling DataCite semantic/config from PID configuration :)

I have to admit I'm a bit confused by the "protocol" naming, since it reminds me of HTTP/transfer protocol. Since we've already did the bad thing and hardcoded special rules for the DOI in these classes, maybe it makes sense to just double-down and name the param/field doi_enabled_cfg_key.

I would later on deprecate this class and refactor to fully disassociate DATACITE_ENABLED from it, make the "doi" magic-string configurable, etc. and then either:

  • make a major version bump, and break the API
  • keep the old class for backwards compact and make a new one

* with this it is possible to create doi's for parent and record
  independently.

* this removes the semantically overload of DATACITE_ENABLED

* it adds also the possibility to change from DATACITE to another doi
  provider
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.

Parent PID configuration for non-DataCite setup
2 participants