Modify the obsolescence chain process to accommodate the use case where both old and new PIDs are present on the CN for v1 MNs
See SEAD as an example. SEAD is a v1 MN and has had the case where both old and new PIDs were on the CN and they wished to establish an obsolescence chain "after the fact". See the attached diagram.
Discussion at the 6/20/16 MNW was:
Investigation determined that the setObsoletedBy process works as designed; result is that for V1 MNs, one can't set obsolescence chain after the fact using this method. For V2 MNs who "own" their system metadata, this is not a problem. To be continued: it is desirable that a method (maybe setObsolescence) be developed that incorporates the existing setObsoletedBy, a new setObsoletes, and an updateMetadata [systemMetadataChanged(PID) AND systemMetadataChanged(newPID)] call from CN to the MN - probably low priority in the grand scheme of things. Ticket?? yes, assign to Dave