Skip to content

Commit

Permalink
Add links
Browse files Browse the repository at this point in the history
  • Loading branch information
carlinmack authored and lnielsen committed Dec 13, 2023
1 parent ad48503 commit 565417c
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion content/help/faq/general/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ answer:

Once the record has been published you can no longer change its files. Nonetheless, there are several options:
1. If the record has a Zenodo DOI (prefix: ``10.5281``):
* In most cases it is recommended to create a new version of a record (more details available [here](/#versioning)). For example: modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.
* In most cases it is recommended to create a new version of a record ([more details](/faq/#versioning)). For example: modifications of the dataset/software, addition or removal of files, new versions of datasets, software or revisions of the papers, including major revisions as well typos and formatting/styling.
* Exceptionally, we allow small modifications to the record's files, if and only if the record was published recently (in the past month). If you have spotted mistakes such as typos, accidental omission of important files/inclusion of hidden files or confidential files and would like to update them, please contact us.
1. If the record has a non-Zenodo DOI:
* Since it is not possible to create new versions for non-Zenodo DOIs you should contact us about updating files directly.
Expand Down
2 changes: 1 addition & 1 deletion content/help/faq/github/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ category: github
#### qaitem ####
question: I made a GitHub release, but it does not show up on Zenodo.
----
answer: Make sure the repository was enabled before the release was made, otherwise feel free to contact us.
answer: Make sure the repository was enabled before the release was made, otherwise feel free to [contact us](https://zenodo.org/support).
----
category: github
#### qaitem ####
Expand Down
2 changes: 1 addition & 1 deletion content/help/faq/policies/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ category: policies
#### qaitem ####
question: Is Zenodo OAIS compliant?
----
answer: Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our infrastructure page for further details on Zenodo’s organizational and technical infrastructure.
answer: Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our [infrastructure page](https://about.zenodo.org/infrastructure/) for further details on Zenodo’s organizational and technical infrastructure.
----
category: policies
#### qaitem ####
Expand Down
6 changes: 3 additions & 3 deletions content/help/faq/versioning/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ This is best illustrated by an example of a software package. If the software ha

The first two DOIs for versions **v1.0** and **v.1.1** represent the specific versions of the software. The last DOI represents all the versions of the given software package, i.e. the concept of the software package and the ensemble of versions. We therefore also call the them **Version DOIs** and **Concept DOIs** (note, technically both are just normal DOIs).

You may notice that the version DOIs do not include a “.v1”-suffix. Read below to find out why.
You may notice that the version DOIs do not include a “.v1”-suffix. [Read below](/faq/#cversioning-8) to find out why.
----
category: versioning-col1
#### qaitem ####
Expand Down Expand Up @@ -109,6 +109,6 @@ category: versioning-col2
#### qaitem ####
question: Do you duplicate all the files for every new version of a record?
----
answer: No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. Invenio v3, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new 10kb.
----
answer: No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. [Invenio v3](https://inveniosoftware.org/products/framework/), the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new 10kb.
---
category: versioning-col2

0 comments on commit 565417c

Please sign in to comment.