Date
Call-in Information
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
To join the online meeting:
- Go to: https://lyrasis.zoom.us/my/vivo1
One tap mobile:
US: +16699006833,,9358074182# or +19292056099,,9358074182#
Or Telephone:
US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257
Meeting ID: 935 807 4182
International numbers available: https://zoom.us/u/aeANHanzED
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
- Community updates
- VIVO 1.11.0 release candidate planning
- Release candidate to be published: today?
- Update/Release
- Release Testing - 1.11.0
- Issues
- Transition to Java 11? (pom.xml) (travis.yml)
- Sprint planning
- Community mailing lists
- In-review tickets
Tickets
Status of In-Review tickets
Received
Bugs (1.11)
Notes
- Don Elsborg: Innovation grants: Two proposals
- Working with LASP. Expose publication data (currently in facet view) - HTML widget that can be embedded in iframes (remember iframes?!) with their branding
- Integrated federated campus knowledge graph
- Intra-institution
- Inter-departmental
- Instruments, observable phenomena, PIs,Co-PIs
- Would be surfaced and linked to upper level data (publications, affiliations)
- Possibly build on cross-VIVO EarthCollab work
- Similar to questions/discussions by Amalia/Rafael’s team
- Andrew: Is this work contingent on the grant?
- Don: If approved, an official sanction exists. Can devote time and resources to it within this framework.
- Andrew: Seems like this would be a good time to address these issues
- Rafael: Trying to deploy the EarthCollab code that was shared to test it out.
- Does Don have implementation yet of this work?
- Don: Not right now. LASP has domain-specific implementation of VIVO for solar satellites.
- Andrew: Exciting stuff.
- Grant recipients finalized probably by end of the month. Advancement round before 22nd. Part of this grant is to work with Leeds Business school to develop pitch. Takeaway: how do we surface these ideas to the business? Need 3 minute elevator pitch for slides.
- Behovement for pitchness (it would behove us to have this kind of pitch)
- Don has dreams. The linked data kind.
- Andrew is hell-bent on giving us homework to come up with a pitch “but not at this moment”. (Phew)
- 1.11!!
- Ralph: In progress. The door is closed on checking in additional code.
- Will announce for test
- Tagging release candidate in GitHub
- Pre-release with standard artifacts
- 66 issues in 1.11 - will go through those and set up summary to put into the emails that will be sent out to VIVO Tech etc.
- Summarizing headliner changes (and not just “here is a full JIRA list” without context)
- Supporting projects: VIVO-vagrant and vivo-docker
- Should also be tagged and have associated release candidates
- Andrew: anyone on call who can make sure these projects are pulling the VIVO/Vitro release candidate artifacts
- Ralph: Will be using docker for testing
- Don: Vagrant no longer works on Don’s system. Abandonnee (is that French? Does it matter?)
- Andrew describes how he will be traveling quite a bit over the next few weeks. Wants to ensure release candidate process sorted out beforehand.
- https://wiki.duraspace.org/display/VIVO/Release+Testing+-+1.11.0
- Integration/UI tests
- Andrew: takes little over three hours on machine
- Seems like these tests exist more so because we don’t have integration tests but have UI tests
- Might be useful to compare these UI tests (which can be done manually) with the set (https://github.com/vivo-community/vivo-acceptance-tests) that Jim Blake had created “before he pedalled off” into the horizon
- API tests
- Upgrade tests: Could do this with sample data but would be useful for people to have 1.10 to actually try this out
- Vagrant and Docker tests
- If release testing is done before the conference, could do release. Open to possibility for extending the release testing candidate period if required
- Don: RedHat 7 system which would eventually be a production level system. Could do Docker test on that system as well as natively and run through some tests.
- Spreadsheets and swarms (discuss amongst yourselves)
- Last time, spreadsheet was set up to track which tests were done. Not too many other people filled in that spreadsheet. Could do this again if need be (if an appropriately-sized “swarm” wants to use the spreadsheet) .
- Don: compelling reasons for upgrading
- Steven: Probably 1.8 version of Vitro
- Still things that would be appealing for upgrade, but need to devote resources
- Would like to use TDB instead of SDB
- One of the things to discuss at conference: editing interface dependent on quirks of VIVO. One of the motivations behind editing interface redesign is to make future upgrades easier.
- Focus on SPARQL update APIs for interactions with VIVO installation.
- Current update: seam within VIVO - repurposes the POST API that that native interface uses. Snuck in there and reused that code in a way that could be further optimized.
- Andrew: Perhaps testing in this context for release candidate would be more general testing with sample data instead of upgrading own installation
- Steven: may not participate in this cycle but would like to in general
- JAVA 11
- Currently VIVO/Vitro are on JAVA 8
- JAVA 11 next long-term support version
- Ralph and Graham may have reviewed building VIVO on JAVA 11
- Ralph: Everything in past year has been with JAVA 11. One tweak: check style kept asking for 1.5. Complains about check style version. Pointing to 11 good idea since 12 already coming out. Don’t want to get too behind.
- Andrew’s suggestion: as general principle, put out VIVO releases based on latest long term support version of JVM
- Target OpenJDK vs Oracle JDK going forward (not in this release)
- Don’s question: Tested VIVO 1.11 with Java 8?
- Ralph: does work
- Andrew: For 1.11 release, targeting JAVA 8. Putting forward proposal for JAVA 11 and OpenJDK
- Brian and Andrew: Upgrades to more recent versions of JAVA may not always be possible for certain installations (based on IT department and other requirements). At the same time, we still need to be aligned with more recent versions.
- Andrew: Better to not have sysadmin dependencies/requirements and enabling VIVO to be built using pre-built artifacts.
- No immediate plan to switch to JAVA 11.
- Andrew: Sprint about month from now. Series of sprints put on calendar in line with what came out from product direction statement and architectural fly-in
- Upcoming sprint focused on ingest assuming specific entities for read only UI effort (VIVO scholar task force)
- Data models/shapes not clearly defined yet
- Still value in defining clarity on them, bringing in shapes with SHACL/ShEx
- Wanted to talk about what we want upcoming sprint to look alike and what would be valuable to accomplish in this sprint
- Don: If grant gets accepted, would be focusing on cross-linking.
- Also externalizing the triple store in theme of modularizing and decoupling
- +1 from Don
- Ralph: all 3 good topics.
- Andrew: I’m out y’all for 4 weeks. And then the sprint. So help needed. (He didn’t say y’all).
- Expect an invitation by owl (he didn’t say that either)
- Please look at community mailing list emails
Actions
Previous Actions
