-
Notifications
You must be signed in to change notification settings - Fork 6
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
Ensure we can identify and merge duplicate objects #47
Comments
I've developed some scripts for doing this both automatically and with minor manual intervention. In general there seem to be a lot of discrepancies between even the old db and fairshakejam. A thing that often seems to occur is different versions of the same tool existing at the same url--we need to think about how we want to manage this within FAIRshake. While tools like a |
I suggest assigning GUIDs to assessments and digital objects the moment an assessment was submitted... and somehow link these two and date stamp them... |
@AviMaayan I'm having a hard time finding resources for how I am supposed to be creating GUIDs. I ultimately found these: Both have Assessments are already timestamped, and I can add version control throughout the entire database (for tracking all modifications), perhaps this is enough--I don't think we need attempt to assess older-than-today versions of a given digital object. Finally, we should be resolving existing GUIDs, if we just create new ones we'll just be creating more duplicates. |
The text was updated successfully, but these errors were encountered: