Open
Description
Right now, a source or collection is either public or private, and this access control applies to all aspects of that repository. From the perspective of a standards development organization, reference access (searching/browsing) is treated separately from distribution.
How could we allow admins to control reference access to a source/collection separately from distribution access?
For now, we can keep these definitions simple:
- Reference - search, browse, viewing details of resources, basic API access (though we should probably put a ceiling to the
limit
parameter) - Distribution - users may download full exports
Open questions:
- How do we (and should we) limit mappings and references
@bmamlin FYI