Calls are held every Thursday at 1 pm eastern standard time (GMT-5) – convert to your time at http://www.thetimezoneconverter.com
Please add additional agenda items or updates – we always welcome suggestions
- Brown - hiring!
- Colorado - getting department data in, and focusing on prep for the Implementation Fest
- Cornell - has a renewal of Provost funding; working
- Duke - "has hired an ontologist
- Florida - "Peoplesoft ingest from a messaging service; working on the ability to hide information in VIVO and remove ancillary information such as pictures without discarding the data – a secondary TDB graph outside of VIVO; subsequent harvests can then put that data back in, as in the case when a person's record is marked private and then made public again. Working on Rochester CTSA intellectual property harvest from 60 universities and putting that in a test VIVO instance with help from regular expression pattern matching. Also working on the CTSAconnect project work (see http://ctsaconnect.org)
- Indiana - "Working on continuing to bring in more data from other campuses – once have gotten to a sufficient point of progress, will use a web service provided by SciVal experts at the Med School. Also planning on when to do the upgrade to v1.4, now that they have a developer.__
- Johns Hopkins -
- North Texas - "continuing to work with data
- Scripps - "deduplicating article titles (Stephen is helping with an endless loop problem in Harvester script – the score keeps running)
- Stony Brook - co-author visualization changes – reading the fine print about thresholding so can explain if not all co-authors are showing up.
- Weill Cornell - Eliza has checked in the code and configuration files of Scopus Harvester to Github, and is testing larger scale ingest of publications using Scopus Harvester.
UF Demos and Discussion
Stephen Williams led a demo and discussion of GitHub.
- GitHub is all about code; while it has a basic wiki and issue tracker, we may well want to stay with SourceForge (MediaWiki) and Jira for those functions
The site works with SSH keys, not passwords, so takes some getting used to
- Developers work out of the*develop repository and typically create new branches when they start work for a new feature or release
- These developers then do a*pull request before their work is pulled into the main develop repository
- At the appropriate time, all of the changes from*develop are merged into the master
- A pull request provides an opportunity for one of the admin developers on the project to review the commits individually or as a group before accepting or rejecting them
- It would also be possible to release a modified version of the code from a branch, were someone to want to do that
Chin Hua from IU also pointed out that it's possible to fork the code, or create a complete local copy, usually with the intention of doing independent development, that may or may not be submitted back to develop via a pull request
Features for VIVO 1.5
Based on last week's discussion, Jon has added more VIVO 1.5 features to http://vivo.ideascale.com for review, comment, and voting.
Notable Development List Traffic
- position at Brown University
- CVs and biosketches
- Solr configuration
- co-author sqarql
- finding duplicate article titles
- OSCON 2012
Implementation Fest update
Registration is open for the Implementation Fest at http://vivoweb.org/2012-vivo-implementation-fest
Send announcements to the development and implementation and ontology lists.
VIVO Book, Chapter 5 Extending VIVO, aka the Dev Chapter
- Updates from Chris Barnes
An outline and some sections are already there – and we have a fair amount of material from previous presentations. Looking for material even if you don't consider yourself a writer of exquisite prose.
Items for next week
The University of Florida will demonstrate the latest on their course ingest and their implementation of logging for the Harvester and for VIVO itself, including the ability to produce reports of all the changes made to the UF VIVO every day.
1. Please join my meeting. https://www1.gotomeeting.com/join/322087560
2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.
Dial +1 (773) 897-3008
Access Code: 322-087-560
Audio PIN: Shown after joining the meeting
Meeting ID: 322-087-560