##Risk Description

= Risk Description =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

Some collections cannot be described in the DOMS data model

The DOMS model is very flexible, and should thus encompass most collections. However as an example of what might be difficult to put in the DOMS, the DOMS does not attempt to emulate any interactivity as is.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.
When we have examples of data we cannot, or do not wish to represent in the DOMS.

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

## E.g. We accept the risk and change the tire if we suffer a puncture.

It is acceptable that a few systems live outside DOMS, like the netarchive.

If the changes needed to encompass the new collection are minor, try to update the data model.

If the collection fundamentally contradicts the DOMS data model, get the steering committees approval that we will not have this collection in DOMS.

== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]