NAKALA
nakala.fr · 2 records in Storage · JSON
Records 2
- caveatNAKALA (IR* Huma-Num, CNRS / French national HSS data repository)
Storagefree tieridentity institution?card?evidence reportedstale on 2026-11-05disagrees
- fails: identityNakala (Huma-Num, France) - no formal size limit, but a HumanID gate and a conversation with the team
Storagefree tieridentity institutionno cardevidence reportedstale on 2026-11-05disagrees
Sibling records disagree:
- verdict:
storage/nakalasays qualifies-with-caveat, storage/nakala-no-formal-size-limit-but-a-humanid-gate-and-a-con says fails-identity
- Free allowance
- Public deposits are explicitly uncapped: 'Il n'existe aucune limite pour les dépôts publics' (there is no limit for public deposits), and 'Un accès à vos données sans limite de volumétrie, ni de temps' (access to your data with no volume or time limit).
- 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
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Public deposits are explicitly uncapped: 'Il n'existe aucune limite pour les dépôts publics' (there is no limit for public deposits), and 'Un accès à vos données sans limite de volumétrie, ni de temps' (access to your data with no volume or time limit). The only quota is on PRIVATE staging: 10,000 private deposits or 100 GB equivalent. unit GB; metered on unstated |
|---|---|
| Price | none stated |
| Identity | institution (inferred, not read) not published |
| Egress | Free. Files are served from Huma-Num/IN2P3-hosted infrastructure in France with no metering and no egress charge; public deposits are downloadable by any visitor and IIIF image endpoints are exposed for tif/tiff/jpg/jpeg/jp2. |
| Per-object cap | not stated |
| Retention | Publication mints a DOI via DataCite and is irreversible — deletion requires a request to Huma-Num, so this is a permanent archive, not scratch space |
| Interface | rest, rclone rest |
| Tooling | Documented REST API split into search / datas / collections / groups / users / vocabularies, with a per-account API key ('Certaines opérations nécessitent ... sa clé d'API disponible dans son compte personnel'); swagger at api.nakala.fr/doc, separate test instance apitest.nakala.fr. Also OAI-PMH (api.nakala.fr/oai2?verb=Identify), a SPARQL triplestore, IIIF Image API, and a published notebook at gitlab.huma-num.fr/huma-num-public/notebook-api-nakala. No rclone backend. |
| Composes with | Unlimited public deposits per account, no volume cap per deposit — so the account is the only unit and it does not need multiplying for 500 GB. Groups feature shares deposit rights across a project team, so a lab can pour many researchers' output into one quota-free surface. |
| Reliability | CRITICAL liveness flag: nakala.fr and api.nakala.fr both returned HTTP 503 on 6 consecutive probes across ~25 minutes (site and API, direct and through the proxy), so the quota is docs-verified but the service was NOT live at probe time. Budget-stable (CNRS-funded national infrastructure) but treat availability as unconfirmed. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | documentation.huma-num.fr/nakala/ | 'Il n'existe aucune limite pour les dépôts publics' and 'Le nombre de dépôts privés par déposant est limité à 10 000 (ou l'équivalent de 100 Go)' |
| 2026-10-21 | documentation.huma-num.fr/nakala-API/ | REST API endpoint list, api.nakala.fr/doc, OAI-PMH, SPARQL, IIIF |
| 2026-10-21 | nakala.fr/ | probe: GET -> 503 six times; GET https://api.nakala.fr/oai2?verb=Identify -> 503 (service down at probe time) |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: 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
Sibling records disagree:
- verdict:
storage/nakalasays qualifies-with-caveat, storage/nakala-no-formal-size-limit-but-a-humanid-gate-and-a-con says fails-identity
- Free allowance
- 'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first.
- Verdict
- fails: identitythe identity required is not reachable without it
- Cost
- free tier
- Identity
- institutionno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first. Private pre-publication space is capped far lower (9,999 items or 100 GB), so the large-volume path is publish-as-you-go. unit objects; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
Account path is HumanID -> request Nakala access -> 'Discuss the scientific and technical project associated with the deposit with HumaNum's team'. Research data only, must be documented to a metadata schema, licence from a closed list, ORCID checked on authors. Published deposits cannot be deleted unilaterally. |
| Identity | institution institution |
| Egress | Free public HTTPS with a DOI per deposit; no egress metering published. |
| Per-object cap | 10 GB per file (10000000000 bytes) |
| Retention | not stated |
| Interface | rest rest |
| Tooling | Nakala REST API plus nakalot (multipart batch uploader driven by a CSV/XLS manifest); OAI-PMH. |
| Composes with | Per deposit, unlimited deposits - but the gate is identity, not bytes. |
| Reliability | MESR-funded national infrastructure, data preserved at CINES after audit; ~100 TB of storage on the ISIDORE/Nakala stack. French research context in practice. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | documentation.huma-num.fr/nakala-faq/ | 'Il n'y a pas formellement de limitation pour la taille des donnees deposees. Cependant... superieur a 10 GOs par fichier, il est necessaire de prendre contact avec l'equipe NAKALA' |
| 2026-10-21 | documentation.huma-num.fr/en/nakala-workflow-en/ | 'Request a HumanID login'; 'Discuss the scientific and technical project... with HumaNum's team'; mandatory pre-curation for level 2/3 |
| 2026-10-21 | www.orient-mediterranee.com/wp-content/uploads/2024/01/2023_ | 'Espace de depot limite a 9 999 donnees ou a 100 Go' for the private status |
More fields 1
| dead end | {"failure_class": "quota","why": "'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first. Private pre-publication space is capped far lower (9,999 items or 100 GB), so the large-volume path is publish-as-you-go.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
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