...
- Dragan Ivanovic
- Brian Lowe
- Miloš Popović
- Georgy Litvinov
- Doug ChestnutMaxim Prokopenko
- Samantha Emerson
- B. Henderson
- Rishabh Tatiraju
- Michael Bentz
- Stanley Welling
- Michel Héon
- Kshitij Sinha
- William Welling
- Mark Vanin
- Yuji Shinozaki
- Christopher P. Barnes
Agenda
- Questions/Issues/Pull requests/Announcements
- SWIB - VIVO meeting
- SciDataCon
- workshop about mappings
- CERIF2VIVO mapping ???
- workshop about mappings
- WCAG compliance
- Deque performed analysis of VIVO compliance with WCAG in 2021
- VIVO conferences/events
- how well it is supported?
- Customization of ontologies
- appear in the list of ontologies, but no classes
- New pull requests
- Change PropertyKey class name and namespace (VIVO 1.14.0 - Brian)
- Prevents creation of button to add new object property if neither of 'select from existing' nor 'provide selection' options are set in object property configuration (VIVO 1.14.0 - Georgy)
- Propagate selectFromExisting and offerCreateNew settings from base object property to new faux property (VIVO 1.14.0 - Brian)
- Handle preferred language when creating new class and property groups (VIVO 1.14.0 - Brian)
- slight modification of PR for fixing a bug with empty VIVO_HOME (VIVO 1.14.0 - Dragan)
- a commit for "Create vivo/home on application start-up" PR (VIVO 1.15.0 - William)
- Extended search (VIVO 1.15.0 - Georgy)
- Parameter substitutions (Dynamic API - Georgy)
- Priorities
- What would you like to have in some future version of VIVO?
GDPR alignmentSPARQL API endpointGUI
InteroperabilityOAI-PMH endpointdata ingestionCross-site linking and searchingJSON-like REST endpoint
- VIVO as a service
- hosting
- decoupling data store
- vivo_home
- solr
- multitenancy
- Consolidation of data
- Deduplication
- Splitting two person profiles
- Enrichment of data
- OpenAIRE broker - https://graph.openaire.eu/develop/broker.html
- Altmetrics
- Reporting
- Project centered VIVO
- Which improvements are needed?
- Installation
- Documentation
- Customization
- What would you like to have in some future version of VIVO?
Notes
SciDataCon workshop about mapping, interesting event to consider. Not sure when the deadline is for submitting an abstract.
Talking about transition to new theme. WCAG Compliance review (that has been done couple years ago) - lot of issues are related to css (Color Contrast) that does not require changing a lot of frontend layout. Waiting too much to fix those compliance issues could cause loss of clients.
Some of those pull requests are linked with VIVO 1.14, some of them are investigation of releases for vivo 1.15, one of them is linked to dynamic api.
Extended search will be part of 1.15 update
Priorities for future:
Vivo as a service. We should discuss about hosting, decoupling data store, solr…
Do we see need for this first of all?
Brain: It would be great to have this, this is usually a lot of pain because of unexpected performance issues. Standard service would be a nice thing. Having a standard hosting service to offer
William: We should be concerned should we use Solr or Elastic search.
There is an elastic search implementation for vivo that probably should work.
Lyrasis is going in that path, it is possible to get requirement in one or two year for VIVO as a service.
Vivo-Solr is using an old scheme.
Some solr vulnerability was in solr 8 which we are using in a lot of legacy components.
It would be good to update to solr 9
Next week we will speak about Consolidation of data.
...