Use case and requirements collection

[reisingerf]

A high level issue to keep track of use cases and requirements.

Obvious use cases, combining data from several core services:

• workflow lookup by library metadata, e.g. find all workflows for a given list of libraries e.g. that failed QC -> to be used to annotate workflows and for subsequent data cleanup operations
• find results e.g. specific reports for all analysis of a particular patient / cohort and check if data is available / archived -> could be used in cohort building / result sharing
• particularly useful for end user facing clients like the UI where complex data queries across several back-end services are the norm

Possible technical use cases:

• use OrcaHouse as only client facing interface -> could remove the need for detailed authorisation from the back-end services and aggregate access control on the OrcaHouse (would need to include support to "pipe-though" write operations)
• abstraction of back-end services from end users adding flexibility for back-end service migrations

Use cases for improved UI capabilities combining data from multiple back-ends

• aggregation of sequencing QC / stats which may come from multiple other workflows in a sequence run centric view (requested by the lab)