Curation policy
The TextRefs Zenodo Community preserves archival copies of official TextRefs outputs.
TextRefs is an open, persistent, machine-readable registry for canonical text references. The Zenodo community is used for long-term preservation, citation, and discovery of project-maintained releases. It is not a submission channel for proposed registry entries, corrections, mappings, documentation changes, or software contributions.
Scope
The community accepts only deposits created or approved by the TextRefs maintainers.
Accepted deposits are limited to:
-
automatic monthly TextRefs registry dumps;
-
regular releases from the official TextRefs GitHub repository;
-
release artifacts, metadata, documentation snapshots, or related files that belong to an official TextRefs release.
Monthly registry dumps follow the TextRefs versioning and data packaging rules and may include JSON Lines exports and a Frictionless Data Package descriptor.
Out of scope
The community does not accept direct submissions through Zenodo.
Please do not submit:
-
proposed new registry records;
-
corrections to existing records;
-
mapping proposals;
-
resolver-target updates;
-
documentation changes;
-
software patches;
-
derived datasets not produced by the TextRefs maintainers;
-
publications, presentations, or other materials that are not official TextRefs releases.
Out-of-scope submissions may be declined, removed from the community, or left outside the community without further review.
How to contribute
Contributions should be made through GitHub, not through Zenodo.
To report issues, suggest changes, or contribute data, documentation, or code, use the TextRefs contributing guide and the official GitHub repository.
Relevant contribution channels include:
-
GitHub Issues for bug reports, mapping inconsistencies, broken links, documentation gaps, and other problems;
-
GitHub Pull Requests for proposed code, content, or data changes;
-
GitHub Discussions for general questions and discussion.
Review and inclusion
Deposits are curated by the TextRefs maintainers. Inclusion in the Zenodo community means that the record is an official TextRefs archival deposit.
Zenodo curation does not replace the TextRefs GitHub review process. Registry, mapping, documentation, and software changes must be reviewed and merged through the project’s normal GitHub workflow before they can appear in an official release or monthly dump.
Rights and licences
Deposits follow the licences used by the TextRefs project:
-
registry data: CC0 1.0;
-
documentation and standard text: CC BY-SA 4.0;
-
code: AGPL-3.0-or-later.
Individual Zenodo records may include more specific licence metadata. Where record-level metadata differs from this general policy, the metadata of the individual Zenodo record applies to that archived deposit.
Contact
For questions about contributions, open a GitHub Discussion or issue.
For questions about TextRefs governance or contact details, see the TextRefs contact page.