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

Re-work CMR Updater to Use Actual Database Objects #524

Open
CarsonDavis opened this issue Jun 14, 2023 · 0 comments · May be fixed by #525
Open

Re-work CMR Updater to Use Actual Database Objects #524

CarsonDavis opened this issue Jun 14, 2023 · 0 comments · May be fixed by #525
Assignees

Comments

@CarsonDavis
Copy link
Collaborator

The current DOI updater uses the most recent update draft to formulate its new action (create, update, published update). However, some historic update drafts do not actually contain all the necessary metadata, such as concept_id.

New System to Identify Existing Drafts

Existing drafts tied to a concept_id were previously identified based on a matching draft.update['concept_id']. However, since not all doi drafts have a concept_id, we need to use a dual pronged approach.

Unpublished Create Drafts - these should have a concept_id
Everything Else - search the actual database for a matching concept_id, then search the updates for the most recent matching model_instance_uuid.

New System to Create Update Draft Contents

Basically, if an unpublished update draft exists which does not have a concept_id

@CarsonDavis CarsonDavis linked a pull request Jun 14, 2023 that will close this issue
@CarsonDavis CarsonDavis self-assigned this Jun 14, 2023
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 a pull request may close this issue.

1 participant