September 11, 2015, 1 PM EST

Attendees

Steering Group Members

Paul Albert, Jon Corson-Rikert ,  Kristi Holmes,  Dean B. Krafft, Robert H. McDonald, Andi Ogier, Bart Ragon, Julia Trimmer

...

NEW DIAL-IN: 641-715-3650 (was 209-647-1600), Participant code: 117433#

Agenda

Notes

Updates

Discussion of upcoming euroCRIS event

...

• Jon, Paul, Alex, Jim Blake, and Laura from UPenn worked on a task force to go over the various 'things' VIVO had accumulated, roughly since 2009
  • Trying to understand what those things are – websites, email lists, communication channels, etc.
    
  • Trying to understand what to do with/for them
• The spreadsheet of assets was put out for comments several times through VIVO Updates
• Many newcomers to VIVO are overwhelmed, and sometimes we aren't consistent in how we use resources because we have so many different ones – we lose coherence as a result
• The recommendations are grouped
  • There are questions of whether things even should be done – which headings are worth pursuing
  • Then a question of priority
• Some are obvious and have already been discussed
  • E.g., completing the move from SourceForge to GitHub (cluster 4)
• Steering can also act to indicate which items in the report it endorses and/or has plans to move forward with
• Some things we are not ready to do very much about – such as item #10
  • We haven't kept vivo.vivoweb.org up, so it doesn't really serve the purpose of being a demonstration of the system
  • We can either shut it down or decide we need a demonstration that shows well
  • And there are potentially several kinds of demo systems – one with sample data, another to highlight software and related apps&tools
    
  • We should take down anything that looks bad and would not help the project
    
    • Similar to removing software from the release that is broken, to avoid giving a negative impressions
    • We could replace with a series of screencasts or screen images of places that have a VIVO, until we get a working demo system, that won't be tomorrow
  • Cleaning up edges of the project that don't show well
    • Some of the recommendations may not go clearly enough in that direction
    • Implementation of a demo system may involve
      
  • Would this be a chance to have a sprint?
  • A different kind of demo that is a demonstration of a scholarship site is not what we have now
    
• Several of these will require spinoff activity with concerted planning, and some dedicated effort
• Looking for guidance on whether Steering wants the report amended, or whether it will accept the report and consider prioritization and further recommendations
  • 3 or 4 of us could write up a response to the report suggesting action steps – what we will do
  • Thinking of a step where Steering accepts the report, states it expects to go in this direction, and will review the list of tasks to prioritize and refine and suggest actions (e.g., a task force, a single volunteer)
    
  • • But if there are objections to elements of the report, we should hear them
    • Are we ready to do that today? This is a more complex report
  • The email recommendation, for example
    • Integrating with the CRM system at DuraSpace – we don't even know if its feasible
    • Also mentions a product called Discourse, but that would put us out of sync with the other DuraSpace projects that use Google Groups
    • These will require a more detailed response, and we are not likely to act on all of these
  • Any of these 10 items could have feasibility issues that affect priority and timeline
  • If we are doing a qualified acceptance, then a smaller group should go through to come up with action recommendations
  • May also involve the availability volunteer effort available for any task
• Accepted for further review to assess priority and possible implementation

Action Items

•  Dean B. Krafft will follow up with EuroCris
•  Mike Conlon will ask community about EuroCris and follow up based on feedback
  

...