Project

General

Profile

Bug #5622

Modify morpho package id management when we switch to dataone

Added by Jing Tao almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
morpho - general
Target version:
Start date:
06/08/2012
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5622

Description

currently morpho package id consists of three parts:
site code + id+ revision.

To my understanding, dataone doesn't have the revision this concept at all.

If morpho locally has tao.23.1 and tao.23.2, the search result will only shows up tao.23.2 since tao.23.1 is considered as an older version of tao.23.2.

However, if we switch to dataone, the older mechanism for revisioning wouldn't work any more. For example, we create a new package and save it locally. From the dataone service, we get an id tao.25 for this package. Then we modify the document and save locally again. This time we get an id tao.30 for this package. So we need a new mechanism linking tao.25 to be an older version of tao.30.

History

#1 Updated by ben leinfelder almost 8 years ago

This (revision history) is handled in SystemMetadata using the obsoletes and obsoletedBy elements.

#2 Updated by ben leinfelder over 7 years ago

Moving to 2.0.0 milestone -- I believe this feature is addressed in another bug and is well underway.

#3 Updated by ben leinfelder over 7 years ago

Revision handling is finished. We are still discussing an alternative local Id scheme (UUID) and this will be addressed in a different bug.

#4 Updated by Redmine Admin about 7 years ago

Original Bugzilla ID was 5622

Also available in: Atom PDF