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

merge duplicate records in Airtable #1515

Open
Smullz622 opened this issue Mar 19, 2024 · 0 comments
Open

merge duplicate records in Airtable #1515

Smullz622 opened this issue Mar 19, 2024 · 0 comments

Comments

@Smullz622
Copy link
Contributor

Smullz622 commented Mar 19, 2024

As of now, if an older work version is in Airtable and we have an updated version ready for curation, we leave the old version and add the new version with an 'Updated Version' label. Admins transfer the notes from the old version to the new one and remove the old one once they're finished.

One possibility to reduce manual work for the admins is to merge the old version with the new addition. Airrecord does have a built in update method. This needs more investigation to see if it is a viable option. If it's not viable, CurationTaskClient.find_all returns all of the data on an existing task, so we can get all additional information from that, add it to the new task, and remove the outdated task.

Curation analytics consideration: Right now if records get merged we would need to think of a way to document the work from the first version. Sometimes folks will make new versions to add additional datasets or files. In these cases, this would constitute another round of curation and we would want to be able to count both. One possibility is to keep the label indicating it's an updated 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

1 participant