Will do later when we have strategy for enforcing in pull requests.
README: Use generic documentation link so we don’t need to update the link for each version?
Seems like the best solution. Brian will check the text.
ChangeSet user info PR will be merged for next release.
Jena 4 upgrade
Great work from Kevin during sprint but needs to be continued.
Brian will find time in coming weeks to work on this.
Dump/restore script
Dragan: Should some settings continue to be specified in the script itself vs. command line parameters?
Brian: would be nice to have them all specified the same way.
Dragan: Args currently depend on position, not flag like -p -u.
Brian: Seems error prone; maybe move all to config file / environment vars?
Dragan: Where should script go?
Georgy: /bin directory?
Dragan: Problematic because of git ignore.
Dragan: If in vivo.home, need to be careful not to wipe out existing dumps on redeployment. Will need to think more about these issues before including.
Building/installation improvements
Dragan will wait a day or so for comments about deployment practices survey, then will distribute more widely
Dynamic API + JS frontend
Is Angular still the frontrunner?
William: Could be, but also depends on whether we want to dive into a static UI or make it dynamic with ontology defining UI on the backend
Brian would be interested in starting to draft that ontology with current UI features as a starting point.
Dynamic API meeting time may need to be shifted again because new time is very early in Texas.
Dragan Ivanovic to work on documenting new features for VIVO 1.13.x Documentation
Dragan Ivanovic to create the third one google form for reporting the testing results, that form should be used for testing new features introduced in VIVO 1.13.0
Dragan Ivanovic to investigate organizational (management) aspects of DSpace community and to prepare discussion for the next meeting what might be adopted from there (GitHub actions, labels for issues, template for issue, template for PR)