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
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Questions/Issues/Pull requests/Announcements
- We are back in a weekly meeting mode
- Rename googleAnalytics.ftl to webAnalytics.ftl - https://github.com/vivo-project/VIVO/issues/3735
- We decided to close this issue
- VIVO 1.13.0 RC-4 prepared and ready for testing
- Release Testing - 1.13.0
- Deadline - 8/31/2022
- Dynamic API
- Decoupling SparqlQuery- https://github.com/vivo-project/Vitro/pull/327
- SHACL based validation - https://github.com/vivo-project/Vitro/pull/297
- Examples of dynamic actions - https://github.com/vivo-project/Vitro/pull/311
- To be closed
- VIVO development fund - https://docs.google.com/document/d/1k_fzP8O59Um1FnePje7JKGlKzfqv4dzxgYN4oqPCpu8/edit?usp=sharing
- DSpace-VIVO integration further steps - https://docs.google.com/document/d/1bYRH4fl4ubOoq6KmxCxGSofHRd9iF7m7gV2tDZDUJYs/edit?usp=sharing
- The next sprint
- When?
- 19.09. - 07.10.
- What?
- Improvement of expressiveness of notation
- Iterative steps
- Operation data / DataStore - should be ready before sprint
- Improvement of UI
- Support for more rich structure of entities
- Notation for UI layouting
- Completion of authorization and authentication
- Extension of SHACL rules
- Editor for definition of a dynamic action
- VIVO based on dynamic actions
- Improvement of expressiveness of notation
- Who?
- When?
Notes
- Announcements:
- We are back in weekly meeting mode
- Issue 3735 should be closed do reduce risks for users
- VIVO 1.13.0 release
- 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.
- 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
- Dynamic API
- PRs: Need resolve conflicts for 297 and 311. Also, 297 and 327 need reviews
- 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/).
- DSpace integration:
- 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.
- 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.
Task List
- Dragan Ivanovic to resolve conflicts for https://github.com/vivo-project/Vitro/pull/311 and https://github.com/vivo-project/Vitro/pull/297
- Dragan Ivanovic to write script for preparing a release candidate
- All to test the release candidate - Release Testing - 1.13.0
- Dragan Ivanovic to publish VIVO 1.13.0 release (if there is no reported issue till 1st of September)
Previous Tasks
- Dragan Ivanovic to prepare presentation for demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to send reminder for the demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
- All to consider participation in the sprint and if decide to participate to register for the sprint - link
- Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
- All please help in filling this document - spreadsheet
- Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
- Committers to review the structure of the document and to fill it with data for JS and CSS frameworks