organisation - dataset relationship: use HOSTS and OWNS exclusively

10814
Reporter: ahahn
Type: Improvement
Summary: organisation - dataset relationship: use HOSTS and OWNS exclusively
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-13 17:41:06.067
Updated: 2013-12-16 17:50:55.51
Resolved: 2012-02-23 11:31:11.39
        
Description: The data portal will need to allow overviews on Member pages like
Participant Node:
1) Node contributes the following datasets: (...)
2) Node hosts these datasets for others: (...)
- where the Node itself does not have an installation (typically), but the organisations underneath do.
- Also, this would only list those datasets hosted for not-same-node owners, i.e. not if DK institution X hosts for DK institution Z)
3) Node contributes these datasets, hosted by other Nodes: (...)

Currently, datasets can be both owned and hosted by the same organisation. To determine whether the hosting is a service for others, the owning and hosting organisation would need to be determined and checked for being identical or not. This could be simplified if the HOSTS relationship were used only for real hosting scenarios

Proposal:
- for any given organisation-dataset pair, OWNS and HOSTS are exclusive,
where HOSTS is defined narrowly as "hosts a resource _for another institution_": an organisation can either own a dataset, or it can host it for somebody else, but you are not "hosting" your own datasets.

NB:
- the API that the IPT uses does not enforce this. Need to consider when the API is re-written.
- on the registry side, this would need to be rule-enforced, so that a HOSTS relationship cannot be set if an OWNS relationship already exists for the same pair, and vice versa]]>
    

Author: mdoering@gbif.org
Created: 2012-02-23 11:29:01.535
Updated: 2012-02-23 11:29:01.535
        
Decision now is to use explicit relations for OWNS and HOSTS, see http://dev.gbif.org/wiki/display/POR/Agent+types+and+relations
Can we close this issue?