Harvard Dataverse

dataverse.harvard.edu · 2 records in Storage · JSON

Records 2

★ qualifiesHarvard Dataverse Repository - per-collection quota
Storagefree tieridentity emailno cardlimit per-object-capevidence reportedstale on 2026-11-05
caveatHarvard Dataverse
Storagefree tieridentity institution?card?limit per-object-capevidence documentedstale on 2026-11-21

Harvard Dataverse Repository - per-collection quota

Storage

dataverse.harvard.edu/Academicstorage/harvard-dataverse-repository-per-collection-quotaJSON compare report an error

Free allowance: 1 TB per Dataverse Collection allocation (2.5 TB for Harvard affiliates).
Verdict: ★ qualifiesusable as stated; the read path was probed
Cost: free tier
Identity: emailno card, no phone
Binding limit: per-object-capPer-file 2.5 GB
Evidence: reported7 sources; a third party said so
Freshness: stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05

Free tier	1 TB per Dataverse Collection allocation (2.5 TB for Harvard affiliates). Per-file 2.5 GB through UI/API; larger via the S3 direct-upload path. The 1 TB is enforced as a collection allocation, not a per-person cap: GET /api/dataverses/<alias>/storage/quota?showInherited=true returns {"Total quota allocation for this collection": 1099511627776} for ordinary collections, and one live collection returns 2748779069440 (2.5 TB). unit TB; metered on stored-bytes
Price	none stated
Limits	write-gated Review' spam screen before publication source per-object-cap (binding) Per-file 2.5 GB source write-once: publishing is irreversible, no delete without support intervention, no embargo; 'Submit for Review' spam screen before publication; per-file 2.5 GB in the browser path; 1,000 files/dataset is the observed effectiveDatasetFileCountLimit; S3 direct upload is admin-enabled per install and is the only route past the 2.5 GB file cap.
Identity	email email
Egress	Free, anonymous, no login: GET /api/access/datafile/<id> returns 303 to a signed dvn-cloud-iqss S3 URL (X-Amz-Expires=3600), which serves 200 with Content-Length and honours Range (206 + Content-Range).
Per-object cap	Per-file 2.5 GB (2500000000 bytes)
Retention	\| write-once: publishing is irreversible, no delete without support intervention, no embargo; 'Submit for Review' spam screen before publication; per-file 2.5 GB in the browser path; 1,000 files/dataset is the observed effectiveDatasetFileCountLimit; S3 direct upload is admin-enabled per install and is the only route past the 2.5 GB file cap.
Interface	s3, rest, rclone, cli rest
Tooling	REST native API (create dataset, add files, direct S3 upload), plus the official Python/CLI clients. dataset count 306,027 live. rclone has no native backend but the S3 direct-upload path accepts any S3 client.
Composes with	#207 comment 2024-07-24: 'Anyone can create collections in Harvard Dataverse now, as of sometime in June 2024'. N collections = N x 1 TiB allocations. Sibling collections can also be nested, so a 'Dataverse Collection' tree is the natural shard key.
Reliability	Anonymous read is a 1-hour signed S3 redirect, so re-resolve per request; quota API is rate-limited and starts returning 403 after a short burst of collection probes.
Parsed numbers	has-free-tier 1 per-object-cap 2.5 GB

Evidence 7

date	source	what it proved
2026-10-21	support.dataverse.harvard.edu/researchers	'All researchers from any discipline, both inside and out of the Harvard University community, can deposit files of up to 2.5GB, and store up to 1TB of data on the Harvard Dataverse Repository.'
2026-10-21	neurips.cc/Conferences/2025/DataHostingGuidelines	hosting restriction stated as '1TB per dataset (2.5GB per file) Any file types'
2026-10-21	dataverse.harvard.edu/api/dataverses/SEE_Precursors/storage/	probe returned 1099511627776 bytes
2026-10-21	dataverse.harvard.edu/api/dataverses/kgwas/storage/quota?sho	probe returned 2748779069440 bytes (2.5 TB), proving allocations are set per collection and can exceed 1 TB
2026-10-21	dataverse.harvard.edu/api/access/datafile/13913528	303 then 200, Content-Length 16393, file written and SHA-256 fed450c5dfa423d6a51168611bbb9f4179e862a9c831ee41c37b23b128cc24fa (16,393 bytes, exact)
2026-10-21	dataverse.harvard.edu/api/access/datafile/13913528	with Range: bytes=0-1048575 - HTTP 206, Content-Range: bytes 0-16392/16393
2026-10-21	github.com/IQSS/dataverse.harvard.edu/issues/199	and #207 - collection creation was disabled for :authenticated-users in Nov 2022, reopened June 2024

Unknown values 2

per object cap notes: the field may be stated in a source that was not read
retention notes: the field may be stated in a source that was not read

Harvard Dataverse

Storage

