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 
  3. Brian Lowe
  4. Huda Khan 
  5. Benjamin Gross (star)
  6. Nicolas Dickner
  7. Georgy Litvinov
  8. Ralph O'Flinn
  9. Michel Héon 
  10. Benjamin Kampe 

Agenda

  1. Sprint updates
    1. 1.12 release planning
      1. Merge and test of sprint-18n into master: week of Feb 8th
      2. 1.12 release candidate #1: Feb 15st
        1. Two week RC-1 testing period
        2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      3. 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.
        1. Next steps?
  2. Inference mechanism: how to activate the mechanisms to infer universal and existential restrictions
  3. Potential patch releases?
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  4. Tickets that should be close to merge
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  5. Post-i18n priorities
    1. VIVO-in-a-box
    2. Ingest / Kafka
    3. Advanced Role Management
    4. 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. 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 

    1. Sprint updates
      1. Merge and test of sprint-18n into master: week of Feb 8th
      2. 1.12 release candidate #1: Feb 15st
        1. Two week RC-1 testing period
        2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      3. Do we want the `war` install in 1.12? - VIVO-1443 - Decouple VIVO build from installation REOPENED
        1. Next steps?
        2. Still interest in this? 
        3. William Welling is still potentially interested in taking it over the line.
        4. William - question, should I prioritize this over i18n work? Andrew- Yes please
        5. End result should still meet the needs of people that are customizing VIVO
        6. Won’t automatically move into Tomcat
        7. Home directory management - will require the VIVO webapp to deploy the home directory during startup 
        8. Michel: Does the delivery of 1.12 depend on finishing this ticket? Andrew: Maybe. There is a lot of interest. Benjamin - optimistic that it will get done, but wouldn’t want it to be a blocker for 1.12
      1. Andrew: Planning on a wrap up meeting on Friday. 11am perhaps to give people a little time to wrap things up
      2. Andrew q to Georgy: Are Russian translations of interest for VIVO? Georgy: I have started it two years ago, a year ago started this project and have been waiting for a release to continue working on the translation. Will there be translations in ontologies, as well? Andrew: Will be documented. Will be looking for input. Re: ontologies documentation should also include this. Since annotation properties are stored in RDF. Brian: All that must be altered are 1. Properties files 2. Set of RDF get loaded for language-specific labels for ontology entities 3. Some templates (.ftl)
      3. Sprint - progress is being made, people are self--assigning tickets 
      4. Discussion on capability map issue: There are multiple objects (instead of multiple labels on a single object). Perhaps could be changed from a CONSTRUCT query to a SELECT query which is easier to work with using the filter. See https://github.com/vivo-project/VIVO/commit/f32dea3628d8a0d8570ad9edead4ac15fe349816#diff-4697ae5cbe1a399c32538efd6[…]78724a0f2b131bce789bfR168-R187 for example
      5. Regression test PR- one minor change https://github.com/vivo-community/vivo-regression-tests/pull/5 Andrew will help
      6. NIcolas - working on splitting out large PR into separate smaller ones
      7. Andrew - focusing on resolving open PRs/reviews
      8. 1.12 release planning
    2. Potential patch releases?
      1. VIVO-1950 - Google visualization libraries not loading - sparklines broken OPEN
      2. Don Elsborg , any interest in picking this up?
  1. Inference mechanism: how to activate the mechanisms to infer universal and existential restrictions
    1. Michel - would like to see in abox, in the individual
    2. Brian - That’s an unimplemented feature. Could repurpose the simple reasoner but may not be a trivial amount of work.
    3. Michel - JFact can make inferences on instances. But not implemented within VIVO.
    4. Brian - originally there were no good solutions because memory was too limited to perform reasoning on the entire abox, but the tbox can sit in memory just fine. 
    5. Michel - what’s the shortest path forward? Brian - suck your whole abox into JFact (in memory), maybe servers can support this now. Could even alter RDF service so it talks directly to JFact.
    6. MIchel - is there documentation on the current reasoner? 
    7. Brian - nothing up to date 
    8. We allow people to edit the tbox… that can have huge consequences in running production VIVOs, i.e. result in millions of new triples depending on how the reasoner works
    1. Brian - are the inferences in the tbox? Were you expecting to actual individuals to get properties? 

Actions

  •  



  • No labels

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