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

Write SOP for updating a dataset to a new data version #115

Open
Clare72 opened this issue May 1, 2024 · 0 comments
Open

Write SOP for updating a dataset to a new data version #115

Clare72 opened this issue May 1, 2024 · 0 comments
Assignees

Comments

@Clare72
Copy link
Contributor

Clare72 commented May 1, 2024

Some datasets are not 'final', but 'snapshots' that need to be updated every so often. We should have an SOP for this (to add to the curation manual wiki?) to make sure all steps get carried out each time. This might be different depending on whether VFB IDs are generated by us (e.g. hemibrain) or supplied by the source (e.g. FlyWire).

Things to consider:
updating node annotations - label, comment etc. (anat record)
adding new (and removing old?) site/api xrefs
updating typing info (newmeta record? - but may want to remove old info)
deprecation of any nodes not in the new version

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

4 participants