Skip to end of metadata
Go to start of metadata


Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:



(star)  Indicating note-taker

  1. William Welling 
  2. Andrew Woods 
  3. Bruce Herbert (star)
  4. Ralph O'Flinn 
  5. Brian Lowe 
  6. Michel Héon 
  7. Don Elsborg 
  8. Huda Khan
  9. Benjamin Gross


  1. Community questions
    1. Error when trying to link a person with a grant
  2. Update from VIVO Leaders meeting
  3. Don Elsborg : Explore using the i18n files to store local institutional RDF label and description changes.
  4. Current community sprint updates?
    1. ORCID
    2. Kafka
    3. Messaging
  5. 1.11.2 patch release
    1. VIVO-1929 - Getting issue details... STATUS
    2. VIVO-1943 - Getting issue details... STATUS
  6. Working towards 1.12
    1. To be reviewed 
      1. VIVO-1918 - Getting issue details... STATUS
      2. VIVO-1934 - Getting issue details... STATUS
      3. VIVO-1937 - Getting issue details... STATUS
      4. VIVO-1944 - Getting issue details... STATUS
    2. Documentation needed
      1. VIVO-1914 - Getting issue details... STATUS
    3. 1.12 release planning
      1. Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
      2. Sprint to test merge of sprint-18n into master: week of Jan 25th
      3. 1.12 release candidate #1: Feb 1st
        1. Two week RC-1 testing period
        2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      4. Do we want the `war` install in 1.12? - VIVO-1443 - Getting issue details... STATUS
  7. Tickets that should be close to merge
    1. VIVO-1652 - Getting issue details... STATUS
    2. VIVO-1734 - Getting issue details... STATUS
  8. Post-i18n priorities
    1. VIVO-in-a-box
    2. Messaging
    3. Moving Scholars closer to core - next steps

Future topics

  1. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be?
  2. Renaming of 'master' branch? (ZDNet, BBC)
    1. Guidance from GitHub 
    2. DSpace has done it
    3. Fedora has done it
    4. Samvera is doing it
  3. Incremental development initiatives
    1. VIVO-1688 - Getting issue details... STATUS
    2. VIVO-1751 - Getting issue details... STATUS
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven


  1. Status of In-Review tickets

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due


Draft notes in Google-Doc 

Community questions

  1. Error when trying to link a person with a grant
    1. Juan has provided some information.  VIVO is swapping some variables in his instance.  The error has not been reproduced by developers. It is a URI variable.  Brian: maybe he has a invalid URI that is being used later.  The value is not substitutable. 
    2. Is there a SPARQL query that Juan could run?  Brian suggested a query. 
    3. ASK { <> owl:inverseOf <> }

Leadership Group approved next release schedule

The schedule:

  1. Final review and merge of the i18n into the core codebase
   - One week-long sprint during the week of Jan 25th

  2. Publication and community testing of a release-candidate (RC-1)
   - Two week-long period of community testing from Feb 1st through Feb 12th
  3. Iteration based on community testing (RC-2, RC-3, etc)
   - Each iteration will be another two weeks. We should expect at least an RC-2, maybe more.

  4. Final release of VIVO 1.12
   - Optimistically, early March

Leadership Group applauded the strong UQAM and TIB contribution.

Michel, Brian, Benjamin, and William all can contribute to the sprint.

Don Elsborg : Explore using the i18n files to store local institutional RDF label and description changes.

Discussion: can i18N be used to create local labels aligned with institutional context.  Don talked about need at UC Boulder. Michel thought this was not good practice. Brian had an idea that would take more development effort.  Short term solution is update to VIVO file and then make changes there.  At TAMU, we use the UI to customize the ontology.

Don: asked that when an upgrade to newer version of VIVO, are local changes preserved?  Brian explained that it depends. Andrew suggested that the release notes contain instructions to address this potential issue. Benjamin: The current 3rd tier process would still work, but there are some new files that will need to be overlaid (see difference between two propertyconfig files above)

Brian suggested a potential solution. 

  1. Have a separate directory (following on the first time change detection work ongoing) that will detect triples we want to overlay. 
  2. Changes are made and then the software lays over the graph. 
  3. Benjamin: This would be nice since we would only need to track our specific changes, rather than having to totally overlay the file that contains the one or two changes we want to make.

Current community sprint updates

  1. ORCID
  2. Kafka
  3. Messaging



  • No labels