Versions Compared

Old Version 1

changes.mady.by.user Alex Viggio

Saved on

compared with

New Version Current

changes.mady.by.user Layne M. Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Calls are held every Thursday at 1 pm eastern time – convert to your time at http://www.thetimezoneconverter.com

 

Google doc for notes: http://goo.gl/NXauB7

 

Announcements

  • VIVO 1.6.1 Release Notes

  • Ontology Working Group: next call is Thursday, April 17 at noon EST/ 9 am PST – note proposed new time

    • addressing persistent VIVO URIs and related issues

    • next call will be focused on datasets and dataset ontologies, including options to engage with a W3C working group active in that area

  • The next Apps & Tools call is April 15 at 1PM EST

    • A great call with Violete Ilik from Texas A&M demonstrating  -- she has recorded special specific YouTube videos on how to ingest data into VIVO

    • Find links to YouTube videos of all previous calls there

    • Alex Rademacher (IBM Brazil) and getting specialized data into RDF and then into VIVO  - Alex will present later in the month or in May.  

    • Apps and Tools workshop at the conference. Looking for participants to do demos -- looking for the best ways to create, use, visualize VIVO data and would love to have additional authors and help

  • VIVO Bootcamp at ELAG 2014(June 10 at University of Bath, United Kingdom)

  • 2014 VIVO Conference Call for Paper/Poster/Panel Proposals is open – deadline extended to this Friday, April 11

Upcoming Activities 

  • First Roll out of first annual survey of VIVO sites

  • Will be circulating to working group leads for review and will then put it out more widely

  • Scheduling next themed weekly call topic – April 24th: Topic TBA – seeking volunteer facilitators for themed calls

Site Updates

  • Moving to bi-weekly update schedule – updates next week

  • Attendees: Cornell, Weill-Cornell, Smithsonian, UF (Florida), Virginia Tech, RPI, Duke, Stony Brook, Brown, Symplectic

Theme: Launch of First Annual VIVO Survey

  • Designed

    • designed

  • to be one survey per site, that can be passed from one team member to another

  • We are thinking of using this call next week as time for facilitated survey submission from participating sites  

