Date
Call-in Information
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
To join the online meeting:
- Go to: https://lyrasis.zoom.us/my/vivo1
One tap mobile:
US: +16699006833,,9358074182# or +19292056099,,9358074182#
Or Telephone:
US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257
Meeting ID: 935 807 4182
International numbers available: https://zoom.us/u/aeANHanzED
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
- Brian Lowe
- Huda Khan
- Mike Conlon
- Don Elsborg
- Benjamin Gross
- Ralph O'Flinn
- Andrew Woods
- Steven McCauley
- Jane of Wollongong
Agenda
- TDB/SDB special topic follow-up
- Continuing with the "special topics" series
- Open issues
- Moving to the `master` branch
- Installation process
- Vitro pull-requests
- Developer from uow.edu.au may be able to join call to troubleshoot issues they are seeing. Adding to agenda in case they can make it.
Tickets
Status of In-Review tickets
Notes
Start with issue agenda #4, Jane for UOW
Profile load page took forever
When profile first updated, first time takes a while, after that takes less time.
They’ve also tried to get 1.11 running on docker
Huda tried this too, but not too familiar with docker.
From Jane
Researchers running slowly.
She tried to do this on 1.11, but imports via backend running very slowly.
UOW running 1.8.1
"Wallace, Gordon" profile running very slow on first load
Ben - go to site admin in dev panel and log sparql queries to time this
Jane - some other VIVO/institutions had a lot of pubs which loaded quick
Huda - listview queries have some optionals and also have new properties vs. stock vivo
Don - this shouldn’t be a SOLR issue
Jane - optionals in select queries, but unions in construct queries. No optionals in construct queries
Jane - can’t show SPARQL queries as far as she knows
Huda - thinks Jane wanted to see queries through UI, but it shows in the logs
Jane - when moving to 1.11
Don - did you do a full load of all your data into 1.11? What is the env like?
Jane - hardware config for 1.11 was larger then required
Mike - easier to debug in docker, but in 1.8 we have no idea how much customization was involved. Their 1.8 env is old and not a controlled env.
Ben - some of the queries are very data dependent
Request to load Janes data into 1.11 docker
Is it possible to get Janes UOW data?
Jane wants to know where to share it? What forms of data?
Huda/Mke - rdf/xml would be good
Ben - could also share a compressed version of sql db
Huda could get this data on Box or some share site, Jane will send this to Huda
Jane also has issues with the images directory, copied images data but still couldn’t display image
Don thought there was a place where the image upload directory names were set.
Huda - work this offline
Jane - also issues with adding customized themes
UOW is an older site, Jane not exactly sure when it slowed down. A researcher looked at their site and noticed it was slowing down, also that data is getting larger.
Issues
TDB/SDB topic call
What to follow up on?
Can we come to a recommendation.
Also, is solution externalizing the 3store
Ralph - short term default should be TDB with eye towards TDB2, with ability to have people use others
Mike - default should be TDB. We should have a document with rationale. Encourage people to participate in Jena. Carefully worded doc with intention for TDB in 1.12. Look for community input. More open process.
Don - incorporate Grahams SDB fixes and add to new VIVO
Ralph - seconds that
Mike - social goal to avoid a fork. Need to enable ability for folks to run what they need.
Grahams versions are in Jena.
Grahams jena fixes not in Vitro library dependencies yet.
Andrew - james creel also had some library fixes for SDB.
https://github.com/vivo-project/Vitro/pull/109
Ralph has his branch for SDB fixes from Graham and others.
How to change wording for SDB on Jena site.
Mike - we have our own wording on our site regarding SDB
Andrew - immediate action to update Jena, perhaps isolate this to just a Jena lib update. Create a ticket for this. Update Jena libs and call it 1.11.1
Ben - thinks Grahams fixes are in VIVO 1.11, specifically using Jena 3.11 which has Grahams Jena PR in it. Benjamin confirmed this. We are also using Jena 3.11 in VIVO.
Mike - will check with Graham to check.
Don - want to verify if optionals really are fixed with Grahams SDB patch.
Brian - I believe Graham’s fixes to SDB automatically rewrite OPTIONALS in queries to mimic what his new directives do for the list view queries already, so I don’t think we would expect to see any immediate performance change for the complicated list view queries by dropping the extra directives. The underlying SDB improvements would help other queries and simplify the writing of the list view files. Also the externalized triplestore code is already in VIVO. So what else is different?
Andrew - make this default. Eg UF is using Virtuoso. Would be nice to get rid of the SDB/TDB code and just use an external triplestore.
Brian - before we make a public statement, do more experimentation with external triplestore to verify that things work.
Mike - make sense but issue we come to is that we need a test suite. Weill tried to move to Virtuoso years ago and then eventually backed off. UF is also saying Virtuoso looks good, but they need a full prod test suite.
Brian - yes, we need a full prod test suite, also Virtuoso did some munging of datatypes.
Actions
- Organize a session on Brown's work on editing