-
Notifications
You must be signed in to change notification settings - Fork 15
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
Index Herbariorum sync is creating institutions and collections in GRSciColl of already existing institutions #579
Comments
Thanks @EstebanMH-SiB, so your suggestion would be to create new entries as suggestions to review? That way a reviewer would be able to spot when there is a duplicate created and link the existing entries to IH instead. @marcos-lg what do you think? Would that be possible? |
That would be possible yeah. Would it be for all the new entries or just the ones whose name matches with an existing one? |
Yes, create the entries as suggestions and I think this should be done only to the ones whose name matches an already existing one, that way we avoid duplicates. With the new ones, they can proceed directly |
@marcos-lg I think what Esteban writes makes a lot of sense. We should make the make the addition of new entries via the IH synch as suggestion. That way, we could avoid duplicate entries. At least one other GRSciColl mediator told me that they would like that as well. |
If there is an existing name it will create a suggestion of collection. |
We are doing a review of our institutions and collections in GRSciColl and discovered that ih-sync is creating entries for already visible institutions.
For example this institution Universidad Católica de Oriente was created by us 2 years ago, and ih-sync created the same institution and herbarium 11 months ago Universidad Católica de Oriente.
Perhaps a validation can be put in place so new entries from ih-sync that have the same name of an institution or collection, will be put on hold until a manual review, that way we can avoid duplicates.
Thanks in advance,
The text was updated successfully, but these errors were encountered: