GitHub-Zenodo linkage - Revision history

Neteler: add Zenodo DOI

2024-02-05T08:45:18Z

add Zenodo DOI

@@ Line 74: / Line 74: @@
 == Necessary steps to set up GitHub-Zenodo integration for GRASS GIS  (according to https://guides.github.com/activities/citable-code/)==
 # DONE {{done}}: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )
 # Log into [https://www.zenodo.org/ Zenodo account] (Login button) using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).
@@ Line 96: / Line 99: @@
 * If the GRASS or OSGeo communities should decide in the future to become DOI-minting entities (by signing a contract with DataCite), it is feasible to link already existing Zenodo-DOI for the GRASS GIS releases to "new" OSGeo (or GRASS GIS) DOI. From the DOI-perspectice, there is no "vendor lock-in" by using the Zenodo archive.
 * Develop best practices how to tie independent GRASS-add-on modules which are already archived in Zenodo independently into the GRASS GIS codebase Zenodo archive.

Neteler: micro-cosmetics

2019-05-19T13:22:01Z

micro-cosmetics

← Older revision		Revision as of 13:22, 19 May 2019
Line 74:		Line 74:

	== Necessary steps to set up GitHub-Zenodo integration for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==		== Necessary steps to set up GitHub-Zenodo integration for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==
	# DONE: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )		# DONE {{done}}: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )
	# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).		# Log into [https://www.zenodo.org/ Zenodo account] (Login button) using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).
	# Zenodo will redirect you back to GitHub to ask for your permission to share your email address ('''zenodo-grass-legacy@osgeo.org''') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to the GRASS project (which is considered an ''organization'') on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.		# Zenodo will redirect you back to GitHub to ask for your permission to share your email address ('''zenodo-grass-legacy@osgeo.org''') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to the GRASS project (which is considered an ''organization'') on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.
	# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.		# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.

⚠️Peter.loewe at 09:14, 19 May 2019

2019-05-19T09:14:55Z

← Older revision		Revision as of 09:14, 19 May 2019
Line 76:		Line 76:
	# DONE: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )		# DONE: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )
	# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).		# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).
	# Zenodo will redirect you back to GitHub to ask for your permission to share your email address (''~~zenodo_grass~~@osgeo.org ?'') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to an organization ~~(OSGeo~~) on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.		# Zenodo will redirect you back to GitHub to ask for your permission to share your email address ('''zenodo-grass-legacy@osgeo.org''') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to the GRASS project (which is considered an ''organization'') on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.
	# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.		# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.
	#Check repository settings: By enabling archiving in Zenodo, you have set up a new webhook on your repository. Click the '''settings tab''' on your repository, and then '''click ‘Webhooks’ in the left-hand menu'''.		#Check repository settings: By enabling archiving in Zenodo, you have set up a new webhook on your repository. Click the '''settings tab''' on your repository, and then '''click ‘Webhooks’ in the left-hand menu'''.

⚠️Peter.loewe: added function email zenodo-grass-legacy

2019-05-19T09:13:09Z

added function email zenodo-grass-legacy

← Older revision		Revision as of 09:13, 19 May 2019
Line 74:		Line 74:

	== Necessary steps to set up GitHub-Zenodo integration for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==		== Necessary steps to set up GitHub-Zenodo integration for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==
	# Create a function address (email) for the Zenodo account (''~~zenodo_grass~~@osgeo.org ?'')		# DONE: Create a function address (email) for the Zenodo account ('''zenodo-grass-legacy@osgeo.org''': forwards to Markus Neteler and Peter Löwe )
	# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).		# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).
	# Zenodo will redirect you back to GitHub to ask for your permission to share your email address (''zenodo_grass@osgeo.org ?'') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to an organization (OSGeo) on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.		# Zenodo will redirect you back to GitHub to ask for your permission to share your email address (''zenodo_grass@osgeo.org ?'') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to an organization (OSGeo) on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.

⚠️Peter.loewe at 17:14, 18 May 2019

2019-05-18T17:14:09Z

← Older revision		Revision as of 17:14, 18 May 2019
Line 76:		Line 76:
	# Create a function address (email) for the Zenodo account (''zenodo_grass@osgeo.org ?'')		# Create a function address (email) for the Zenodo account (''zenodo_grass@osgeo.org ?'')
	# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).		# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).
	# Zenodo will redirect you back to GitHub to ask for your permission to share your email address (''zenodo_grass@osgeo.org ?'') and the ability to configure webhooks on your repository. Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to an organization (OSGeo) on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.		# Zenodo will redirect you back to GitHub to ask for your permission to share your email address (''zenodo_grass@osgeo.org ?'') and the ability to configure webhooks on your repository (https://github.com/OSGeo/grass-legacy). Go ahead and click '''Authorize application''' to give Zenodo the permissions it needs. '''Important!''' We need to archive a repository that belongs to an organization (OSGeo) on GitHub: Make sure that the organization administrator has enabled '''third-party access''' to the Zenodo application.
	# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.		# At this point, you’ve authorized Zenodo to configure the repository webhooks needed to allow for archiving and DOI-issuing. To enable this functionality, simply click the '''On''' toggle button next to the GRASS repository.
	#Check repository settings: By enabling archiving in Zenodo, you have set up a new webhook on your repository. Click the '''settings tab''' on your repository, and then '''click ‘Webhooks’ in the left-hand menu'''.		#Check repository settings: By enabling archiving in Zenodo, you have set up a new webhook on your repository. Click the '''settings tab''' on your repository, and then '''click ‘Webhooks’ in the left-hand menu'''.

⚠️Peter.loewe at 17:03, 18 May 2019

2019-05-18T17:03:29Z

← Older revision		Revision as of 17:03, 18 May 2019
Line 88:		Line 88:

	== Loose ends and options for future extensions ==		== Loose ends and options for future extensions ==
			* Integration of ORCID IDs for human persons. The concepts and workflows of DOI and ORCID are interlinked. If a DOI is minted which includes one or many ORCIDs of the content owners, the DOI will be automagicaly referenced in the ORCID profiles of these persons.
	* Fine-grained citation of individual GRASS modules is provided by the GRASS GIS [https://grass.osgeo.org/grass76/manuals/addons/g.citation.html add-on module g.citation]. The citation strings are generated from the man page of the module(s) to be cited. Since GRASS GIS module man pages are currently only referenced by URL, not DOI. Therefore all citation strings are based on URLs. Once a best practice has been identified to cite a specific GRASS module based on the Zenodo DOI of the GRASS GIS release, g.citation should be extended to include this capability. This would allow DOI-based citation of individual GRASS modules. The issue of adequate authorship information (DOI-for-a-GRASS-release: GRASS Developer Team, GRASS module: A number [1..n] of persons) needs to be discussed in this context.		* Fine-grained citation of individual GRASS modules is provided by the GRASS GIS [https://grass.osgeo.org/grass76/manuals/addons/g.citation.html add-on module g.citation]. The citation strings are generated from the man page of the module(s) to be cited. Since GRASS GIS module man pages are currently only referenced by URL, not DOI. Therefore all citation strings are based on URLs. Once a best practice has been identified to cite a specific GRASS module based on the Zenodo DOI of the GRASS GIS release, g.citation should be extended to include this capability. This would allow DOI-based citation of individual GRASS modules. The issue of adequate authorship information (DOI-for-a-GRASS-release: GRASS Developer Team, GRASS module: A number [1..n] of persons) needs to be discussed in this context.
	* In scientific citations of the GRASS GIS project, the due credit is given to the "GRASS GIS developer team" as a group. The members of this group have changed over time as new members joined the group while others have departed. Also, persons take on different roles within the group which can also change over time. Some members chose to remain anonymous. There seems to be currently no mechanism to determine easily who were the members of the GRASS GIS developer team at a specific point in time and to link them to the DOI.		* In scientific citations of the GRASS GIS project, the due credit is given to the "GRASS GIS developer team" as a group. The members of this group have changed over time as new members joined the group while others have departed. Also, persons take on different roles within the group which can also change over time. Some members chose to remain anonymous. There seems to be currently no mechanism to determine easily who were the members of the GRASS GIS developer team at a specific point in time and to link them to the DOI.

⚠️Peter.loewe at 16:56, 18 May 2019

2019-05-18T16:56:12Z

← Older revision		Revision as of 16:56, 18 May 2019
Line 19:		Line 19:

	=== Scientific citation by DOI ===		=== Scientific citation by DOI ===
	Currently, the GRASS GIS web presence (only) recommends citation by ~~BibTEX~~[http://BibTeX BibTeX]		Currently, the GRASS GIS web presence (only) recommends citation by [http://BibTeX BibTeX]

	All content archived in Zenodo receives a persistent identifier, a [https://en.wikipedia.org/wiki/Digital_object_identifier DOI (Digital Object Identifier)]. DOI can be used through webbrowsers. Unlike an URL (-> 404 error) they can by design never expire. The technical infrastructure for this is provided by the [https://en.wikipedia.org/wiki/DataCite DataCite] non-profit organisation.		All content archived in Zenodo receives a persistent identifier, a [https://en.wikipedia.org/wiki/Digital_object_identifier DOI (Digital Object Identifier)]. DOI can be used through webbrowsers. Unlike an URL (-> 404 error) they can by design never expire. The technical infrastructure for this is provided by the [https://en.wikipedia.org/wiki/DataCite DataCite] non-profit organisation.

⚠️Peter.loewe at 16:55, 18 May 2019

2019-05-18T16:55:38Z

← Older revision		Revision as of 16:55, 18 May 2019
Line 6:		Line 6:
	== Introducing Zenodo ==		== Introducing Zenodo ==

	[https://www.zenodo.org/ Zenodo] is a general-purpose open-access repository. It is developed under the European [https://en.wikipedia.org/wiki/Framework_Programmes_for_Research_and_Technological_Development#OpenAIRE OpenAIRE] program (a network of Open Access repositories, archives and journals that support Open Access policies) and operated by [https://en.wikipedia.org/wiki/CERN CERN].		[https://www.zenodo.org/ Zenodo] is a general-purpose open-access repository for scientific information. It is developed under the European [https://en.wikipedia.org/wiki/Framework_Programmes_for_Research_and_Technological_Development#OpenAIRE OpenAIRE] program (a network of Open Access repositories, archives and journals that support Open Access policies) and operated by [https://en.wikipedia.org/wiki/CERN CERN].
	The services provided by Zenodo are based on an Open Source software stack. To users, including the GRASS GIS developer team, Zenodo provides long term archiving of digital content, including software.		The services provided by Zenodo are based on an Open Source software stack. To users, including the GRASS GIS developer team, Zenodo provides long term archiving of digital content, including software. Every user can uplaod up to 50Gb of digital scientific content.

	* [http://about.zenodo.org/policies/ Zenodo policies]		* [http://about.zenodo.org/policies/ Zenodo policies]

⚠️Peter.loewe at 16:54, 18 May 2019

2019-05-18T16:54:00Z

← Older revision		Revision as of 16:54, 18 May 2019
Line 9:		Line 9:
	The services provided by Zenodo are based on an Open Source software stack. To users, including the GRASS GIS developer team, Zenodo provides long term archiving of digital content, including software.		The services provided by Zenodo are based on an Open Source software stack. To users, including the GRASS GIS developer team, Zenodo provides long term archiving of digital content, including software.

			* [http://about.zenodo.org/policies/ Zenodo policies]
			* [http://about.zenodo.org/terms/ Zenodo terms of use]
	* [https://doi.org/10.5281/zenodo.1327310 Zenodo Documentation: Software Deposit - Guidance for Researchers]		* [https://doi.org/10.5281/zenodo.1327310 Zenodo Documentation: Software Deposit - Guidance for Researchers]
	* [https://blog.zenodo.org/2019/01/10/2019-01-10-asclepias/ Software citations now available in Zenodo]		* [https://blog.zenodo.org/2019/01/10/2019-01-10-asclepias/ Software citations now available in Zenodo]

⚠️Peter.loewe at 16:23, 18 May 2019

2019-05-18T16:23:06Z

← Older revision		Revision as of 16:23, 18 May 2019
Line 71:		Line 71:
	''If you want to use our GitHub integration, then you must move the source code to GitHub and activate the repository in Zenodo (see the GitHub guide). Afterwards, you make a new release in GitHub for each of your releases (see also the GitHub guide). You have to make the releases in the order you want them to appear in Zenodo. '''If you have tags push to GitHub, then you can upgrade a tag to a release in the GitHub interface''' ''.		''If you want to use our GitHub integration, then you must move the source code to GitHub and activate the repository in Zenodo (see the GitHub guide). Afterwards, you make a new release in GitHub for each of your releases (see also the GitHub guide). You have to make the releases in the order you want them to appear in Zenodo. '''If you have tags push to GitHub, then you can upgrade a tag to a release in the GitHub interface''' ''.

	== Necessary steps ~~for~~ GitHub-Zenodo ~~intergation~~ for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==		== Necessary steps to set up GitHub-Zenodo integration for GRASS GIS (according to https://guides.github.com/activities/citable-code/)==
	# Create a function address (email) for the Zenodo account (''zenodo_grass@osgeo.org ?'')		# Create a function address (email) for the Zenodo account (''zenodo_grass@osgeo.org ?'')
	# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).		# Log into Zenodo account using the credentials of the GitHub account of the GRASS Developer team ('''Log in''' button at the top right of the Zenodo page).