Project

General

Profile

Bug #5798

ORE documents generated by Morpho do not include obsolescence chain

Added by ben leinfelder almost 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
morpho - general
Target version:
Start date:
01/22/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5798

Description

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.


Related issues

Related to Morpho - Feature #6083: Morpho should use MN.query() to look for existing resourceMaps (OREs) when saving new versions of packagesClosed

History

#1 Updated by ben leinfelder almost 8 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.

#2 Updated by ben leinfelder almost 8 years ago

now doing this identifier-based ORE revision tracking. It's not really how we want to do it, but it will owrk for the time being as we transition toward a full ORE-based packaging approach.

#3 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 5798

Also available in: Atom PDF