Synchronization should allow valid replicas held by MNs to set obsoletedBy and archive flags
Need to discuss what Matt has to say about client-MN interactions of Morpho. Someone may have update capability on an object but not have permission to modify on the authoritative MN.
#9 Updated by Robert Waltz about 8 years ago
- Product Version changed from 1.4.0 to *
- Parent task deleted (
- Priority changed from High to Normal
- Milestone changed from CCI-1.4 to None
- Assignee changed from Skye Roseboom to Dave Vieglais
Deferred until we can clarify this issue.
Also, we have no way of locking the object on a replicated node. In V2, if MemberNodes control systemMetadata then the authoritative Membernode should be the membernode modifying the systemMetadata and not a archival membernode.
This request hinges on DataONE's distributed architecture, whether DataONE Membernodes form an LOCKS system, a Peer-to-Peer network, or a Computer Cluster. Each architecture has its own set of problems that need to be addressed.