Closed mbjones closed 6 years ago
Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2013-02-12T23:40:06Z
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.
Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-02-19T01:02:52Z
In the local save and delete processes, the obsoletedBy element is handled.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:54Z
Original Bugzilla ID was 5858
Author Name: Jing Tao (Jing Tao) Original Redmine Issue: 5858, https://projects.ecoinformatics.org/ecoinfo/issues/5858 Original Date: 2013-02-11 Original Assignee: Jing Tao
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:
But, the system metadata doesn't have the obsoletedBy element.
And the system metadata of foo.2 it does have the obsoletes element.