This is a complement of information to one of the items listed in ticket #431
In order for some organizations to feel comfortable to start sharing the content of their master list(s) we need to give them the possibility to decide if all of the data elements (attributes) should be accessible or not when making the set public, restricted (not yet implemented) or private
Problems this relates to
GPR content accessibility
Proposed solution
Give the RA the possibility to decide the accessibility level for each data element
The following option would be given at the data element in the geo-object type and hierachies module:
public: data element that will appear in public, restricted and private sets
restricted: data element that will appear in restricted and private sets but not in public ones
private: data element that will only appear in private sets, not in public or restricted ones
User stories
This is a complement of information to one of the items listed in ticket #431
In order for some organizations to feel comfortable to start sharing the content of their master list(s) we need to give them the possibility to decide if all of the data elements (attributes) should be accessible or not when making the set public, restricted (not yet implemented) or private
Problems this relates to
GPR content accessibility
Proposed solution
Give the RA the possibility to decide the accessibility level for each data element
The following option would be given at the data element in the geo-object type and hierachies module:
Considered alternatives
Additional context
accessibility rights propagation schema: https://bit.ly/3WfxRH2