1 / 10

Raptor-JUSE

Raptor-JUSE. Mimas, The University of Manchester . Cardiff University; Cranfield University; EvidenceBase, Birmingham City University. . Raptor-JUSE. Integration of Raptor with JUSP. Raptor-JUSE. Raptor-JUSE.

upton
Download Presentation

Raptor-JUSE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Raptor-JUSE Mimas, The University of Manchester. Cardiff University; Cranfield University; EvidenceBase, Birmingham City University.

  2. Raptor-JUSE • Integration of Raptor with JUSP. Raptor-JUSE

  3. Raptor-JUSE • Raptor collects event based information about what resources people authenticate to. • Shibboleth • Ezproxyetc. • Raptor has a UI to report on this information. • JUSP collate and aggregate Journal usage from the service provider end. • NESLi2 publishers using Counter Statistics. • JUSP presents this information through their stats Portal.

  4. Raptor-JUSE (Raptor) • Raptor can collect and report on a wide range of authentication events e.g. journal publishers through to an institutions local wiki or mail provider etc. • However, when logged into a publishers website, lacks fine grained information about what articles, journals, and books etc. a user accesses.

  5. Raptor-JUSE (JUSP) • One-stop-shop for libraries to view, download and analyse their fine grained usage reports. • However, only currently supports a limited subset of sites in use. Furthermore, other types of resource usage information is of course out of scope.

  6. Raptor-JUSE • Provide a single, unified place to obtain information from both sources of information. • Treated individually at first. • Will look at ways to map between systems (identifier) where possible. • will look at statistical overlaps. • Deal with different reporting periods i.e. Raptor is per event, JUSP uses defined reporting periods.

  7. Project Plan • Work package 2. (1st August 2012 until 31st May 2013) • Discuss architecture of integration • Review data model from Raptor and JUSP • Explore options to view JUSP usage in Raptor • Work package 3. (1st September 2012 until 31st March 2013) • Develop linkage between Raptor and JUSP • Develop JUSP API • Enhance Raptor UI • Produce technical unit and integration tests • Work package 4. (1st August 2012 until 30th April 2013) • Evaluate quality of integration and usefulness from pilot institutions. • Work package 5. (1st August 2012 until 31st May 2013) • Dissemination and reporting • Workshops • Promote live service • Work Package 6. (1st May 2013 until 31st May 2013) • Productionalise new service components • Support documentation, sustainability planning • Announce service

  8. Integration • Use a modified Raptor ICA component to pull information from the newly developed JUSP-API on a monthly basis.

  9. Raptor Presentation of JUSP • The modified Raptor component can then be configured to push these JUSP-Events to an institutions Raptor server. • An institutions Raptor server then persists this information alongside other Raptor-Events. • JUSP monthly stats can then be viewed in Raptor in a way consistent with other Raptor events.

  10. Immediate Future Work • Produce a new wizard like interface for easy selection of Raptor-Events and JUSP-Events within Raptor. • Allow the wizard interface to *show* both Raptor authentication events alongside JUSP events (Jr1 etc.) for a given period graphically for visual comparison.

More Related