AbbVie Hackathon

Requirements

• Support for ~40 users accessing the primary workbench instance on June 20th
• They've suggested only 2 tools, along with Raspberry RaspberryPi and Data APIs. 

Open questions:

• Are we supporting this?
  
  • Maybe
• How long are we supporting the system for AbbVie?
  • June 20th-23rd
• Who are the users (the demo instance is for NDSC/RDA members, right)?
• Will users have long-term access to the main instance (since this is our "demonstration" instance, we should probably revoke access after the workshop)
• How will users be informed of the registration workflow? 
• How much support are we providing during the workshop?
• Would it make sense to just setup a dedicated instance to simplify things?
• Tools
  • We'll need to dedicate time to exploring whether we can support them and then dockerization
• APIS
  • We don't really have API support
• RaspberryPi integration
  • Unknown

Tasks

• Propose support plan/requirements including account management. 
• Dedicated instance: NDS-901
• Upgrade instance from 1.0.8 to 1.0.10 (stability and container timeouts): NDS-894
• Investigate support for requested tools: 
• Dockerize requested tools
• Investigate support for APIs (what does it mean for Workbench to support APIs? – documentation?)
• Investigate options for RaspberryPi integration (seems unlikely)
• Document and communicate expectations and process to AbbVie organizers.
  
  

Background

• Industry partners
• Evaluating workbench for use for a hackathon around June 20th (first accounts approved 5/23)
• Drug interactions in data
• Number of users unknown : ~40
• Tools unknown: below along with data APIs
• They seem to have run something similar in 2015
  • https://disruptsf2015.devpost.com/
  • Participants are given a list of challenges
    • https://disruptsf2015.devpost.com/forum_topics/5161-abbvie-challenge-2-a-gamified-patient-experience-to-empower-people-living-with-chronic-disease
    • https://disruptsf2015.devpost.com/forum_topics/5159-abbvie-challenge-1-wearable-to-monitor-people-suffering-from-neurological-diseases
  • And some APIs
    • https://disruptsf2015.devpost.com/details/apis
  • (Could serve as a set of requirement for future events. For example, see forums)
    • https://disruptsf2015.devpost.com/forum_topics

Tools/APIs

From 5/25 emails

"We will have about 40 participants. Not all will be using the sandbox, but just in case…"

"Below is a list of Tools/APIs that have been suggested.  There are only 2 tools, and they seem to fall under the general category of ‘cool AI’. Additionally, we had mentioned that we’d like to do some RaspberryPi integration, so I’m not sure how that would work.

Tools

• https://www.h2o.ai/
• https://www.tensorflow.org/
  
  

Data APIs (These are mainly just for open source data, however there are some tools associated with some of these links. Nobody here has requested any particular tool, though.)

• https://wwwcf.nlm.nih.gov/nlm_eresources/eresources/search_database.cfm
• https://wonder.cdc.gov/wonder/help/WONDER-API.html
• https://tools.cdc.gov/syndication/api.aspx
• https://rxnav.nlm.nih.gov/APIsOverview.html
• https://www.ibm.com/watson/developercloud/doc/common/index.html
• https://open.fda.gov/
• http://www.ensembl.org/info/docs/tools/index.html
• http://www.uniprot.org/"