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
- Conferences
- CRIS 2022 - program
- OR 2022 - program not yet published
- VIVO 2022 - ???
- Self-registration for Slack - http://bit.ly/vivo-slack
- The license issues - https://github.com/vivo-project/VIVO/issues/3690, https://github.com/vivo-project/VIVO/issues/3692
- discussed at VIVO LG
- Action - establish communication with Cornel University
- Conferences
- DSpace-VIVO integration
- DSpace-VIVO integration task force
- The next Tuesday, May 10th, a 15 minutes presentation
- The next sprint
- date
- May 30th - June 17th
- Registration
- please register until May 15th, 2022
- link
- Two registered participants so far
- Infrastructure
- Wiki page - Sprint - Dynamic API based on an ontology 2
- Slack channel created
- Project board
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- but extend it with new issues (features, bugs)
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- Topics
- Update the ontology
- GET all and GET one - two dynamic actions or one
- Implement more complex workflows
- iteration step,
- conditional step
- Implement N3Template deletion and modification
- User interface for execution of a dynamic action
- User interface for definition of a dynamic action
- Validation of dynamic action
- Authorization - roles
- Update the ontology
- Selection of the frontend technology/framework
- date
- Publishing of a minor release
- Completion of PR reviews and merging
- Preparation of a release candidate
- Updating of technical documentation - VIVO 1.13.x Documentation
- Testing
- Standard features test - https://forms.gle/BsAz3ongzU1BR5nE7
- Advanced features test - https://forms.gle/BX7o8gwwVfCujWes5
- New Features test - https://forms.gle/35hNEjMnfcYC1ZpMA
Notes
Few updates about the CRIS conference. It is held in a week, and a ‘VIVO day’ is on Friday. It might be possible to attend the conference remotely, but Dragan is not sure yet. He will let us know when he finds out. DSpace - VIVO integration will be presented in one of the papers at the OR 2022 conference.
Google form for slack membership seems not to be working. We need to figure out who gets the information from filled up google forms. Andrew should be asked, he maybe knows, and if not, a new google form could be created. We can also potentially automate the process of adding new members to the slack channel.
Cornell university was contacted to ask whether some other entity could be named as VIVO license holder (still waiting for the response). If so, then we need to figure out which entity will be a “license holder”: VIVO-organization, Lyrasis or some other entity.
Sprint registrations are open, and it would be great to have a full list of participants by May the 15th, so that we can start planning on who will do what. Private slack channel will be created for the sprint participants. We will use the same project board since we are working on the same feature (dynamic api). The main goal of this sprint is to create some sort of UI for the new Dynamic API feature.
Dragan created a new google sheet where all the potential frontend frameworks are listed. Michael suggested Angular because DSpace is using it, and both webapps are under the Lyrasis umbrella. Dragan believes that there is no overlap in DSpace and VIVO developers, so there is no need to force the same techstack. Brian agreed with Michael. Michael also suggested prioritizing finishing the backend API before starting the work on UI. Dragan explained the current state of Dynamic API, how we will use RDF for describing an endpoint, and how those endpoints will communicate with clients via JSON. Frontend expertise of current VIVO developers should be one of the main factors when choosing the frontend framework.
Georgy suggested spending a bit more time planning for the sprint. Dragan agreed, suggesting 5 one-hour meetings in the week leading up to the sprint. This suggestion is mainly for the new dynamic api feature, as this isn’t a simple straight forward functionality or bug fix, but rather an entirely new architecture which should be discussed and thought through thoroughly.
When it comes to spring dependency, Brian said he will probably work on it at the end of the week, and it should not take more than a few hours.
Task List
- 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
Previous Tasks
- 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
