Date

Call-in Information

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

To join the online meeting:

  • https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09

    Meeting ID: 843 7861 5572
    Passcode: 556561
    One tap mobile
    +16699006833,,84378615572#,,,,*556561# US (San Jose)
    +19292056099,,84378615572#,,,,*556561# US (New York)

    Dial by your location
            +1 669 900 6833 US (San Jose)
            +1 929 205 6099 US (New York)
            +1 253 215 8782 US (Tacoma)
            +1 301 715 8592 US (Washington DC)
            +1 312 626 6799 US (Chicago)
            +1 346 248 7799 US (Houston)
            877 853 5257 US Toll-free
            888 475 4499 US Toll-free
    Meeting ID: 843 7861 5572
    Passcode: 556561
    Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. Georgy Litvinov 
  3. Brian Lowe (star)
  4. Benjamin Kampe 
  5. William Welling
  6. Michel Héon 
  7. Huda Khan              
  8. salm

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. We are back in a weekly meeting mode
    2. VIVO conference - probably postponed for a couple of months (spring 2023)
    3. i18n issue with ordering and filtering by the first letter 
      1. https://github.com/vivo-project/Vitro/pull/321
      2. https://github.com/vivo-project/vivo-solr/pull/6
    4. Dynamic API
      1. reengineering of io - https://github.com/vivo-project/Vitro/pull/319
      2. SHACL based validation - https://github.com/vivo-project/Vitro/pull/297
    5. NORA and Research Portal Denmark - https://forskningsportal.dk/about-research-portal/events/   
    6. Rename googleAnalytics.ftl to webAnalytics.ftl - https://github.com/vivo-project/VIVO/issues/3735
  2. VIVO development fund - https://docs.google.com/document/d/1k_fzP8O59Um1FnePje7JKGlKzfqv4dzxgYN4oqPCpu8/edit?usp=sharing
  3. DSpace-VIVO integration further steps - https://docs.google.com/document/d/1bYRH4fl4ubOoq6KmxCxGSofHRd9iF7m7gV2tDZDUJYs/edit?usp=sharing
  4. The next sprint
    1. When?
      1. 19.09. - 07.10. 
    2. What?
      1. Improvement of expressiveness of notation
        • Iterative steps
        • Operation data / DataStore - should be ready before sprint 
      2. Improvement of UI
      3. Completion of authorization and authentication 
      4. Extension of SHACL rules
      5. Editor for definition of a dynamic action
      6. VIVO based on dynamic actions
    3. Who?
      1. https://forms.gle/qLi1PhRrrpvUrrYRA

Notes

  1. Questions/Issues/Pull requests/Announcements
    1. Talk of trying to merge with Open Repositories or Expert Finder Systems
    1. https://github.com/vivo-project/Vitro/pull/321
    2. https://github.com/vivo-project/vivo-solr/pull/6
      • Reviewed by Dragan and Matthias; should be able to be merged.
      • William: What are the semantics of the next release?  Is it a patch release?
      • Georgy: this PR is a bugfix.  Existing multilingual sites will experience improper sorting without it.
      • Dragan: bugfix is important; has been reported multiple times.  Something the community is looking for.
      • Georgy:  Fix is backwards compatible.  User doesn’t need to change anything.
      • Dragan:  Traditionally haven’t had patch releases; have moved forward with a new minor release.  I can prepare release(s).  Testing is always the hardest part.  Do we have testing capacity?
      • Need to make a new release of vivo-solr.
      • Managing vivo-solr changes and/or reorganizing should be discussed during committers’ meeting.
    1. reengineering of io - https://github.com/vivo-project/Vitro/pull/319
    2. SHACL based validation - https://github.com/vivo-project/Vitro/pull/297
      • Need review/merging.
    1. Brian:  Potential for existing sites to have problems if googleAnalytics.ftl is no longer included; sites using third tiers probably overlay this file and if they don’t rename appropriately, might lose analytics.  Maybe we could conditionally include googleAnalytics.ftl if found; not sure if Freemarker allows this.
    2. Dragan:  Potentially not a big enough benefit to worry about if there’s a risk of problems for existing sites.  Will discuss more with Christian.
    1. We are back in a weekly meeting mode
    2. VIVO conference - probably postponed for a couple of months (spring 2023)
    3. i18n issue with ordering and filtering by the first letter
    4. Dynamic API
    5. NORA and Research Portal Denmark - https://forskningsportal.dk/about-research-portal/events/   
    6. Rename googleAnalytics.ftl to webAnalytics.ftl - https://github.com/vivo-project/VIVO/issues/3735
  2. VIVO development fund - https://docs.google.com/document/d/1k_fzP8O59Um1FnePje7JKGlKzfqv4dzxgYN4oqPCpu8/edit?usp=sharing
    • Dragan: important items, but need to be attractive to potential donors.
    • Dragan: Some topics are already included under the adoption/customization heading.
    1. New contribution option separate from membership.
    2. Effort to define features in which the community might be interested in investing money. Draft list in linked document. Includes cloud/cross-site scalability, interoperability with other software/data sources, UI.  
    3. Georgy: proposed addition of core maintenance needs
    4. Brian:  Could potentially build in “overhead” type percentage into donations, so that we could allocate some funding for critical core maintenance.  The other features depend on this, and shouldn’t seem like a foreign concept to donors.
    5. Dragan:  Could be added to another part of the development fund proposal.  Also the question of whether people will donate to specific features or make general donations if they are in agreement with the project roadmap.  Maintenance would be built into that roadmap.
    6. Michel: The  need for ingest tools may be greater than that for UI decoupling, for example.
    7. Dragan:  Document will likely be discussed at tomorrow’s (Wednesday’s) Leadership Group meeting. Please comment before then if able.

Draft notes in Google Docs

Task List

Previous Tasks 

  • No labels

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