Repository navigation
Preprint DOI bibtex record (and DOI) lack information about corresponding PrePrint archive @ OSF #11755
Description
We published a fresh preprint
but DOI record for it, if exported to BibTeX lacks any information about which arxiv it comes from
❯ curl --silent -L -d "" --header "Accept: application/x-bibtex; charset=utf-8" https://doi.org/10.31222/osf.io/f3h82_v1 | bibtool
@Article{ macdonald_2026,
title = {STAMPED principles for reproducible research objects},
url = {http://dx.doi.org/10.31222/osf.io/f3h82_v1},
doi = {10.31222/osf.io/f3h82_v1},
publisher = {Center for Open Science},
author = {Macdonald, Austin and Baker, Cody and To, Isaac and
Halchenko, Yaroslav O},
year = {2026},
month = may
}that information is present in some other fields, as e.g. if I request csl+json:
❯ curl --silent -L -d "" --header "Accept: application/vnd.citationstyles.csl+json; charset=utf-8" https://doi.org/10.31222/osf.io/f3h82_v1 | jq . | grep MetaArXiv
"group-title": "MetaArXiv",full record
{
"indexed": {
"date-parts": [
[
2026,
5,
26
]
],
"date-time": "2026-05-26T22:02:39Z",
"timestamp": 1779832959327,
"version": "3.53.1"
},
"posted": {
"date-parts": [
[
2026,
5,
26
]
]
},
"group-title": "MetaArXiv",
"reference-count": 0,
"publisher": "Center for Open Science",
"license": [
{
"start": {
"date-parts": [
[
2026,
5,
26
]
],
"date-time": "2026-05-26T00:00:00Z",
"timestamp": 1779753600000
},
"content-version": "unspecified",
"delay-in-days": 0,
"URL": "https://creativecommons.org/licenses/by/4.0/legalcode"
}
],
"content-domain": {
"domain": [],
"crossmark-restriction": false
},
"abstract": "<p>Scientific claims increasingly rely upon the interplay of code, data, and computational environments. Yet the record of how they are used together is often incomplete, scattered, or lost. This undermines rigor, reproducibility, reusability, and efficiency. Previous approaches have improved the governance of digital objects but do not specify how research objects ought to be structured and managed so they can be re-executed and extended. The community is missing a shared vocabulary for this operational layer. Building on recurrent practices and convergent patterns across disciplines, we formalize seven principles: Self-containment, Tracking, Actionability, Modularity, Portability, Ephemerality, and Distributability (STAMPED). Together they give researchers guidelines for building and assessing research objects that others can trust, rerun, and build upon. We frame each principle as a spectrum so that adoption is incremental and starts from existing practice. We support each principle with normative requirements, an interactive checklist, and a map of enabling tools. As conventions mature, tooling improves, and AI agents become increasingly involved in research workflows, the goals of rigor, reproducibility, reusability, and efficiency are becoming more attainable. STAMPED gives researchers, collaborators, reviewers, and agents a common language, concrete goals, and an aligned direction for making computational research more durable.https://github.com/stamped-principles/stamped-paper/</p>",
"DOI": "10.31222/osf.io/f3h82_v1",
"type": "posted-content",
"created": {
"date-parts": [
[
2026,
5,
26
]
],
"date-time": "2026-05-26T21:14:42Z",
"timestamp": 1779830082000
},
"source": "Crossref",
"is-referenced-by-count": 0,
"title": "STAMPED principles for reproducible research objects",
"prefix": "10.31222",
"author": [
{
"given": "Austin",
"family": "Macdonald",
"sequence": "first",
"affiliation": [],
"role": [
{
"vocabulary": "crossref",
"role": "author"
}
]
},
{
"given": "Cody",
"family": "Baker",
"sequence": "additional",
"affiliation": [],
"role": [
{
"vocabulary": "crossref",
"role": "author"
}
]
},
{
"given": "Isaac",
"family": "To",
"sequence": "additional",
"affiliation": [],
"role": [
{
"vocabulary": "crossref",
"role": "author"
}
]
},
{
"ORCID": "https://orcid.org/0000-0003-3456-2493",
"authenticated-orcid": true,
"given": "Yaroslav O",
"family": "Halchenko",
"sequence": "additional",
"affiliation": [],
"role": [
{
"vocabulary": "crossref",
"role": "author"
}
]
}
],
"member": "15934",
"container-title": [],
"original-title": [],
"deposited": {
"date-parts": [
[
2026,
5,
26
]
],
"date-time": "2026-05-26T21:14:42Z",
"timestamp": 1779830082000
},
"score": 1,
"resource": {
"primary": {
"URL": "https://osf.io/f3h82_v1"
}
},
"subtitle": [],
"short-title": [],
"issued": {
"date-parts": [
[
2026,
5,
26
]
]
},
"references-count": 0,
"URL": "http://dx.doi.org/10.31222/osf.io/f3h82_v1",
"relation": {},
"subject": [],
"published": {
"date-parts": [
[
2026,
5,
26
]
]
},
"subtype": "preprint"
}
now -- compare to the bibtex etc from e.g. arxiv -- publisher stays arxiv
❯ curl --silent -L -d "" --header "Accept: application/vnd.citationstyles.csl+json; charset=utf-8" https://doi.org/10.48550/arXiv.2401.00077 | jq . | grep -i arxiv
"id": "https://doi.org/10.48550/arxiv.2401.00077",
"DOI": "10.48550/ARXIV.2401.00077",
"publisher": "arXiv",
"URL": "https://arxiv.org/abs/2401.00077",
❯ curl --silent -L -d "" --header "Accept: application/x-bibtex; charset=utf-8" https://doi.org/10.48550/arXiv.2401.00077 | grep arXiv
publisher = {arXiv},
Since you are in full control over those entries AFAIK, I think what worth doing is
- at least making publisher to include the name of the preprint arxive, e.g. "MetaArXiv @ Center for Open Science" or alike
- reflect in DOI the arxive as well, e.g. could be http://dx.doi.org/10.31222/osf.io/MetaArXiv_f3h82_v1 or alike (I think could even be more levels http://dx.doi.org/10.31222/osf.io/MetaArXiv/f3h82_v1)
Activity