Indicating note-taker
Time: 10:00 am, Eastern Daylight Time (New York), 4:00 pm Central European Summer Time
To join the online meeting:
Meeting ID: 836 8591 6724
Passcode: 556561
Calendar invitation - ICS file
Indicating note-taker
References to docker for 1.7 and 1.8 on https://wiki.lyrasis.org/display/VIVODOC116x/Docker
https://wiki.lyrasis.org/pages/viewpageattachments.action?pageId=298811785&metadataLink=true or https://wiki.lyrasis.org/pages/viewpageattachments.action?pageId=176488523&metadataLink=true -> it seems like all docs since 1.10 have a PDF of the 1.10 documentation attached.
On the main page of every version documentation a PDF of the respective version can be created and attached. This would be a fixed version. It should be discussed if this should be done or not at all. Upside is the existence of an easily redistributable documentation, that could even be part of a version release. https://wiki.lyrasis.org/display/VIVODOC116x/SPARQL+Queries - The YASQUE website is down since some time. Do we really use YASQUE or YASGUI? I remember a discussion about it a year ago, but I am not sure if it went somewhere.
VIVO Vagrant for VIVO for 1.11. Still relevant? https://wiki.lyrasis.org/display/VIVODOC116x/Vagrant
https://wiki.lyrasis.org/display/VIVODOC116x/Direct2Experts+API Direct2Experts does not seem to exist anymore - the information about the endpoints is interesting, though!
Charlott: Is it possible to hide the "Edit this individual" link (next to Admin Panel in the profiles) for specific roles like for e. g. editors ?
Charlott explained the requirement, Georgy think we have a permission for that.
Charlott to try to remove line 11 into this file - https://github.com/vivo-project/Vitro/blob/main/home/src/main/resources/rdf/accessControl/firsttime/simple_permissions_editor.n3
Amin: two search boxes on the homepage (navbar and in the middle)
Amin confirmed that the solution recommended by Brian works. It should be added to the documentation.
New issues
Execute SPARQL CONSTRUCT page in Ingest Tools - https://github.com/vivo-project/Vitro/pull/517
Folke should test this, but there is an issue with SearchEngineSmokeTest failing. Georgy confirmed that rebasing Brian branch on top of the main branch should resolve the issue. Brian will rebase his branch, Folke will try to test.
Spanish labels - https://github.com/vivo-project/VIVO/issues/4151
Dragan created a PR for addressing this request - https://github.com/vivo-project/VIVO/pull/4153
Brian will review the PR.
Capability map person detail - https://github.com/vivo-project/VIVO/issues/4152
Brian thinks this is not a blocker for VIVO 1.16.0 release, although it would be nice to resolve this bug.
Docker action for vivo-es - https://github.com/vivo-project/VIVO/issues/4154
Dragan raised a concern about missing a github action for depositing Docker images for Elasticsearch and OpenSearch to the Docker hub, which he assigned to Milos for resolution.
ElasticSearch and VIVO
Christian asked whether ElasticSearch integration might be a solution for the BrCris team. Dragan explained that the BrCris team is using VIVO as storage while building a new UI that communicates with Elasticsearch with a custom created index structure for their own UI. He noted that while this might simplify their technology stack by potentially reducing the need for Solr, it would not completely replace the need for their Elasticsearch index structure. The team discussed the possibility of creating Kibana dashboards using Elasticsearch integration with Vivo, which Ivan had previously attempted by replicating functionality from a Brazilian instance. While the initial implementation was successful, there were concerns about security implications of making ElasticSearch publicly accessible. Ivan noted that Kibana should typically be used for admin visualizations rather than public-facing content, and suggested that authorization controls would need to be carefully considered for any public access. Georgy raised concerns about authorization implications, noting that direct Elasticsearch access would create another layer of authorization separate from existing VIVO controls. The team also mentioned a previous project by Asim that involved shielding Elasticsearch from public access, though the specific repository for this work could not be immediately located. Dragan suggested Ivan create a pull request on top of vivo-es repository with exported Kibana templates.
VIVO-ORCID
The team also discussed the VIVO-ORCID project timeline, with Dragan setting a goal to complete the pull request by May and work on documentation in June. VIVO-ORCID contributions should be published as part of VIVO 1.16.0. The team discussed testing requirements for ORCID integration, with Ivan explaining that they need specific credentials and API keys from ORCID sandbox to test properly. Ivan will add more details in the testing instructions within the PR description.
Outdated documentation
Dragan had updated PDF attachments linked with technical documentation (1.11 release and above).
VIVO-MVP
Regarding the data distribution API for OAPMH export, Georgy explained that ETAG-based caching headers are not currently supported in Elasticsearch due to the removal of timestamp functionality in version 5.0, and suggested implementing a search implementation agnostic solution until a proper Elasticsearch implementation is found.