Automatically update resMap to aggregate newest version of data files when editor is opened #2014
Description
Related to #1675
A user on OPC was attempting to update a package and got the "This identifier was already made obsolete by..." message. That error was from the update call to one of the data files. After investigating, I found that every data file in the package was already obsoletedBy a newer version, but the resource map was still aggregating an older version. I'm not sure how this happened - if the data files were updated via R or MetacatUI - but nevertheless, the editor should be able to handle this use case.
Possible editor behavior:
- Automatically update the package to aggregate the newest version of the data file as soon as the editor is opened (only save to Metacat when the Submit button is clicked).
- Ask the user if they want to update the data file to the newest version
I'm leaning towards the automatic behavior since I think it is rare that someone would update a data object but exclude it from the package.