A dataset is an entity.
Yellow entities connect to purple production activities and pentagonal agents. Arrowheads follow the RDF statement: a generated dataset points to the activity that generated it.
Data, work, and the people behind it
Where the data
comes from.
Explore the AdV landscape through its entities, activities and agents. Follow a relation. Get to know a resource.
The provenance view
From source to story.
Hover or focus for details.
Click to pin. Use + to expand connected triples.
Change view or inspect the SPARQL query DTK10–1000 · DOP20 · source data · expansion
Choose a workflow preset and press Run to follow its plans, recorded production and source data. The page opens with the full landscape. You can edit any query; the graph and statement table share its results.
How does expansion work? Use the default or configure your own query
By default, + reveals incoming and outgoing triples from the current view. Apply a SELECT query below to choose what + reveals from the loaded document. Collapse removes added branches; the base view stays visible.
Resource: DTK50Plan (example)
The SELECT returns the same edges as the CONSTRUCT. SLC displays the SELECT rows; GraphDB custom expansion uses CONSTRUCT ↗.
The preview shows your applied SELECT query with the selected term inserted. Edit the template and apply it again to change the rule.
The check runs SELECT against the complete loaded document. Default + expands only the current view’s query results. Applying a custom query makes + use that query against the loaded document too. Neither action fetches linked documents.
A plan is not a run.
Plans use the entity shape. Qualification nodes keep the association to an authority and a plan explicit. Nothing here turns a documented procedure into an actual execution.
Classification has its own links.
Enable RDF context to explore the selected view’s SKOS and DCAT resources. Dashed links retain their original predicates. Specification dates describe specifications.