ORE documents generated by Morpho do not include obsolescence chain
Because there is currently no good way for Morpho to know if an ORE package exists for a given set of EML+data, we end up generating a new ORE object every time we save a package even if it is an update to an existing package. This means that we will have many ORE objects that are not marked as obsolete.
Updated by ben leinfelder almost 11 years ago
I think the best we can do right now is to check for an existing ORE object to obsolete by using the standard id pattern that Morpho uses when creating an ORE object: "resourceMap_" + sciMetadataIdentifier. This is better than nothing and will handle Morph-generated content as well as Metacat-generated ORE objects (from upgrade), but not necessarily arbitrarily added ORE packages on other MNs that we haven't been closely administering with that id convention.