Skip to end of metadata
Go to start of metadata

Calls are held every Thursday at 1 pm eastern daylight time (GMT-5) – convert to your time at

These calls now use WebEx – see the "Call-in Information" at the bottom of this page.

Please add additional agenda items or updates --

Jon Corson-Rikert will be leading this week's call.


  • Brown – on Monday sending out a memo to 767 faculty asking them to look at VIVO profiles and correct and update them in the next couple months – looking for a February launch. Tapping into other campus data layers for authentication, department information, and courses."
  • Colorado – releasing 1.5.1 for the Colorado Springs campus. Have the git-based release working; for the Boulder (main campus) data will put it on a test server today and hope to roll out to production next week, depending on what is found. Made a couple of fixes yesterday to sorting of positions on a person's profile and sorting of degrees – changed the ordering of sort operations. The approach that Stephen set up for using GitFlow allows them to push a release to either the test or production environment from a development laptop. Uses a post-receive hook to push to the desired server. Will post documentation on the wiki to describe the process when it's fully in place.
  • Cornell – release into production of the "quick view" and "full view" page templates for people. Might move the current foaf:person template into the Wilma them. Have other sites had feedback that VIVO is competing with their personal/department website? Stephen – people want their own web pages linked. Eric – did 2 things at UCSF to make people happy – did make it possible to add links to their departmental websites (and automatically populated them), and made it possible for faculty to grab publication lists from the Profiles research networking system for display on their departmental pages. Have also put so much search engine optimization, the research networking tool almost always comes up first. At UCSF is a real effort by central IT and central executive office to have a single central profile page for everyone, including staff, and see it as a benefit to not have such a high degree of variation across independent systems – an enterprise reference URL. Stanford has done a very good job of gaining acceptance of the CAP system – layering in social networking in a similar way that UCSF is, despite being heavily decentralized organizationally – recognition that some kind of social networking system will be important and it just can't happen on top of a completely decentralized set of independently managed systems.
  • Duke – Did a first import of 133,000 publications from Symplectic – took a little over a week. Will be doing some optimizations, but they look very good – coming in through ReachNC, a SciVal product. Does have the co-author relationships, and are linked for people at Duke. Not trying to make foaf:person stubs for non-Duke people – don't show up on the visualizations, but you do know that any author on the visualizations is another author at Duke.
  • EPA
  • Florida
  • Indiana
  • Johns Hopkins
  • NYU --NYU does have an enterprise research board that tries to unify all the systems under one profiling system, but using something based on PeopleSoft now – executive decision. NYU is very top-down and centralized, but has multiple campuses, each of which is on their own – e.g., medical school, main campus, NYU Poly, etc. – and each campus has bought their own system. Will have to come down from the Provost level.
    Sandy recovery – services are slowly coming back on line. Some clinical departments were seeing patients soon; hospital was slower. All research involving animals was lost, and imaging equipment that was too heavy to move was destroyed. Main IT infrastructure is in New Jersey, but the test servers for VIVO were local and were flooded – did lose the ingest so will have to re-run the Harvester and re-import everything again. Had completed rewriting the search ranking algorithm to optimize discovery of people – matches what had previously with an in-house system. Has been a delay to get infrastructure going again. Glad to hear that the code is on Github"
  • Penn
  • UCSF – working hard to get the RDF version of Profiles in place by end of year. OpenSocial building a new website and looking for news about VIVO and Open Social. Harvard has a very specific version, and one other new Profiles site has started with the RDF version, but UCSF will probably be the first major one. In fact the next version of RDF Profiles might come out of the UCSF version, and might possibly host Profiles for other UC sites.
  • Weill - 1) Upgraded to 1.5.1 2) How to "Person" from barchart on front page? And adjust the total count? 3) Performance tuning - Squid?

Three-tier build

Stephen has been working with Jim's three-tier build pattern at Colorado and finds it very useful – something we started doing at Cornell to go beyond Vitro and VIVO to a third layer with additional customizations for VIVO Cornell. We wanted to be based on the standard VIVO but had a lot of local mods that we wanted to take precedence. Stephen started doing this at UF on a sub-project, and has now operationalized it at Colorado.

This might be a good thing to get started with when moving to Github. It's a mix of code and documentation – an example build script, plus additional documentation.

Any way to have new code that could be cherry-picked bug fixes by specific check-in into a forked local branch? Jim – we're still pretty new with Git here at Cornell – trying to establish processes that can leverage the branching capabilities and the pull requests. Sometimes we do put a bug fix into trunk as well as our local branch, but the trunk gets new development as well as bug fixes. Yin – if there's a way to identify what's a general bug fix, that would be helpful. Jim – happy to listen if there's ways to do this or any other improvements.

Strategy for alerting people of bug fixes

Alex has been looking at other projects using Git and notices that they use the Git issue tracker for bug fix alerts, making it easy for people who may not follow the project closely to find updates that they may wish to use before the next release. While we will likely continue to manage our backlog and new development in a separate Jira instance (currently at Cornell but soon at DuraSpace), not all developers may realize that's where they should go to look for documentation on changes.

Wiki Move Update

Jim Blake has progress to report on his preparations for the move of this wiki from SourceForge to DuraSpace.

Proof of concept is at
which you may browse

No page histories.

We are negotiating a date now. I will attempt to schedule it over a weekend:

  • Announce freeze on a Friday, at close of business
  • Convert over the weekend.
  • Duraspace team completes the migration on a Monday (hopefully Dec 10)
  • Announce the location of the new wiki space

How to "shut down" the SourceForge wiki?
Put a prominent banner up, state that this is no longer the home of the wiki, and that any changes will not be migrated. Could also remove editing privileges (brute force).


Jim has also developed an approach to internationalization of the VIVO interface using Java resource bundles to manage text strings in multiple languages. He will demonstrate a working example, describe the technical approach, and requests feedback.

My slides and supporting files can be found at

Notable Development List Traffic

  • what's up with's being moved from an Amazon EC2 instance at UF to a virtual machine at Cornell. We hope to get it back in service this week
  • setting the default selected menu item to always be the top item
  • missing inverse property statements between faculty members and performances
  • suggestions for embarking on data ingest to match up with Symplectic data in a new VIVO


  • map of science and temporal graph visualizations – Chin Hua from the visualization team at Indiana University wrote to say he is working on another project but will get back to improving the visualization caching work in December

Call-in Information

Topic: VIVO weekly developer call

Date: Every Thursday, no end date

Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)

Meeting Number: 645 873 290

To join the online meeting

To view in other time zones or languages, please click the link:

To join the audio conference only

Access code:645 873 290

last meeting | next meeting