Announcements

• Ontology Working Group: next call is Thursday, July 3 at noon EDT

• Agenda to be determined

• Lisa and Max are working on a Knowledge Mobilization ontology as an extension of the VIVO-ISF. They have been helpful in surfacing bugs with the VIVO-ISF ontology.

• Apps & Tools Working Group: next call is Tuesday, June 25 at 1pm EDT

• Agenda to be determined

• VIVO Conference: August 6-8 Austin, TX

• Registration is open – early bird rate expires tomorrow (June 20)

• Organizers circulating draft schedule to confirm with speaker availability – final schedule should be available soon

Working Group Activities 

• VIVO 1.7 Release Candidate 1

  • The files for the release candidate are here:

    • VIVO: http://rollins.mannlib.cornell.edu/download/vivo-rel-1.7-rc1.tar.gz or http://rollins.mannlib.cornell.edu/download/vivo-rel-1.7-rc1.zip

    • Vitro: http://rollins.mannlib.cornell.edu/download/vitro-rel-1.7-rc1.tar.gz or http://rollins.mannlib.cornell.edu/download/vitro-rel-1.7-rc1.zip

    • or you can get the latest and greatest directly from the maint-rel-1.7 branches of the repositories on GitHub

  • See VIVO v1.7 release planning and notes from last call for more info

  • Dev team looking at a 1.6.3 release after identifying a SPARQL query that does not scale well

Theme: Project planning and communication for VIVO teams 

Suggested topics and questions:

• What tools does you or your site use to plan projects?
  • examples: Service Now, Scrum, kanban, wikis
• How do you track issues?
  • examples: JIRA, Service Now, email
  • How do users report issues? Do they call or email a help desk, complete a web form, or email the VIVO team directly?
• How do you communicate within your project?
  • How often do you have project meetings?
• How do you manage your release(s) to production?
  • Email targeted users, e.g. faculty/researcher with VIVO profiles
  • Campus-wide e-memo
  • Web posting on VIVO site or other
• Who are the stakeholders for your project?
  • examples: Provost, CIO, representative body of users (faculty senate), Deans, Department Chairs
  • How do you report to them?

The last 10 minutes of the call will be saved for discussion around which themes attendees would like covered in future calls.

Call-in Information