Skip to end of metadata
Go to start of metadata

Note change in time – this call will be held at 1 pm Eastern time, not 3 pm


Any updates

  • Colorado
  • Cornell
  • Florida
    • image loading – sizes from ID cards similar in size to what VIVO wants; some random sizes – scaling the smallest number to 250 pixels and centering the image; uses Apache messaging (Active MQ) server at UF; still in dev; will work through staging server next; ~10,000-20,000 images
    • a separate utility that uses the Harvester, similar to the DSR import script that uses the Harvester and is packaged with it
  • Indiana
  • Johns Hopkins
    • talking with University IT - have Digital Measures system (Activity Insight), but not widely used
  • North Texas
  • Weill
    • still trying to figure out the best way to disambiguate names – e.g., K. Lee
    • Griffin Weber has identified that his tool is available separately from Profiles
      From: CTSA Research Networking Affinity Group CTSA_RES_NET@LIST.NIH.GOV On Behalf Of Weber, Griffin M griffin_weber@HMS.HARVARD.EDU
      Sent: Saturday, September 24, 2011 11:09 PM
      Subject: Re: Two things (Direct2Experts, author disambiguation)

Harvard Catalyst Profiles uses a "Disambiguation Service" to import Medline publications for people. This is an XML-based web service that can be used independently of the Profiles software. In other words, you can use it to populate any research networking tool with publications. It uses coauthors, MeSH terms, journal names, affiliations, article title words, and other configurable heuristics in its algorithm. The documentation for the Disambiguation Service is located at the bottom of this page:

    • could potentially be added to the Harvester, or folded in
  • Wisconsin
  • Other:

Mini-grant updates

  • Digital Vita – have sent a proposed My Documents Interface Specification
  • ORCID/Leicester (Mummi Thorisson)
    • Still interested in finishing the CrossRef publication lookup – we should schedule a separate call about what is missing in the VIVO infrastructure to easily use JRuby
    • Will likely adapt v1.3 rich export capability to export data desired for seeding ORCIDs
    • a useful precursor for mass ingest from universities to ORCID
  • Duke Widgets
    • would like to do updates, but focusing on implementation now
    • will use widgets as part of rollout at Duke – have something similar now, so need to to continue

Release 1.4 Planning

  • Harvester plans
    • Plans still being formed – bug fixes and refactoring, comment improvements
    • further integration of the Harvester into VIVO would be a 1.5 thing
  • Visualization plans for 1.4 and representing them in Jira
    • Map of Science visualization – will need some help with the VIVO sparql query part – may be creating new sparql queries
  • updates to the VIVO development Jira space
    • including simple first stage
    • provenance discussions – graph based approach per data source – have to make
    • considering support for sameAs assertions
      • starting to sound a lot like Geoff Bilder's proposal for provenance – Mummi will share that
      • ORCID leaning toward semantic approaches

Release 1.5 Planning

Other topics

please add additional agenda items here


  • Is Vitro capable of handling workflow ontologies?
    • an ontology that would drive forms with semantic data – an existing workflow ontology, a sequence of how certain actions should take place
      • there exists a Tim Berners-Lee document on a workflow ontology – classes of actions and states
    • how could Vitro handle this if it can't now?
      • what did Brian Lowe's RDF workflow language support?
    • use case – a workflow for entering a patient's research/data permissions
      • I select the patient, I see the forms I have to fill out; as soon as they hit the save, goes to the next form
      • Vitro doesn't handle that flow - should there be a separate process that pulls data from Vitro and writes changes back? Or augmented listeners that can look at the state of data in the application? Nothing now to push out a second form to you
      • would need separate application code to run the process that follows an RDF ontology
  • Will Vitro be used for other projects?
    • It would be useful to know, especially if they are doing different things from what VIVO does
    • Note when migrated from version 1.0 to 2.0 of SourceForge, we made Vitro a subproject even thought it's the engine under VIVO
    • New DataStaR IMLS grant will mean that work will go forward, with collaboration with the ANDS/VIVO work
    • Do we need a DataStaR project page? should we look at GitHub, too, if we are going to make a move

Call-in Information

1. Please join my meeting, Thursday, September 29 at 01:00 PM EDT.

2. Call in using your telephone, or use your microphone and speakers (VoIP) - a headset is recommended to avoid echo problems.

Dial 630-869-1015
Access Code: 232-787-753
Audio PIN: Shown after joining the meeting

Meeting ID: 232-787-753

last meeting | next meeting