Project

General

Profile

Bug #5858

Does the system metadata need the obsoletedBy element?

Added by Jing Tao over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
morpho - dsp
Target version:
Start date:
02/11/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5858

Description

I created data package foo.1 and saved it locally. Then I modified the data package and saved it foo.2. The system metadata of foo.1 should have something like:
<obsoletedBy>foo.2</obsoletedBy>
But, the system metadata doesn't have the obsoletedBy element.

And the system metadata of foo.2 it does have the obsoletes element.

History

#1 Updated by ben leinfelder over 6 years ago

It is probably a good idea to set them both, but I am not sure it is required locally. On the MN we do set the obsoletedBy value on the old object's SystemMetadata since you can only obsolete (update) an object that already exists.

The old object - whether local or on network - should know that it is not the most current version and this would be determined by whether obsoletedBy was null or not.

#2 Updated by Jing Tao over 6 years ago

In the local save and delete processes, the obsoletedBy element is handled.

#3 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5858

Also available in: Atom PDF