...
- When I run apache and set the tomcat server.xml for connection, vivo does connect to tomcat via apache without the 8080 and '/vivo', but it cannot connect to vivosolr – because everything runs clean under tomcat, I still believe my problem is with mod_jk configuration
- How can I do complex termSearches with the pubmed harvester that require parenthesis? (Stephen will respond)
- Help with listViewConfig and propStatement modification
- 1.5.1 logging issues (Laura will follow up with the Auditor code)
- Need to configure Tomcat with Memcached (no replies yet, Stephen is interested also)
- Building with ant war with Weblogic and Glassfish (Jim managed to miss it. Mike will share his info.)
- Still nobody able to get sparql update working with Fuseki?
- Research areas – where/how to create an xml sniplet for the research area and ingest it (Colorado does that - will respond)
- I would much rather do without any reliance on SDB as it is very slow and does not scale. OWLIM has a very fast built in OWL2 RL reasoner, which removes the need for any Vitro-side inferencing in the Jena style (which accounts for a lot of the speed loss) ... I managed to setup VIVO from Github with the SPARQL backend (and without the simple reasoner). However, triples I add to the tripestore do not show up in the interface (even though the indexer notices them). May have something to do with using skos:prefLabel instead of rdfs:label ... (Brian Lowe says that the current code doesn't work well with the unnamed graph. He will look at other cases that need to be updated)
- Solr to speed page load times for people with 100+ publications? Some doubts expressed on the list ...
- From a development point of view, you then have some bits of the page accessed by Jena api calls, some via SPARQL and some via SOLR... I have an aversion to this
- there's a script we run that does an HTTP GET on each faculty member page with more than a threshold number of publications. (We usually use 200 as our threshold, but 100 would work as well.) Our mysql server has a large enough cache that once those pages have been fetched once, they're typically quite a bit faster to load on later fetches.
- (Alex says that more Tomcat memory could help, He will share his init parameters on the list)
- Other topics as time permits
...
- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
- Call-in toll-free number (US/Canada): 1-855-244-8681
- Call-in toll number (US/Canada): 1-650-479-3207
- Global call-in numbers: https://cornell.webex.com/cornelluniversity/globalcallin.php?serviceType=MC&ED=161711167&tollFree=1
- Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:645 873 290
last meeting | next meeting