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
For data.json type of harvest source, the harvester should be able to uniquely identifier a dataset, regardless the dataset state is deleted or not. However, the dedupe process simply mark one dataset deleted, therefore we still have two datasets sharing the same identifier. If we can not purge the duplicated from the system, the next best thing is removing the identifier from the package.
For data.json type of harvest source, the harvester should be able to uniquely identifier a dataset, regardless the dataset state is deleted or not. However, the dedupe process simply mark one dataset deleted, therefore we still have two datasets sharing the same identifier. If we can not purge the duplicated from the system, the next best thing is removing the identifier from the package.
Same thing applies to non-datajson harvest types.
Related to #2989.
The text was updated successfully, but these errors were encountered: