...
- VIVO 1.14.1
- procedure for publishing patches
- Is it the same as for releasing minor release?
- https://github.com/vivo-project/Vitro/pull/441
- procedure for publishing patches
- VIVO 1.15.0
- Open PR
- I forgot my password
- Avoid lock on graph uri update in RdfServiceSparql
- robots.txtIndividual access objects
- Replace qtip dependencySearch sort optionsVitro431, VIVO
- Docker
- 3928
- https://github.com/vivo-project/VIVO/issuespull/39383940
- Freemarker dataGetter directiverobots.txt
- Role based search filters438Replace qtip dependency
- Open PR
- Improvement of reviewers' reports
- Adding commenting permissions to anonymous wiki users
- CRIS 2024 conference
- https://githubdocs.google.com/vivo-projectdocument/VIVO/pull/3937d/1n7XA9JZpkcH_jun9EbqZIMLJQ0XcNl_y76ePQaH-j_c/edit?usp=sharing
- Statistics at home pagegithub
- google Image charts API
- The slack message - https:/
- p1706190324794669
- Anyone using sparkline charts and facing issues with the google Image charts API?https:
- Improvement of reviewers' reports
- CRIS 2024 conference
- Statistics at home page
- google Image charts API
- The slack message - https://vivo-project.slack.com/archives/C8RL9L98A/p1706190324794669
- Anyone using sparkline charts and facing issues with the google Image charts API?https://github.com/vivo-project/VIVO/blob/main/webapp/src/main/webapp/templates/fr[…]ker/visualization/coauthorship/coAuthorshipSparklineContent.ftlWe noticed intermittent issues with our Google main/webapp/src/main/webapp/templates/fr[…]ker/visualization/coauthorship/coAuthorshipSparklineContent.ftlWe noticed intermittent issues with our Google Image Charts that we load on individual author pages and in other visualizations we have available for our authors starting last week. When we investigated, we found that the Google API these depend on is being formally decommissioned, and the outages were a result of the Google team beginning rolling blackouts to flush out any remaining users from the platform to something newer. We pull the charts in from Public VIVO when we build, and were hoping to get some direction on if the Dev team is planning to replace the charts anytime soon with something new, or what they may recommend as a stopgap. Thank you for the insights!
- Google Image Chart API - https://developers.google.com/chart/image/
- Google Image Chart - https://developers.google.com/chart
- Quick Chart - https://quickchart.io/documentation/migrating-from-google-image-charts/
- The slack message - https://vivo-project.slack.com/archives/C8RL9L98A/p1706190324794669
- Identification of a Identification of a researchers with same names
- additional information (title, position, email, etc.)
Notes
I forgot my password
The committers discussed how to proceed with this PR. At the end, the team voted and made following decision:
- The feature will be disabled by default
- The PR will be divided into two PRs, the first one without spam mitigation, this PR might be merged on time for VIVO 1.15.0, and the second with current implementation of spam mitigation which might be further discussed later and improved before merging.
...
VIVO 1.14.1
Before publishing a patch we need to test at least part of basic VIVO features. Georgy emphasized the importance of having a stable main branch at any moment so that we can safely cherry pick some commits for the needs of patching previous minor releases.
VIVO 1.15.0
Skipped this point to have enough time for other points in the agenda. This will be discussed next time.
Improvement of reviewers' reports (and process)
Georgy will draft updates for https://github.com/vivo-project/VIVO/wiki/Development-Processes#process-for-reviewing-contribution, and we will discuss that once it is ready. That wiki page might be linked from https://wiki.lyrasis.org/display/VIVO/Contributing+code+with+a+fork%2C+branches%2C+and+pull+requests and from PR template.
Dragan will draft updates for the PR template to include more structured expertise needs from reviewers.
Adding commenting permissions to anonymous wiki users
It looks there might be more drawbacks (cleaning spams), than benefits. Let’s hope people will be willing to report issues via other channels (slack, mailing list, github issues) or ready to open a wiki account and then provide a comment.
CRIS 2024 conference
The extended abstract draft available at https://docs.google.com/document/d/1n7XA9JZpkcH_jun9EbqZIMLJQ0XcNl_y76ePQaH-j_c/edit?usp=sharing
Deadline is at the end of the month. Committers are welcome to join the team of coauthors.
Statistics at home page
We should encourage Arif to open a ticket for this. It might be this is also a request from other VIVO customers. Dragan will contact Arif.
Google Image charts API
Preferences for the solution are:
- Some open source non-Google library
- Quick Chart API
- Google Image Chart library
Identification of a researchers with same names
There is some sense in adding ORCID and email as not mandatory fields in the form for creation of a person profile. To make it mandatory might be too restrictive for some VIVO customers. Whether some field is mandatory or optional is highly coupled with ftl code, meaning unfortunately it is not so easy to make customizable (which might be the best solution).
The other issue is looking up persons, at the moment there is only first name and last name in the list of persons matching query.
Actions
- Georgy Litvinov to draft updates for https://github.com/vivo-project/VIVO/wiki/Development-Processes#process-for-reviewing-contribution
- Dragan Ivanovic to draft updates for PR template
- Dragan Ivanovic to contact Arif regarding opening a ticket (feature request) for home page statistics
Previous actions
- Dragan Ivanovic will inform Ivan about decisions for I forgot my password PR
Previous actions
- Georgy Litvinov to review https://github.com/vivo-project/Vitro/pull/427
- Brian Lowe to review https://github.com/vivo-project/Vitro/pull/424
- Georgy Litvinov to improve https://github.com/vivo-project/Vitro/pull/433 (UI options for defining policies)
- Dragan Ivanovic to work on wiki documentation
- Dragan Ivanovic to contact Ralph O'Flinn about https://github.com/vivo-community/create-wsl2-vivo-dev-env
- Dragan Ivanovic to communicate with the Lyrasis team about adding commenting permissions to anonymous wiki users
- Ivan Mrsulja to implement suggested improvements into https://github.com/vivo-project/Vitro/pull/427
- Georgy Litvinov to improve https://github.com/vivo-project/Vitro/pull/390 in accordance with Miloš Popović review
- Dragan Ivanovic to review https://github.com/vivo-project/Vitro/pull/431
- Dragan Ivanovic to review https://github.com/vivo-project/Vitro/pull/432
- Georgy Litvinov to complete https://github.com/vivo-project/Vitro/pull/433
- Dragan Ivanovic to discuss with Milos Popovic about usage of JQuery in the nemo theme
- Georgy Litvinov to provide Dragan the information about volume size needed for mirroring GitHub into GitLab
- Dragan Ivanovic and Georgy Litvinov to complete merging the ABAC PRs
- Dragan Ivanovic to review extended search PR and Avoid lock on graph uri update in RdfServiceSparql PR
- William Welling will continue working on vivo-solr upgrade branch
- Ivan Mrsulja will consider adding a configuration flag for turning on/off the "I forgot my password" feature
...