Merge pull request #388 from tilfischer/main

License to Licence, page on licences and proofreading pub std and licence page

docs/00_intro/10_fair.mdx

@@ -124,7 +124,7 @@ Repositories should provide data publishers with the opportunity to include a pl
 
 #### R1.1. (meta)data are released with a clear and accessible data usage license
 
-The metadata should include human and machine-readable use conditions, such as a [license](/docs/licenses). [Creative Commons](https://creativecommons.org/) licenses are commonly used for scientific data. [re3data](https://www.re3data.org/) lists whether a repository allows researchers to directly select a license or terms of use agreement when depositing data. At a minimum, repositories should allow researchers to add a license file.
+The metadata should include human and machine-readable use conditions, such as a [licence](/docs/licences). [Creative Commons](https://creativecommons.org/) licences are commonly used for scientific data. [re3data](https://www.re3data.org/) lists whether a repository allows researchers to directly select a licence or terms of use agreement when depositing data. At a minimum, repositories should allow researchers to add a licence file.
 
 #### R1.2. (meta)data are associated with detailed provenance
 

docs/30_data/50_data_storage.mdx

@@ -52,7 +52,7 @@ Many of the requirements are often solved by dedicated [repositories](/docs/repo
 _see [RDMKit](https://rdmkit.elixir-europe.org/preserving)_
 :::
 
-Documentation or conversion of files into long-term backup formats. The data-holding facility must for its part guarantee security, quality and availability. Consider any license regulations or data protection of personal data when releasing it to the public.
+Documentation or conversion of files into long-term backup formats. The data-holding facility must for its part guarantee security, quality and availability. Consider any licence regulations or data protection of personal data when releasing it to the public.
 
 If you publish your data in public repositories, your data will also be preserved.
 

docs/40_smartlab/15_choose_eln.mdx

@@ -36,7 +36,7 @@ Therefore, choosing the right ELN is crucial for a successful implementation of
 
 |Category|Explanation|
 |:------------|:------------|
-|License model|Commercial ELNs mostly use proprietary file formats, the source code is closed source and a license fee is charged. Open source ELNs are free of charge, use open standard formats, source code is openly accessible and further developed by an active developer community. Implementation and maintenance require the appropriate human resources.|
+|Licence model|Commercial ELNs mostly use proprietary file formats, the source code is closed source and a licence fee is charged. Open source ELNs are free of charge, use open standard formats, source code is openly accessible and further developed by an active developer community. Implementation and maintenance require the appropriate human resources.|
 |Providing model|Software can be provided either in a cloud (SaaS - Software as a Service) or server-based for local installation at the customer's site (on-premises).|
 |File storage|Data storage in the cloud of the ELN provider (or their service provider, e.g. in the EU) or the possibility of storage on own local servers/in the own cloud are offered.|
 |Concept|Concept refers to the subject-specific orientation. Generic tools can be used in all subjects, but usually do not provide specific features, such as structure editors for chemistry.|

docs/50_data_publication/10_repositories.mdx

@@ -21,7 +21,7 @@ Repositories can be hosted at institutional servers or are provided by broader o
 
 A repository is constituted by a repository software and a database. Researchers transfer their data to the repository typically via a browser-based user interface, and/or the repository operators **harvest** the data from other platforms via appropriate protocols and interfaces.
 
-Some, but not all, repositories curate and review the data before **ingestion** with regard to their content and quality, sometimes also regarding legal aspects (copyright, data protection, [licenses](/docs/licenses)).
+Some, but not all, repositories curate and review the data before **ingestion** with regard to their content and quality, sometimes also regarding legal aspects (copyright, data protection, [licences](/docs/licences)).
 
 In order to allow data reuse by other researchers, [metadata](/docs/metadata), including [provenance information](/docs/provenance/), are required beside the actual data. Metadata describe the research data and provide information about its creation, the methods or software used as well as legal aspects. Metadata can be either added manually via a metadata editor or can be provided through other applications. The process to manually add metadata via a metadata editor can be compared to the process of submitting a manuscript to a publisher via the publishers submission system.
 

docs/50_data_publication/20_choose_repository/10_choose_repository.mdx

@@ -37,7 +37,7 @@ Based on the [criteria](https://doi.org/10.3897/rio.6.e55852) chosen by Task Are
 -   [Inorganic Crystal Structure Database](/docs/csd_icsd/)\*<br/>Field-specific repository for x-ray diffraction data of inorganic compounds, elements, minerals, intermetallic phases and ionic solids, operated by FIZ Karlsruhe.
 -   [Joint CCDC/FIZ Access Structures Service](/docs/csd_icsd/)<br/>Service that provides open access to the CSD Structure Depot, but not to all CSD data.
 
-\*Resource for which a license agreement is required.
+\*Resource for which a licence agreement is required.
 
 ## Further Repositories
 
@@ -47,7 +47,7 @@ Based on the [criteria](https://doi.org/10.3897/rio.6.e55852) chosen by Task Are
 -   [Zenodo](https://zenodo.org/)<br/>Generic repository developed under the European OpenAIRE program, operated by CERN.
 -   [EUDAT B2SHARE](https://sp.eudat.eu/catalog/resources/709c053d-3b3f-4c54-8ef4-6efeea387816)<br/>Generic repository operated by a pan-european network consisting of more than 25 research organisations, data and computing centers.
 
-\*Resource for which a license agreement is required.
+\*Resource for which a licence agreement is required.
 
 ## Currently under Development within NFDI4Chem
 
@@ -65,6 +65,6 @@ Further details of the repositories listed above can be found on the sub-pages o
 
 Main authors: [ORCID:0000-0001-7696-7662](https://orcid.org/0000-0001-7696-7662), [ORCID:0000-0003-4480-8661](https://orcid.org/0000-0003-4480-8661) and [ORCID:0000-0002-5035-7978](https://orcid.org/0000-0002-5035-7978)
 
-_This page is licensed under a Creative Commons Universal ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/deed.en)) Public Domain Dedication International License to allow for reuse of these lists._
+_This page is licensed under a Creative Commons Universal ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/deed.en)) Public Domain Dedication International Licence to allow for reuse of these lists._
 
 ![CC0 badge](/img/cc-zero.svg)

docs/50_data_publication/20_choose_repository/50_nmrxiv.mdx

@@ -36,7 +36,7 @@ The immediate goal of nmrXiv is to integrate and execute the following objective
 
 ### Software Development
 
-To develop nmrXiv based on a voluntarily FAIR, cloud-based infrastructure that uses freely shared source code and deployment methods. Apply industry-grade development practices to ensure platform reliability, safety, and efficacy. Use Continuous Improvement principles will ensure an always-on user experience and high reliability. Release the codebase and infrastructure details (including the development, documentation, and usage practices) through MIT Open Source License for openness.
+To develop nmrXiv based on a voluntarily FAIR, cloud-based infrastructure that uses freely shared source code and deployment methods. Apply industry-grade development practices to ensure platform reliability, safety, and efficacy. Use Continuous Improvement principles will ensure an always-on user experience and high reliability. Release the codebase and infrastructure details (including the development, documentation, and usage practices) through MIT Open Source Licence for openness.
 
 More details about the platform architecture and related topics – [here](https://docs.nmrxiv.org/developer-guides/architecture.html)
 

docs/50_data_publication/20_choose_repository/60_radar4chem.mdx

@@ -32,7 +32,7 @@ _Research Data Repository for Chemistry_
 
 :::
 
-RADAR4Chem is a **multidisciplinary** repository for the publication of research data from **all disciplines** of **chemistry**. It was created in 2022 and is hosted at FIZ Karlsruhe (Leibniz Institute for Information Infrastructure). RADAR4Chem is based on the established research data repository **RADAR Cloud**. RADAR Cloud is primarily used by academic institutions for institutional research data management (data archiving and publication). The use of **RADAR Cloud** is subject to a **fee** and requires the stipulation of a **contract**. **RADAR4Chem**, on the other hand, is exclusively directed to researchers in the field of chemistry at publicly funded research institutions and universities in Germany. **No contract** is required and **no fees** are charged. RADAR4Chem allows discipline- and format-independent publication and storage (**at least 25 years**) of **research data** from all disciplines of chemistry. It complements the already existing portfolio of discipline specific repositories and is e.g. ideally suited for cross-disciplinary data or datasets with a multitude of different data formats. RADAR4Chem is easy and low-threshold to use. The researchers are responsible for the upload, organisation, annotation, and curation of research data as well as the peer-review process (as an optional step) and finally their publication. Using the service requires [advising from FIZ Karlsruhe](https://www.nfdi4chem.de/index.php/2650-2/), registration to RADAR4Chem, and consent to the [RADAR4Chem license and usage instructions](https://radar.products.fiz-karlsruhe.de/sites/default/files/radar/docs/terms/License_and_User_Instructions_for_Data_Providers_RADAR4Chem.pdf). Authentication is supported after self-registration and via [DFN-AAI](https://doku.tid.dfn.de/en:dfnaai:start) ([Shibboleth](https://www.incommon.org/software/shibboleth/). **Metadata** are recorded using the internal [RADAR Metadata Schema](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/radar-metadatenschema) (based on [DataCite Metadata Schema 4.0](https://schema.datacite.org/)), which supports 10 **mandatory** and 13 **optional metadata fields**. Annotation can be made on the dataset level and on the individual files and folders level. A [user license](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/lizenzen-fuer-forschungsdaten) which indicates re-use rules for the data, must be defined for each dataset. Each published dataset receives a **DOI** which is registered with [DataCite](https://datacite.org/). RADAR Metadata uses a combination of controlled lists and free text entries. Author identification is ensured by ORCID iD and funder identification by [CrossRef Open Funder Registry](https://www.crossref.org/pdfs/about-funder-registry.pdf) (more interfacing options will be implemented in the future). Datasets can be easily linked with other digital resources (e.g. text publications) via a **“related identifier”**. To maximise data dissemination and discoverability, the metadata of published datasets are indexed in various formats (e.g. RADAR and DataCite) and offered for public metadata harvesting e.g. via an [OAI-provider](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/radar-oai-provider). The **research data** is **stored permanently** on magnetic tapes redundantly in three copies at different locations at the Steinbuch Centre for Computing (SCC) of the Karlsruhe Institute of Technology (KIT, 2 copies) and at the Centre for Information Services and High Performance Computing (ZIH) of the TU Dresden (1 copy).
+RADAR4Chem is a **multidisciplinary** repository for the publication of research data from **all disciplines** of **chemistry**. It was created in 2022 and is hosted at FIZ Karlsruhe (Leibniz Institute for Information Infrastructure). RADAR4Chem is based on the established research data repository **RADAR Cloud**. RADAR Cloud is primarily used by academic institutions for institutional research data management (data archiving and publication). The use of **RADAR Cloud** is subject to a **fee** and requires the stipulation of a **contract**. **RADAR4Chem**, on the other hand, is exclusively directed to researchers in the field of chemistry at publicly funded research institutions and universities in Germany. **No contract** is required and **no fees** are charged. RADAR4Chem allows discipline- and format-independent publication and storage (**at least 25 years**) of **research data** from all disciplines of chemistry. It complements the already existing portfolio of discipline specific repositories and is e.g. ideally suited for cross-disciplinary data or datasets with a multitude of different data formats. RADAR4Chem is easy and low-threshold to use. The researchers are responsible for the upload, organisation, annotation, and curation of research data as well as the peer-review process (as an optional step) and finally their publication. Using the service requires [advising from FIZ Karlsruhe](https://www.nfdi4chem.de/index.php/2650-2/), registration to RADAR4Chem, and consent to the [RADAR4Chem license and usage instructions](https://radar.products.fiz-karlsruhe.de/sites/default/files/radar/docs/terms/License_and_User_Instructions_for_Data_Providers_RADAR4Chem.pdf). Authentication is supported after self-registration and via [DFN-AAI](https://doku.tid.dfn.de/en:dfnaai:start) ([Shibboleth](https://www.incommon.org/software/shibboleth/). **Metadata** are recorded using the internal [RADAR Metadata Schema](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/radar-metadatenschema) (based on [DataCite Metadata Schema 4.0](https://schema.datacite.org/)), which supports 10 **mandatory** and 13 **optional metadata fields**. Annotation can be made on the dataset level and on the individual files and folders level. A [user licence](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/lizenzen-fuer-forschungsdaten) which indicates re-use rules for the data, must be defined for each dataset. Each published dataset receives a **DOI** which is registered with [DataCite](https://datacite.org/). RADAR Metadata uses a combination of controlled lists and free text entries. Author identification is ensured by ORCID iD and funder identification by [CrossRef Open Funder Registry](https://www.crossref.org/pdfs/about-funder-registry.pdf) (more interfacing options will be implemented in the future). Datasets can be easily linked with other digital resources (e.g. text publications) via a **“related identifier”**. To maximise data dissemination and discoverability, the metadata of published datasets are indexed in various formats (e.g. RADAR and DataCite) and offered for public metadata harvesting e.g. via an [OAI-provider](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/radar-oai-provider). The **research data** is **stored permanently** on magnetic tapes redundantly in three copies at different locations at the Steinbuch Centre for Computing (SCC) of the Karlsruhe Institute of Technology (KIT, 2 copies) and at the Centre for Information Services and High Performance Computing (ZIH) of the TU Dresden (1 copy).
 
 Please note: currently, the free-of-charge use of RADAR4Chem is **limited to a maximum of 10 GB** storage volume per research project. Researchers from the NFDI4Chem community whose research data volume exceeds this free quota and are interested in using RADAR functions institution-wide or in archiving research data, can stipulate a [regular RADAR Cloud contract](https://radar.products.fiz-karlsruhe.de/en/radaragreementsprices/vertraege-preise).
 

docs/50_data_publication/20_choose_repository/90_csd_icsd.mdx

@@ -20,7 +20,7 @@ _Joint CCDC/FIZ access structures service_
 />
 
 :::info Note:
-Link to [CSD](https://www.ccdc.cam.ac.uk/solutions/software/webcsd/) (requires license) [ICSD](https://icsd.fiz-karlsruhe.de/) (requires license) and [Joint CCDC/FIZ Access Structure](https://www.ccdc.cam.ac.uk/structures/) that provides open access to the CSD Structure Depot, but not all CSD data.
+Link to [CSD](https://www.ccdc.cam.ac.uk/solutions/software/webcsd/) (requires licence) [ICSD](https://icsd.fiz-karlsruhe.de/) (requires licence) and [Joint CCDC/FIZ Access Structure](https://www.ccdc.cam.ac.uk/structures/) that provides open access to the CSD Structure Depot, but not all CSD data.
 
 CSD: Link to [FAIRsharing](https://doi.org/10.25504/FAIRsharing.vs7865)
 Link to [re3data](http://doi.org/10.17616/R36011)

docs/50_data_publication/30_licences.mdx

@@ -0,0 +1,34 @@
+---
+title: "Licences"
+slug: "/licences"
+---
+
+import useBaseUrl from "@docusaurus/useBaseUrl";
+
+# Licences
+
+Licences for research data often cause confusion among researchers. One of the main reasons for this is the interplay between **licences used for research data** and the requirements for referencing previous scientific work on which the current work is based, in accordance with the [Guidelines for Safeguarding Good Scientific Practice (DFG Code of Conduct)](https://wissenschaftliche-integritaet.de/en/code-of-conduct/). 
+
+The DFG Code of Conduct requires researchers to cite original sources, i.e. to include original sources in reference sections. Providing a licence for research data is a way to provide permission to share and reuse the data.
+
+Work on dedicated licences for research data is ongoing. Until these licences are available, we recommend switching to [Creative Commons]((https://creativecommons.org/)) licences, which were developed to license creative works.
+
+:::info Recommendation:
+NFDI4Chem recommends the use the least restrictive [Creative Commons](https://creativecommons.org/) licences such as [CC0](https://creativecommons.org/public-domain/cc0/) and [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.en) 
+:::
+
+:::danger Notice:
+As a first starting point for further information, we strongly recommend the page on [Licenses for research data](https://radar.products.fiz-karlsruhe.de/en/radarfeatures/lizenzen-fuer-forschungsdaten) provided by FIZ Karlsruhe, which also includes information on certain rights that authors cannot waive in Germany, that copyright only protects personal intellectual creations, and that isolated research data are not protected by copyright.  
+:::
+
+Disclaimer: It should be checked on a case-by-case basis whether research data is protected by copyright. If the copyright status is unclear, please contact a legal professional at your institution.
+
+In order to provide you with further helpful information, we have compiled a list of links:
+
+- [Heidi Seibold - Choosing an open license](https://heidiseibold.ck.page/posts/choosing-an-open-license)
+- [Forschungsdaten.info - Forschungsdaten Veröffentlichen](https://forschungsdaten.info/themen/rechte-und-pflichten/forschungsdaten-veroeffentlichen/) (in German)
+- [Forschungsdaten.info - Urheberrecht](https://forschungsdaten.info/themen/rechte-und-pflichten/urheberrecht/) (in German)
+- [Creative Commons - About CC Licenses](https://creativecommons.org/share-your-work/cclicenses/) 
+- [Creative Commons - License Chooser](https://creativecommons.org/choose/)
+- [Forschungsdaten in den Naturwissenschaften: Eine urheberrechtliche Bestandsaufnahme mit ihren Implikationen für universitäres FDM](https://doi.org/10.11588/heibooks.979.c13728) (in German)
+- [Open Knowledge Foundation - Open Data Commons](https://opendatacommons.org/licenses/odbl/)