Calls are held every Thursday at 1 pm eastern time – convert to your time at http://www.thetimezoneconverter.com

Link to Google Doc for meeting notes: http://goo.gl/JvCfjU

 

Themes

  • Attendees: Cornell, Smithsonian, IFPRI, Emory, CU-Boulder, UCSF, Virginia Tech, DuraSpace, Duke, Northwestern, Brown

  • VIVO Annual Survey Results

    • the anonymized results and conference presentation slides can be found here

    • questions?

      • possible refinements to or gaps in the survey questions?

      • interpreting the survey results? how might the survey results be used?

        • Layne: a lot of data in the survey result, taken along with presentations at Leadership meeting in Austin, useful input for planning a technical roadmap… are there any questions/concerns not addressed in the survey, that would be helpful in developing this strategy?

        • Mary: support model slide… this could be a springboard for exploring in deeper detail in the wiki... how can we start… (Alex: interesting idea using the wiki to explore requirements before creating JIRA tickets or items on a technical roadmap)... Layne: useful to have a place on the wiki to explore concerns/requirements emerging from survey… had a phone call for use by community to help with planning and strategy development…

        • Mary: strength of overall survey… good coverage for all the different considerations of a VIVO implementation… helpful as a framework…

        • Paul: UCSF Profiles has clear goals for their users (that’s a good think we think)… are their goals that we have for the VIVO community? Learning from how Drupal community has a Proficiency Scale (Alex: links? Google didn’t find for me… also thinking about Scrum certification model)... Layne: good idea… Eric: we has a simple endpoint in mind, not necessarily a simple journey/path, but that goals are easy to understand: “make the researchers look good (not for vanity, but for utility)”... Anirvan studies traffic patterns to try to figure out why people visit UCSF Profiles… “is a bounce a good thing or a bad thing?”

        • Paul: slide on “what is your site’s priority?” -- anyone have comments on this?

          • Jim: addressing concerns of the top item (Tools for read/write access) in VIVO 1.6 and 1.7… focus on getting data in, getting data into the right shape

          • Don: we want a sustainable ingest process

          • Paul: “tools and apps” -- implies something that is not core, whereas some things on this slide are core, some note core, and some inbetween or not related (“marketing”)... Don: tools and apps at LASP… allowed them to build externally without concern for integration/coordination with VIVO core team… but there might be applications where core team might be interested (faceted search)... Paul: how can the core dev team make provision for these requirements/applications (VIVO as a platform), but make it easier for any given site to implement/extend? Anything about 1.6 API that LASP would have wanted… Don: 1.6 API made LASP’s work easier… maybe some of the functionality proposed for 1.8 API… Jim: I saw no response when this was tossed out, so not looking at it as a priority for 1.8 now...

        • Action items?

          • Mary’s suggestion of pulling requirements and goals out of Survey, as bullet points on wiki page that link to more detailed wiki pages (or identify gaps in wiki documentation)?

          • Layne mentioned using survey as input for a task force (Julia Trimmer, others)

          • email survey questions to dev or impl mailing lists if you aren’t ready to edit wiki, but want to raise them

  • VIVO Hackathon Planning

    • general information and proposed topics can be found here

      • questions about the proposed topics?

      • Holly has put together a registration form (to be launched soon), and not certain if she’ll be able

      • Mary: harvesting directly from Symplectic -- Alex: will add myself as a Resource Person on VIVO Harvester row to support this… also will there be space for a user group meeting? Could this fit into Wednesday morning -- send Jon an email and copy Mary and Don… interest in a room where we could host a WebEx conference call to invite remote attendees

      • Patrick (Duke): interested in visualization topic, also an app that is consuming VIVO data using JSON (maybe combined with viz)

      • Paul: might be able to attend, looking to learn and lending a hand

      • Brown: Ted and Steve will be there

      • Keith: there to learn, to see how to best contribute

    • logistics information

      • Jon is planning to go ahead with plan for Sunday winery tour… “you can’t throw a rock without hitting a winery”

Notable List Traffic

See the vivo-dev-all archive and vivo-imp-issues archive for complete email threads

Call-in Information

  • Date: Every Thursday, no end date
  • Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)
  • Meeting Number: 641 825 891

To join the online meeting

1. Call in to the meeting:

   1-855-244-8681 (Call-in toll-free number (US/Canada))

   1-650-479-3207 (Call-in toll number (US/Canada))

2. Enter the access code:

   641 825 891 #

3. Enter your Attendee ID:

   8173 #

  • No labels