Notable development list traffic

As documented in this mailing list thread, UF's problem with re-indexing it's data in 1.5.1 hasn't been resolved. Possible root cause is bad data in MySQL evidenced by repeated errors in logs, but there should be a way to trap for certain characters and not have either Jena or VIVO throw exceptions. Should this be the topic of dedicated development meeting? Who wants to be involved and what time slot would work – does the 2 pm ET Thursday slot work for people?
- Chin Hua also needs to have this bug resolved to be able to debug the visualization issues Florida and Penn have been experiencing
Problems with non-Roman characters – make make sure your server.xml contains URIEncoding="UTF-8" in the active <Connector> element.
Recent versions of Vitro require a setting change in Tomcat's server.xml file that was not needed in 2009. Make sure your server.xml contains URIEncoding="UTF-8" in the active <Connector> element. Without this, non-ASCII characters won't work properly. For example,
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"
URIEncoding="UTF-8" />
more
Transport error in connecting to Solr
Updating Solr to be able to use new modules/add-ons
Connecting VIVO to a REST-style web service to migrate existing profiles to VIVO
Generating a list of keywords from VIVO
Last data update date
Other issuesOnly when I omit the URIEncoding attribute can I can reproduce the problem you've shown.

Call-in Information

Topic: VIVO weekly call

Date: Every Thursday, no end date

...