Calls are held every week at 1 pm eastern standard time (GMT-5) – convert to your time at http://www.thetimezoneconverter.com

Please add additional agenda items or updates

Updates

  1. Colorado
  2. Cornell – working through minor issues, updating courses and HR, and preparing a 1.4.1 bug fix release
  3. Duke – updated pilot instance, getting into grants more, working with web service group on changes to branding
  4. Florida – updating to 1.3 and dealing with folder permissions issues; fixed breaking tests and libraries in Harvester and modifying based on UF ingests; refactoring some code
  5. Indiana
  6. Medical College of Wisconsin
  7. North Texas – "trying to make sense of a PHP/MySQL faculty reporting system – going to Google Scholar for pubs and NSF for grants
  8. Notre Dame
  9. Stony Brook – "Tammy working with ways to list Pubmed; is there a way to hide local titles? have done a lot modification of individual pages
  10. UCLA – "trying to restore a MySQL database from a VIVO RDF dump – could add a feature to dump out all of the RDF graphs in VIVO using a serialization that retains the graph ids, producing a single file that could have all the information you would need to restore a VIVO from an RDF dump
  11. Weill Cornell – preparing to upgrade to VIVO 1.4; fixed index builder for our "community search tool" (local vivosearch.org implementation), it is now able to index more than 9000 faculty members across Cornell VIVO and Weill VIVO instead of the previous 30; for info regarding local implementation of vivosearch.org, go to How-To: Implement a multi-institutional search site
  12. Any other sites represented

Notable Development List Traffic

  • Mummi Thorisson – I wonder if anybody has come across & looked into specs coming out of the W3C Provenance working group, in relation to provenance of data loaded into VIVO repositories? There's a recent blog post from Paul Groth, one of the chairs of the working group. The PROV model primer includes some example Turtle RDF.
    Update on collaborative project with ORCID and VIVO – working on report. ORCID technical working group involved in hiring permanent staff – there is an API simulator on the ORCID Github account that demonstrates what the ORCID api will do and uses OAuth, and some specification documents. http://vivo.crossref.org running 1.3 - do a virtual machine machine snapshot? Stephen and Mummi will be in touch
  • WashU – Filter performance in a SPARQL query, individuals not showing up in the UI and search index is not completing – sent a report to the list with log messages. Index has been running more than 24 hours; elapsed times in the logs start showing negative numbers after a while (probably a red herring). Jim is working with Brian Caruso to evaluate.
  • NIH – harvesting an internal HR database
  • Otago – upload photo error solved by setting a Catalina option for a "headless" Java (export CATALINA_OPTS=-Djava.awt.headless=true). Happens when trying to rescale an image for a thumbnail – not clear why AWT was trying to get a console, but specifying a headless AWT solves the problem. Extending the ontology to describe datasets, data property vs. object property
  • Medical College of Wisconsin – where is vivosearch.org going, how can they participate using data from their existing faculty database
  • Sourceforge HTML page has old SVN version number – may have caused Melbourne's issue with a java file missing from maintenance branch appears related to version. Stephen is looking into this and will contact the list.

Other topics

  • Should VIVO participate in CTSA Research Networking Affinity Group subgroups
    Policy
  • Holly Falk-Krzesinski (Northwestern) (co-lead)
  • Jihad Obeid (MUSC)
  • Griffin Weber (Harvard)
  • Kristi Holmes (Washington University)

Deployment

  • Yin Aphinyanaphongs (NYU)
  • Dave Eichmann (U Iowa)
  • Holly Falk-Krzesinski (Northwestern)
  • Jihad Obeid (MUSC)
  • Griffin Weber (Harvard)

Prototyping

  • Yin Aphinyanaphongs (NYU)
  • Dave Eichmann (U Iowa)
  • Titus Schleyer (U Pitt)
  • Griffin Weber (Harvard)
  • VIVO 1.4.1 maintenance release with minor bug fixes
    • template errors
    • race conditions in FreeMarker
    • faster generation of autocomplete lists
    • improved rendering of dates on grants
  • Vivosearch.og
    • how it works
    • its current state as a prototype
    • how to make your data compatible with it –
      • URIs
      • RDF compatible with the VIVO ontology
      • the services required
    • how to advocate to have vivosearch.org become a permanent, supported site
    • what would be required to set up a vivosearch-style search for another set of data sources
  • From Miles Worthington – the new linked-data-api spec and 2 implementations

Next week

Call-in Information

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

last meeting |  next meeting

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.