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

These calls now use WebEx and have no limit on the number of attendees – see the "Call-in Information" at the bottom of this page.

Global VIVO call February 20 at 4 pm ET

Alex Viggio and Jim Blake are en route to Australia for next weeks Research Networking event February 18 and will be meeting with other VIVO implementers and developers from Australia and New Zealand next week.  They have worked out plans to do a live call on February 20 at 4 pm with updates from Down Under; we hope to have participation from the UK and Netherlands as well.

Updates

  • Brown
  • Buffalo -
  • Colorado
  • Cornell
  • Duke
  • Florida
  • Indiana - trying to load some UF SQL dumps to test performance and caching of visualizations. Taking 18+ hours to load to load on Mac system; getting access to a faster machine which should allow them to move forward.
  • Johns Hopkins --
  • Memorial University --
  • NYU –
  • Scripps --
  • Stony Brook – Erich wrote up a demo of WebID work he's done.  Go to ebremer.com to see webID in action. Stony Brook implementation is going forward, had to reboot some things as administrators have come and gone.  WebID attractive for VIVO because foaf profiles already in place, with the only real new addition being the public key data.  There's a small ontology for public key; Erich will send out an email to the dev group about this.  Would be good to be included in VIVO distribution / ISF.   Some security/stability issues to consider related to hackers and malicious or simply oversized "foafiles."  Do we want to have a shorter "business card" profile would link to larger things so servers don't have to download giant profiles in one fell swoop?   For optimization reasons it would be useful to have a short and long version with a seeAlso kind of reference. 

  • UCSF – Eric - very busy week.  Finally launched new version of Profiles that supports the VIVO ontology, several months in the making.  Probably, other than Harvard, the only ones to upgrade to the new version.  Frees up time to do other things they want to do.  The older code had API for extracting data – native XML, but they created a JSON version.  Extremely popular; dozens of sites that use this API to consume data in real time.  All but one use the JSON API; people love JSON.  Now that they're on the new version, they're going to migrate things to linked open data.  Promote people using things outside of OpenSocial.  Looking at how to get the Linked Data out as JSON.  JSON-LD seems more standard than Elda, and there are libraries that support it.  Lots of Drupal sites that integrate data right at the HTML layer doing runtime grabs.  With JSON that's a feasible solution. 

    • BL: What should we include in standard/"extended" linked data responses?  EM: Very PubMed-centric, people want PubmedID in any deep copy of data.  It would be nice to specify shallow/deep linked data request that would be standardized across systems. 

    Repost a lot of live data that they get from other places, e.g. tweets from Twitter, slides from SlideShare, going to do a Youtube thing.  There's a need for people who contact their APIs to get some of that data re-sent through their API.  Question of republishing linked open data from other systems?  Pragmatic concern.  People don't care about where exactly data is coming from; they just want it.  BL: Licensing questions?  EM: Most things they're using are pretty open about their data.  Most things have textual branding that at least points back to source.  Search benefits – would be good to get tags from things like Youtube videos into the internal search engines.

  • Weill Cornell --
  • other --

2013 Implementation Fest plans

  • Thursday and Friday, April 25-26 have been selected as the dates for the VIVO Implementation Fest.
  • A community hands-on development day is planned as an optional additional activity on Saturday the 27th.
  • The 2013 VIVO Implementation Fest page has basic information on transportation and hotels and will be fleshed out in the coming weeks as the schedule is confirmed. The 2012 VIVO Implementation Fest page has additional information about last year's schedule and presentations.

Notable implementation and development list traffic

Call-in Information

Topic: VIVO weekly call

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 view in other time zones or languages, please click the link: https://cornell.webex.com/cornell/globalcallin.php?serviceType=MC&ED=167096322&tollFree=1

If those links don't work, please visit the Cornell meeting page and look for a VIVO meeting.

To join the audio conference only

Access code:645 873 290

last meeting | next meeting

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.