Project

General

Profile

Task #6832

Feature #6498: V2 Metacat MN and CN Support

Task #6734: Implement the feature to support SID in MN and CN apis

How do we check the SID validation in the CN.create method

Added by Jing Tao about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2015-02-03
Due date:
% Done:

100%

Milestone:
CCI-2.0
Product Version:
*
Story Points:
Sprint:

Description

In the CN.create method we will apply those rules for checking SIDs (comply one of them will be fine):

The SID is a unique identifier which doesn’t exist in the system.
The SID matches the SID in the system metadata of the object in the “obsoletes” value.
The SID matches the SID in the system metadata of the object in the “obsoletedBy” value.

It is possible that we need information from the previous or next version object to decide if the SID is valid.

However, the synchronization probably doesn't follow the order of the chain itself. It may cause an issue.
Here is an example of chain:
P1(S1) <-> P2(S1) <-> P3(S1) <-> P4(S1)

The order of synchronization can be P1, P4, P3 and P2.
For cn.create(P1), it is fine since the S1 doesn't exist in the system.
For cn.create(P4), we can't decide if the S1 is valid since we don't have the information about the object P3 (it hasn't been synchronized yet).

So we should have some mechanism to fix the issue.

History

#1 Updated by Jing Tao about 9 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • translation missing: en.field_remaining_hours set to 0.0

In April 14's meeting, we decided not to check the validation of the sid in CN.create and CN.registerSystemMetadata.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)