search

datadryad / dryad-product-roadmap

Repository of issues for Dryad project boards
https://github.com/orgs/datadryad/projects
8 stars 0 forks source link

System not correctly updating status for some datasets #2768

Closed bryanmgee closed 1 year ago

bryanmgee commented 1 year ago

Curators have identified two datasets where status changes are not being correctly logged by the system:

  1. DOI: 10.5068/D1339F. This dataset was initially curated on 8/23/23 by BG (metadata) and then remained dormant for several days (took a while to download and check 185 GB of files...). The last modified date (Aug 23, 2023, 1:56 PM) records this curation. Since 8/27/23, I have been trying to publish this dataset, but it constantly gets hung up on the pop-up window, even though other datasets can be published without issue in the same interval (i.e. not clearly a DataCite issue). However, it then adds/updates the publication date on the table view of the Admin Site, even though this is not logged in the Activity Log, and the DOI remains inactive.

  2. DOI: 10.5061/dryad.zcrjdfnh5. This dataset was initially curated on 8/23/23 by @lauradryad and returned to the author that day. The last modified date (Aug 23, 2023, 11:26 AM) records this action. In this case, the author actually returned the dataset within 48 hours (Aug 25, 2023, 10:20 AM), which is recorded in the Activity Log but not reflected on the table view, which still displays the status as 'Action Required' (should have been returned to 'Curation' in the old workflow, as indicated by the Activity Log).

It is interesting to note that the last modified timestamps of both are very close together, but a cursory examination of other datasets that have last modified timestamps in the same range and that were curated in some fashion did not identify any additional datasets with these issues.

ahamelers commented 1 year ago

  1. Is showing a network error when trying to update, which says to check the logs, but I can't find the error in the production logs on either server (due to not knowing well enough how the logs work, I'd wager). I think we could force this, but it would be good to know what the cause of the issue is first. Maybe @ryscher could help me look at this one?

  2. For a couple of minutes this one was showing as in "Curation" in the table, but when I looked at the curation activities it was actually "Published". However, I went back and forth a couple of times and the table did eventually also show "Published". Not sure of the source of the delay (some kind of caching, I'm guessing!) but it did eventually catch up.

ryscher commented 1 year ago

10.5068/D1339F. DataCite was giving us a 403 Forbidden when trying to register the metadata. The root cause was an incorrect tenant setting. In ticket #2727, the tenant was changed from a UC tenant to a non-UC tenant, which does not work because of the legacy special handling for UC DOIs.

I returned the tenant to its original ucla setting and published the dataset.