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
I've been working on a data package that has run into many errors from the PI and from the datateam when making updates to it (ticket, dataset). The PI has run into a missing resource map and missing data files when she tries making updates to files with the web editor. She emailed me 5 CSV files and asked me if I could try replacing them for her since she's run into errors when she's tried. I downloaded her 5 CSV files and replaced them in the web editor. When I tried to save the changes, I got this series of errors. And when I went back to the data package, it was updated, but now a lot of the data files are missing and some only have their PID listed instead of their file name (here's the current dataset). Here's a progression of screenshots of what I saw when I clicked submit after replacing the files.
This had happened to me once already this morning, and I ended up with a data package with no resource map. I added the files back with update_resource_map() and tried it one more time to see if I could recreate the error. The same errors occurred, but instead of ending up with a data package with no resource map, I ended up with this data package that had only a couple files missing.
This seems to be an issue with MetacatUI. It looks like, the csv files that Justin posted above were all updated and replaced by MetacatUI, but the changes were not propagated to either EML or ResMaps.
So, on re-try to update the resourceMap with replacing the files - where the resourceMap is still pointing at obsoleted files, MetacatUI gave the error Justin posted in the second screenshot.
The text was updated successfully, but these errors were encountered:
Describe the bug
Report from @justinkadi:
Screenshots
Additional context
From initial investigation:
debugging_log
The text was updated successfully, but these errors were encountered: