Persistent identifiers(pid) - Revision history

Neteler: +OSGeo folks on ORCID

2024-09-26T08:06:09Z

+OSGeo folks on ORCID

Neteler: +:Category: Persistent identifiers

2024-09-26T08:00:22Z

+Category: Persistent identifiers

Gisix: /* Examples */

2022-01-15T18:07:13Z

Examples

Gisix: /* Sustainable Approach: Create a live link between the GitHub Repo and Zenodo */

2022-01-13T14:56:40Z

Sustainable Approach: Create a live link between the GitHub Repo and Zenodo

Gisix: /* Examples */ added mapserver DOI

2022-01-13T08:54:41Z

Examples: added mapserver DOI

Gisix: added MapServer & more candidates

2022-01-12T15:55:21Z

added MapServer & more candidates

Gisix: added sample json file and DOI reservation option

2022-01-12T15:53:20Z

added sample json file and DOI reservation option

Gisix: /* Examples */

2022-01-12T10:51:08Z

Examples

Gisix: /* Requirements */

2022-01-12T10:48:31Z

Requirements

Gisix: /* Howto */

2022-01-09T15:56:37Z

Howto

@@ Line 32: / Line 32: @@
 ==== Open Researcher and Contributor ID (ORCID) ====
 * [https://en.wikipedia.org/wiki/ORCID Definition of ORCID by Wikipedia]
 === PID for documentation ===

← Older revision		Revision as of 08:00, 26 September 2024
Line 133:		Line 133:
	== FAQ ==		== FAQ ==
	* [https://help.zenodo.org/ Zenodo FAQ]		* [https://help.zenodo.org/ Zenodo FAQ]
		+
		+	[[Category: Persistent identifiers]]

@@ Line 123: / Line 123: @@
 ====Examples====
+# [https://doi.org/10.5281/zenodo.5854561 GeoServer]: [https://doi.org/10.5281/zenodo.5854561
-* [https://doi.org/10.5281/zenodo.5825144 MOSS (simple example from a static heritage project)]
+# [https://doi.org/10.5281/zenodo.5854653 GeoTools]: https://doi.org/10.5281/zenodo.5854653
-* [https://doi.org/10.5281/zenodo.5810537 GRASS GIS (complex example from a highly dynamic project)]
+# [https://doi.org/10.5281/zenodo.3407865 GMT]: https://doi.org/10.5281/zenodo.3407865
-* [https://doi.org/10.5281/zenodo.5708769 GMT]
+# [https://doi.org/10.5281/zenodo.5849091 gvSIG]: https://doi.org/10.5281/zenodo.5849091
-* [https://doi.org/10.5281/zenodo.5842013 MapServer]
+# [https://doi.org/10.5281/zenodo.5176030 GRASS GIS]: https://doi.org/10.5281/zenodo.5176030
-* pycsw (ready for DOI minting)
+# [https://doi.org/10.5281/zenodo.5842012 MapServer]: https://doi.org/10.5281/zenodo.5842012
-* pygeoapi (ready for DOI minting)
+# [https://doi.org/10.5281/zenodo.5140318 MOSS]  https://doi.org/10.5281/zenodo.5140318
 == FAQ ==
 * [https://help.zenodo.org/ Zenodo FAQ]

@@ Line 89: / Line 89: @@
 *Pro: Immediate automated updates of DOI payload and metadata for each software release on GitHub
 *Con: Takes a bit longer than option 1 (20 minutes ?)
-*Beware: If no .zenodo.json file is included, the author section of the DOI landing page will be reset to the username of the owner of the GitHub repo (as shown [https://zenodo.org/record/4723586#.Yd7r0WjMJD8 here] ). This can be manually edited afterwards, but is awkward. Also, the citation style service in the lower right of the page will not work. It is set up to provide on the fly references according to many established citation styles (e.g. AIMS Geoscience, Springer, etc.).
+*Beware: If no .zenodo.json file is included, the author section of the DOI landing page will be reset to the username of the owner of the GitHub repo upon each release update (as shown [https://zenodo.org/record/4723586#.Yd7r0WjMJD8 here] ). This can be manually edited afterwards, but is awkward and can be avoided. Also, the citation style service in the lower right of the page will not work. It is set up to provide on the fly references according to many established citation styles (e.g. AIMS Geoscience, Springer, etc.).
 ==== Example of a .zenodo.json file ====

@@ Line 127: / Line 127: @@
 * [https://doi.org/10.5281/zenodo.5810537 GRASS GIS (complex example from a highly dynamic project)]
 * [https://doi.org/10.5281/zenodo.5708769 GMT]
-* MapServer (ready for DOI minting)
+* [https://doi.org/10.5281/zenodo.5842013 MapServer]
 * pycsw (ready for DOI minting)
 * pygeoapi (ready for DOI minting)

@@ Line 89: / Line 89: @@
 *Pro: Immediate automated updates of DOI payload and metadata for each software release on GitHub
 *Con: Takes a bit longer than option 1 (20 minutes ?)
-*Beware: If no CFF or .zenodo.json file is included, the author section of the DOI landing page will be reset to the username of the owner of the GitHub repo. This can be manually edited afterwards, but is awkward.
+*Beware: If no .zenodo.json file is included, the author section of the DOI landing page will be reset to the username of the owner of the GitHub repo (as shown [https://zenodo.org/record/4723586#.Yd7r0WjMJD8 here] ). This can be manually edited afterwards, but is awkward. Also, the citation style service in the lower right of the page will not work. It is set up to provide on the fly references according to many established citation styles (e.g. AIMS Geoscience, Springer, etc.).
 ====Howto====
 * [https://guides.lib.berkeley.edu/citeyourcode How to make your code citable (Berkeley Library)]
 * [https://www.youtube.com/watch?v=A9FGAU9S9Ow Tutorial video (YouTube)]
-* Not covered in the video and the Berkeley guido: A file (hard-)named ".zenodo.json" may be added to the top-level of the GitHub repo for advanced author info handling ([https://github.com/OSGeo/MOSS/blob/main/.zenodo.json Example from MOSS project]).
+* Not covered in the video and the Berkeley guide: A file (hard-)named ".zenodo.json" may be added to the top-level of the GitHub repo for advanced author info handling ([https://github.com/OSGeo/MOSS/blob/main/.zenodo.json Example from MOSS project], see above for a code example).
 ====Examples====

@@ Line 68: / Line 68: @@
 === Requirements ===
-This should be done by a person who represents the software project (member of PSC or similar).
+This should be done by a person who represents the software project (member of PSC or similar). This step requires login credentials for both the GitHub and the Zenodo account. A Zenodo account can be easily set up.
 === Options ===

@@ Line 81: / Line 81: @@
 ==== Howto ====
-Coming real soon
+ *[https://www.youtube.com/watch?v=S1qK_TA52e4 Howto video]
 ====Examples====
 *[https://doi.org/10.5281/zenodo.1163021 rasdaman project]