Skip to content

Zenodo discovery and project publishing

Find public research records, cite a specific version, and review the files you choose to share as a project snapshot.

Preview feature. This guide describes the Zenodo integration in development. It applies to builds with the Zenodo source and Publications widget. Successful authenticated sandbox upload and publication are not yet validated end to end.

Find research material

Ask Kosmo to search Zenodo for a dataset, software release, publication, poster, presentation, or other research material. Provide a specific record URL or numeric record ID when you want to inspect an existing deposit.

The agent returns public metadata, related identifiers, licenses, versions, and available file links. This search does not download or execute files, open private deposits, or publish anything. Check a record's explicit related identifiers before claiming that its data or software belongs to a paper. Repository hosting does not establish peer review.

Cite a specific version

Give Kosmo the Zenodo record URL or DOI and ask it to add the citation to your project bibliography. Citation retrieval resolves the record's actual DOI and fetches BibTeX. The bibliography writer then adds the retrieved entry to the managed bibliography.

Prefer the record URL or version DOI when citing a particular dataset or software release. Check the title, authors, version, and DOI. A concept DOI covering all versions is not an interchangeable identifier for one release. Adding a citation neither downloads the files nor creates a new deposit.

Include publications in Deep Research

Select Zenodo in the Deep Research source configuration before starting the run. It is opt-in. For an agent-proposed run, request Zenodo explicitly and review the sources before approving the start.

The academic provider includes publication records and merges them with the other selected sources. Use the dedicated Zenodo agent search for datasets and software. Restricted files and failed PDF downloads remain unavailable; choosing a source does not bypass access restrictions.

Prepare a selected project snapshot

  1. Open the project Dashboard.
  2. Choose Add widgets, then Publications.
  3. Choose Prepare publication.
  4. Select and preview the files or folders to share. Nothing is preselected.
  5. Enter the title, description, authors, optional ORCIDs, version, resource type, license, and destination.
  6. Review the exact file list and download the ZIP to inspect it.

The ZIP contains selected files under project/, a generated README, and a SHA-256 checksum manifest. Eligible bibliography and review exports, and research-session summaries, can be selected where offered. This is a selected snapshot, not an automatic export of every application record or the complete execution history.

Upload and publication controls

Sandbox is the default destination. Enter a token for the chosen destination in the widget, with deposit:write and deposit:actions. Never paste the token into chat. It stays in memory and must be re-entered after reopening the app. Production and sandbox credentials are separate.

Upload Zenodo draft and Publish snapshot are separate actions. Publication requires an additional confirmation. Confirm the returned Zenodo record and DOI before describing the snapshot as published. The widget retains draft metadata and publication history, offers status refresh, and provides a next-version flow for published records. The agent can explain the steps but has no unattended upload or publishing tool.

Limits and responsibilities

  • Selected uncompressed contents and the final ZIP are each limited to 40 MiB.
  • Only public/open records are offered, with CC-BY-4.0, CC0-1.0, MIT, or Apache-2.0. Private, restricted, and embargoed publishing are not offered.
  • Hidden paths, dependency folders, and credential-like filenames are excluded, apart from the explicitly offered exports. This is not a content secret scanner. Inspect what you select and check your right to publish it.
  • Save local editor changes first: desktop snapshots read local files from disk. Cloud text uses synchronized content.
  • Resuming rebuilds and verifies the snapshot. Changed files require a new review. This flow does not edit published files in place or stream larger projects.

Selected files and checksums do not certify reproducibility or scientific correctness. Include the methods, dependencies, instructions, licenses, and data needed to understand your work. Omitted files, private chats, internal reasoning, and logs are not reconstructed automatically.