HAL

hal.science · Storage · 1 record · JSON

HAL (Hyper Articles en Ligne, CCSD / CNRS) Storage

fails: quotainstitution?card?Rper-object-cap

hal.science · academic · storage/hal · JSON · compare

Free tier	200 MB maximum per file in the deposit UI, plus a 5 GB per-account FTP staging space that is provisional only: 'pour une durée provisoire pouvant aller jusqu'à 31 jours maximum'. No aggregate storage quota is published. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	200 MB maximum per file (200000000 bytes)
Retention	\| Very stable national infrastructure (CCSD/CNRS) with permanent URLs, but the per-file 200 MB cap and the bibliographic-record model make it useless for bulk blobs; the 5 GB FTP space decays in 31 days. (31 days)
Egress	Free public PDF/fulltext download, no metering; metadata is harvested by OpenAIRE, BASE, Google Scholar.
Identity	institution (placeholder) inferred from the category 'academic'; the source record states no identity cost, so this is a class assumption, not evidence
Limits	per-ip-shaping transfer is limited to 3 MB/file and 10 MB total source per-object-cap 3 MB/file source per-object-cap 200 MB cap source Per-object-cap 200 MB (soft, varies with traffic); FTP staging 5 GB / 31 days; the deposit must be a scholarly document with a document type, so raw data blobs are out of scope. arXiv transfer is limited to 3 MB/file and 10 MB total.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, ftp rest
Tooling	Deposit API + SWORD for programmatic submission (api.archives-ouvertes.fr/docs), FTP staging at ftp.ccsd.cnrs.fr with explicit TLS (FileZilla), OAI-PMH, and a TripleStore. This is a genuinely automatable write path.
Composes with	Unlimited deposits x 200 MB/file — 2,500 files for 500 GB, but each deposit is a bibliographic notice, so the multiplier is records not blobs. 5 GB FTP staging expires in 31 days.
Reliability	Very stable national infrastructure (CCSD/CNRS) with permanent URLs, but the per-file 200 MB cap and the bibliographic-record model make it useless for bulk blobs; the 5 GB FTP space decays in 31 days.
Notes	200 MB maximum per file in the deposit UI, plus a 5 GB per-account FTP staging space that is provisional only: 'pour une durée provisoire pouvant aller jusqu'à 31 jours maximum'. No aggregate storage quota is published.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-ip-shaping 3.0 MB `$.limits[1].value` limit:per-object-cap 3.0 MB `$.limits[2].value` limit:per-object-cap 200.0 MB

Evidence (3)

date	source	what it proved
2026-10-21	doc.hal.science/en/faq/	'La taille maximum d'un fichier est de 200Mo'; mentions the FTP staging space as the alternative route for larger sets
2026-10-21	doc.hal.science/en/gerer-ses-depots/espace-de-stockage-ftp/	'Chaque compte utilisateur dispose d'un espace de 5 Go sur le serveur FTP du CCSD... pour une durée provisoire pouvant aller jusqu'à 31 jours maximum'
2026-10-21	doc.hal.science/en/faq/	arXiv transfer capped at 3 MB per file / 10 MB total

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "200 MB maximum per file in the deposit UI, plus a 5 GB per-account FTP staging space that is provisional only: 'pour une durée provisoire pouvant aller jusqu'à 31 jours maximum'. No aggregate storage quota is published.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (5)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted