Skip to content
Event Meet us at IBC 2026 · RAI Amsterdam, 11–14 Sept · EBU stand 10.D21 Plan your visit →
Use cases & services

What can you do with TAMIS

Each case below is a concrete exchange between organisations: what goes wrong today, how it works, and what it changes. Some are running with pilot partners, others are still a track we have discussed, and the status is written on each one.

What you can reach through the data space

The first thing you find in a data space (opens in a new tab) Data space A decentralised infrastructure enabling trustworthy data exchanges based on commonly agreed rules. is somewhere to look for what other participants (opens in a new tab) Participant An organisation admitted to the data space, identified under its rules and able to exchange within it. offer, and somewhere to describe what you offer yourself. It is one mechanism used in both directions, and a participant is usually on both sides of it.

From inside the data space, you can search the federated catalogue (opens in a new tab) Federated catalogue The mechanism that makes the offerings of every participant discoverable together, without centralising any data. for what other participants have published. Some offerings give access to data, such as the metadata a participant holds about its works. Others give access to a service, such as looking up an identifier. Each offering states what it covers and the terms attached to it, so you can tell on what conditions you could get access before contacting anyone.

Publishing works the same way, and it counts for as much. You describe an offering of your own in your local catalogue (opens in a new tab) Local catalogue The list of offerings a participant publishes from its own connector, describing the data and services it exposes. : what it covers, which of your works, records (opens in a new tab) Record The whole set of metadata held about one audiovisual work, kept as a single living object instead of scattered across spreadsheets and systems. or files it concerns, and the rules that come with it. Only the description becomes findable by the others, and what you hold stays where it is. Nothing you have not described is exposed, so publishing is decided one offering at a time.

An offering is a description, not a delivery. Finding one is not the same as having access to it: access is agreed afterwards, bilaterally, with the participant who published it. It is also why a set of records (opens in a new tab) Record The whole set of metadata held about one audiovisual work, kept as a single living object instead of scattered across spreadsheets and systems. and a service are published the same way and read the same way, neither being a special case of the other.

None of this happens on this website. It happens inside the data space, between participants, each of them running its own connector.

This is the plumbing, and the use cases on this page are the particular business needs it makes possible.

Already developped

Book a demo

Also on the horizon

Tracks we have discussed and nobody has built yet. They carry the status they deserve: concept. If one of them is what you need, say so, and it stops being a concept.

Bring your own use case

The use cases running today are not the boundary of what the data space can do. If the exchange you need is not among them, it is not missing: it is unproposed.

See how a use case gets in

Value for every seat at the table

The TAMIS data space makes audiovisual metadata findable across the chain, wherever it is held. What that means concretely depends on where you sit. Here is the value for each role.

Producers

Describe once, deliver clean everywhere.

  • Register a work once and give it a persistent, resolvable identity.
  • Auto-extraction and ISAN lookup pre-fill the record: no blank forms.
  • Deliver validated metadata to every broadcaster without re-keying.
  • Turn a dormant collection into discoverable, well-described assets.
  • Rights get paid to the right people, and sooner: a work correctly identified in broadcast data is a work whose rights holders can be found.

Relevant use cases

Broadcasters

Receive metadata you can accept as-is.

  • Get clean, validated records in a format your systems accept directly.
  • Cut manual re-entry and the errors that come with each hand-off.
  • See field-level provenance: who wrote each field, and when.
  • Know which version you are looking at, and where the value that counts is held.
  • Accept, refuse or correct the fields you receive, and have that validation travel back up the chain.

Relevant use cases

Registries & CMOs

Authoritative identity, connected.

  • Act as a trusted source that enriches records across the data space.
  • Link works to persistent identifiers (ISAN and beyond).
  • Strengthen rights identification with shared, provenance-aware data.
  • Reduce reconciliation work between databases.

Relevant use cases

Service & solution providers

Any service around the data, or the content, of audiovisual works.

  • Metadata processing, AI-based extraction, localisation, packaging, discovery, infrastructure: the data space is built to reach all of it.
  • Plug into one interoperable layer instead of one integration per client.
  • Reach participants who were not going to look for you otherwise.
  • Serve the ecosystem without becoming a lock-in platform.
See the service families

Not sure where you fit? Let’s map it to your workflow.

Talk to the team