From: De Almeida, Jonas (NIH/NCI) [E] firstname.lastname@example.org
Sent: Monday, November 25, 2019 9:27 AM
To: Hadley King email@example.com @HadleyKing … (full list removed)
Subject: Re: BioCompute Technical Steering Committee Meeting Notes - 08-22-19
As promised Thursday, the note on running workflows in github:
40M developers on github woke up last week with a new tab, “actions”, and a workflow engine integrated in their developer environment – which already includes hosting web applications and authentication services, all of this with versioning and a marketplace where workflows can be published and found. So the conversation Thursday was about creating a BCO example in this environment to establish its FAIR use. I suspect most developers (definitely most students) have already migrated to serverless execution environments and having a one-click place where to validate, and disseminate, a workflow manifest/language, really is the place to be if you want to reach them. So the suggestion is to have a simple and compelling example of a BCO as a github action others can fork and investigate.
I left the same comment in gitter [this one :smile:] in case you want to discuss it further (not a fan of email conversations here …)
Jonas S Almeida, PhD, Senior Investigator
NIH/NCI/DCEG Chief Data Scientist
It is thought that a token-based system will be implemented, however, we are open to other methods of authenticating requests.
my 3 cents:
@stain @carmstrong1gw made a fork for you for the BCO portal API.
compare.py is the command line script
he should run everything in a virtual environment
he'll probably need to install jsonschema in the virtual environment
he'll also need a folder to place the BCOs in and they have to follow a certain naming format