Task #7395
Feature #6498: V2 Metacat MN and CN Support
Task #7380: Check the v1/v2 api methods, which alter the system metadata, how to handle the set of the modification date and the serial version
Reject those methods on v2 API when clients apply them on an object whose authoritative node is a v2 mn
Start date:
2015-09-29
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
V2 API
Allow a v2 client to call an object whose authoritative node is v1 or v2 through those methods
CN.setReplicationStatus (CN and MN)
CN.setReplicationMetadata (updateReplicationMetadata?) (CN only)
CN.deleteReplicationMetadata(CN only)
CN.registerSystemMetadata
If the object's authoritative mn is v1 only, it is fine to call the following methods. If the objects's authoriative mn is v2, the request will be throw a NotAuthrozied exception. CN.setReplicationPolicy CN.setAccessPolicy CN.setArchive CN.setRightsHolder CN.setObsoletedBy
History
#1 Updated by Jing Tao about 9 years ago
The NotAuthorized exception looks like:
NotAuthorized ("The Coordinating Node is not authorized to make systemMetadata changes on this object. Please make changes directly on the authoritative Member Node.")
#2 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
