NISO RP-10-2010 Cost of Resource Exchange (CORE) Protocol《资源成本交换协议(CORE)》.pdf

1、 NISO RP-10-2010 Cost of Resource Exchange (CORE) Protocol August 2010 Abstract: CORE defines an XML schema to facilitate the exchange of financial information related to the acquisition of library resources between systems. The two systems may be within the same organization, e.g., an ILS and an ER

2、MS, or from two different organizations, e.g., a subscription agent and a library. A Recommended Practice of the National Information Standards Organization About NISO Recommended Practices A NISO Recommended Practice is a recommended “best practice“ or “guideline“ for methods, materials, or practic

3、es in order to give guidance to the user. Such documents usually represent a leading edge, exceptional model, or proven industry practice. All elements of Recommended Practices are discretionary and may be used as stated or modified by the user to meet specific needs. This recommended practice may b

4、e revised or withdrawn at any time. For current information on the status of this publication contact the NISO office or visit the NISO website (www.niso.org). Published by NISO One North Charles Street Suite 1905 Baltimore, MD 21201 www.niso.org Copyright 2010 by the National Information Standards

5、Organization All rights reserved under International and Pan-American Copyright Conventions. For noncommercial purposes only, this publication may be reproduced or transmitted in any form or by any means without prior permission in writing from the publisher, provided it is reproduced accurately, th

6、e source of the material is identified, and the NISO copyright status is acknowledged. For permission to photocopy or use material electronically from NISO RP-10-2010, Cost of Resource Exchange (CORE) Protocol, ISBN 978-1-880124-84-0, please access or contact Copyright Clearance Center, Inc. (CCC),

7、 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and registration for a variety of users. Printed in the United States of America ISBN: 978-1-880124-84-0 NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO iii Content

8、s Foreword v 1 Purpose 1 2 Scope 1 2.1 CORE Transactions 1 2.2 Transport Mechanism .1 2.3 Out of Scope1 3 References 2 4 Definitions 2 5 CORE Schema Synopsis 5 5.1 General 5 5.2 CORE Namespace5 5.3 CORE Transactions 5 5.4 Request Design.6 5.5 Reply Design .6 6 Data Dictionary Reference Guide 7 6.1 E

9、lement Listings 7 6.2 Graphic Representations7 6.3 Data Types 8 6.4 Attributes9 7 CORE Data Dictionary 10 7.1 COREDocument10 7.2 Request11 7.2.1 DocumentId 12 7.2.2 Query.14 7.3 Response.19 7.3.1 DocumentId 20 7.3.2 Query.20 7.3.3 RequestProblem.20 7.3.4 Query Reply21 8 Transaction Failure 31 8.1 Fa

10、ilures 31 8.2 Unknown Version Problem .32 8.3 Resubmitted Requests32 NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO iv 9 Profiles 32 Appendix A : CORE Schema 33 Appendix B : CORE Use Cases and Scenarios 40 Appendix C : Security Considerations 44 Appendix D : Summary of CORE El

11、ements 46 Figures Figure 1: CORE protocol interoperability 5 Figure 2: COREDocument element.11 Figure 3: Request element11 Figure 4: DocumentId element12 Figure 5: Query element .14 Figure 6: payment-type attribute17 Figure 7: DatePair element 18 Figure 8: Response element.20 Figure 9: RequestProble

12、m element21 Figure 10: QueryReply element.22 Figure 11: ErrorRecord object .23 Figure 12: AcqRecord element.24 Figure 13: Medium element25 Figure 14: PaymentDetailsRecord element 28 Figure 15: PaymentAmount element .31 NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO v Foreword

13、The NISO Cost of Resource Exchange (CORE) project was first proposed by Jeff Aipperspach (Product Manager, Serials Solutions), Ted Koppel (AGent Verso (ILS) Product Manager, Auto-Graphics, Inc.), and. Ed Riding (Technical Product Manager, SirsiDynix). They felt that the ability to request financial

14、data (whether for display or for writing to populate an ERM) from an ILS acquisitions system would enable both real-time lookups and cost-per-click and other cost-related reports in the ERMS all the more possible, without the work of manually entering the same data in two different systems. Using de

15、fined XML data schemas, they anticipated, a standard would provide a common method of requesting cost-related information from an ILS for a specific electronic resource, within the boundaries of a subscription period. Once defined, implemented and successful, it is likely that this standard could be

16、 expanded to include other elements for purposes not yet envisioned. The CORE Working Group was approved in June 2007 with a three-goal charter: 1) To develop and refine the list of data elements exchanged between an Electronic Resource Management System (ERMS), and Integrated Library System (ILS),

17、Business Systems, and other interested parties holding acquisitions metadata to support the population of the ERMS with financial and vendor information in the automated system. 2) To create a transport protocol useful in moving these data elements from one system to another. 3) To write a small num

18、ber of use cases that will help all parties understand the capabilities of the protocol. Previously, in late 2006, as a next step in the progress of the Digital Library Federations (DLF) Electronic Resource Management Initiative, a subcommittee of the DLF Electronic Resource Management Initiative, P

19、hase II, constituted by Norm Medeiros (Haverford College), Linda Miller (Library of Congress), Adam Chandler (Cornell), and Angela Riggio (UCLA), queried a number of librarians, ERMS suppliers and ILS vendors to discover which elements from an ILS would most likely be required to facilitate cost man

20、agement within the context of the ERMS. They published their findings in the White Paper on Interoperability between Acquisitions Modules of Integrated Library Systems and Electronic Resource Management Systems1. In that white paper, the authors summarized the data elements critical to exchange in a

21、cquisitions as follows: 1Medeiros, Norm, et al. White Paper on Interoperability between Acquisitions Modules of Integrated Library Systems and Electronic Resource Management Systems. Prepared by a Subcommittee of the Digital Library Federations Electronic Resource Management Initiative, Phase II. Wa

22、shington, D.C.: Digital Library Federation, January 2008. Available at: http:/www.diglib.org/standards/ERMI_Interop_Report_20080108.pdf NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO vi Critical Acquisitions Elements Element Name UCLA Cornell University Tri-College Consortium

23、Library of Congress purchase order number X X X X price X X X X start/end dates X X X X vendor X X X X vendor ID X X X X invoice number X X X X fund code X X X invoice date X X X selector X X vendor contact information X purchase order note X line item note X invoice note X The CORE Working Group bu

24、ilt on this work in assembling the data dictionary portion of this recommended practice, defining and validating the data elements to be exchanged, specifying which are required and which are optional, as well as specifying the protocol to be used to transport the data from one system to another. In

25、 March 2009, NISO issued CORE (Cost of Resource Exchange) as a draft standard with a trial period of 12 months. In June 2010, the NISO CORE Working Group met to discuss the progress of the draft standard for trial use (DSFTU) and determine next steps for this publication. During the trial period no

26、systems vendors (ILS or ERMS) implemented or tested the draft standard, and few, if any, systems vendors were willing to commit to implementing the draft standard soon enough to warrant an extension to the DSFTU period. The working group concluded that the lack of implementation is the direct result

27、 of the worldwide economic downturn and not a lack of demand from librarians or interest from vendors. The working group further concluded that there is still high interest in this work. The CORE Working Group is unanimous in believing the work useful for future development as the economy picks up a

28、nd as demand for the exchange of cost information increases. It was with that in mind that they recommended to NISOs Business Information Topic Committee that the CORE draft standard be issued as a NISO Recommended Practice document, with a provision that the Topic Committee revisit this topic in on

29、e year to determine if economics and interest have improved such that the vendor community begins to implement it. The working group further recommended that a standing committee for CORE promotion and review be created to market the recommended practice and help the library community understand its

30、 role in the standards implementation process by requiring its adoption and testing from system vendors. This standing committee would also be responsible for monitoring use of the recommended practice and in making recommendations to NISO regarding future steps regarding the draft standard/recommen

31、ded practice. The Business Information Topic Committee agreed with the CORE Working Group and approved the publication of this document during their July 20, 2010 meeting, with provision to review the document annually for a period of no less than three years, and with the establishment of a standin

32、g committee to provide support and outreach for this protocol. NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO vii Trademarks, Service Marks Wherever used in this recommended practice, all terms that are trademarks or service marks are and remain the property of their respectiv

33、e owners. Business Information Topic Committee At the time this recommended practice was approved for publication, the following were members of the Business Information Topic Committee: Ivy Anderson California Digital Library Karla Strieb Association of Research Libraries (ARL) Linda Beebe American

34、 Psychological Association Helen Szigeti HighWire Press, Stanford University Denise M. Davis American Library Association Helen Henderson Ringgold Kathleen Folger (Co-chair) University of Michigan Library Tim Jewell University of Washington Libraries Herbert Gruttemeier INIST Institut de lInformatio

35、n Scientifique et Technique CORE Working Group Members The following members of the CORE Working Group developed this recommended practice: Jeff Aipperspach Serials Solutions, Inc. Rose Nelson Colorado Alliance of Research Libraries Eric Graham Polaris Library Systems Joined February 2009 Ed Riding

36、(Co-Chair) SirsiDynix Rafal Kasprowski Rice University Dani Roach University of St. Thomas Kathy Klemperer EDItEUR Brian Rosmaita VTLS, Inc. Ted Koppel (Co-Chair) Auto-Graphics, Inc. Clara Ruttenberg Georgetown University Nettie Lagace Ex Libris, Inc. Gracemary Smulewitz Rutgers University Libraries

37、 Debbie Logan EBSCO Information Services Mary Walker Wichita State University Joyce McDonough Columbia University Kelvin Watson The Library Corporation (TLC) Bob McQuillan Innovative Interfaces, Inc. Candy Zemon Polaris Library Systems Through December 2008 NISO RP-10-2010 - Cost of Resource Exchang

38、e (CORE) Protocol 2010 NISO viii Acknowledgments The CORE Working Group gratefully acknowledges the substantial contributions made by Mark Wilson in creating the schema files for the protocol. NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO 1 Cost of Resource Exchange (CORE) Pr

39、otocol 1 Purpose The purpose of the Cost of Resource Exchange (CORE) specification is to facilitate the transfer of cost and related library acquisitions information from one automated system to another. This transfer may be from: 1) an Integrated Library System (ILS) acquisitions module (the data s

40、ource and CORE responder) to an Electronic Resource Management System (ERMS) (the data recipient and CORE requester), both belonging to the same library; 2) a book or serials vendor to a librarys ERMS; 3) a transfer of cost and transaction data among members of a consortium; or 4) any transaction pa

41、rtner to another that can benefit from the sharing of cost and library acquisitions-related data. Using the defined CORE XML data schema, this recommended practice provides a common method of requesting cost-related information by a client application (an ERMS, for example) for a specific order tran

42、saction, a specific resource, or all resources that the library owns, within the boundaries of a payment period or access period. The client requester must supply sufficient request information (e.g., a unique order identifier, a date range) in its request, so that the responding system (an ILS, for

43、 example) can interpret the request, identify the appropriate financial record(s), and respond with the appropriate financial and/or resource data elements. 2 Scope 2.1 CORE Transactions The CORE protocol has been generalized in order to be useful for a variety of transaction partners by identifying

44、 and defining data elements that are generally supported by ILS, ERMS, subscription agents, and materials vendors. The CORE protocol defines the semantics for a set of transactions implied by three defined CORE use cases (see Appendix B). While not every CORE implementation may require the full set

45、of use cases, the design supports all three. An XML schema conveys CORE protocol transactions (see Appendix A). The schema, using CORE-specific derived data types (see Section 6.3), frequently restricts the form and value of data components. The schema presented supports single-query requests with p

46、ossible multi-part replies. 2.2 Transport Mechanism The CORE protocol describes a data structure and not the transport mechanism. While the NISO CORE Working Group recommends SOAP be used as the Web Services transport mechanism, the specifics of the SOAP configuration are beyond the scope of the COR

47、E recommended practice and are left to trading partners to devise. Implementers of the CORE protocol may also use other transport mechanisms that are already in place, such as FTP or SMTP, or even physical transfer media. 2.3 Out of Scope It is not the intent of this recommended practice to specify

48、or restrict whether the request shall be initiated automatically or manually, nor whether the data provided in the response should be used for NISO RP-10-2010 - Cost of Resource Exchange (CORE) Protocol 2010 NISO 2 purposes of display or data population. The recommended practice is only intended to

49、specify the data elements and a schema used in such an exchange. CORE, by definition, is transmitting financial information and, therefore, data transferred in the CORE message should be considered confidential between the two parties. CORE, being the payload, does not include methods for secure transmission. Some suggested methods for securing the CORE payload are provided in Appendix C. 3 References This recommended practice references the following documents. When cited in the text of the recommended practice, the below standards may be referred t