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

Ensure we can identify and merge duplicate objects #47

Closed
2 tasks done
u8sand opened this issue Aug 22, 2018 · 4 comments
Closed
2 tasks done

Ensure we can identify and merge duplicate objects #47

u8sand opened this issue Aug 22, 2018 · 4 comments

Comments

@u8sand
Copy link
Contributor

u8sand commented Aug 22, 2018

  • Potentially add a way for users to communicate with the authors of the duplicates to agree to resolve them and in what way. -> Moved to Enable users to request modifications #60
  • At least ensure we can do it administratively and allow users to report duplication
@u8sand
Copy link
Contributor Author

u8sand commented Sep 4, 2018

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 guid may assist us in determining previous versions of a resource, if we want to keep assessments with another version of a resource we need to save that version information.

@u8sand u8sand added the question label Sep 4, 2018
@AviMaayan
Copy link
Contributor

I suggest assigning GUIDs to assessments and digital objects the moment an assessment was submitted... and somehow link these two and date stamp them...

@u8sand
Copy link
Contributor Author

u8sand commented Sep 4, 2018

@AviMaayan I'm having a hard time finding resources for how I am supposed to be creating GUIDs.

I ultimately found these:

Both have doi and ark but judging by the metadata requested, I'm unsure assessments or digital objects fit.

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.

@AviMaayan
Copy link
Contributor

AviMaayan commented Sep 4, 2018 via email

@u8sand u8sand closed this as completed in 21b5bc9 Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants