-
Notifications
You must be signed in to change notification settings - Fork 5
communities: add "About communities" and "Manage" pages #20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sakshamarora1
merged 1 commit into
CERNDocumentServer:main
from
palkerecsenyi:about-communities
Apr 10, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,56 @@ | ||
| # Communities | ||
|
|
||
| ## New community | ||
| On CDS, communities are spaces in which records are curated by specific groups of people, depending on the community's scope. | ||
| Communities can allow: | ||
|
|
||
| ## Your communities | ||
| - **Curating** records; specific community members can review submitted records before publication. | ||
| - **Managing permissions** by specifying which users or CERN Groups can submit new records. | ||
| - **Creating custom pages** such as an About page or a Curation Policy | ||
|
|
||
| All records on CDS belong to at least one community. | ||
| When a record is created, it must be submitted to a community, but after publication it can also be submitted | ||
| to additional ones. | ||
|
|
||
| ## Create a community | ||
|
|
||
| In order to ensure communities have a coordinated, user-friendly structure, the CDS team creates communities on request, following careful evaluation. | ||
| Please [contact the CDS team via ServiceNow](https://cern.service-now.com/service-portal?id=sc_cat_item&name=request&se=CDS-Service), specifying the following details: | ||
|
|
||
| - The intended name | ||
| - A square logo (maximum 1MB) | ||
| - A short description of what the community will be used for | ||
| - The type of records that will be published in the community (please send links to examples if possible) | ||
| - Whether reviews should be mandatory for newly submitted records (see [Submission policy](./manage.md#submission-policy)) | ||
| - Whether the community's contents should be publicly visible | ||
| - The name of a dedicated [GMS group](https://auth.docs.cern.ch/groups/overview/) to set as the initial member of the community | ||
|
|
||
| ## Members and roles | ||
|
|
||
| Communities have members, each with a role which describes their level of access. | ||
| A member can be a CERN user or a group. | ||
| Community owners can specify the initial members, which can then later be edited. | ||
|
|
||
| Each member can have one of the following roles: | ||
|
|
||
| - **Reader**: Can view all records inside the community, including restricted ones. | ||
| - **Curator**: Can curate/review records submitted to the community and can view all records. | ||
| - **Manager**: Can manage members and roles, can curate records, and can view all records. | ||
| - **Owner**: Full administrative control over all aspects of the community. | ||
|
|
||
| !!! info "Access for non-members of the community" | ||
|
|
||
| CDS users who are not members of a community can still view its public records and its details. | ||
| This can be changed in the community's settings. | ||
|
|
||
| Non-members cannot view the community's restricted records, unless they have been granted [explicit permission](../deposit/access-share.md) on a per-record basis. | ||
|
|
||
| [Find out more](./manage.md#members) about managing community members. | ||
|
|
||
| ## View your communities | ||
|
|
||
| To view the communities you are a member of, or to see a full list of communities on CDS, click on the "Communities" tab at the top of the page. | ||
|
|
||
|  | ||
|
|
||
| The communities you are a member of are listed under "My communities", while the latest communities created on CDS are under "New communities". | ||
| To show more results in either section and to search for communities, click "See all". |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,117 @@ | ||
| # Manage a community | ||
|
|
||
| Communities can be managed by their members. What each member can do depends on their role. | ||
| See [About communities](./communities.md#members-and-roles) for the list of roles and what they mean. | ||
|
|
||
| ## Settings | ||
|
|
||
| Properties of a community can be changed by members who have the **Manager** or **Owner** role. Open the community and use the **Settings** tab. | ||
|
|
||
| ### Profile | ||
|
|
||
| On the "Settings" tab you can change public-facing information about the community. | ||
| We recommend filling in as much of this as possible so visitors understand the purpose and background of the community. | ||
|
|
||
|  | ||
|
|
||
| The profile picture acts as a logo, shown across CDS wherever the community is referenced. | ||
|
palkerecsenyi marked this conversation as resolved.
|
||
|
|
||
| Please ensure the picture meets the following criteria: | ||
|
|
||
| - Stays clear even when very small | ||
| - Square shaped | ||
| - Maximum 1MB | ||
|
|
||
| ### Visibility | ||
|
|
||
|  | ||
|
|
||
| On the "Privileges" section of the "Settings" tab, you can control whether the community itself is public or restricted. | ||
|
|
||
| - **Public** communities are visible to everyone and show up in the list of communities on the CDS website. All parts of the community's profile can be seen by everyone, as well as the public records that belong to it. Restricted records can be seen by the members of the community or users with explicit access. | ||
|
|
||
| - **Restricted** communities are only accessible by members. The community does not show up search results and its profile cannot be viewed by non-members. All records of the community must be restricted too. | ||
|
|
||
| You can also configure whether the list of members is visible to everyone or only to members. | ||
|
|
||
| ### Submission policy | ||
|
|
||
|  | ||
|
|
||
| The submission policy defines who is allowed to submit records to the community and whether they will need to undergo a review before publication. | ||
|
|
||
| The review policy sets which submissions require a review. | ||
| By default, all submissions require a review. | ||
| You can change this so that members with certain roles (as shown) can submit directly without a review. | ||
| When these users submit a record, the record will get associated with the community instantly. | ||
|
|
||
| You can also disable reviews entirely by selecting "Allow all members to publish without review". | ||
| Records submitted by non-members of the community (if allowed) still require a review. | ||
|
|
||
| By default, any CDS user can submit records to a public community. | ||
| You can change the records submission policy to "Closed" so that only members can submit records. | ||
|
|
||
| ### Pages | ||
|
|
||
|  | ||
|
|
||
| On the "Pages" section of the "Settings" tab, you can customise the "Curation policy" and "About" pages, which are shown to all users viewing the community. | ||
|
|
||
| - The **Curation policy** can be used to specify criteria and guidelines for records submitted to the community. Specify as much detail as possible to make reviewing submissions easier. | ||
| - The **About** page can be used to provide more information about the community and its purpose. | ||
|
|
||
| ## Members | ||
|
|
||
| ## Browse & collections | ||
| You can view a list of the community's members and their roles in the "Members" tab. | ||
|
|
||
|  | ||
|
|
||
| Members can be either **people** (referring to CERN users) or **groups** (referring to [GMS groups](https://auth.docs.cern.ch/groups/overview/), formerly known as e-groups). | ||
| If a role is applied to a group, it will be applied to all members of the group. | ||
|
|
||
| !!! info "Permissions for managing members" | ||
|
|
||
| Only members with the **Owner** and **Manager** roles can manage members. See more details about roles in [About communities](./communities.md#members-and-roles). | ||
|
|
||
| To **add a new member**: | ||
|
|
||
| 1. Click on "Invite". | ||
| 2. Select either the "People" or "Groups" tab | ||
| 3. Search for the user or group you want to add. | ||
| 4. Select the role to assign to the member | ||
| 5. Click on "Invite". | ||
|
|
||
| Users will receive an email invitation to join the community; their membership will only be confirmed once they have accepted the invitation. | ||
| Groups will be added immediately. | ||
|
|
||
| You can view pending invitations in the "Invitations" tab. | ||
| Invitations that have not yet been accepted or rejected will be shown in the "Open" tab. | ||
| You can change the member's role before they accept the invitation. | ||
|
|
||
|  | ||
|
|
||
| - To **cancel an invitation**, click on the invited member's name, and click on the "Cancel" button. | ||
|
|
||
| - To **remove a member**, click the "Remove" button next to their name. | ||
|
|
||
| - To **change a member's role**, select a new role from the dropdown menu. | ||
|
|
||
|  | ||
|
|
||
| !!! info "Membership visibility" | ||
|
|
||
| You can change whether others can see your membership by selecting an option from the dropdown menu next to your name. | ||
|
|
||
| ## Managing submission requests | ||
|
|
||
| When someone submits a new record to your community, it may appear as a **submission request** for your community to review, depending on the community's [review policy](#submission-policy). | ||
| These requests are shown in the community's "Requests" tab. | ||
|
|
||
| Curators review submitted records and suggest changes to ensure their content and metadata meet the community's requirements. | ||
|
|
||
|  | ||
|
|
||
| ## Submissions: requests & reviews | ||
| Community members with a role of **Curator** or above (see [more details about member roles](./communities.md#members-and-roles)) can view these requests from the community interface, **review** the submitted record, leave **comments**, and **accept** or **decline** it. Until a request is accepted, the record is in the "In review" stage and is not publicly visible as part of the community. | ||
| The record may still be accessible if it has already been published to another community. | ||
|
|
||
| ## Curation | ||
| See [About reviews](../review/review.md) for more details. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change the title in .yml file