Mapping any database to a reference schema

The same organisation, location or activity appears differently in different databases. Their records cannot be compared reliably until those differences are resolved.

How this work runs.

The run as one route: which tools get involved, in what order, and where the chain is not mechanised yet.

TWO SHAPES, ONE FACTONE REFERENCE SHAPETarget schema asa parameterANY DATABASE (SOURCE)SCRIBEANY DATABASE (TARGET)NOT MECHANISED YETNOT MECHANISED YET

One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.

reads what the other publishes
Nothing is sent. The next tool reads what the one before it has published, at the moment it needs it.

What this work delivers.

A mapping to a reference schema that lets records be compared or exchanged while preserving their origin.

  1. Inspect the source

    Identify the source structure, identifiers, units and relationships.

  2. Define the mapping

    Scribe proposes how each source construct corresponds to the reference schema.

  3. Resolve exceptions

    Check ambiguous identities, missing values and differences of meaning with an operator.

  4. Validate the output

    Confirm the mapped records meet the target requirements and retain their provenance.

Mapping is not permission to share. The data holder separately decides whether mapped information becomes discoverable or accessible.

Explore connections through Spine

Which tools, in what capacity.

actuate

Scribe

Renders the source against the target schema, given as a parameter

Put this to work in your context.

Tell us what you need to achieve and what you already have.