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
- Self-registration for Slack - http://bit.ly/vivo-slack
- fixed
- New issues and PRs
- Performance issue - https://github.com/vivo-project/VIVO/issues/3695
- Exporting data - https://github.com/vivo-project/VIVO/issues/3696
- 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
- Spring dependency - https://github.com/vivo-project/VIVO/issues/3686
- Slack discussion
- A reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Migration of permissions - https://vivo-project.slack.com/archives/C8RL9L98A/p1651831688329669
- DSpace-VIVO integration
- DSpace-VIVO integration task force
- 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
- Questions/Issues/Pull requests/Announcements
- Conferences
- Self-registration for Slack - http://bit.ly/vivo-slack
- Fixed
- Backlog of people have been added
- They will be added to dev channel
- New issues and PRs
- Performance issue - https://github.com/vivo-project/VIVO/issues/3695
- Brian: fairly big issue, should be done sooner rather than later if it can be reproduced
- Have not had chance to look at it yet
- Did not affect admin or root users
- Might be related to permissions checks
- Exporting data - https://github.com/vivo-project/VIVO/issues/3696
- PR - https://github.com/vivo-project/Vitro/pull/291
- Submitted by Christian, resolved by Benjamin G
- 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 Cornell University
- Had to find right person
- It might be complicated, he’s not sure. Fork code?
- Spring dependency - https://github.com/vivo-project/VIVO/issues/3686
- PR - https://github.com/vivo-project/VIVO/pull/3697
- Brian has submitted the PR to resolve
- Slack discussion
- A reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Creating a problem with building URLs
- Likely an issue with using a proxy other than AJP (e.g. a normal HTTP proxy)
- Would it make more sense to allow a custom URL be defined in runtime.properties?
- Setup of modern Tomcat a little more complicated than in the past for security, so maybe less likely that people are using AJP
- Migration of permissions - https://vivo-project.slack.com/archives/C8RL9L98A/p1651831688329669
- Question references advance role management. Do they store permissions in a different place?
- Brian: Since the introduction of faux properties, it’s more complicated
- Overall, we’ve done a good job of cleaning up old pull requests. Still not sure what will we do with the very old, very large PRs, like advanced role management.
- DSpace-VIVO integration
- DSpace-VIVO integration task force
- a 15 minutes presentation from Michel
- ETL notes
- Using the Dspace-VIVO exchange data schema (DVExDS)
- Source database > extract source data > transform target data > load to target database
- Data structure in Dspace: REpository > community > collection > Item > (type, e.g. BitStream)
- Everything gets a freestyle ID (as a string), not unambiguous unique IDs
- Within VIVO, all metadata from Dspace is brought over
- Mapped to type via dc:type, plus asserted as a ‘DSpace item’
- Must consider how to map people in DSpace (who have many non-unique records) to a single unique record in VIVO
- Copies keywords from DSpace documents into ‘research areas’ for people in VIVO
- Population of VIVO can come from multiple DSPace sources
- Example use case: Departments at university have their own DSpace. Can merge into a single VIVO
- Capability maps work
- Many people in DSpace -> 1 VIVO
- Could add metadata into DSpace that has VIVO URI. Not great because it needs to be done for every record.
- Could have x-walk registry. A link between VIVO URI and all possible name variants in Dspace.
- Could have governance rule within university that requires names in Dspace be written exactly in the right way
- Dragen: Will unfortunately require some manual effort in every approach
- Another tough point: classification of DSpace item in VIVO. You can extend the item types in DSpace, so can’t account for random custom types in crosswalk to VIVO automatically.
- The next sprint
- date
- May 30th - June 17th
- Pre-sprint meetings the week before
- Registration
- please register until May 15th, 2022
- Link (https://forms.gle/whYvMwgpbo7q6DgC9)
- Two registered participants so far
Task List
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
Previous Tasks
- 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