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
- Dragan Ivanovic
- Brian Lowe
- Georgy Litvinov
- Rolf Guescini
Agenda
- Questions/Issues/Pull requests/Announcements
- OR 2022 - paper about DSpace-VIVO integration accepted
- DSpace-VIVO integration
- Publishing of a minor release
- Completion of PR reviews and merging
- Preparation of a release candidate
- Updating of technical documentation
- Testing
- Update of the Roadmap - https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing
- Specifying date
- May 30th - June 17th
- Registration - link
- 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
- Specifying date
- Selection of the frontend technology/framework
Notes
Dragan: A new form to participate in the Sprint https://forms.gle/whYvMwgpbo7q6DgC9
One important aspect for us is selection of frontend framework.
What is important for us?
William: we should also choose CSS Framework.
William: Most people will say that React is only a library while Angular is definitely a framework, but React also imposes some structure. React has many pieces, including Redux, which is the most popular centralized state store.
William: We need to have server-side rendering for SEO. Angular has Angular Universal; there is something for React, something for Ember. Need to consider this very heavily: need to be able to retrieve/index all the content without Javascript.
Georgy: Svelte is different because it doesn’t have a virtual DOM.
William: All browsers support shadow DOM. In Angular it is used for change detection. Not clear how Svelte is better. Also need to see whether Svelte supports server-side rendering. If not, we shouldn’t consider it.
William: Always the option to use WebComponents and write everything in ES6 without adding a framework. But WebComponents don’t handle single-page app routing.
William: We need to make sure that whatever we choose affords building dynamic routes and having a dynamic UI.
William: Should have a vote.
Georgy: Create a spreadsheet? Define columns with requirements. Those who know each option best can fill in the rows.
Georgy: Should consider (add column) whether institutions have staff familiar with these frameworks. May differ between European and American institutions.
Dragan: Who will fill in the data once we have defined the spreadsheet? Invite whole community?
William: Committers should have a voice, but should also include the active community.
Task List
- 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
Previous Tasks
- Dragan Ivanovic to make demo of what we have developed as a result of the sprint
