1. An Application Profile and Prototype Metadata Management System for Licensed Electronic Resources Adam Chandler Information Technology Librarian Central Technical Services 110C Olin Library Cornell University Ithaca, NY 14853-5301 email: alc28@cornell.edu CS502, 12 March 2001

3. N authentication session management menu system authorization ERL Z39.50 URL THIN interlinking source: Herbert Van de Sompel

10. Dublin Core Metadata Element Set Title: A name given to the resource. Creator: An entity primarily responsible for making the content of the resource. Subject: The topic of the content of the resource. Description: An account of the content of the resource. Publisher: An entity responsible for making the resource available. Contributor: An entity responsible for making contributions to the content of the resource. Date: A date associated with an event in the life cycle of the resource. Type: The nature or genre of the content of the resource. Format: The physical or digital manifestation of the resource. Identifier: An unambiguous reference to the resource within a given context. Source: A Reference to a resource from which the present resource is derived. Language: A language of the intellectual content of the resource. Relation: A reference to a related resource. Coverage: The extent or scope of the content of the resource. Rights: Information about rights held in and over the resource. source: http://dublincore.org/documents/dces/

11. Dublin Core Qualifiers source: http://dublincore.org/documents/dcmes-qualifiers/

13. Missing Metadata (1/2) Access — Is the resource or aggregation freely accessible to all users? To the entire university community (including visiting scholars, emeritus faculty, alumni, distance learners, etc.) or only to currently registered students, active faculty, and currently employed staff? To only those students and staff affiliated with certain departments or programs? Only from certain IP addresses? (List address ranges.) Only from on-site locations (individual libraries, buildings, etc.)? Is access available to walk-in users not affiliated with the university? Number of simultaneous users — Mention any special provisions for temporary use by larger numbers of workshop or seminar participants. Price — Include special pricing information. Discount if ordered by a particular date? Discount based on membership in consortia or other organizations? (Include membership number.) Discount tied to continuation of print subscription? (Include link to record for print version, if applicable.) Are there separate costs for content, print access, and electronic access? Or are print and electronic versions priced separately? Payment history — Payments made, payments due, payments anticipated in future. source: http://campusgw.library.cornell.edu/corc/

14. Missing Metadata (2/2) Library’s representative — Person responsible for negotiating with the publisher and initiating subsequent inquiries. Usually the acquisitions librarian, although this role may be delegated to someone else (a selector, government information librarian, etc.). Publisher’s representative — Name, address, e-mail address, and phone number of the individual representing the publisher or distributor. Indicate when contact information was last updated. Fund code. Subject or department code (a separate field — not part of the fund code). Endowment budget code (a separate field — not part of the fund code). License highlights — Does the license allow for printing? Downloading? Sharing with outside users (interlibrary loan)? File transfer in electronic form? Transfer in printed form? Educational use only? Duration of the license? Who keeps back issues if the license expires? Do we own or lease the resource? (In general, the license fields should indicate which uses are authorized — not which uses are not authorized.) Link to full-text image of the complete license agreement. source: http://campusgw.library.cornell.edu/corc/

16. Application Design Considerations Borrow metadata element definitions (e.g., Dublin Core) where possible Facilitate agreement on necessary metadata elements required for this application Identify redundant metadata in other, related systems Locate hooks (identifiers) for future linking to other systems Create a prototype Web database which may be adapted to various local needs Create (and register?) XML Schema

19. A Web Hub for Investigating Metadata Management Systems for Licensed Electronic Resources. Maintained by Adam Chandler and Tim Jewell http://www.library.cornell.edu/cts/elicensestudy/home.html