Page History

...

• The process and priorities of developing road maps (for VIVO, for the VIVO-ISF ontology, and for VIVO apps & tools) is on the Leadership Group agenda for a meeting at the VIVO conference. It would be useful to have community input about how to increase transparency in these areas.
• Jim has some progress on the TDB front to report but nothing conclusive about the chief concern (performance at scale).  Beyond that we have not thought a lot yet beyond what’s was discussed during the DuraSpace Summit in March, except that it’s become more clear that we need to either find resources to update the visualizations in VIVO (particularly the Map of Science) or to have a project to pull them outside and figure out how to embed them from a service.
• VIVO multi-institutional search is also a priority. Another consideration is whether, as a community, the lack of clarity of how to do data ingest (both documentation and tools) is holding us back, more than lack of progress in core development — where should our limited development resources be applied?
• Jon has been looking into scheduling a VIVO development/hackathon event here at Cornell for October 13 & 14th (developer training on the 13th and possibly extending into the 15th for serious hacking) — Jim has suggested that the focus could be on developing a REST API for VIVO that would deliver the contents of a page as JSON, which would allow people to both work in the core app (hopefully expanding the core developer base) and others to work on developing one or more apps to consume the JSON from the api.  The event isn’t definite yet, and Chris and Ted need to have a chance to think about the implications of it for their work, but it seems like a positive step forward as a chance to work together on features that might be in VIVO 1.8, as well as a deadline for doing roadmap planning for 1.8.  If we’re releasing 1.8 on schedule this fall that will leave us only a little over a month of development time before a late November code freeze.

• Jon has set up a WebProtege project at http://webprotege.stanford.edu/#Edit:projectId=82f678bc-b3eb-4dc1-8054-318225ac7d89 that is publicly visible and comment-able, and hopes that we can start working on changes and extensions for 1.8 there. There's also interest to make the VIVO-ISF OWL file something that can be generated automatically from the ISF repository, currently on Google Code.

Call attendees planning to be at the Conference are also encouraged to bring up any questions they might have, e.g. "will there be Birds-of-a-Feather sessions" or "what 6th Street bar might feature Jim Blake singing folks songs?"

...