为你的项目分配一个Doi,建立GitHub与Zenodo的连接

Knowledge_Is_Infinit

已于 2024-08-12 19:21:43 修改

阅读量2.8k

点赞数 24

文章标签：笔记

于 2024-08-12 13:44:09 首次发布

本文链接：https://blog.csdn.net/2301_79829900/article/details/141124375

版权

数字对象唯一标识符（DOI）是数据和项目代码的身份证，针对数字产品。

作用：为你的数据找一个存储库，数据存储库将会为你的数据生成一个数字对象唯一标识（DOI）.许多大学正在为研究人员提供研究数据和软件管理以及合规要求方面的支持，这些服务通常是通过图书馆提供的。图书馆员可以是研究数据管理支持的优秀来源，包括存储库选择，并且可以帮助您遵守资助者，出版商和大学的要求.世界上或者特别国家也提供了非盈利性的数据存储库。为小容量数据提供免费存储。常见的存储库有:Zenodo、Dryad或Figshare。Dryad对美国国家科学基金会资助的作者收取费用。

1、注意

（1）gituhub上的数据是公开的，zenodo只能访问公开的数据。

（2）如果您希望归档属于某个组织的存储库，则组织所有者可能需要批准Zenodo应用程序的访问权限。

（3）确保在您的存储库中包含许可，以便读者知道如何重用您的作品。

2、获取DOI步骤

（1）登录zenodo（login page）账号，用GitHub账号登录，Click Log in with GitHub.

（2）、后面按照页面点击操作即可成功完成登录。

Review the information about access permissions, then click Authorize zenodo.

（3）对于以后新建的仓库，zenodo会自动下发一个doi,而对于已经创建好的仓库，需要去获取doi，下面我将介绍如何为已创建的仓库获取doi。Navigate to the Zenodo GitHub page.然后按照下图（To the right of the name of the repository you want to archive, toggle the button to On）

（4）点击上图中的create a release,进入获取doi的教程，或者安装我的步骤 create a release

1) 进入自己的仓库中(点击头像，然后点击Your repositories)

2）点击仓库右边的release

3)，点击create a new release

4) 完善下图的细节，各个部分的问题描述如下（引自 Managing releases in a repository）

特别注意：********下图中Target中main是自己项目所在的分支，并不是所有人的都是main

To choose a tag for the release, select the Choose a tag dropdown menu.
- To use an existing tag, click the tag.
- To create a new tag, type a version number for your release, then click Create new tag.
If you created a new tag, select the Target dropdown menu, then click the branch that contains the project you want to release.
Optionally, above the description field, select the Previous tag dropdown menu, then click the tag that identifies the previous release.
In the "Release title" field, type a title for your release.
In the "Describe this release" field, type a description for your release. If you @mention anyone in the description, the published release will include a Contributors section with an avatar list of all the mentioned users. Alternatively, you can automatically generate your release notes by clicking Generate release notes.
Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
Optionally, to notify users that the release is not ready for production and may be unstable, select This is a pre-release.
Optionally, select Set as latest release. If you do not select this option, the latest release label will automatically be assigned based on semantic versioning.
Optionally, if GitHub Discussions is enabled for the repository, create a discussion for the release.
- Select Create a discussion for this release.
- Select the Category dropdown menu, then click a category for the release discussion.
If you're ready to publicize your release, click Publish release. To work on the release later, click Save draft. You can then view your published or draft releases in the releases feed for your repository. For more information, see "Viewing your repository's releases and tags."