fshy

fshy / Storage

Materials Cloud

materialscloud.org · Storage · 2 records · JSON

Materials Cloud Archive (EPFL / NCCR MARVEL) Storage

caveatanonymousno cardRper-object-capdisagrees

archive.materialscloud.org · academic · storage/materials-cloud-archive · JSON · compare

Sibling records disagree:

Free tierPer-record, not per-account: '5 GB for general materials science research data, 50 GB for AiiDA databases. For larger datasets please contact us.' Records are unlimited and each gets a DOI, so this is a per-record-unlimited pattern rather than a 500 GB single-shot store.
unit GB; metered on stored-bytes
Pricenone stated
Per-object capPer-object-cap 5 GB (5000000000 bytes)
Retentionnot stated
EgressFree, and unusually well-instrumented: 'Access to metadata and data files is provided over standard protocols such as HTTP and OAI-PMH.' No metering. Probe: GET /record/2026.196 -> 200, 90,945 bytes of record page.
Identityanonymous derived from the record's prose, not from an identity field, and no signup was executed: -quality requirement) and rate-policed — the opposite of an anonymous dump. Data survives; throughput is editorially throttled. Unlimited records x 5 GB (or 50 GB for AiiDA databases). 100
Limits
  • write-gated reviewed by the Materials Cloud moderators'), scope-gated to computational materials sci source
  • per-object-cap Per-object-cap 5 GB source
Per-object-cap 5 GB / 50 GB per record; moderation gate ('Once you submit your record for publication it will be reviewed by the Materials Cloud moderators'), scope-gated to computational materials science, and moderators explicitly police 'excessive submission rate'.
Bindingper-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
Interfacerest rest
ToolingEmail self-registration with a personal work area; HTTP + OAI-PMH read; DOI minting per record; versioning of published records. AiiDA provenance integration is the native client for the 50 GB tier.
Composes withUnlimited records x 5 GB (or 50 GB for AiiDA databases). 100 records at 5 GB = 500 GB; the 50 GB AiiDA tier halves that to 10 records.
ReliabilityEPFL-hosted and stable, but moderation is substantive (refereeable-quality requirement) and rate-policed — the opposite of an anonymous dump. Data survives; throughput is editorially throttled.
NotesPer-record, not per-account: '5 GB for general materials science research data, 50 GB for AiiDA databases. For larger datasets please contact us.' Records are unlimited and each gets a DOI, so this is a per-record-unlimited pattern rather than a 500 GB single-shot store.
Evidence rungreported One page read moves it to documented.
Checked2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers
  • $.limits[1].value limit:per-object-cap 5.0 GB
Evidence (3)
datesourcewhat it proved
2026-10-21archive.materialscloud.org/information'Volume and size limitations: 5 GB for general materials science research data, 50 GB for AiiDA databases. For larger datasets please contact us'
2026-10-21archive.materialscloud.org/help'By registering with your email to the Materials Cloud Archive...' (open self-registration), moderated before publication
2026-10-21withheldprobe: GET /record/2026.196 -> 200 (90,945 bytes); 1,551 published records live
Unknown or withheld values (5)
  • $.evidence[2].url private-url
  • $.free_tier.notes process
  • $.per_object_cap.notes not-extracted
  • $.retention.notes not-extracted
  • $.retention.stated not-extracted

materials cloud archive Storage

fails: quotaemail?card?Rdisagrees

archive.materialscloud.org/uploads/new · rejected-provider · storage/materials-cloud-archive-2 · JSON · compare

Sibling records disagree:

Free tierInvenioRDM node with a hard login wall before any upload; publishing is tied to a Materials Cloud workflow rather than open deposit.
unit none; metered on none
Pricenone stated
Per-object capnot recorded
Retentionnot recorded
Egressnot recorded
Identityemail (placeholder) not published
Bindingnone no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interfaceunknown
Toolingnot recorded
Composes withnot recorded
ReliabilityInvenioRDM node with a hard login wall before any upload; publishing is tied to a Materials Cloud workflow rather than open deposit.
NotesInvenioRDM node with a hard login wall before any upload; publishing is tied to a Materials Cloud workflow rather than open deposit.
Evidence rungreported
Checked2026-10-21 (inherited); stale on 2026-11-04
Evidence (2)
datesourcewhat it proved
2026-10-21archive.materialscloud.org/uploads/newInvenioRDM node with a hard login wall before any upload publishing is tied to a Materials Cloud workflow rather than open deposit.
2026-10-21archive.materialscloud.org/api/records?size=1cited as the basis of the rejection: InvenioRDM node with a hard login wall before any upload; publishing is tied to a Materials Cloud workflow rather than open deposit.
More fields (1)
{
 "dead_end": {
  "failure_class": "quota",
  "why": "InvenioRDM node with a hard login wall before any upload; publishing is tied to a Materials Cloud workflow rather than open deposit.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}
Unknown or withheld values (15)
  • $.chaining not-recorded
  • $.confidence_note withheld
  • $.egress.terms not-recorded
  • $.extras.dead_end.retry_when process
  • $.free_tier.notes process
  • $.identity_cost.detail defaulted
  • $.identity_cost.kind identity-defaulted
  • $.interface interface-unknown
  • $.interface_detail withheld
  • $.limits_note process
  • $.per_object_cap.notes not-recorded
  • $.per_object_cap.stated not-recorded
  • $.retention.notes process
  • $.retention.stated not-recorded
  • $.tooling not-recorded