Implementation and Development Call 20130829

Calls are held every Thursday at 1 pm eastern time (GMT–4 in daylight savings, GMT-5 standard time) – convert to your time at http://www.thetimezoneconverter.com

View and edit this page permanently at https://wiki.duraspace.org/x/-eYQAg, or use the temporal Google Doc for collaborative note taking during the call.

VIVO 1.6

• VIVO 1.6 release standup meetings are happening every weekday noon (excepting Labor Day 9/2)– open to all, but likely primarily of interest to those committing code for this release

• For background, see the  VIVO 1.6 release planning (including notes from last week's version number discussion) and VIVO 1.6 JIRA issues

Apps & Tools Working Group

Chris Barnes held the first meeting of the new VIVO Apps & Tools working group on Tuesday, 8/27 – view the notes and notes from the BOF at VIVO 2013

• Next meeting: Tuesday, September 10 at 1 pm Eastern

• Following meeting: Tuesday, September 24 at 8 am Eastern - 9 am in Costa Rica, 1 pm in London, 2 pm Amsterdam and Rome, 3 pm in Nairobi, 8 pm in Beijing, 10 pm in Melbourne, and 12:00 AM in Christchurch

• Apps and Tools Working Group would like to ask for presenters for upcoming meetings, giving people a chance to showcase their work and describe what how they did it and what further they’re working on -- inspiring others to share any tools

• Just email Chris at cpb@ufl.edu if you would like to present. Please Please Please share your tools!

• Make suggestions of what you’d like to see presented, or make a suggestion for an app you’d like to see built

• Alex would love to see another demo of OpenSocial and the ORNG gadgets/apps that have been developed

• The Slideshare and YouTube gadgets plug right in

• Ways to obtain data from Google Scholar -- is there an app for that for individual VIVO faculty/researchers to use (button on their profile page)? Also maybe allow for generic BibTeX import?

• Profiles RNS disambiguation tool (NickB?)

• Duke VIVO widget

• VIVO Searchlight (latest code linked to from AgriVIVO)

• Funnelback search technology, Griffith VIVO extensions, Melbourne capability mapping

Updates

• UF (Nicholas, Chris B.) -- testing updated version of people ingest software written in Python that incorporates an exception list to avoid bringing back people who have been removed, and have more control over the creation of new departments. Have some SQL queries generating CSVs that get fed into the Python logic that could be fairly generic.

• UCSF (Eric)

• moving forward with trying to host other Profiles instances and link them together; VIVO might be part of what might be building, as a means for ingesting RDF and potentially for tying data together

• Texas A&M -- the Colorado team had a call with 3 people from Texas A&M this week and will be talking with Liz about the business side

• Scripps (Michaeleen) - working on big grad student publications metrics project

• Penn State (Michael) - over the hump with Karma and running into a odd artifact with the 2nd ingested item

• talks are underway with the Hershey campus (Penn State is one university geographically dispersed on 22 campuses)

• Memorial (John) -- a few victories over the beasts of data ingest (using the Harvester, mainly) and getting heads wrapped around it, so will be working more on mapping data from Yaffle, a relational database, to VIVO. Will have a new hire to help with data cleanup before ingest starting next week as well. Also starting to look at designs for the front page and debating whether to use an external CMS fed by VIVO vs. a site directly VIVO-powered

• EPA (Laura) -- focusing on starting some communications and preparing for a pilot rollout -- seeking feedback on paper guidance and documentation. Will be letting users curate data in addition to what have put in directly; have VIVO set up with LDAP so user are linked to profiles populated from HR system

• Duke (Patrick, Sheri, and Jim) - We are working on getting artistic works in. We are still figuring out what data will be entered in Elements and what, if any, will need to be captured separately via the admin app tied into the Scholars@Duke VIVO instance. Also working through ontology questions: like how to use roles and relationships. Concerned that roles may not attach directly to the artistic work -- Jon CR will set up a call via Damaris.

• Cornell (Jim, Tim, BrianL and Jon)

• 6 FTEs working on 1.6 release with daily standups

• Jim working on release management tools/process, e.g. to work with Git

• Tim and Jon discussing best approach to documentation, tackling challenges like maintaining older release docs on wiki while adding new 1.6 documentation and preparing to have a spot for documentation to be developed for the subsequent release.

• Colorado (Stephen and Alex) - contributing to the release preparation and to do testing. Getting a new server online for a staging environment to replace a single VM for testing and staging. Working through an issue showing up in the logs -- showing up as errors with bad characters in data

Notable list traffic

Moving the RDF initialization files (Jim & Stephen adjusted for the 3-tier build)

Freemarker formatting help for Stephen's pull request:

Unchecking "collate by subclass" on the relevant object property screen when implementing a custom sort of publications (Eliza, Tim)

Creating a VIVO authorization policy - an example (Jim, Eliza) – allowing users to edit publications associated with them in the main graph but not in a named graph ingested from an authoritative source

Missing addAuthorsToInformationResource.ftl template in 1.5.1, and missing 1.5.2 zip file? (Michel)

Giving anonymous users access to the VIVO SPARQL page (Patrick@RPI, Jim) – see  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Does VIVO not use standard content negotiation for the endpoint? – looks like I have to add &resultFormat=RS_JSON&rdfResultFormat=N3 or whatever I'm wanting to get back

• The page is structured more like a query page, so we had not anticipated needing content negotiation

SPARQL query to add citation counts for articles (Eliza, Tim)