During Registry Synchronization, investigate how feasible it is to spot cases where in the protocol response, the provider (or organization) matches with a pre-existing Organization in the Registry.
Summary: During Registry Synchronization, investigate how feasible it is to spot cases where in the protocol response, the provider (or organization) matches with a pre-existing Organization in the Registry.
Description: How far could the synchroniser be used to point at cases where hosting and owning organisation are not identical? In many protocol responses, this could be deduced from the metadata.
Created: 2012-06-08 16:11:21.242
Updated: 2013-12-16 17:50:31.844
Resolved: 2013-12-10 17:10:52.251
Created: 2012-06-08 16:20:28.604
Updated: 2012-06-08 16:20:28.604
scenario 1: new dataset - can we flag if it appears to be owned by a different oraganisation than the one serving it? If so, a) can the organisation be identified as existing in the registry, or if this is not unambiguously possible (most likely), b) could just the fact that a different owning institution seems to be involved be pushed into some messaging cue, so that a human editor can pick it up and follow up?
scenario 2: existing datasets - at some point this will require a one-time rewiring session to reconnect datasets to the correct owning institutions where the technical installation acts as a host only. What options could there be to support spotting the relevant cases (from metadata)?