Change the behavior to archive the older version of the resource map object when a new package is pushed to Metacat
Do you know if Morpho is by default archiving the resource map when a new version of a data package is pushed to KNB?
I am asking because I realized that when I try to go back to previous versions of our SNAPP packages, it seems that all the previous resourceMaps were archived (thanks for @peter for helping me to understand that) restricting the access to previous versions to the EML only. Here as example: https://knb.ecoinformatics.org/#view/karakoenig.46.14 as the lateset and https://knb.ecoinformatics.org/#view/karakoenig.46.12 as a previously shared version with the PIs.
#1 Updated by Jing Tao over 2 years ago
I’m pretty sure the behavior described here: (https://nceas.slack.com/archives/C0N49FM9V/p1502908030000459) isn’t what is intended. We’ve struggled with setting objects to be archived because the definition of what it means to be `archived` has changed slightly from pre-DataONE to post-DataONE. I think it would be worthwhile to review the code, and if appropriate, not calle `archive()` on content that truly isn’t being archived, but rather just set the `obsoletes` and `obsoletedBy` fields to maintain the version chain, which it should already do.