Issues should be added for instance in a dedicated VIVO backlogs project board for triage (similarly as DSpace Backlogs -https://github.com/orgs/DSpace/projects)
Proxy editing: Issue with assigning profiles to account for editing, but account can edit everything
Brian: Check role for username. Since it’s “editor”, that means that account can edit everything. Set to “self-editor” to turn off overall editing privileges and then check proxy editing
Works as intended
Dragan: Besides that, didn’t notice any issues. Performance also looks ok.
Situation for being able to edit relationships to others
Instead of being set to root, appropriate to set that at editor/self-editor level
Update level: usually editor or self-editor instead of root
Language search issue discussed in dev call earlier
Brian: Issue is with dynamically adding language with the necessary analyzers
For different project, had three different document modifiers - processing for each language. Populate fields other than the default used for sorting - three different fields for languages. Then piped in the field based on locale.
Appears to be an important issue prior to release. So good with intermediate solution with dynamic fields. Maybe language specific analyzers in next release.
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)