- Free allowance
- No dataset-size limit at all: 'Repozytorium akceptuje zbiory danych o dowolnej wielkości.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap5 GB per single file; 5 GB/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 | No dataset-size limit at all: 'Repozytorium akceptuje zbiory danych o dowolnej wielkości. Jedynym ograniczeniem jest limit wielkości pojedynczego pliku, wynoszący 5GB' (the repository accepts datasets of any size; the only limit is 5 GB per single file). A sibling UW deposit guide adds '20 GB for the sum of files transferred simultaneously'. Storage itself is unpriced: 'Korzystanie z repozytorium nie wiąże się z żadnymi opłatami' (using the repository involves no fees). unit GB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) 5 GB per single file source
- per-object-cap (binding) 5 GB/file source
Per-object-cap 5 GB/file and 20 GB per simultaneous transfer batch are the only hard numbers; there is NO per-dataset and NO per-account byte ceiling. 1,000 files per zip ingest (Dataverse default). Publication assigns a DOI and freezes that version — versions are immutable after publish, so this is write-once-per-version, not mutable working storage. Embargo up to 36 months. |
|---|
| Identity | institution (inferred, not read) not published |
|---|
| Egress | Free and unmetered. Public files are plain HTTP from repod.icm.edu.pl with no egress pricing anywhere in the product; downloads are the same Dataverse /api/access/datafile path used by Harvard. Probe: GET /api/access/datafile/39782 -> 200, 7,459 bytes returned, MD5 published per file for verification. |
|---|
| Per-object cap | 5 GB per single file (5000000000 bytes) |
|---|
| Retention | Publication assigns a DOI and freezes that version — versions are immutable after publish, so this is write-once-per-version, not mutable working storage |
|---|
| Interface | rest, rclone rest |
|---|
| Tooling | Native Dataverse 4.11 REST API, live and unauthenticated for reads: GET /api/info/version -> {"version":"1.3.2-05b9a3acf7fe552a849e874762b86d0605e47186"}; GET /api/search?q=*&type=dataset -> total_count 4545; type=file -> 65370 items. The repository's own policy page states uploads work 'zarowno przez graficzny interfejs ... jak i za pomocą interfejsu API' (both GUI and API). Standard Dataverse ingest: DVUploader (github.com/GlobalDataverseCommunityConsortium/dataverse-uploader), pyDataverse, SWORD v2. No rclone backend, but the REST loop is ~15 lines. |
|---|
| Composes with | Per-record cap is the unit, not per-account: unlimited datasets x unlimited size each, so 500 GB is 100 files of 5 GB inside one dataset — no account multiplication needed. Multiple datasets multiply further. One email/password account is enough; signup is self-service ('Sign up for an account to log in with your email or username and password'). |
|---|
| Reliability | Institutional (ICM UW, Polish national open-science infrastructure since 2020), CoreTrustSeal-lineage Dataverse with per-file MD5 published; the real friction is moderation-by-metadata-quality, not bytes, and published versions cannot be edited in place. |
|---|
| Evidence note | documented The conditional range behaviour was reproduced, both legs. Was documented; now documented. |
|---|
| Parsed numbers | - has-free-tier 1
- per-object-cap 5 GB
- per-object-cap 5 GB
|
|---|