...
Please add additional agenda items or updates --
Updates
- Stony Brook --Brook – upgrading VIVO to jdk1.7 – has it working on the dev site with but connection pooling is not working with 1.7 the SUNY REACH site. Needs this for his WebID development. We should then change the documentation from saying it won't work with 1.7 to saying it will.
- Florida –
- Weill - Thanks for all the help from Cornell Ithaca on troubleshooting the performance issue. Demoing a product call new relic
– long listings of publications, and putting up a copy of Cornell VIVO so can compare rendering times on Weill and Ithaca servers using the same code and data. Brian sent Eliza a note about a command line tool called SDBprint that will write out the SQL produced from translation of a SPARQL query, as a way to debug what appear to be inefficient queries. - UCSF –
- Duke --
- SUNY Buffalo –
- Scripps –
- Cornell –
- Colorado –
- Duke – upgrading VIVO from 1.4 to 1.5 and want to export publications en masse and re-load them, vs. re-importing them from Symplectic Elements, which can take as long as a week. They are also finding issues around which publications are marked to be visible in VIVO – trying to work out a way to flow through this kind of preference from Elements down to VIVO as a downstream. Some colleges such as Medicine only want representative publications to come through.
- SUNY Buffalo – Doing a project that involves a student instance of VIVO as an e-Portfolio system connected with the institutional repository (DSpace at Buffalo and also SUNY-wide) and expose them to open access patterns of scholarship. Purchasing a new server and wanting to use jdk1.7 since support for 1.6 is going away. Looking to recruit students for a pilot that would use the SUNY-wide DSpace and back-feed individual campus institutional repositories. Alex: the Library at Colorado is looking at an open repository.
- Scripps – VIVO is fine but staff have been out sick, but are pursuing a contract to bring in grants from NIH Reporter
- Cornell – Jim has been working with the build script and data getters and multiple language support. Tim will be introducing horizontal tabs to control the display of each property group, based on user feedback on the length of the scrolling with the more vertical pages in the current VIVO. Had tried to use collapsible property groups, but are finding the horizontal tabs preferable, especially for entities with very little data. Will be factoring this as an optional template to include in the individual person page template for the next release.
- Huda – working on additional search facets for Datastar, and has everything but the type and time facets done – getting equivalent classes on the types facet; time is tricky because there can be either single dates or time intervals.
- Colorado – working on concatenations of lists in cases where people have multiple positions in an organization or multiple degrees from one organization and don't want them showing up several times on the organization page. Trying to figure out how the file download mechanism works so people could do a .csv file of contacts of people they want to list on a grant proposal or for similar purposes. It's the faculty reporting time window at both the Boulder and Colorado Springs campuses, so are trying to do frequent updates. Presented VIVO to a campus interest group including some research centers (university and federal) in the area, including a person from NASA; discussion focused on general semantic web questions as well such as strict or loose ontologies, the practicality of using sparql, etc. Alex encourages others to find others on campus who may be interested in using VIVO/Vitro technologies, even if for other purposes including research.
- NYU – NYU --
- Johns Hopkins --
- Indiana --
- Brown --
- other --
...
- Implementation Fest dates and tentative agenda
- Tentative dates are April 15-16th OR April 22-23, both being Monday-Tuesday – hoping to finalize by early next week
- Simon Porter is experimenting with Joseki over Oracle as a semantic triple store at Melbourne
- Internationalization – Jim has worked out the framework and recommends a pattern that has been tested in a couple of proofs of concept, but extracting the English out of all the templates and in some cases the controllers as well is a fair amount of work.
- Can we put out out the template and request others to help with one template/controller pair at a time?
- Jim has checked in the examples completed so far and is creating wiki pages to document the recommended approach.
- This might lend itself to be a collective distributed path, including participation from native speakers of other languages
Notable development list traffic
...