dataverse.harvard.eduAcademicstorage/harvard-dataverseJSON compare report an error

Free allowance: 2.5 GB per file; 1 TB per Dataverse Collection for non-Harvard researchers (2.5 TB for Harvard affiliates).
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: institution?placeholder, not evidence; card unknown, phone unknown
Binding limit: per-object-cap2.5 GB per file
Evidence: documented5 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21

Free tier	2.5 GB per file; 1 TB per Dataverse Collection for non-Harvard researchers (2.5 TB for Harvard affiliates). The 1 TB is real and stated by Harvard, but it is a service/support threshold, not a hard enforced cap — see limits. unit TB; metered on unstated
Price	none stated
Limits	per-object-cap (binding) 2.5 GB per file source write-gated Review' spam-check gate, not peer review source write-gated curator rejecting a deposit at the review gate, and the storage-quota feature is flagge source Per-file 2.5 GB through the Harvard UI/API; larger files require the S3 direct-upload path, which Harvard has enabled (downloads already redirect to S3, so upload-redirect is configured). Dataset file-count cap observed live: effectiveDatasetFileCountLimit=1000 (12 used on the sampled dataset). No enforced collection quota: GET /api/dataverses/harvard/storage/quota?showInherited=true -> {"message":"No quota defined for this collection"}. Publishing is a 'Submit for Review' spam-check gate, not peer review.
Identity	institution (inferred, not read) not published
Egress	Free and unmetered. Public file access returns 303 -> a presigned S3 URL (dvn-cloud-iqss.s3.amazonaws.com) valid 3600s; S3 honours Range requests. No egress pricing exists anywhere in the product. Probe: GET /api/access/datafile/11685194 -L -H 'Range: bytes=0-1023' -> 303 then HTTP 206, Content-Range: bytes 0-1023/21269528, Server: AmazonS3.
Per-object cap	2.5 GB per file (2500000000 bytes)
Retention	not stated
Interface	s3, rest, rclone rest
Tooling	Native REST API v6.10.1 (live: GET /api/info/version -> {"version":"6.10.1"}); SWORD v2 deposit; OAI-PMH harvest; S3 direct-upload API for files >2.5 GB (docs: 'This option can handle files >300GB'). Python client pyDataverse; R package dataverse. No rclone backend, but a REST loop is trivial (~15 lines) and the platform is a well-documented Invenio-free Java stack.
Composes with	Unlimited Dataverse Collections per account (Harvard: 9,755 collections / 306,011 datasets exist, anyone may create one). x 1 TB per collection. 20 collections = 20 TB in one account; 20 accounts = 400 TB. Also multiplies per dataset rather than per collection if the 1 TB is read as a guidance number, since no per-dataset quota is enforced on the root collection.
Reliability	Mature, 15+ year old service with DOI permanence and S3-backed bytes; the only soft failure mode is a curator rejecting a deposit at the review gate, and the storage-quota feature is flagged 'new and still experimental' upstream.
Evidence note	documented The quota endpoint answers were re-read. The record keeps `reported` because the per-file cap and the identity field were not measured. Was reported; now documented.
Parsed numbers	has-free-tier 1 per-object-cap 2.5 GB

Evidence 5

date	source	what it proved
2026-10-21	support.dataverse.harvard.edu/researchers	'can deposit files of up to 2.5GB, and store up to 1TB of data on the Harvard Dataverse Repository'
2026-10-21	support.dataverse.harvard.edu/sites/g/files/omnuum821/files/	(updated Dec 3 2024) — 'free support for research data collections up to 1.0TB for non-Harvard researchers and groups and 2.5TB for Harvard affiliates'; paid Large Data Services only above 2.5TB
2026-10-21	source not published	probe: GET /api/dataverses/harvard/storage/quota?showInherited=true -> 'No quota defined for this collection'; GET /api/access/datafile/11685194 -> 303 to presigned S3 -> 206 Partial…
2026-10-22	dataverse.harvard.edu/	the instance answers.
2026-10-22	probe: `https://dataverse.harvard.edu/api/dataverses/harvard/storage/quota?showInherited=true`	GET 2026-10-22: harvard 200/73 B 'No quota defined for this collection'; SEE_Precursors 200/104 B 'Total quota allocation for this collection: 1,099,511,627,776 bytes'; kgwas 200/104 B 2,748,779,069,440 bytes

More fields 2

verified	`[{"url": "https://dataverse.harvard.edu/","date": "2026-10-22","via": "none","http_status": 0,"bytes": 0,"sha256": null,"pattern_found": false,"what_changed": "not read","capture": null}]`
unconfirmed	`[{"url": "https://dataverse.harvard.edu/","status": 0,"bytes": 0,"why": "not read"}]`

Unknown values 3

per object cap notes: the field may be stated in a source that was not read
retention notes: the field may be stated in a source that was not read
retention stated: the field may be stated in a source that was not read