Manually Issue Zenodo DOI for Repo #106652
Replies: 2 comments
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Yes, as I filled out the package submission form I understood that I can just upload a new package and edit the metadata manually. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have a public repo within my organization's GitHub and would like to have a DOIs (concept and version) issued via Zenodo. I think that my org will not allow the required Zenodo access permissions to do this automatically. Are there other options? Would I have to instead upload my code and each version to Zenodo to do this? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions