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. Alexander (Sacha) Jerabek  
  4. Benjamin Gross (star)
  5. Ralph O'Flinn
  6. Huda Khan
  7. Don Elsborg
  8. Brian Lowe

Agenda

  1. i18n update
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - need one more review, Benjamin Grosshas "approved"
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - the final lynchpin
  2. Simplifying installation
    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.
      1. Two tasks: process for auto-configuration and determining the correct configuration
  3. Moving Scholars closer to core - next steps
    1. SelectQueryDocumentModifier
    2. Entities: Collection, Concept, Document, Organization, Person, Process, and Relationship
    3. Configuring Solr
  4. Moving Data Ingest Task Force forward
  5. Renaming of 'master' branch?
    1. Update: "GitHub to replace 'master' with 'main' starting next month"

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
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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. i18n update
      1. Andrew - I don’t think much has been done since our last call. True.
      2. VIVO-1848 - i18n: Improve Identification of files to filter IN REVIEW - need one more review,
        1.  Benjamin Gross has "approved"
        2. Another review would be preferred 
        3. Removes the available.langs file
        4. Changes structure of rdf directory - see https://github.com/vivo-project/Vitro/pull/169 for the new directory structure
        5. Retains the directory of the language agnostic files from before
      3. VIVO-1885 - i18n-regression-test documentation IN REVIEW
          •  Just here FYI
        1. Andrew: It’s challenging, but he’s gotten it to work from the documentation
      1. VIVO-1918 - i18n: Reload firsttime files on start-up if changed IN PROGRESS - the final lynchpin
        1. Leading to a more exciting discussion on RELEASING THE BETA (of the merged i18n work).
        2. Brain Lowe should have an opportunity to work on it in October
        3. Brian: Is there still a concern about page rendering speed with language filtering turned on? 
        4. Andrew: Is caching a possibility?
        5. Brian wants to look at the filtering mechanism algorithm. The actual amount of data returned when languages are enabled is not significantly more, but we lose a lot of time in the filtering mechanism itself.
        6. Or can we order the result set from the queries so the language data is grouped together?
        7. Andrew: Is there a small example dataset to evaluate the difference between languages on and off?
        8. So remaining issues: Reload firsttime, performance, and a boatload of documentation (Andrew points to Sacha gently)
        9. Does it make sense to schedule another sprint? 
        10. Ralph: Perhaps a two week sprint? Andrew: Perhaps first week, finish i18n work then second week prepare the release.
        11. Ok, so do we need a sprint? If so, what is the nature of the sprint? Sacha says he could focus on documentation for a week. Brian and Benjamin will not be able to devote an entire week to a sprint. Others may be able to participate (eg Dominik) and we will rely on the committers for reviews.
        12. Huda will provide ONE WEEK of moral support 
        13. Andrew will attempt to schedule with Ralph and Sacha (plus Dominik and Mathias and UQAM folks).
    1. Distillation of priorities: https://docs.google.com/spreadsheets/d/17tfl5-q8DmRTI-Vc2MiONsscaQ4JBlAWy7SbvzXdL40/edit#gid=0
      1. Note #7 - simplifying installation
    2. Simplifying installation
      1. VIVO-1443 - Decouple VIVO build from installation IN PROGRESS
          • Not actively in progress
    1. VIVO-1752 - Instantiate Solr core via API OPEN
      1. Two tasks: process for auto-configuration and determining the correct configuration
      2. See updates to https://jira.lyrasis.org/browse/VIVO-1752
      3. TAMU uses a Spring solr library to manage the schema. Still requires an initial config. 
      4. It’s not clear if Solr is really intended to be built this way
      5. Andrew is concerned if Solr exists outside the VIVO server
      6. Brian reports that in the past people have requested having Solr on a separate server… but we don’t usually do that.
      7. Brian - even if we can’t create the config via API perhaps the Schema could be created?
      8. Spring API solr requires a collection to exists… could be default. Will read your annotated solr document files and update the schema for you.
        1. Some gotchas… e.g. can’t mutate certain types of fields
  1. Moving Data Ingest Task Force forward
    1. Haven’t heard from them in awhile
  2. Renaming of 'master' branch?
    1. Update: "GitHub to replace 'master' with 'main' starting next month"
    2. Might still be some work on the GitHub side for easy migration


Actions



  • No labels

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