You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/communities/submit.md
+12-45Lines changed: 12 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Submit to a community
2
2
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.
4
4
5
5
## Where should I submit?
6
6
@@ -12,7 +12,12 @@ If you are unsure which community to submit to, the table below covers the most
12
12
| Internal CERN report, note, or technical document | The relevant experiment or department community, if one exists |
13
13
| Dataset or software produced as part of a CERN experiment | The relevant experiment community |
14
14
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.
16
21
17
22
!!! tip
18
23
@@ -26,26 +31,6 @@ Before a record can be accepted into a community, CDS checks that the record's m
26
31
27
32
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.
28
33
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.
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
-
49
34
## Multiple communities
50
35
51
36
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:
66
51
67
52
Each community has its own review process. Submitting to multiple communities means each community's curators will independently review and decide on your record.
68
53
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
87
55
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).
89
58
90
59
If a submission is still under review (not yet accepted), you can withdraw it instead of removing it:
91
60
@@ -101,18 +70,16 @@ If a submission is still under review (not yet accepted), you can withdraw it in
101
70
102
71
## CERN Research
103
72
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.
105
74
106
75

107
76
108
77
### Who should submit
109
78
110
79
You should submit to CERN Research if your record is:
111
80
112
-
- A publication or preprint authored by CERN staff, fellows, or associates.
113
81
- 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.
Copy file name to clipboardExpand all lines: docs/deposit/upload.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,26 @@ Because metadata is submitted to DataCite when registering a DOI, you cannot req
92
92
93
93
When requesting a DOI, CDS will register two DOIs. Read more in the [DOI versioning FAQ](https://repository.cern/help/versioning).
94
94
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.
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
+
95
115
## Other metadata fields
96
116
97
117
The deposit form supports many additional metadata fields to help describe your upload. Common fields include:
0 commit comments