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 
  4. Benjamin Kampe 
  5. William Welling
  6. Michel Héon 
  7. Huda Khan (star)             
  8. Jose Salm
  9. Veljko Maksimovic 

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. We are back in a weekly meeting mode
    2. Rename googleAnalytics.ftl to webAnalytics.ftl - https://github.com/vivo-project/VIVO/issues/3735
      1. We decided to close this issue
  2. VIVO 1.13.0 RC-4 prepared and ready for testing
    1. Release Testing - 1.13.0
    2. Deadline - 8/31/2022
  3. Dynamic API
    1. Decoupling SparqlQuery- https://github.com/vivo-project/Vitro/pull/327
    2. SHACL based validation - https://github.com/vivo-project/Vitro/pull/297  
    3. Examples of dynamic actions - https://github.com/vivo-project/Vitro/pull/311
    4. To be closed
      1. https://github.com/vivo-project/Vitro/pull/310
      2. https://github.com/vivo-project/Vitro/pull/306
      3. https://github.com/vivo-project/Vitro/pull/287
  4. VIVO development fund - https://docs.google.com/document/d/1k_fzP8O59Um1FnePje7JKGlKzfqv4dzxgYN4oqPCpu8/edit?usp=sharing
  5. DSpace-VIVO integration further steps - https://docs.google.com/document/d/1bYRH4fl4ubOoq6KmxCxGSofHRd9iF7m7gV2tDZDUJYs/edit?usp=sharing
  6. 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. Announcements:
    1. We are back in weekly meeting mode
    2. Issue 3735 should be closed do reduce risks for users
  2. VIVO 1.13.0 release
    1. VIVO 1.13.0 RC-4 prepared and ready for testing. Short period for testing. Dragan proposes to wait a week more and publish the release.
    2. In the last couple of days some correction PRs were merged.

Dragan: Release process could be automatised with shell script files. Dragan will work on that. 

William: I think we can also automate snapshots creation.

There are github actions for DSPACE that basically builds docker image and runs tests against that.

https://github.com/DSpace/DSpace/blob/main/.github/workflows/docker.yml 

https://github.com/DSpace/DSpace/blob/main/.github/workflows/build.yml 

  1. Dynamic API
    1. PRs: Need resolve conflicts for 297 and 311. Also, 297 and 327 need reviews
    2. William: We should consider specifying and implementing administrative UI for dynamic actions. It will be some kind of UI for the definition of dynamic actions (and REST endpoints). Dragan: to implement that after implementation of generic UI for dynamic actions. William: no, it might be better to implement that before, it might help in defining dynamic actions for already existing features in VIVO (moving part of Java code from VIVO to n3 files). Generic UI for dynamic actions is a complex problem, we might use part of the next sprint to do a Spike (https://www.scaledagileframework.com/spikes/). 
  2. DSpace integration: 
    1. After the first phase of the DSpace VIVO integration project - script to migrate data in a clean VIVO, VIVO can be used only in read-only mode, be only visualization of DSpace data.
    2. Dragan: now the project is outside of the VIVO and outside of DSpace. Should integration with DSpace be part of VIVO core codebase? William: Harvester in VIVO. Symplectic element is an example of a harvester. It is better to not include implementation into VIVO. We shouldn’t add harvester inside VIVO. Dragan: We can implement some standard protocols for interoperability in VIVO Core (OpenAIRE guidelines for CRIS managers, Linked Data Notification (LDN) Specification for COAR Notify), and use those protocols for integration with DSpace and other file repositories.

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.