You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: