Skip to content

Commit b12526d

Browse files
committed
submit: update remobing from a community section
1 parent 9cdc430 commit b12526d

3 files changed

Lines changed: 32 additions & 45 deletions

File tree

docs/communities/submit.md

Lines changed: 12 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Submit to a community
22

3-
When you are uploading a record, you can submit it for review to a community. Communities may have their own metadata requirements and review workflows. This page explains what happens during submission, how to handle metadata issues, and how to manage community membership for your records.
3+
When you are uploading a record, it needs to be reviewed by a community. Communities may have their own metadata requirements and review workflows. This page explains what happens during submission, how to handle metadata issues, and how to manage community membership for your records.
44

55
## Where should I submit?
66

@@ -12,7 +12,12 @@ If you are unsure which community to submit to, the table below covers the most
1212
| Internal CERN report, note, or technical document | The relevant experiment or department community, if one exists |
1313
| Dataset or software produced as part of a CERN experiment | The relevant experiment community |
1414

15-
You can always submit to more than one community if the record fits multiple scopes. See [Multiple communities](#multiple-communities) below.
15+
!!! note "Can't find your community?"
16+
If your community does not appear in the new CDS or the deposit form, it may still only be present in the legacy CDS. Communities are being migrated progressively to the new CDS.
17+
See the [CDS Migration page](https://new-cds-project.docs.cern.ch/) for updates on the migration status and timeline.
18+
19+
You can submit your record to more than one community only **after** your record has already been published to an initial community.
20+
Only then can you submit it to additional communities if it fits multiple scopes. See [Multiple communities](#multiple-communities) below for details.
1621

1722
!!! tip
1823

@@ -26,26 +31,6 @@ Before a record can be accepted into a community, CDS checks that the record's m
2631

2732
If any required fields are missing or invalid, you will see the list of issues that must be resolved before the submission can proceed as shown.
2833

29-
## Related identifiers
30-
31-
If your record is related to another resource — for example, a preprint that has since been published in a journal, or a dataset associated with a paper — you should link them using **Related identifiers** in the deposit form. This improves discoverability and helps readers find all versions of a work.
32-
33-
Common relationships to declare:
34-
35-
| Situation | Relation type to use |
36-
|---|---|
37-
| This record is a preprint; a published version exists elsewhere | `IsVersionOf` (this record) → journal DOI |
38-
| This record is the published version; a preprint exists | `HasVersion` (this record) → preprint DOI |
39-
| A new version of this record exists | `IsPreviousVersionOf` → new version DOI |
40-
| This record supersedes an older version | `IsNewVersionOf` → old version DOI |
41-
| This record is a dataset used by a paper | `IsSupplementTo` → paper DOI |
42-
43-
To add a related identifier, open the deposit form, scroll to the **Related works** section, and enter the identifier (DOI, arXiv ID, handle, etc.) along with the appropriate relation type.
44-
45-
![Related identifiers](./images/related_identifiers.png)
46-
47-
For a full list of supported relation types and detailed guidance, see the [DataCite documentation on connecting related works](https://support.datacite.org/docs/connecting-to-works).
48-
4934
## Multiple communities
5035

5136
You can submit the same record to more than one community. Each submission is independent: a record can be accepted by one community while still under review in another.
@@ -66,26 +51,10 @@ To submit to an additional community after the record is already published:
6651

6752
Each community has its own review process. Submitting to multiple communities means each community's curators will independently review and decide on your record.
6853

69-
## Removing from community
70-
71-
You can remove a record from a community if you no longer want it listed there, or if the community no longer fits the record's scope.
72-
73-
To remove a record from a community:
74-
75-
1. Open the record's page.
76-
2. Navigate to the Communities Panel (on computers, it's on the right; on phones/tablets, scroll down to the bottom of the page).
77-
3. In the dropdown menu, select **Manage communities**.
78-
4. Click **Remove** and confirm the removal.
79-
80-
Removal is allowed in the following situations:
81-
82-
- The record has been accepted into the community and you are the record owner.
83-
- The community curator removes the record from their community.
84-
- A CDS administrator removes the record.
85-
86-
!!! warning
54+
## Removing from a community
8755

88-
Removing a record from a community does not delete the record itself. The record remains published and accessible via its DOI and direct URL. Only the community association is removed.
56+
!!! note "Removing from a community is not possible"
57+
If you need to change/remove the community associated with your record, please contact the [CDS support team](https://cern.service-now.com/service-portal?id=service_element&name=CDS-Service).
8958

9059
If a submission is still under review (not yet accepted), you can withdraw it instead of removing it:
9160

@@ -101,18 +70,16 @@ If a submission is still under review (not yet accepted), you can withdraw it in
10170

10271
## CERN Research
10372

104-
[**CERN Research**](https://repository.cern/communities/cern-research) is the one of the primary communities for storing scientific output produced at or in collaboration with CERN. It is intended for peer-reviewed publications, preprints, conference papers, theses, and other research outputs directly associated with CERN's scientific programme.
73+
[**CERN Research**](https://repository.cern/communities/cern-research) is the one of the primary communities for storing scientific output produced at or in collaboration with CERN. It is intended for peer-reviewed publications, preprints, conference papers, theses, and other research outputs.
10574

10675
![CERN Research](./images/cern_research.png)
10776

10877
### Who should submit
10978

11079
You should submit to CERN Research if your record is:
11180

112-
- A publication or preprint authored by CERN staff, fellows, or associates.
11381
- A thesis carried out at CERN or under CERN supervision.
114-
- A conference contribution or proceedings paper from a CERN experiment or project.
115-
- Any other research output that acknowledges CERN or is produced within a CERN experiment.
82+
<!-- TODO: Add more when finalized -->
11683

11784
### Review workflow
11885

File renamed without changes.

docs/deposit/upload.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,26 @@ Because metadata is submitted to DataCite when registering a DOI, you cannot req
9292

9393
When requesting a DOI, CDS will register two DOIs. Read more in the [DOI versioning FAQ](https://repository.cern/help/versioning).
9494

95+
## Related identifiers
96+
97+
If your record is related to another resource — for example, a preprint that has since been published in a journal, or a dataset associated with a paper — you should link them using **Related identifiers** in the deposit form. This improves discoverability and helps readers find all versions of a work.
98+
99+
Common relationships to declare:
100+
101+
| Situation | Relation type to use |
102+
|---|---|
103+
| This record is a preprint; a published version exists elsewhere | `IsVersionOf` (this record) → journal DOI |
104+
| This record is the published version; a preprint exists | `HasVersion` (this record) → preprint DOI |
105+
| A new version of this record exists | `IsPreviousVersionOf` → new version DOI |
106+
| This record supersedes an older version | `IsNewVersionOf` → old version DOI |
107+
| This record is a dataset used by a paper | `IsSupplementTo` → paper DOI |
108+
109+
To add a related identifier, open the deposit form, scroll to the **Related works** section, and enter the identifier (DOI, arXiv ID, handle, etc.) along with the appropriate relation type.
110+
111+
![Related identifiers](./images/related-identifiers.jpg)
112+
113+
For a full list of supported relation types and detailed guidance, see the [DataCite documentation on connecting related works](https://support.datacite.org/docs/connecting-to-works).
114+
95115
## Other metadata fields
96116

97117
The deposit form supports many additional metadata fields to help describe your upload. Common fields include:

0 commit comments

Comments
 (0)