Posted by Nick on November 13, 2009
The diagram below is Arthur’s update of my earlier quick sketch to illustrate what Bibliosight will aim to achieve by the formal #jiscri deadline.
It is numbered and colour coded – stages 1 – 3 (shades of blue) are within the #jiscri timeframe; stages 2 (green) & 5 (buff) will require ongoing work beyond the deadline.
(N.B. Click on the image for a full size view in a separate browser window.)
Posted in Bibliosight | Tagged: #jiscri, #UseCase, Bibliosight, JournalTOCsAPI, quick sketch, use case, XML, XSLT | 2 Comments »
Posted by Nick on October 1, 2009
I’ve just had a meeting with Sue and Sam (from URO) about use cases. It was useful, as always, to put our heads together and we came up with a quick sketch of a potential infrastructure for Bibliosight that we would like feedback on:
A quick sketch
N.B. This assumes it is possible to programmatically bulk upload XML records to EndNote – I have no idea if this is possible – and to intraLibrary which should be possible based on discussion at the meeting on Tuesday.
The sketch arose from the fact that research administrators currently use EndNote which they wish to continue using as dedicated citation management software for its high level functionality and the need to simplify their workflow rather than expect them to add records to two separate systems. Such an approach could also inform our developing use cases to a) auto-populate the repository with metadata from WoS and b) alert repository/research administrators when an article is published so we can pursue an appropriate full text version for the repository.
Posted in Use cases | Tagged: #jiscri, EndNote, quick sketch, use case, WoS API, XML, XSLT | 5 Comments »
BiblioSight News 