Versions Compared

Key

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

...

  • Brown (Steven) – doing another rollout in April; have done a lot of modifications to the list view configurations but are starting to look at custom form changes, too. Are starting to import courses and are trying to decide whether to import some SKOS controlled vocabularies into VIVO to standardize references to the subject areas of courses and publications.
  • Duke –
  • Florida – 
  • Johns Hopkins (Jing) – see highlighted panel below
  • Memorial University of Newfoundland –
  • NARCIS (Netherlands) – 
  • Scripps –
  • UCLA –
  • Weill Cornell – (Paul) – Continuing to implement a method of publications ingest based on individually saved searches for the faculty they most need to track, and to use VIVO to feed another system used for annual reporting. They have been creating links from publications to independent Subject Area entities corresponding to MeSH headings. Question – does Weill use the Stony Brook UMLS web service?
  • Cornell Ithaca – 

Current open issues

Panel
titleResearch interest descriptions

research 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 2013-02-06 VIVO Ontology 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.

In continuing the discussion on this call, Brian mentioned a recent focus by the W3C on support for annotations via the http://openannotation.org/spec/core – it seems more straightforward than reification (giving an RDF statement its own URI and adding multiple additional statements about that statement) and appears to be intended for a similar purpose (applying terminology to resources) to what Jing describes as the use case at Hopkins.

See the Research Areas, Keywords, Interests and Expertise page for additional discussion.

...