Task · role · organisation connections
Pick one of our tasks to see what has to arrive before it can move, and what breaks downstream if it slips.
This function's own prerequisite analysis — not in the proposal or the task register.
The foundation stone. Define the minimum viable semantic model for services, technologies, facilities and workflows; pick and align controlled vocabularies; set the PID strategy (ORCID / ROR / DOI / PIDINST) that every later record hangs off.
How many tasks each output carries — filtered by the same WP selection above. The wide bars are where a slip is expensive.
Computed from the task register's dependency column, not the Part B proposal (which only documents dependencies at WP level).
Not an org chart — a list of who this work has to agree something with, and what.
Owns the WP2 line end to end; the axis for T2.1–T2.4 and the WP5 pilots.
The connective tissue: model in T2.1, catalogue in T3.2, landscape in T3.1, curation into T3.3.
Primary consumer of the model. Needs a frozen schema and a change log more than anything else.
Supplies intents and exemplar queries that define what the model must answer; carries the mappings into T3.4; also GA lead on WP8 coordination.
Builds against the published schemas; every schema change is an adapter change.
Brings external catalogues that must be crosswalked to.
Decides what personal data may enter the knowledge base.
Consumes the data inventories for the DMP; owner of the explanation requirements and WP7 monitoring.
Turns the catalogue into Node-facing training material; named participant across WP5 and WP7.
Gatekeeper for the T2.3 content package.
Co-owner of WP8 reporting; receives progress and data-inventory input alongside Erika.
Validate terms and records; the ontology decision is not made unilaterally.