Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use case and requirements collection #10

Open
reisingerf opened this issue Jan 9, 2025 · 0 comments
Open

Use case and requirements collection #10

reisingerf opened this issue Jan 9, 2025 · 0 comments

Comments

@reisingerf
Copy link
Member

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

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant