CORE - ER&L Conference 2011 - NISO

fortnecessityusefulDéveloppement de logiciels

14 déc. 2013 (il y a 3 années et 10 mois)

128 vue(s)

Bob McQuillan

Senior Product Manager

Innovative Interfaces


CORE:
C
ost
O
f
R
esource
E
xchange Protocol


(NISO RP
-
10
-
2010)


NISO Recommended Practice


Defines an XML schema to facilitate the
exchange of cost data and other financial
information related to the acquisition of
library resources between one automated
system to another


Request / response model



Integrated Library System (ILS) acquisitions
module (the data source and CORE responder)
to an Electronic Resource Management System
(ERMS) (the data recipient and CORE
requester), both belonging to the same library


Book or serials vendor to a library’s ERMS

(or ILS)


Transfer of cost and transaction data among
members of a consortium


Any transaction partner to another that can
benefit from the sharing of cost and library
acquisitions
-
related data.


Request


ERM


ILS

Response


ILS


Book/Serials Vendor



Cost data pulled into ERMS (or ILS) from
other systems


End duplicate data entry in multiple
systems


Institutional identifiers can help in
automation of data transfer


Derive cost
-
per
-
use in ERM when tied with
COUNTER usage statistics data



DLF Electronic Resources Management
Initiative (ERMI), Phase II (2008)


White Paper on Interoperability between
Acquisitions Modules of Integrated Library
Systems and Electronic Resource Management
Systems
(Norm Medeiros et al)


Several ERM and ILS vendors discussed
feasibility at ER&L 2007, ALA and other
venues



NISO Business Information Topic Committee
approved CORE Working Group


Solicitation of Working Group Members


13 Vendors/Standards organizations


6 Libraries


First meeting: August 6, 2008





Ted Koppel (Auto
-
Graphics)

`
Ed Riding (
Sirsi
-
Dynix
)


Kathy Klemperer (
EDItEUR
)


Nettie
Lagace

(Ex
Libris
)


Brian
Rosmaita

(VTLS)


Rose Nelson (Colorado Alliance)


Joyce McDonough (Columbia)


Debbie Logan (EBSCO)


Bob McQuillan

(Innovative Interfaces)


Kevin Watson (TLC/CARL)





Dani

Roach

(Univ. of St. Thomas)


Mary

Walker (Wichita State)


Clara

Ruttenberg (Georgetown)


Bill

Hoffman (
Swets
)


Jeff

Aipperspach (Serials Solutions)


Rafal

Kasprowski

(Rice University)


Gracemary

Smulewitz

(Rutgers)


Candy
Zemon

(Polaris)


Karen Wetzel (NISO)


Mark Wilson (retired, XML advice)





Not just ERM
-
ILS exchange, but broader
applications


Book/serials vendors, consortia, etc.)


Avoid duplicating work of existing standards
(SOH, etc.)


Keep it simple and generic


Define the data


not the application!!





2008 projects:


Use cases


Common needs, vocabulary, and data elements


Refined use cases to identify CORE elements


XML message structure, transport mechanisms


Draft Standard for Trial Use (DSFTU)

published in March 2009


NISO Z39.95
-
200x











NISO Recommended Practice published in
August 2010


NISO RP
-
10
-
2010


CORE Standing Committee formed in
September 2010











Ted Koppel (Auto
-
Graphics)
-

Chair


Kathy Klemperer (
Harrassowitz
)


Vice
-
Chair


Harry
Kaplanian

(Serials Solutions)


Rafal

Kasprowski

(Rice University)


Joyce McDonough (Columbia University)


Bob McQuillan (Innovative Interfaces)


Rose Nelson (Colorado Alliance)


Dani

Roach (University of St. Thomas)


Clara Ruttenberg (University of Maryland)





XML Schema defines the request and
response mode payload


Simple and compact


Is the “payload” for any web service messages


CORE schema outlines repeatable fields,
Booleans, etc.



Two levels of request / response:

1.
Cost information only

2.
Cost information + Order/Product information


Three types of requests:

1.
Request info for a single order

2.
Request info for a single product

3.
Request transaction info on all products


Queries can filter any of these by access
(subscription) or fiscal year data range



Delivers the CORE payload


Web services can be used as the envelope


Real
-
time/cost information retrieval is
possible using CORE, not just system
generated reports


Also allows adopters to leverage existing
options


E.g., SOAP, FTP, tape, etc.


Requester ID


Order ID


Product ID


Customer ID


Access Period (subscription) data range


Payment Period (fiscal year) date range


Requested data fields


Product ID/Product Name


Payment Amount, Payment Date, Currency


Publisher, Medium, Platform


Vendor, PO Number, Consortium ID


Order ID, Invoice Number, Invoice Date,
Line Item Number, Quantity, Library Fund
Code


Vendors write their applications to use
CORE


Standing Committee (SC) to monitor uptake
of Recommended Practice


SC to provide support and outreach of
protocol


SC to conduct annual review of the Best
Practice document with aim to make future
recommendation for re
-
release as a
Standard publication


Main Website:


http://www.niso.org/workrooms/core/coresc


CORE Protocol:


http://www.niso.org/publications/rp/RP
-
2010
-
10.pdf


Press and Presentations:


http://www.niso.org/workrooms/core/press/


Contact Us:


coreinfo@list.niso.org