Design Pacs-pull complete workflow

[NicolasRannou]

Design Pacs-pull complete workflow

[NicolasRannou]

[FE]: Front-End

[BE]: Back-End

HTTPS Connection to Django Server: https://docs.djangoproject.com/en/1.9/ref/settings/#std:setting-SECURE_SSL_HOST

(user preferences, such as PACS IP, AETITLES..?)

(where does services run? server, cluster, VM)

Login

❌ [FE]- login page, user enter credential and contacts the server.
❌ [BE] - which type of authentification?
✅ [FE] - on success, go to home page.

Run the pacs-pull

✅ [FE] - pacs-pull app page
✅ [FE] - set search parameters
❌ [FE] - run pacsQuery FS "service"
❌ [BE] - run pacsQuery with given parameters
❌ [BE] - return CJ Object with list of results (or link to file containing results? Current chris uses a file for large amount of results)
✅ [FE] - display list of results nicely
✅ [FE] - user selects results to retrieve
❌ [FE] - run pacsRetrieve DS "service"
❌ [BE] - run pacsRetrieve with given parameters
❌ [BE] - return CJ Object with new Feed that is running.
❌ [FE] - add new running feed to the feed-list.

Polling the pacs-pull

❌ [FE] - Plugin, Feed or Chris-ultron polls the API to know running Feeds? (what does running feed mean? at list one plugin inside the feed is running? which parameters?)

Chris-ultron polling is probably the most efficient.

Finish the Feed

❌ [BE] - Feed ID is done! Feed/Plugin CJ returned to the Front-end on the next poll event.
❌ [[FE]] - Update Feed/Plugin status.
❌ [[FE]] - Update Files in Plugin that finished.

View the results

✅ [[FE]] - Select view to look at the results.
❌ [[FE]] - AMI (WebGL view) needs the Real file to upload it.
❌ [[BE]] - Send Real files that are queried by the front end.
❌ [[FE]] - Look at the beautiful results :)