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

Linking exposed dataset to a project does not assign Accession number to project #461

Open
vildead opened this issue Sep 8, 2023 · 0 comments

Comments

@vildead
Copy link
Member

vildead commented Sep 8, 2023

This is rather edge case:

  1. create dataset without specifying owning project
  2. expose dataset - dataset has now accession number
  3. edit dataset -> assign project

Issues:

  • Accessing Django admin page of the project takes quite some time (database issue?)
  • The project does not have ID assigned

Solutions/Suggestions:
a) Assign ID already when creating an object in DAISY (no only on exposure). This puts more load on the id-service.
b) Do not allow exposing dataset which is not linked to a project. With current process, this seems to be meaningful as dataset metadata should be complete (including project metadata)
c) Ensure the ID is assigned upon this action.

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

No branches or pull requests

1 participant