Bug #7584
MNStorage.create() doesn't set sysmeta "authoritativeMemberNode" field if not already set by client
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-01-12
Due date:
% Done:
0%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
If authoritativeMemberNode element is not set in the sysmeta submitted with an object during create() the MN doesn't set it, leading to the object or metadata not being able to be updated.
This is the case with https://mn-stage-ucsb-2.test.dataone.org/knb/d1/mn/v2/meta/urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c , which can't be updated or have it's sysmeta
updated. When this is attempted, the error is printed:
Error updating urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c: Coudn't find the authoritative member node in the system metadata associated with the pid urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c
History
#1 Updated by Peter Slaughter over 8 years ago
- Status changed from New to Rejected
Moved to https://projects.ecoinformatics.org/ecoinfo/issues/6938 as this is a metacat issue.
