Agenda

please add or suggest any additional items

Updates

  • Brown – (Steve). Two new sources of information from campus databases – one that tracks departments and faculty positions, and a course management system.  They are working on defining courses, and have added a couple of new classes for departments and positions.  Have added an administrative unit class, and have differentiated current and historical positions so that they can be tracked in different parts of the page. Have also created a class for honorary positions.
    Digging into unclassified documents from the bulk dump from the outsourced CV data extract – and see the reprints issue described below. It's more common in the humanities to have works re-published in other formats or as excerpts, with the persistence of a work significant in addition to the number of works – e.g., the number of translations of a work or the number of anthologies it is brought into, as one form of recognition by your peers.  In music the example might be that a work the person composed being performed by a prestigious symphony orchestra – which could be shown on the work but also wants to appear on the faculty member's page.
  • Duke – (Amber) – focusing on support materials, development, and the user manual for the School of Medicine rollout – focusing on power users, and doing a gap analysis against current legacy system – hopes to have some items to report from that effort in the future.  Doing a "bug mash" with the development team this week to do a lot of testing of drop-down lists, etc, and checking for accurate representation. Would be happy to do a demo of their customized interface at a future meeting.
  • EPA –
  • Florida – 
  • Memorial University of Newfoundland – (Lisa). Still planning the knowledge brokering ontology work; looking at VIVO in the development environment and doing hiring.
  • Johns Hopkins – (Jing). Working on the match between the current enterprise research profile and the VIVO research profile; and still working on the Pubmed Harvester, though are trying to cover all faculties.
  • NARCIS (Netherlands) – 
  • Scripps –
  • UCLA –
  • Weill Cornell – (Paul).  Still working on new publications ingest method, and looking with the Faculty Affairs at Person types to characterize who is faculty (~1315) vs. courtesy, affiliated, emeritus, part-time, etc., including people who fall into multiple categories.  One use case is to define the boundaries for certain types of reports, but are also interested in who's publications to grab – especially if someone has an adjunct appointment at Weill but a primary appointment at another institution. Can likely not to be able to get review of publication data for people with only secondary appointments.  If want to distinguish primary faculty from affiliates, we recommend making two subclasses of Faculty Member to be able to keep the counts separate.
    We need a wiki page to review the different requirements for types of people and need to avoid defining types by what they are not – non-faculty academic, or non-university personnel.
  • Cornell Ithaca – 

Current open issues

  • Adjunct and visiting appointments, plus who is and isn't faculty
Recognition for secondary works (from Steve at Brown)

On the humanities front, I'm still wrestling with the notion of recognition or accolades implied by the mention, translation, reprinting, etc. of a work. That is, many humanities faculty list on their CVs if a work (or worse, a selection from a work, like an excerpt from a book of poems) is reprinted in a journal, incorporated into visual art, included in an anthology, etc.

The VIVO ontology has ample properties for representating these relationships ("Work1 includedIn Anthology1"), but the way RDF markup and VIVO's display works, these properties are related to the document object. While that is logically and ontologically correct, those relationships will only be displayed on the document's profile page. I think faculty want to see these reprint/inclusion events represented on their own profile page as well. So, that's the long way of asking: how do we deal with reprints as a form of professional achievement? Is this something that has to be modeled, or should we just find new ways to display existing property relationships?

Notes on the call: probably want the original works in one section of the CV, but additional re-instantiations somewhere else.

  • research area/interest and description (JHU) - Some faculty would like to separate expertise from research interest, and have description associated with each research area.  For a faculty with several research areas, vivo:researchOverview need be sliced for consumption by a project website, which only display description of one or two research areas.

    • in a brief discussion on the call, we ascertained that the descriptions of research interests need to be separate entities linked to both the person and the research area, a concept typically from a controlled vocabulary, that may be linked to by several people and/or organizations or projects. This is not a role but more of an annotation on the connection between the person and the research area or topic.

Implementation Fest planning

  • Will be held in Boulder, Colorado, a 45-minute bus ride from Denver International Airport
  • Dates still being finalized pending confirmation of rooms, with April 11-12, April 15-16, and April 25-26 the most likely

Upcoming CTSA Ontology Workshop

  • The workshop agenda includes some VIVO and CTSAconnect presentations on the Integrated Semantic Framework and Kristi Holmes discussing Impact Assessment and Evaluation
  • meeting on February 11 & 12 is full but presentations will be online afterwards

Other issues as time permits

WebEx Call-in Information

  • Topic: 2013 Bi-weekly VIVO Ontology Call
  • Date: Every 2 weeks on Wednesday, from Wednesday, January 23, 2013 with no end date
  • Time: 11:00 am, Eastern Standard Time (New York, GMT-05:00)
  • Meeting Number: 648 855 983
  • Meeting Password: (This meeting does not require a password.)

To join the online meeting

Call-in Information

 

  • No labels

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