Calls are held every Thursday at 1 pm eastern daylight time (GMT-5) – convert to your time at http://www.thetimezoneconverter.com
Please add additional agenda items or updates – we always welcome suggestions
- Weill Cornell – 1) Thanks to Vincent of UFL for consultation on implementing Shibboleth. Surprising behavior asking users with no profiles to create a VIVO account. Possible to suppress this feature? Jim will look at where the account creation is triggered and confer with Eliza about the options Weill would prefer. Note that the code does not create a profile, just a user account. 2) Problems encoding special characters during PubMed Harvester ingest. Data (vivo-additions.rdf.xml) seem properly encoded. Just not sure why the encoding couldn't make it to VIVO. e.g. should it be β or β in the vivo-additions.rdf.xml file? It may be necessary to add a method in the harvester to read in the additions file and convert any Latin-1 (ISO-8859-1) characters to UTF8 – Stephen indicated UF would look into whether there is the same issue at UF that had just not been detected yet, or whether there's a difference in default character sets between the Mac (Weill) and Linux (UF).
- Colorado – have been meeting with their Laboratory for Atmosphere and Space Physics (LASP), who are interested in running VIVO but adding additional detail about instrumentation including satellites. Stella helped out with questions at one of the meetings. Otherwise evaluating 1.5 to see about when to update.
- Florida – finishing up the people harvest using biztalk messages for updates instead of database access; the harvester team is looking at 3 possible ways to reduce memory usage in the harvester – upgrading jena, changing the jenaconnect query to bring back only a subset of the VIVO data model, and testing to see whether SDB's performance is fast enough that the harvester can query dynamically for scoring and other purposes. They will want to work with Cornell on how they might leverage the RDF API in v1.5. It would be appealing to add a connection to a SPARQL endpoint as a new type of datasource for the harvester.
- Duke – has their hiding feature in test; this allows a person to remove any unwanted data from their profile. The data are removed from VIVO but the identifier in the source system is stored in a hides table and consulted with each subsequent data load. Enough information is stored with the hidden identifier to offer the profile editor a choice of bringing the data back, at which time new data is fetched from the appropriate source system of record. Duke is also testing ingest of data from Symplectic Elements via their library, and will be working on areas of interest next month; Pat Gamsby has been in touch with Jon about coordinating with Cornell and potentially Colorado
- Still tracking down links and references to 1.4 on the wiki, vivoweb.org, and sourceforge – and we welcome help welcome in identifying missing documentation and/or outdated links
- Collecting issues for a VIVO 1.5.1 maintenance update
- Vitro installation guide
- new data property default list view files in the VIVO productMod but not Vitro
- please notify us of other bugs and/or omissions and confusing or missing documentation
- need to make instructions for adding HTML menu pages clearer – if the desired HTML is in the custom template already, there's no need to put HTML into the page management form, but the field is required to be non-empty on the form. This will be fixed in 1.5.1, but for now it would work to just put a tag into the form to make the validation work
- Schedule very close to being finalized and released
- Taking proposals for BOF sessions
- Seeking session moderators
- Will be asking all implementing sites to prepare a simple poster using (optionally) a provided template to minimize the work required – emphasizing that these do not have to represent completed work or public production VIVO instances. There will be a lot of interest at the conference in seeing the full range of VIVO projects, no matter how new and exploratory.
Notable Development List Traffic
- Developer documentation and codebase from the Melbourne Central Research Data Registry, prepared by Tom Sullivan and Judd Kirby of ]
- building the DV Docs code locally (see also How to implement a Digital Vita CV and biosketch web service for VIVO Eliza recommends downloading the XSPARQL Jar files from the Digital Vita repository rather than recompiling them locally
- referencing profile photos across sites - Jim has been in touch with Tammy
- VIVO Harvester install docs not clear on connecting to VIVO with 1.4 changes – Chris Haines has been working with Jess Meek and Stephen will check in to see whether additional questions or issues remain
- VIVO with Fuseki SPARQL endpoint – Vince sent a link to the full Fuseki package with all of the jars and files that are required. If this tar file is extracted to a location, it has a service script and shell script for starting it automatically.
- 1.5 page management – Tim Worrall worked this out with Tammy – if the HTML for a menu page is in the custom page template already, it's only necessary to put anything in the HTML field on the 'add menu page' form because of form validation; we can fix that with 1.5.1
- VIVO at Eindhoven University of Technology and a Youtube video of a research output discovery application based on that VIVO installation
Items for next week or as information becomes available
- options for migrating off the SourceForge hosted wiki
- the larger question of whether and when to move to Github (possible guest speaker from Github in the next few weeks)
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