...
- When it's not possible to access a source database directly, what VIVO tool supports harvesting data via that source's API?
- Mainimage inverse extension (to point from the image back to the person) – the inverse relationship would be helpful in finding the way from an image to the person as part of batch image uploading
- Rebuilding the search index from a crontab after adding data (presumably not interactively but via ingest)
- Change in deploy.properties for developers (developer.defeatFreemarkerCache=true) - Jim did this to make an undocumented developer-focused feature more visible when making changes to templates and not wanting to have to restart Tomcat – becomes a 1-minute default cache for templates so they get loaded faster
- A new, generalized approach that will allow you to define a DataGetter and associate it with the Freemarker template of your choicechoice – triggered by a request to put a global variable into the footer of every VIVO page; this can be done through configuration with only having to make changes in the templates, not the Java code.
- An example where people might like to cherry-pick the commits in the development branch
- Colorado keeps a test instance with the current dev branch and will deploy to production with the next release
- The recent update of Solr from 3.1 to 3.6 in the dev branch The update of Solr appears to require replacing the Solr index, not just a rebuild – "I couldn't rebuild the index, because Solr wasn't responding to commands. However, I did fix it by deleting my [vitro-home]/solr/data directory, restarting VIVO, and then rebuilding the search index
- This same issue has been experienced at Colorado as well as Cornell
- The Solr upgrade was about 5 different point releases
- We might something in the build that would remove the files automatically with the upgrade if still running Solr 3.1 – a bit scary, but should at least be in the
Call-in Information
Topic: VIVO weekly call
...