CDLUC3 / mrt-doc

Documentation and Information regarding the Merritt repository
8 stars 4 forks source link

Missing DataONE content from Individual collection to Dryad migration #637

Open sfisher opened 3 years ago

sfisher commented 3 years ago

Describe the bug Datasets from the "DataONE Dash" merritt collection are not available in the Dryad merritt collection.

We receive 401 response codes when users try to access these old datasets.

To Reproduce

Go to the DataONE Dash Merritt collection and look at these datasets:

Then go to the Dryad collection and attempt to find any of these items by name such as these and they do not seem to have been transferred over into the Dryad collection.

Expected behavior We should probably migrate these over so they are available for access in the Dryad Merritt collection.

Additional context We get nightly error messages about some of these. I think DataONE is also scanning (or some automated process).

sfisher commented 3 years ago

Hi @elopatin-uc3 . Daniella asked me to follow up on this one since it seems to be the cause of https://github.com/CDL-Dryad/dryad-product-roadmap/issues/1209 which a researcher is asking about.

elopatin-uc3 commented 3 years ago

Hi @sfisher we have not started on this ticket because the work David is doing on improving Audit has taken priority. I'll this same note in #1209.

sfisher commented 3 years ago

Hi Eric,

This is the list of the ARKs in Merritt that didn't make the DataONE --> Dryad collection transfer.

mrt_dataone_arks_to_transfer.txt

elopatin-uc3 commented 3 years ago

@dloy Here is a list of DOIs that map to the list of ARKs Scott provided: dataone_dash_dois_min.txt

dloy commented 3 years ago

The dataone_dash content did not get copied to the cdl_dryad collection. I did not copy the content because it already was in the dryad bucket. The problem is that I failed to inform Scott that the collection on the Dryad side needed to remain dataone_dash.

At this point I do not see any cdl_dryad collection objects with the same doi as the dataone_dash. If I'm correct on this, there should not been any updates on the dash_dryad content that incorrectly went to cdl_dryad.

Not sure what the easiest fix is for this. I can copy this content as I have with other content to the cdl_dryad collection. It will then behave as other dryad content and not require any special handling on the dryad side. At this point this requires 537 versions and should complete easily this week.

elopatin-uc3 commented 3 years ago

Deciding to move this back to the Icebox after checking in. Essentially these objects are saved to the Dryad bucket. They would be a significant amount of work to move, and they are showing up in the consistency reports (objects in more than one collection, and objects with only two copies). Dryad has had an update process in place for a while now, so we're choosing to let this be.