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.

Sign up for GitHub

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

Jump to bottom

Allow for dataset status changes #69

Open

JoanneBogart opened this issue Sep 21, 2023 · 1 comment

Labels

medium_priority

Collaborator

JoanneBogart commented Sep 21, 2023

We should ultimately support the following:

archive a dataset (with or without deleting the copy on disk)
retrieve archived dataset not currently on disk
delete a dataset (non-production only)
move a dataset from one owner-type to another

This entails changes - mostly additions - to the dataset table and several new methods, probably in Registrar

JoanneBogart added the medium_priority label

Collaborator Author

JoanneBogart commented Sep 21, 2023

Proposed changes to dataset table:

remove is_archived flag. Add archive_date and archive_path
add delete_date
add moved_date, moved_id (if destination is in current schema), moved_production_id (if moved to production)
add on_disk flag

Proposed new methods:

archive(dataset_id, migrate=False)
retrieve(dataset_id) # for archived datasets not currently on disk
delete(dataset_id)
move(dataset_id, new_owner_type, new_owner, new_relative_path, old_schema=None)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment