Guide for Communities

Communities in the Catch-all Repository

By obtaining deposition permissons to the repository, the user becomes a member of the “General community.”

In special cases, it may make sense for a group of users to establish a dedicated community in the repository, e.g. when their own repository is under construction and they need to use a repository service in the meantime, or if they form a small and very lightly organised group for which setting up a full repository would be an overkill.

Properties of the Community

In general, the community in the Catch-all data repository will have the same metadata models and deposition workflows available as the rest of the repository.

The community can support following specific functions:

• if desired, all community members can have access to unpublished records of all other community members (note that in General community, unpublished records are not visible to any other General community member),
• a dedicated DOI prefix can be used for records created under the community; this makes it possible to transfer the records to another repository later.

The community may be discarded if not needed any more, in that case, the records will most likely be transferred to the General community.

Note that dedicated metadata models, curation workflows or similar deviations from standard catch-all repository behaviour will not be supported here. For those, you’ll need a full dedicated repository.

How to Establish a Community

Contact user support (nrp-repo_datarepo@eosc.cz).

Membership in the community will be controlled by a dedicated group in the AAI. Community administrator (typically the representative of the user group who requested establishing the community) will be responsible for managing members of the group.

FIXME:

• do we have restricted records here? Who can see embargoed records?
• did I describe the community correctly?