##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.

Third party requirements for integration with the DOMS data cannot be met.

We know that external parties wish to use data from DOMS. Current plan is availability through Summa and through a web service interface.

Examples of external parties: The "kulturportal" (common culture web site with various digital data sources), edumedia ("YouTube for researchers").

== 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 see third-party demands that are not met

== 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.

== Responsible Persons ==

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

Try to get third party to implement the necessary bridging software on the existing access tools. If they cannot or refuse, get steering committee to decide if we should implement bridging software. If bridging cannot be done, get Steering Committee approval that we will not integrate with third-party software. If impossible, design and estimate now interface to DOMS, get steering committee approval
## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]