Updates

  • Brown (Steve) -- working on getting more pieces needed for release, and then on adding additional publications in prep for release in early May

    • will let us know when we can take a look at it

  • Cornell (Jim, Huda, Brian, Jon)

    • Release 1.6.1 release candidate 3 -- finding some small bugs but we each have other projects -- looking to get this thing tested and out the door

    • At this point we don’t anticipate another bug release before 1.7 -- sometimes difficult to determine when to defer the release for new bugs that crop up

    • The current code is always in the 1.6 maintenance branch on GitHub

  • Duke (Patrick)

    • Initial feedback after rolling out to our A&S school.  Most of the feedback Julia and the provost office has been handling. We are going to be making a couple of tweaks. We have also gotten feedback on potential enhancements/changes to the search results. Still collecting those before making changes.

      • Some faculty didn’t see the “more” button at the bottom of their publications

      • Law School would like to see changes in some of the search results, to have only a named person to show up

      • Julia: “Rollout and fallout”

      • updating to 4.6 version of Elements API

      • released our ontology extensions including artistic works (https://github.com/OIT-ADS-Web/duke_vivo_ontologies) and the vivo_mapper we use for our data ingests on Github (https://github.com/OIT-ADS-Web/vivo_mapper). We will email the group with more details.

  • Florida

    • Sending 3 folks out to American Medical Informatics Association Clinical Research Informatics/Translational Biomedical Informatics conference to present 2 posters on VIVO work.

    • Added 6000 sponsors to our VIVO (NIH, NSF, etc…) and manually cleaned them up -- have categorized as companies, governmental organizations, etc.

    • closed almost 280 “Data Quality” issues on our github DQ site: https://github.com/ufvivotech/ufDataQualityImprovement/issues?state=open 

      • has really helped to have a directed effort towards improving data quality

    • Adding building numbers & locations, ? Need help/advice with the best way to store LAT and LONG in VIVO. aka ontology+label examples?

      • where would you put that? have people’s phone numbers and have the location in buildings based on network jacks

      • Eric -- Profiles has latitude and longitude

        • added a property so anything could have it

        • may not be ontologically the best thing to do

      • Do it through the VCard?

        • Brian -- DBPedia uses the W3C WGS84 geo ontology that has properties for latitude and longitude http://www.w3.org/2003/01/geo/ 

        • as long as those are pretty generic properties in terms of domain restrictions, those are likely the best bet

  • Memorial University (John and Max)

    • Are interested in following the discussion on tagging latitude and longitude to tag projects and other work that academics are doing, so they can be put on a map at some point

    • testing VAGRANT on an Ubuntu install

    • digging ourselves out -- summer is August 1 to August 20 -- a 50 centimeter snowfall in spring is now called a sprinter

  • UCSF (Eric)

    • Diving back into the cross-linking project and hopes to talk about at the project

    • Crawling a bunch of data and switching over to a Fuseki back end from a relational one. Crawling about 20 institutions and putting in coordinates based on the institution, but Profiles has coordinates on the individuals

    • Working with JSON-LD -- the crosslinks tool spits that out for the co-authors, and JSON-LD has advantages. If work with the JSON-LD raw, is not easy to work with, but if goes through a parser there are built-in functions that will do things like pull out all the people to make it easier to work with, and becomes a smaller data packet to send over the wire. Will have it live on UCSF Profiles soon -- in one case have found co-authors at over 20 different institutions

  • Virginia Tech (Julie and Keith)

    • Learning ontologies and SPARQL

    • Elements project is moving forward and have first call with the Symplectic team tomorrow to plan implementation

      • have Web of Science but not Scopus

      • we have Digital Measures -- will be migrating data from that application to Elements

      • had one preliminary meeting with local people on importing data from Banner

      • Cornell has a pathway from Digital Measures (Activity Insight) to VIVO and from VIVO to Elements, and will be developing a pathway from Elements to Activity Insight as well as to the VIVO 1.6 ontology

  • Weill Cornell (Paul)

    • VIVO Dashboard (did I share this before?)

    • we *think* we (Eliza) have succeeded in backporting cache awareness to 1.5.2 and committed the changes to the source; looking forward to promoting it to production before even before moving to 1.6???

    • our performance test results in case anyone is curious - https://docs.google.com/spreadsheets/d/129EUW-ac46ok69g3UZHdfmDtvEMYGEyheSLM-kmYj5s/edit?usp=drive_web 

      • the Ithaca team is loading Weill data, images, and code to try to reproduce timings on a server here – timings will be different absolutely but also may vary relatively

      • it will be then more possible for the development team to instrument the application to detect where time is being lost as well as experiment with changes that could improve performance, especially on very large pages

    • Harvester question

      • sent an email on a Saturday -- several ways to use the Harvester to bring in data, with one being to directly match against records in VIVO and another to indirectly use a third source

      • what is the prevailing practice?

        • Patrick -- don’t use the Harvester but do match directly against the triples the data

        • Cornell -- option B

        • Florida does Amazon RDS that does real-time syncing, but could be done with MySQL

          • database with 21 million triples is just 4 Gb so not necessarily large in scope in comparison

          • and the rate of change in transaction input is not that high -- more like dozens per

        • John Fereira will be the maintainer for the Harvester, and Ted and Chris Barnes have offered to facilitate the process; Stephen Williams is still available to answer questions and suggest changes

Notable list traffic

  • .

    • please use the mailing list for any questions that come up

    • the survey is fairly extensive, but can be saved so it can be filled in via multiple sessions and/or by multiple responders (e.g., a policy person, an ontology person, and a developer)

    • be sure when you save the survey to resume later you record the URL you are given -- if you don’t use that you will have to start over

  • Paul Albert and others will facilitate online survey process for call attendees

    • And Paul will send out the link below and highlight the point that if you save midway you need to copy and save the link to be able to resume

    • How do you want to receive feedback?

      • e.g., what’s the definition of a profile -- all foaf:Person entries or the count of people within the institution -- see the FAQ on the project wiki page listed below

  • Timeline -- encourages submissions by June 30, 2014 to be included in Paul’s proposed conference presentation

    • Note that Profiles institutions are also being surveyed (with a shorter survey)

  • See project wiki page for more information and an FAQ

  • The VIVO survey link: https://www.formstack.com/forms/?1704676-gIMWlsYzom 

  • Early feedback:

    • yes, it’s long but I can leave blank questions that aren’t applicable

    • would provide very useful information in making the case for VIVO

    • looks like good information -- interesting to see some of the results

    • would it make sense to have different responses from the same institution? For this time, one per institution is what we’re looking for

  • Thanks to Paul for creating the survey!

Notable list traffic

Call-in Information

  • Date: Every Thursday, no end date
  • Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)
  • Meeting Number: 641 825 891

To join the online meeting

...

:

...

To join the audio conference only

...

 

1. Call in to the meeting:

   1-855-244-8681 (Call-in toll-free number (US/Canada))

...

   1-

...

650-

...

479-

...

3207 (Call-in toll number (US/Canada

...

))

    

2. Enter the access code:

   641 825 891 #

3. Enter your Attendee ID:

   8173 #