Date
Attendees
Goals
- Review, next steps
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 25 min | Review interviews and next steps | All | How do we "finish" the asset inventory? |
| 25 min | Recommendation Process | All | How will we develop recommendations? |
| 10 min | Next meeting | All | When do we meet again? What do we need to have accomplished? |
Notes
Interviews
- Jim talked with Ted Lawless
- Mike spoke with Chris Barnes, who had 3 assets
- the Youtube videos from Apps and Tools
- Violeta's
- the mailing list archives
- Jon spoke with Miles about his Drupal work
- an asset on GitHub
- Paul – is a Weill Cornell organization on GitHub
- Mike – a larger issue around Apps and Tools – we have a catalog on the Apps & Tools wiki page and those point out to other assets in the community that are not really project assets
- That's why we have an apps and tools task force
- architectural issues
- support issues – e.g., the ORCID API interface that Justin made – could imagine that being just a link in a VIVO template that could link out to a web page that is authorized to talk back to VIVO and put triples in our triplestore
- is Florida hosting a copy of that thing?
- a similar issue with Stony Brook's UMLS service – had gone offline
- a responsibility model – you get nothing, not just a 404
- a similar issue with Stony Brook's UMLS service – had gone offline
- One line in our spreadsheet about these apps & tools
- That's why we have an apps and tools task force
- Other people that we can or should talk to?
- Elly – Jon can try to recover the user scenario work from spring, 2010
Are we ready to share this spreadsheet with the community, following an orientation email to go with it?
- We should first flesh out missing cells – anything that is blank is not helpful
- Hide the recommendations column and the suggested worksheet
- Want two conversations – first about what we have and what's missing; then a separate conversation about what we do with these
- We want to get feedback on our assets, then have this group compile 2-3 pages of recommendations in sentence form about email lists, repositories, etc.
- In preparation for task forces to then be set up to make changes based on the recommendations
- Could share the PDF to discuss on the Thursday call in a week or two
- When to stop editing? 4:30 PM Friday, May 8
- Lauren is willing to make a second, read-only copy and will send a read-only link to a pared-down copy (one sheet, no recommendations) and share the link with the members of this task force
- Mike can send out the link in his updates email on Monday
- Also not wild to ask hundreds of people for suggested assets – don't open Pandora's box just yet
Action items
Members of the task force should help fill in empty cells on the asset spreadsheet (and add any further missing assets) by 4:30 Friday, May 8
Lauren will create a copy of the spreadsheet with a read-only link for Mike to send out Monday to as part of his weekly update email
