design large dataset solution

[krobasky]

Close this ticket when:

• [ ] design has been refined and discussed and agreed upon
• [ ] prototype a very simple instance of the design (including a DOS if there is one)

More detail

Maybe use DOS API from GA4GH over top of an iRODS instance. the use case might look like the following (rough first hack):

Use case I

1. dashboard: requests a

2. fuse-immcellfie-api: json <- fuse-server/Object/ --> fuse-server populates DOS_server with expression data, keyed off DOI

   json: exprs -- DOI OR [expression]

3. dashboard has the json from fuse-immcellfie-api if user requests "input" -- DOS_server/GA4GH/getObj(json.exprs.DOI) <-- this might be iRODS? expression data -> render

Use case II:

1. dashboard: requests a

2. fuse-immcellfie-api: json <- fuse-server/Object/ --> fuse-server populates DOS_server with expression data, keyed off DOI

   json: exprs -- DOI OR [expression]

3. dashboard has the json from fuse-immcellfie-api user requests "analysis" --

4. fuse-immcellfie-api: a. calls fuse-mapper/json b. fuse-mapper gets expression data: DOS_server/GA4GH/getObj(json.exprs.DOI) c. fuse-mapper does the mapping & returns json' (with DOI') d. fuse-immcellfie-api calls fuse-analysis-cellfie(json') e. fuse-analysis-cellfie gets the expressiondata: DOS_server/GA4GH/getObj(json'.exprs.DOI')

[xu-hao]

Update: I create a API spec and discussed with Kimberly and David: https://adminliveunc-my.sharepoint.com/:w:/r/personal/xuh_ad_unc_edu/_layouts/15/Doc.aspx?sourcedoc=%7B4233780E-8AA6-4F93-A577-A877B69034B5%7D&file=Immcellfie%20API.docx&action=default&mobileredirect=true