Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. William Welling 
  2. Andrew Woods (star)
  3. Ralph O'Flinn
  4. Brian Lowe 
  5. Michel Héon 
  6. Don Elsborg 
  7. Sandra Mierz
  8. Sarbajit Dutta
  9. Paul Albert
  10. Huda Khan

Agenda

  1. Community questions
    1. Updates? "Site admins" unable to add People (email)

    2. "Sparql API data limits" (email)

  2. Michel Héon : UQAM VIVO/Kafka sprint in Dec
  3. Sarbajit Dutta : Demo/Deep-dive into setup and scenario resulting in surprising TDB performance
  4. Don Elsborg : Explore using the i18n files to store local institutional RDF label and description changes.
  5. Working towards 1.12
    1. To be reviewed 
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Documentation needed
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    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? - Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  6. Tickets that should be close to merge
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  7. Post-i18n priorities
    1. VIVO-in-a-box
    2. Messaging
    3. Moving Scholars closer to core - next steps
  8. Moving Data Ingest Task Force forward

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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

  1. Status of In-Review tickets

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Draft notes in Google-Doc 

General discussion

  1. Sandra from German National Library is working on integrating ReCiter with VIVO

UQAM / TIB

  1. Kafka sprint in Dec
  2. Pre-sprint planning Wed (tomorrow) morning
  3. Interest in ingesting from ORCID
  4. Success for the sprint includes:
    • example of extracting data from ORCID
    • example using Kafka for ingest

TDB experiences

  1. 50 pubs (these numbers may not have been transcribed correctly)
    • TDB: 148sec when loaded one-by-one
    • TDB: 10sec when loaded all-together
    • SDB: 21sec when loaded one-by-one
    • SDB: 19sec when loaded all-together
  2. Weill Cornell's ingest is heavy on abstracts
  3. Inferencing is disabled
  4. Tip: Tomcat config needs to be increased: Max-post-size
  5. Epiphany: there is a Jena bug:
  6. General comments on SDB/TDB https://wiki.lyrasis.org/display/VIVO/2019-12-06+-+Special+Topic+-+TDB+vs+SDB
  7. Point release would be valuable with:
    • edit config resolution: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Jena patch or upgrade: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  8. Sarbajit to perform more tests with patch



Actions

  •  



  • No labels

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