Agenda
Calls are held every other Wednesday at 11 AM Eastern Time.
Please add or suggest any additional items
Updates
- Brown
- Duke
- Florida
- Johns Hopkins
- Memorial University
- NARCIS
- North Texas
- Scripps
- Virginia Tech
- Weill Cornell
- Cornell Ithaca
Discussion Topics
Shedding light on the reasoning behind the two "editor" properties
- Paul responded: editorOf is similar to authorInAuthorship. This would apply to a specific publication published on a particular date - an article, a book.
On the other hand, the editor role refers more to an ongoing activity in, often enough, a journal's publication management team (e.g. Dr. X is editor of/at the journal Nature). This is not a contribution defined by a particular date, but is more likely to be associated with a certain time range.
That said, I think the distinction is confusing enough to end users that our team is considering hiding the editorOf property from them. We have no authoritative source for these data, and it would probably be used fairly infrequently. What we might lose in comprehensiveness, we might gain in clarity. - (Jon) Paul has nailed down the distinction in intent perfectly. He's also right that (as is Steven, who raised the question) that it's confusing. Some thoughts
- we should at least be consistent in supporting the same pattern for an editor as for an author, via an Editorship comparable to an Authorship. We originally set up the direct editorOf property thinking that multiple editors would be rare and not likely have an established order, which has proven false in an example close to home (look in "additional document info").
- We had some discussions with Hal Warren and Brian Dennis of the APA at the Implementation Fest in Boulder about peer review systems, and what is meant by being editor of a journal is also not clear, and doesn't cover being a reviewer for an article or journal. Quite apart from terminology, they consider individual reviewer information to be highly confidential, even at the level of being a reviewer for a journal, not just an individual article.
- It may be cleaner, especially in the ISF, to think of an editor role as an editor relationship
- It may be cleaner, especially in the ISF, to think of an editor role as an editor relationship
Review and prioritization of changes for VIVO 1.6
see VIVO Ontology v1.6 Planning
and the current list of outstanding issues for version 1.6 in Jira
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
- Call the number below and enter the access code:
- Call-in toll-free number (US/Canada): 1-855-244-8681
- Call-in toll number (US/Canada): 1-650-479-3207
- Global call-in numbers: https://cornell.webex.com/cornell/globalcallin.php?serviceType=MC&ED=169403917&tollFree=1
- Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
- Access code:648 855 983
