Difference between revisions of "DOI"
(→DOI available for OSGeo Projects: Restructuring) |
m (→DOI available for OSGeo Projects: Restructuring: sublevels for each project) |
||
Line 102: | Line 102: | ||
== DOI available for OSGeo Projects == | == DOI available for OSGeo Projects == | ||
+ | === actinia === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 114: | Line 115: | ||
|} | |} | ||
+ | |||
+ | === eodash === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 126: | Line 129: | ||
|} | |} | ||
+ | |||
+ | === GDAL === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 138: | Line 143: | ||
|} | |} | ||
+ | |||
+ | === GeoNetwork === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 149: | Line 156: | ||
| automated | | automated | ||
|} | |} | ||
+ | |||
+ | |||
+ | === GeoMoose === | ||
{| | {| | ||
Line 161: | Line 171: | ||
| tbd | | tbd | ||
|} | |} | ||
+ | |||
+ | |||
+ | === Geopaparazzi === | ||
{| | {| | ||
Line 173: | Line 186: | ||
| tbd | | tbd | ||
|} | |} | ||
+ | |||
+ | === GEOS === | ||
{| | {| | ||
Line 186: | Line 201: | ||
|} | |} | ||
+ | |||
+ | === GeoServer === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 198: | Line 215: | ||
|} | |} | ||
+ | === GeoTools === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 210: | Line 228: | ||
|} | |} | ||
+ | === GMT === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 222: | Line 241: | ||
|} | |} | ||
+ | === GRASS GIS === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 234: | Line 254: | ||
|} | |} | ||
+ | === gvSIG === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 246: | Line 267: | ||
|} | |} | ||
+ | === Hortonmachine === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 258: | Line 280: | ||
|} | |} | ||
+ | === istSOS === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 270: | Line 293: | ||
|} | |} | ||
+ | |||
+ | === Leaflet === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 282: | Line 307: | ||
|} | |} | ||
+ | === Mapbender === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 294: | Line 320: | ||
|} | |} | ||
+ | === MapServer === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 306: | Line 333: | ||
|} | |} | ||
+ | === MovingPandas === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 318: | Line 346: | ||
|} | |} | ||
+ | === MOSS === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 330: | Line 359: | ||
|} | |} | ||
+ | === Orfeo Toolbox === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 342: | Line 372: | ||
|} | |} | ||
+ | === OSGeoLive === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 367: | Line 398: | ||
| } | | } | ||
+ | === PDAL === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 379: | Line 411: | ||
|} | |} | ||
+ | |||
+ | === pgRouting === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 391: | Line 425: | ||
|} | |} | ||
+ | === PostGIS === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 403: | Line 438: | ||
|} | |} | ||
+ | |||
+ | === PROJ === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 415: | Line 452: | ||
|} | |} | ||
+ | |||
+ | === pycsw === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 427: | Line 466: | ||
|} | |} | ||
+ | |||
+ | === pygeoapi === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 439: | Line 480: | ||
|} | |} | ||
+ | === QGIS === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 449: | Line 491: | ||
| 2022 | | 2022 | ||
| manual upload | | manual upload | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| [https://doi.org/10.5281/zenodo.14204331 QGIS] | | [https://doi.org/10.5281/zenodo.14204331 QGIS] | ||
Line 463: | Line 498: | ||
|} | |} | ||
+ | |||
+ | === rasdaman === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 475: | Line 512: | ||
|} | |} | ||
+ | |||
+ | === SMASH === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 487: | Line 526: | ||
|} | |} | ||
+ | === WRADLIB === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project | ||
Line 499: | Line 539: | ||
|} | |} | ||
+ | === ZOO === | ||
{| | {| | ||
! style="text-align:left;"| OSGeo Project | ! style="text-align:left;"| OSGeo Project |
Revision as of 05:32, 14 January 2025
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
- Introduction to DOI (NASA)
- DOI registration 101 @ UC Berkeley (wayback machine memento)
- Introduction to the Zenodo open access repository
- Zenodo FAQ
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."
Do you support versioning for already existing records?
"Yes. However, for uploads published before the 30th of May 2017, you have to first upgrade your record to support versioning. This is done by clicking the “Upgrade to versioned record” button on the record page.
IMPORTANT If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please contact us so we can link the records under one versioning scheme.
Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.
If you used the GitHub integration to archive your software on Zenodo, then we have already migrated and linked your records to support versioning."
Usage examples to cite OSGeo projects by DOI in scientific publications (both Open Access and closed access)
DOI
How to include a DOI-based reference to a LaTEX/Overleaf document.
BEWARE: As of now (2023-03-27) it remains to be confirmed that DOI-tags in citations work without the https://doi.org-header. This might (just) result 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} }
Added-value services based on DOI
Personal due credit from DOI via ORCID
ORCID (Open Researcher and Contributor ID) is a persistent identifier (PID) like DOI. It is used to identify a human person.
DOI and ORCID can be interlinked via the digital infrastructure services provided by the organisations DataCite and CrossRef.
If a OSGeo-related software DOI is minted in Zenodo, the DataCite infrastructure can automatically forward and register this information in the ORCID accounts of the code authors. For this to work, two requirements are needed:
- Code authors ORCIDs must be provided via the CITATION.cff file in the codebase.
- A code author with an ORCID must have added Zenodo as a trusted organisation in the ORCID account settings, as described here.
Once a scientific publication is published (journal article, book, book chapter, etc.) and has received a publication DOI via CrossRef, this information can also be automatically forwarded to registered in ORCID. This requires, that CrossRef is added to the list of accepted parties in the ORCID account settings.
DOI available for OSGeo Projects
actinia
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
actinia | https://doi.org/10.5281/zenodo.5879231 | 2022 | automated |
eodash
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
eodash | https://doi.org/10.5281/zenodo.6547058 | 2022 | tbd |
GDAL
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GDAL | https://doi.org/10.5281/zenodo.5884351 | 2022 | automated |
GeoNetwork
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GeoNetwork | https://doi.org/10.5281/zenodo.7924616 | 2024 | automated |
GeoMoose
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GeoMoose | https://doi.org/10.5281/zenodo.7976084 | 2023 | tbd |
Geopaparazzi
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
Geopaparazzi | https://doi.org/10.5281/ZENODO.5881915 | 2022 | tbd |
GEOS
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GEOS | https://doi.org/10.5281/zenodo.11396894 | 2023 | tbd |
GeoServer
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GeoServer | https://doi.org/10.5281/zenodo.5854561 | 2022 | automated |
GeoTools
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GeoTools | https://doi.org/10.5281/zenodo.5854653 | 2022 | tbd |
GMT
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GMT | https://doi.org/10.5281/zenodo.3407865 | 2019 | tbd |
GRASS GIS
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
GRASS GIS | https://doi.org/10.5281/zenodo.5176030 | 2021 | automated |
gvSIG
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
gvSIG | https://doi.org/10.5281/zenodo.5849091 | 2022 | manual upload |
Hortonmachine
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
Hortonmachine | https://doi.org/10.5281/ZENODO.5881778 | 2022 | tbd |
istSOS
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
istSOS | https://doi.org/10.5281/zenodo.5888498 | 2022 | manual |
Leaflet
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
Leaflet | https://doi.org/10.5281/zenodo.7335489 | 2022 | tbd |
Mapbender
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
Mapbender | https://doi.org/10.5281/zenodo.5887014 | 2022 | tbd |
MapServer
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
MapServer | https://doi.org/10.5281/zenodo.6994443 | 2021 | automated |
MovingPandas
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
MovingPandas | https://doi.org/10.5281/zenodo.3710950 | 2020 | tbd |
MOSS
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
MOSS | https://doi.org/10.5281/zenodo.5140318 | 2022 | automated |
Orfeo Toolbox
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
Orfeo Toolbox | https://doi.org/10.5281/zenodo.2250562 | 2018 | tbd |
OSGeoLive
OSGeo Project | DOI | First minted | Integration Status |
---|---|---|---|
OSGeoLive | https://doi.org/10.5281/zenodo.5884641 | 2022 | tbd |
OSGeo Project | DOI | First minted | Integration Status | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OSGeoLive Documentation | https://doi.org/10.5281/zenodo.5884859 | 2022 | tbd | }
PDAL
pgRouting
PostGIS
PROJ
pycsw
pygeoapi
QGIS
rasdaman
SMASH
WRADLIB
ZOO
<Add your project DOI here, while maintaining alphabetical order> Hint: to automate the Zenodo integration, connect to it to GitHub (see above). DOI-based Citations of OSGeo Projects in Scientific LiteratureThe following citation listings for OSGeo projects are curated both manually and using automated data-harvesting from CrossRef. The list is currently updated annually. This listing is not complete. The total number of scientific publications referencing OSGeo projects by their DOI is most likely much larger. Publications such as FOSS4G Proceedings in The International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences are currently not referenced by CrossRef and must be added manually. actinia(search for this DOI on Google Scholar)
GDAL(search for this DOI on Google Scholar)
Geopaparazzi
GeoServer
GeoTools
GMT
GRASS GIS(search for this DOI on Google Scholar)
gvSIG
Hortonmachine
MapServer
MOSS
OSGeoLive
OSGeoLive Documentation
´ PDAL
PostGIS
PROJ
QGIS
rasdaman
SMASH
Projects considering a DOI
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
(add datasets here) QGIS
(add datasets here) DOI for OSGeo Video Recordings
add your DOI badge to your project pages
See Example Mapbender
You badge looks like this (replace your DOI in the Link and svg name) <a href="https://doi.org/10.5281/zenodo.5887014"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.5887014.svg" alt="DOI"></a> DOI acknowledgement by Publishers and JournalsReferences in indexed scientific literature to research software, including the OSGeo software projects, can be counted as citations and due scientific credit for the persons developing and maintaining the research software). The emerging best practice for software references is reference by DOI. Such a DOI reference can either refer to the software project as a whole (concept DOI), or a particular release of the codebase (version DOI). Keeping track of DOI-based software citations can both be done manually or by automated analysis of metadata about the publication provided centrally by CrossRef or DataCite. The prerequisite for automated analysis and reporting (as in FAIR: machine-actionable and interoperable) is the provision of a full references list for the publication as a complete set of metadata to CrossRef. If only a limited subset of the reference list is provided to CrossRef, metadata-based automated analysis and reporting will return no result, meaning no information about the citation. In such a case, despite the best intentions by the publication authors by using DOI-based software citations in their publication, because of the lack of metadata, automated reporting will return no result and there will be no due credit by citation to the software project. This also affects the software developer team, as there will be no credit / recognition of their roles as (research-)software authors, because there is no automated transitive credit to their individual ORCID accounts will be triggered.
Currently it is difficult at best for propective authors to assess prior to a publication whether software-references by DOI will be indexed by CrossRef, resulting in FAIR credit. To mitigate this, incomplete lists are being compiled (below) of journals, for convenience of prospective authors, to assess wheter software-references will result in credit propagation to the software project and developer team.
For scientific authors, the difference between a publication in a green-, whitelist or greylist journal is wether DOI-based references to OSGeo software, -data or -video will be automagically attributed ("due scientific credit") to the respective OSGeo community / persons. For greylist journals, such attribution needs to be compiled manually. Publisher statements about software citation by DOI
Greenlist: Journals and Publications with confirmed CrossRef-listed software DOI references to OSGeo Projects
Whitelist: Journals and Publications with CrossRef-enabled workflows to acknowledging DOI-based software citations (not yet confirmed but should apply)
Greylist: Journals and Publications reporting DOI references to CrossRef
Related IdentifiersResearch Organisiation Registry (ROR): An ID for the OSGeo FoundationROR is a global, community-led registry of open persistent identifiers for research organizations. OSGeo RORThe OSGeo Foundation is a research organisation. The ROR ID for OSGeo is https://ror.org/00cjqbk89 Usage of RORMany scholarly communication systems are already using ROR, and many others are working on integrating ROR. Background Information (ROR Community) =ORCID (Open Researcher and Contributor ID) - a PID for people
Authentice an ORCID account with a GitHub„We’re excited to announce that GitHub is partnering with ORCID. You can now authenticate your ORCID account with your GitHub account, and display your ORCID iD on your public GitHub profile. ORCID provides a persistent unique digital identifier (an ORCID iD) that researchers own and control, and that distinguishes them from every other researcher." https://github.blog/changelog/2024-03-13-authenticate-orcid-id/ How to include ORCIDs to a LaTEX/Overleaf documentInclude 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) |