1 / 63

eXtensible Catalog

eXtensible Catalog. Jennifer Bowen University of Rochester. Agenda . What is XC and why are we building it? XC’s approach to metadata XC Schema XC Services XC software overview: how does it work? The XC Metadata Services Toolkit Wrap-up, and What’s next?. What do libraries need?.

turner
Download Presentation

eXtensible Catalog

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. eXtensible Catalog Jennifer Bowen University of Rochester

  2. Agenda • What is XC and why are we building it? • XC’s approach to metadata • XC Schema • XC Services • XC software overview: how does it work? • The XC Metadata Services Toolkit • Wrap-up, and What’s next?

  3. What do libraries need? • Better web presence for resource discovery • A low-effort solution (keep ILS) • Metadata that “works” on the web • An affordable solution • Choices, flexibility

  4. Enabling multiple baskets

  5. The eXtensible Catalog • Set of open-source tools • Facilitate resource discovery and metadata management • Funding from Andrew W. Mellon Foundation and from XC partner institutions • Software release: March 2009 (but still being developed) • Governance: not-for-profit

  6. XC will provide… • Architecture for moving and managing metadata using OAI-PMH • Works with other OAI-PMH applications • Five separate “toolkits” • Out-of the-box user-interface functionality • A different paradigm for moving and managing metadata

  7. Partnerships User Research Partners: Cornell Ohio State Yale Rochester Technology Development Partners: Notre Dame SUNY Buffalo Georgia PINES Aleph Evergreen RIT Oregon State LibLime III Koha Rochester CARLI (Illinois) Casey Bisson Voyager Scriblio

  8. eXtensible Catalog Project • Studying users • Building software • Defining governance

  9. Studying Users • Survey of 68 representative libraries • Wanted to address not-yet-identified user needs • Twenty interviews at each site • On-camera search • Magic wands • Team based analysis

  10. Building Software • User Interface: Next-generation library website and search interface • Metadata Tools: Aggregate metadata from various repositories to enable fast searching • Connectivity: Create open standards interfaces to Integrated Library Systems

  11. Defining Governance • Creating the eXtensible Catalog Organization • Host the software and make it available • Foster a community of users and developers • Address software bugs • Encourage code contributions by other software developers

  12. How is XC different? • Metadata management • Aggregation • FRBRization • Improves other discovery interfaces • Uses standards • Native web content • User generated metadata

  13. XC software toolkits • OAI Toolkit • NCIP Toolkit • Metadata Services Toolkit (MST) • Drupal Toolkit • Learning Management System Toolkit

  14. XC’s Metadata Services Toolkit • Based upon proposed NSDL metadata services hub (Hillmann, Sutton, Phipps) • Enables libraries to aggregate metadata and run services on it • User interface for managing metadata services • NOT a metadata editor (but can eventually incorporate one)

  15. XC metadata Suck it in • Harvest metadata using OAI-PMH Clean it up • XC Metadata Services Toolkit (MST) Share it • MST and XC user applications

  16. XC advantages for metadata • Enables automated handling of metadata changes: • New records, updates, deletes • Propagates changes throughout the system • Web interfaces for trouble-shooting • Low risk of data corruption (easy to fix) • Ideal platform for experimentation

  17. The XC schema: Why? • Wanted a FRBR-based schema • Waiting for RDA not an option • Needed a schema to enable XC user interface functionality • Retain granularity of MARC • Facilitate transformation from Dublin Core • Eventually: DC application profile

  18. The XC schema: Elements • All properties from dcterms namespace • 22 RDA elements (rdvocab namespace) • 11 RDA role designators (rdarole namespace) • XC namespace: 37 elements • Parallel elements to DC properties • Other elements needed for XC functionality • User-generated metadata – next step

  19. The XC schema: Structure • Five levels: FRBR Group 1 levels • Work, expression, manifestation, item • Also a level for “Holdings” • Between manifestation and item • “Placeholder” for summary holdings data • A valid record can have any one level, multiple levels, or multiples of one level

  20. Advantages of the XC schema • Flexible, extensible • Optimized to enable XC functionality • Will give us experience manipulating separate records that represent individual FRBR levels • Not intended for general use • Can be as complex as it needs to be

  21. Sharing metadata • Share MARCXML, with enrichments • Share other schemas with enrichments or transformed • Share XC Schema • Share user-generated metadata

  22. Sharing software • Share metadata enrichment services • Libraries can use an existing XC service as is or modify it • Libraries can develop and share additional services

  23. XC metadata services • Normalization: transform coded metadata so that it can be used/displayed • Schema transformation: • MARC to XC, DC to XC • FRBRization • Authority control matching • Aggregation

  24. Normalization Services • MARCXML, Dublin Core • Stays in same schema • Prepares metadata for use in web applications (faceted browse interface) or back into an ILS • Examples of normalized coded data: • Location codes • Languages • Type of material

  25. Transformation Services • MARCXML to XC Schema; DC to XC Schema • Parses data into FRBR Group 1 entity structure (work, expression, manifestation, item, plus holdings) • Creates additional works and expressions for MARC analytics (7XX fields)

  26. Authority Control Services • MARCXML, Dublin Core • Match headings against MARCXML authority resource file • Populate records with authority control identifier • Tool for debugging probable, unlikely matches • Prototype developed by RIT students

  27. Aggregation Service • Prepares metadata for use in XC user interfaces (Drupal and LMS Toolkits) • Aggregates records that represent the same resource • Manages relationships between records • Will give us experience managing FRBRized records

  28. New roles for catalogers • Design and test metadata services • Manage flow of metadata • System/application design • User research

  29. XC Software Overview

  30. Software Overview • User Interface: • Metadata Tools: • Connectivity: Drupal Toolkit LMS Toolkit Metadata Services Toolkit Record Cleanup FRBRization Authority Control Aggregation OAI Toolkit NCIP Toolkit

  31. Software Overview • User Interface: Drupal Toolkit LMS Toolkit Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization NCIP Authority Control Aggregation • Connectivity: OAI Toolkit NCIP Toolkit OAI-PMH OAI-PMH ILS Repository

  32. Software Overview • Moves metadata with OAI-PMH • Existing sources • OAI Toolkit + ILS • OAI Toolkit + repository • All XC components can talk OAI-PMH • Works with any metadata schema • Synchronizes

  33. Software Overview • Integrates circulation with NCIP • NCIP Toolkit + ILS • XC discovery interface talks NCIP • Live circulation status • Authentication • Places circulation requests (hold, recall, etc)

  34. Software Overview • User Interface: Drupal Toolkit LMS Toolkit Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization NCIP Authority Control Aggregation • Connectivity: OAI Toolkit NCIP Toolkit OAI-PMH OAI-PMH ILS

  35. Metadata Services Toolkit • New type of cataloging tool • Services • Automated • Configurable • Pluggable • User interface for library staff, not end users Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  36. Software Overview • User Interface: Drupal Toolkit LMS Toolkit Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization NCIP Authority Control Aggregation • Connectivity: OAI Toolkit NCIP Toolkit OAI-PMH OAI-PMH ILS

  37. Software Overview Search Features • Out-of-the-box search interface • Faceted-browsing of results • Include traditional, digital, and website resources • FRBRization – group related resources by “work” • Easy and robust search customization • User Interface: Drupal Toolkit LMS Toolkit

  38. Software Overview Platform for your library website • Integrate discovery with library website • Capture and display user generated metadata • Free add-on features (e.g. tagging, blogs) • Build custom applications • Share code with other libraries • User Interface: Drupal Toolkit LMS Toolkit

  39. Software Overview Learning Management Features • User interface for librarians and instructors to: • Associate a resource with a course or range of courses • Migrate associations • Display library resources within an LMS • Blackboard plug-ins included • Other LMS support through web services Drupal Toolkit LMS Toolkit

  40. Software Overview • User Interface: Drupal Toolkit LMS Toolkit Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization NCIP Authority Control Aggregation • Connectivity: OAI Toolkit NCIP Toolkit OAI-PMH OAI-PMH ILS

  41. Metadata Services Toolkit • New type of cataloging tool • Services • Automated • Configurable • Pluggable • User interface for library staff, not end users Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  42. Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  43. Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  44. Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  45. Metadata Services Toolkit Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  46. Metadata Services Toolkit Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  47. Metadata Services Toolkit Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  48. Metadata Services Toolkit Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  49. Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

  50. Metadata Services Toolkit • Add Repositories • Schedule Harvests • Orchestrate Services • Browse Records • Make improved metadata available Metadata Services Toolkit • Metadata Tools: Record Cleanup FRBRization Authority Control Aggregation

More Related