Make SciApps a federation interface

[liyawang]

• Run all jobs as maizecode
• Hold maizecode credentials on server
• After login, can access public data, sci_data and community data
• For login, user will be directed to CyVerse for authentication, then direct back to SciApps
• Log in --> Welcome, Someuser Logout
• Log out --> Log in
• Log out means we will close the session
• Work with Peter to add https

[liyawang]

Enhance job history cache

• Cache job history so it won't be erased from refreshing
• Speedup workflow history loading by storing them in a database?

Support checking Agave job history for debugging

• Since all jobs is executed by the maizecode user
• This could be added into the 'i' link in the history panel

Add job management

• Delete_ job in history panel
• Can not re-load the same public workflow after deleting some jobs of the workflow
• Can not build workflow with the remaining jobs (build is also slow without any deletion)

Categorize public apps

• Use Agave ontology (with the file Dennis sent)
• Display Private app (one category) on the top
• User can load app form without logging in
• Display warning message when user try to launch job (if not logged in)

Add workflow management

• List of workflows
• Save, load, delete

User private apps/systems

• Not working unless user wants to share the app with public
• Easier with apps built on CSHL or public systems (just need to share the app)
• difficult since user might not be able to share the system with maizecode user
• Also need to auth with Agave besides CAS4

[liyawang]

Resolved!