Difference between revisions of "DOI"

From OSGeo
Jump to navigation Jump to search
(→‎DOI for OSGeo Projects: Started to add CrossRef queries, returning JSON objects containing all occurances in literature, etc.)
(24 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
== Scope ==
 
== Scope ==
* This wiki page summarises relevant facts about DOI for the OSGeo communities.  
+
* This wiki page summarises relevant facts about DOI and related persistent Identifiers (PID) for the OSGeo communities.  
 
* A DOI is a persistent identifier (PID).  
 
* A DOI is a persistent identifier (PID).  
 
* More infomation about PID for OSGeo is available  [https://wiki.osgeo.org/wiki/Persistent_identifiers(pid) here] in the wiki
 
* More infomation about PID for OSGeo is available  [https://wiki.osgeo.org/wiki/Persistent_identifiers(pid) here] in the wiki
Line 12: Line 12:
 
* [https://help.zenodo.org/ Zenodo FAQ]
 
* [https://help.zenodo.org/ Zenodo FAQ]
  
== Useful Services ==
+
== HowTo information about ORCID (Open Researcher and Contributor ID -> a PID for people) ==
 +
 
 +
* [https://info.orcid.org/researcher-faq/ ORCID FAQ]
 +
* [https://vimeo.com/97150912 ORDID introduction video]
 +
* [https://www.youtube.com/watch?v=VRUUsUqGB9c HOWTO: Register an ORCID (Video tutorial)]
 +
* [https://support.datacite.org/docs/how-to-activate-orcid-auto-update How to set up an ORCID account for credit propagation (e.g. Version-DOI of OSGeo project software releases will automagically appear in the "works" section of the associated ORCID accounts)]
 +
 
 +
== Howto information for GitHub Repo maintainers (source [https://help.zenodo.org/ Zenodo FAQ]) ==
 +
 
 +
 
 +
=== My organizational repository does not show up on the GitHub list ===
 +
 
 +
''"In order to see and archive your organizational repositories on Zenodo you will need to have "Admin" permissions on said repository, either as an Admin of the organization or an Admin of one of your organization's repositories. Additionally, please make sure that the OAuth application on GitHub is granting permissions not only to your personal repositories but also to your organizational ones - to verify that go to your GitHub OAuth settings in your profile, and click on the Zenodo application to see more details. Make sure that Zenodo is given access (green tick) to your organization under "Organization access".
 +
 
 +
After that, navigate to your Zenodo GitHub settings page and click the "Sync now" button at the top."''
 +
 
 +
=== I made a GitHub release, but it does not show up on Zenodo. ===
 +
 
 +
''"Make sure the repository was enabled before the release was made, otherwise feel free to contact ZENODO."
 +
''
 +
 
 +
=== Is it possible to archive a GitHub repository, before it was enabled on Zenodo? ===
 +
 
 +
''"Only the repositories which were enabled before a release was made will be archived automatically. If you want to archive some of your old releases, you can always download a release ZIP from GitHub and upload it to Zenodo using our web interface as a regular upload."''
 +
 
 +
=== How to change the default metadata for my GitHub releases? ===
 +
 
 +
''"You can include metadata in a .zenodo.json file at the root of your GitHub repository. This file's contents should be in line with the Zenodo deposit metadata schema and will be used to update the metadata from future GitHub releases. For more information on how to create a .zenodo.json file, you can have a look at our GitHub integration documenation."''
 +
 
 +
=== Do you support other software metadata files, like CITATION.cff or codemeta.json? ===
 +
 
 +
''"Part of our plans and ongoing work is to take into account or improve our integration of other software metadata schemas such as the Citation File Format (CFF) and CodeMeta. We are working closely with our users and scholarly software and citation communities to figure out exactly when, in what form, and how all these different metadata schemas and their files will be integrated into Zenodo."''
 +
 
 +
=== How does a CITATION.cff file affect the metadata of my GitHub release? ===
 +
 
 +
''"When we find a CITATION.cff file in your GitHub repository's root folder, we make a best-effort attempt at parsing Zenodo-compatible metadata from it.
 +
For backwards-compatibility, if you have a .zenodo.json file in the repository, only the .zenodo.json's metadata will be taken into account. Of course, any existing valid CITATION.cff file will still be used to display the citation box on the GitHub repository page, but will not affect in any way the metadata we extract for your published release Zenodo record."''
 +
 
 +
== Usage examples for people writing articles ==
 +
 
 +
=== DOI ===
 +
 
 +
How to include a DOI-based reference to a LaTEX/Overleaf document.
 +
 
 +
BEWARE: As of now (20230327) it remains to be confirmed that DOI-tags in citations work without the https://doi.org-header. This might (just) reuslt in human readable information, but not machine-readable.
 +
 
 +
==== Publication DOI ====
 +
@article{Chen_2003_Giants, title={On the Shoulders of Giants}, url={\url{https://doi.org/10.1007/978-1-4471-0051-5_5}}, DOI={10.1007/978-1-4471-0051-5_5}, journal={Mapping Scientific Frontiers: The Quest for Knowledge Visualization}, publisher={Springer London}, author={Chen, Chaomei}, year={2003}, pages={135–166} }
 +
 
 +
==== Video DOI ====
 +
 
 +
@article{Inman_1987, title={GRASS}, url={https://av.tib.eu/media/12963}, DOI={10.5446/12963}, abstractNote={Video presentation explaining the features and capabilities of this computer-based mapping system.}, publisher={Moving Pictures, US Army Construction Engineering Research Laboratory}, author={Inman, Roger J.}, year={1987}, language={en} }
 +
 
 +
==== Software Concept DOI (a reference to a software project as a whole) ====
 +
 
 +
@article{GRASS_CONCEPT_DOI, title={OSGeo/grass: GRASS GIS 8.2.0}, url={https://zenodo.org/record/5176030}, DOI={10.5281/ZENODO.5176030}, abstractNote={ .. CONTENT OMMITTED FOR BREVITY ..}, year={2022}, month={Jun} }
 +
 
 +
==== Software Version DOI (a reference to a particular software release) ====
 +
 
 +
@article{QGIS_Contributors_2022, title={QGIS},
 +
url={https://doi.org/10.5281/zenodo.5869837},
 +
DOI={10.5281/ZENODO.5869837}, 
 +
publisher={Zenodo},
 +
author={QGIS Contributors},
 +
year={2022},
 +
month={Jan} }
 +
 
 +
=== ORCID ===
 +
 
 +
How to include ORCIDs to a LaTEX/Overleaf document:
 +
Include these packages:
 +
\usepackage{orcidlink}
 +
\usepackage[hidelinks]{hyperref}
 +
 
 +
 
 +
 
 +
\author{
 +
Peter Löwe\,\orcidlink{0000-0003-2257-0517}~\textsuperscript{1}\thanks{Corresponding author},
 +
Markus Neteler\,\orcidlink{0000-0003-1916-1966}~\textsuperscript{2}
 +
}
 +
(Source: [https://doi.org/10.5194/isprs-archives-XLVIII-4-W1-2022-287-2022 OSGEO, PERSISTENT IDENTIFIERS AND THE SHAPE OF THINGS TO COME])
 +
 
 +
 
 +
=== ROR ===
 +
 
 +
TBD: How to include a PID for an institution (like OSGeo) from the Research Organisation Registry (ROR) ?
 +
 
 +
== Added-value services based on DOI ==
  
 
* [https://citation.crosscite.org/ Citation service by DataCite: Enter a DOI to create properly formatted references according to over 2400 citation styles for books, articles, etc.]
 
* [https://citation.crosscite.org/ Citation service by DataCite: Enter a DOI to create properly formatted references according to over 2400 citation styles for books, articles, etc.]
  
== DOI for OSGeo Projects ==
 
  
# [https://doi.org/10.5281/zenodo.5865317 Actinia]: https://doi.org/10.5281/zenodo.5865317 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5865317 CrossRef event data (JSON)]
 
# [https://doi.org/10.5281/zenodo.5884351 GDAL]:  https://doi.org/10.5281/zenodo.5884351
 
[https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5884351 CrossRef event data (JSON)]
 
# [https://doi.org/10.5281/ZENODO.5881915 Geopaparazzi]: https://doi.org/10.5281/ZENODO.5881915
 
[https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5881915 CrossRef event data (JSON)]
 
# [https://doi.org/10.5281/zenodo.5854561 GeoServer]: https://doi.org/10.5281/zenodo.5854561 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5854561 CrossRef event data (JSON)]
 
# [https://doi.org/10.5281/zenodo.5854653 GeoTools]: https://doi.org/10.5281/zenodo.5854653 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5854653 CrossRef event data (JSON)]
 
  
# [https://doi.org/10.5281/zenodo.3407865 GMT]: https://doi.org/10.5281/zenodo.3407865 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.3407865 CrossRef event data (JSON)]
+
== DOI availabe for OSGeo Projects ==
# [https://doi.org/10.5281/zenodo.5176030 GRASS GIS]: https://doi.org/10.5281/zenodo.5176030 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5176030 CrossRef event data (JSON)]
+
 
# [https://doi.org/10.5281/zenodo.5849091 gvSIG]: https://doi.org/10.5281/zenodo.5849091 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5849091 CrossRef event data (JSON)]
+
{|
# [https://doi.org/10.5281/ZENODO.5881778 Hortonmachine]: https://doi.org/10.5281/ZENODO.5881778 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5881778 CrossRef event data (JSON)]
+
! style="text-align:left;"| OSGeo Project
# [https://doi.org/10.5281/zenodo.5887014 Mapbender]: https://doi.org/10.5281/zenodo.5887014 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5887014 CrossRef event data (JSON)]
+
! DOI
# [https://doi.org/10.5281/zenodo.5842012 MapServer]: https://doi.org/10.5281/zenodo.5842012 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5842012 CrossRef event data (JSON)]
+
! First minted
# [https://doi.org/10.5281/zenodo.5140318 MOSS]https://doi.org/10.5281/zenodo.5140318 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5140318 CrossRef event data (JSON)]
+
! Citation example
# [https://doi.org/10.5281/zenodo.5884641 OSGeoLive]https://doi.org/10.5281/zenodo.5884641 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5884641 CrossRef event data (JSON)]
+
! Integration Status
# [https://doi.org/10.5281/zenodo.5884859 OSGeoLive Documentation]https://doi.org/10.5281/zenodo.5884859 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5884859 CrossRef event data (JSON)]
+
|-
# [https://doi.org/10.5281/zenodo.5879631 PostGIS]https://doi.org/10.5281/zenodo.5879631 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5879631 CrossRef event data (JSON)]
+
|[https://doi.org/10.5281/zenodo.5879231 actinia]
# [https://doi.org/10.5281/zenodo.5884394 PROJ]https://doi.org/10.5281/zenodo.5884394 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5884394 CrossRef event data (JSON)]
+
|https://doi.org/10.5281/zenodo.5879231
# [https://doi.org/10.5281/zenodo.5869837 QGIS]: https://doi.org/10.5281/zenodo.5869837 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5869837 CrossRef event data (JSON)]
+
| 2022
# [https://doi.org/10.5281/zenodo.1040170 rasdaman]: https://doi.org/10.5281/zenodo.1040170 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.1040170 CrossRef event data (JSON)]
+
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
# [https://doi.org/10.5281/zenodo.5882070 SMASH]: https://doi.org/10.5281/zenodo.5882070 [https://api.eventdata.crossref.org/v1/events?mailto=%7Byour-email-address-goes-here%7D&rows=200&obj-id=10.5281/ZENODO.5882070 CrossRef event data (JSON)]
+
| automated
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5884351 GDAL]
 +
| https://doi.org/10.5281/zenodo.5884351
 +
| 2022
 +
| [https://doi.org/10.1038/s41597-023-01929-2 Nature: Scientific data (2023)]
 +
| automated
 +
|-
 +
| [https://doi.org/10.5281/ZENODO.5881915 Geopaparazzi]
 +
| https://doi.org/10.5281/ZENODO.5881915
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| status
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5854561 GeoServer]
 +
| https://doi.org/10.5281/zenodo.5854561
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| status
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5854653 GeoTools]
 +
| https://doi.org/10.5281/zenodo.5854653
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| status
 +
|-
 +
| [https://doi.org/10.5281/zenodo.3407865 GMT]
 +
| https://doi.org/10.5281/zenodo.3407865
 +
| 2019
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| status
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5176030 GRASS GIS]
 +
| https://doi.org/10.5281/zenodo.5176030
 +
| 2021
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| automated
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5849091 gvSIG]
 +
| https://doi.org/10.5281/zenodo.5849091
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| manual upload
 +
|-
 +
| [https://doi.org/10.5281/ZENODO.5881778 Hortonmachine]
 +
| https://doi.org/10.5281/ZENODO.5881778
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| tbd
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5887014 Mapbender]
 +
| https://doi.org/10.5281/zenodo.5887014
 +
| 2022
 +
| tbd
 +
| tbd
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5842012 MapServer]
 +
| https://doi.org/10.5281/zenodo.5842012
 +
| 2021
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| tbd
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5140318 MOSS]
 +
| https://doi.org/10.5281/zenodo.5140318
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| automated
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5884641 OSGeoLive]
 +
| https://doi.org/10.5281/zenodo.5884641
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| tbd
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5884859 OSGeoLive Documentation]
 +
| https://doi.org/10.5281/zenodo.5884859
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| tbd
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5879631 PostGIS]
 +
| https://doi.org/10.5281/zenodo.5879631
 +
| 2021
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| manual upload
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5884394 PROJ]
 +
| https://doi.org/10.5281/zenodo.5884394
 +
| 2022
 +
| [https://doi.org/10.3390/rs14153524 MDPI: Remote sensing (2022)]
 +
| automated
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5869837 QGIS]
 +
| https://doi.org/10.5281/zenodo.5869837
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| manual upload
 +
|-
 +
| [https://doi.org/10.5281/zenodo.1040170 rasdaman]
 +
| https://doi.org/10.5281/zenodo.1040170
 +
| 2017
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| manual upload
 +
|-
 +
| [https://doi.org/10.5281/zenodo.5882070 SMASH]
 +
| https://doi.org/10.5281/zenodo.5882070
 +
| 2022
 +
| [https://doi.org/10.1007/978-3-030-53125-6_30 Springer Handbook of Geographic Information (2022)]
 +
| tbd
 +
|-
 +
!OSGeo projects with DOI
 +
|
 +
|19
 +
|}
 +
 
  
 
<Add your project DOI here, while maintaining alphabetical order>
 
<Add your project DOI here, while maintaining alphabetical order>
  
 
== Projects considering a DOI ==
 
== Projects considering a DOI ==
 
+
# degree
 
# (GeoPython: pycsw)
 
# (GeoPython: pycsw)
 
# (NASA World Wind)
 
# (NASA World Wind)
 +
  
 
<Add your project here>
 
<Add your project here>
 +
 +
== DOI for datasets related to OSGeo  ==
 +
 +
This is an incomplete overview over geospatial data sources which can be referenced by DOI.
 +
Many more datasets are available in Open Access repositories such as [https://www.zenodo.org Zenodo]
 +
=== GRASS GIS ===
 +
 +
# [https://doi.org/10.5281/zenodo.3359642 New Orleans Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3359642
 +
# [https://doi.org/10.5281/zenodo.3749397 Hilltop Arboretum Landform Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3749397
 +
# [https://doi.org/10.5281/zenodo.3359645 Sichuan Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3359645
 +
# [https://doi.org/10.5281/zenodo.5248688 The Hills of Governor's Island Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.5248688
 +
# [https://doi.org/10.5281/zenodo.3359620 Louisiana Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3359620
 +
# [https://doi.org/10.5281/zenodo.3968936 Natural Earth Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3968936
 +
# [https://doi.org/10.5281/zenodo.3359632 Global Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3359632
 +
# [https://doi.org/10.5281/zenodo.5248419 Governor's Island Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.5248419
 +
(add datasets here)
 +
 +
=== QGIS ===
 +
 +
# [https://doi.org/10.5281/zenodo.5701115 Governor's Island Dataset for QGIS] https://doi.org/10.5281/zenodo.5701115
 +
# [https://doi.org/10.5281/zenodo.3359620 Louisiana Dataset for GRASS GIS] https://doi.org/10.5281/zenodo.3359620
 +
(add datasets here)
  
 
== DOI for OSGeo Video Recordings ==
 
== DOI for OSGeo Video Recordings ==

Revision as of 06:29, 27 March 2023

Digital Object Identifiers (DOI)

Scope

  • This wiki page summarises relevant facts about DOI and related persistent Identifiers (PID) for the OSGeo communities.
  • A DOI is a persistent identifier (PID).
  • More infomation about PID for OSGeo is available here in the wiki

Useful background information

HowTo information about ORCID (Open Researcher and Contributor ID -> a PID for people)

Howto information for GitHub Repo maintainers (source Zenodo FAQ)

My organizational repository does not show up on the GitHub list

"In order to see and archive your organizational repositories on Zenodo you will need to have "Admin" permissions on said repository, either as an Admin of the organization or an Admin of one of your organization's repositories. Additionally, please make sure that the OAuth application on GitHub is granting permissions not only to your personal repositories but also to your organizational ones - to verify that go to your GitHub OAuth settings in your profile, and click on the Zenodo application to see more details. Make sure that Zenodo is given access (green tick) to your organization under "Organization access".

After that, navigate to your Zenodo GitHub settings page and click the "Sync now" button at the top."

I made a GitHub release, but it does not show up on Zenodo.

"Make sure the repository was enabled before the release was made, otherwise feel free to contact ZENODO."

Is it possible to archive a GitHub repository, before it was enabled on Zenodo?

"Only the repositories which were enabled before a release was made will be archived automatically. If you want to archive some of your old releases, you can always download a release ZIP from GitHub and upload it to Zenodo using our web interface as a regular upload."

How to change the default metadata for my GitHub releases?

"You can include metadata in a .zenodo.json file at the root of your GitHub repository. This file's contents should be in line with the Zenodo deposit metadata schema and will be used to update the metadata from future GitHub releases. For more information on how to create a .zenodo.json file, you can have a look at our GitHub integration documenation."

Do you support other software metadata files, like CITATION.cff or codemeta.json?

"Part of our plans and ongoing work is to take into account or improve our integration of other software metadata schemas such as the Citation File Format (CFF) and CodeMeta. We are working closely with our users and scholarly software and citation communities to figure out exactly when, in what form, and how all these different metadata schemas and their files will be integrated into Zenodo."

How does a CITATION.cff file affect the metadata of my GitHub release?

"When we find a CITATION.cff file in your GitHub repository's root folder, we make a best-effort attempt at parsing Zenodo-compatible metadata from it. For backwards-compatibility, if you have a .zenodo.json file in the repository, only the .zenodo.json's metadata will be taken into account. Of course, any existing valid CITATION.cff file will still be used to display the citation box on the GitHub repository page, but will not affect in any way the metadata we extract for your published release Zenodo record."

Usage examples for people writing articles

DOI

How to include a DOI-based reference to a LaTEX/Overleaf document.

BEWARE: As of now (20230327) it remains to be confirmed that DOI-tags in citations work without the https://doi.org-header. This might (just) reuslt in human readable information, but not machine-readable.

Publication DOI

@article{Chen_2003_Giants, title={On the Shoulders of Giants}, url={\url{https://doi.org/10.1007/978-1-4471-0051-5_5}}, DOI={10.1007/978-1-4471-0051-5_5}, journal={Mapping Scientific Frontiers: The Quest for Knowledge Visualization}, publisher={Springer London}, author={Chen, Chaomei}, year={2003}, pages={135–166} }

Video DOI

@article{Inman_1987, title={GRASS}, url={https://av.tib.eu/media/12963}, DOI={10.5446/12963}, abstractNote={Video presentation explaining the features and capabilities of this computer-based mapping system.}, publisher={Moving Pictures, US Army Construction Engineering Research Laboratory}, author={Inman, Roger J.}, year={1987}, language={en} }

Software Concept DOI (a reference to a software project as a whole)

@article{GRASS_CONCEPT_DOI, title={OSGeo/grass: GRASS GIS 8.2.0}, url={https://zenodo.org/record/5176030}, DOI={10.5281/ZENODO.5176030}, abstractNote={ .. CONTENT OMMITTED FOR BREVITY ..}, year={2022}, month={Jun} }

Software Version DOI (a reference to a particular software release)

@article{QGIS_Contributors_2022, title={QGIS}, url={https://doi.org/10.5281/zenodo.5869837}, DOI={10.5281/ZENODO.5869837}, publisher={Zenodo}, author={QGIS Contributors}, year={2022}, month={Jan} }

ORCID

How to include ORCIDs to a LaTEX/Overleaf document: Include these packages: \usepackage{orcidlink} \usepackage[hidelinks]{hyperref}


\author{ Peter Löwe\,\orcidlink{0000-0003-2257-0517}~\textsuperscript{1}\thanks{Corresponding author}, Markus Neteler\,\orcidlink{0000-0003-1916-1966}~\textsuperscript{2} } (Source: OSGEO, PERSISTENT IDENTIFIERS AND THE SHAPE OF THINGS TO COME)


ROR

TBD: How to include a PID for an institution (like OSGeo) from the Research Organisation Registry (ROR) ?

Added-value services based on DOI


DOI availabe for OSGeo Projects

OSGeo Project DOI First minted Citation example Integration Status
actinia https://doi.org/10.5281/zenodo.5879231 2022 Springer Handbook of Geographic Information (2022) automated
GDAL https://doi.org/10.5281/zenodo.5884351 2022 Nature: Scientific data (2023) automated
Geopaparazzi https://doi.org/10.5281/ZENODO.5881915 2022 Springer Handbook of Geographic Information (2022) status
GeoServer https://doi.org/10.5281/zenodo.5854561 2022 Springer Handbook of Geographic Information (2022) status
GeoTools https://doi.org/10.5281/zenodo.5854653 2022 Springer Handbook of Geographic Information (2022) status
GMT https://doi.org/10.5281/zenodo.3407865 2019 Springer Handbook of Geographic Information (2022) status
GRASS GIS https://doi.org/10.5281/zenodo.5176030 2021 Springer Handbook of Geographic Information (2022) automated
gvSIG https://doi.org/10.5281/zenodo.5849091 2022 Springer Handbook of Geographic Information (2022) manual upload
Hortonmachine https://doi.org/10.5281/ZENODO.5881778 2022 Springer Handbook of Geographic Information (2022) tbd
Mapbender https://doi.org/10.5281/zenodo.5887014 2022 tbd tbd
MapServer https://doi.org/10.5281/zenodo.5842012 2021 Springer Handbook of Geographic Information (2022) tbd
MOSS https://doi.org/10.5281/zenodo.5140318 2022 Springer Handbook of Geographic Information (2022) automated
OSGeoLive https://doi.org/10.5281/zenodo.5884641 2022 Springer Handbook of Geographic Information (2022) tbd
OSGeoLive Documentation https://doi.org/10.5281/zenodo.5884859 2022 Springer Handbook of Geographic Information (2022) tbd
PostGIS https://doi.org/10.5281/zenodo.5879631 2021 Springer Handbook of Geographic Information (2022) manual upload
PROJ https://doi.org/10.5281/zenodo.5884394 2022 MDPI: Remote sensing (2022) automated
QGIS https://doi.org/10.5281/zenodo.5869837 2022 Springer Handbook of Geographic Information (2022) manual upload
rasdaman https://doi.org/10.5281/zenodo.1040170 2017 Springer Handbook of Geographic Information (2022) manual upload
SMASH https://doi.org/10.5281/zenodo.5882070 2022 Springer Handbook of Geographic Information (2022) tbd
OSGeo projects with DOI 19


<Add your project DOI here, while maintaining alphabetical order>

Projects considering a DOI

  1. degree
  2. (GeoPython: pycsw)
  3. (NASA World Wind)


<Add your project here>

DOI for datasets related to OSGeo

This is an incomplete overview over geospatial data sources which can be referenced by DOI. Many more datasets are available in Open Access repositories such as Zenodo

GRASS GIS

  1. New Orleans Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3359642
  2. Hilltop Arboretum Landform Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3749397
  3. Sichuan Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3359645
  4. The Hills of Governor's Island Dataset for GRASS GIS https://doi.org/10.5281/zenodo.5248688
  5. Louisiana Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3359620
  6. Natural Earth Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3968936
  7. Global Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3359632
  8. Governor's Island Dataset for GRASS GIS https://doi.org/10.5281/zenodo.5248419

(add datasets here)

QGIS

  1. Governor's Island Dataset for QGIS https://doi.org/10.5281/zenodo.5701115
  2. Louisiana Dataset for GRASS GIS https://doi.org/10.5281/zenodo.3359620

(add datasets here)

DOI for OSGeo Video Recordings