1. XCO Spring Meeting The University of North Carolina at Charlotte May 5-6, 2010

2. XC Software and its Value to the Community XCO Spring Meeting Session 1

3. ILS Interoperability DLF ILS Discovery Interfaces Task Group – Version 1.0 recommendations 6/2008 – Version 1.1 recommendations 12/2008 – OAI and NCIP Toolkits started early 2008. – XC addresses all Level 3 requirements except real- time search – Available handout provides more details 3

4. ILS Interoperability ILS Interoperability Group – Code4Lib community initiated effort to select a common infrastructure for interoperating between ILSs and discovery systems – Who is involved – Potential investment of dollars Additional ILSs Improved ease of use of web services for developers – Community of developers to contribute technology roadmap and code enhancements 4

5. ILS Interoperability OAI-PMH Standard – Java Harvester – Java Repository – PHP/Drupal Harvester NCIP Standard – Java NCIP Responder – PHP/Drupal NCIP Initiator – NCIP Implementers Group 5

6. ILS Interoperability ILS Compatibility – Voyager, Aleph, Innovative, NALIS – Connector platform with developer manual – Test bed license negotiations with Exlibris ILS-like System Compatibility (future) – Multiple ILS institutions – Consortial Borrowing software – Interlibrary Loan Systems (Illiad) 6

7. Metadata Opportunities 7 Redesigning from the Inside Out

8. “FRBRizing” MARC, etc. MST = Infrastructure for FRBRization Parses MARC, other metadata into FRBR Group 1 entity records (work, expression, etc.) MST and MST services do this automatically XC User Interface built around this metadata Goal: Merge records that represent the same work, expression, to “collapse” display 8

9. RDA in a non-MARC Environment RDA based on FRBR data model A “container” for RDA data other than MARC? XC Schema: “FRBRized” structure Application Profile – “mix and match” Combines elements from various schemas: Dublin Core (all), some RDA, few XC 9

10. Moving toward Linked Data Semantic Web URIs for all vocabularies, metadata elements Enables library metadata to be used/understood outside of specific “silos” and outside of record structures Linked data is understandable by web applications as well as by humans XC Schema, MST provide a way to get started 10

11. Metadata Opportunities 11 What if we’ve gotten this ALL WRONG?

12. XC Enables Experimentation Harvests a copy of metadata from an ILS or repository Very low risk of data corruption XC propagates changes throughout the system Web interfaces for trouble-shooting “Sandbox” for experimentation 12

13. User Interface Why reinvent the wheel  Drupal CMS Out-of-the-box discovery interface Potential to be the library website platform (seamless) Communities – Open Source: Drupal, SOLR – Library Technologies: RDA, FRBR, Linked Data 13

14. Metadata in Drupal Synchronization: OAI-PMH Storage – Metadata as nodes managed by Drupal and hierarchically related to one another – Modular support for multiple formats (XC, DC) – Hybrid mechanism: mySQL and Apache SOLR Index – Keyed on FRBR manifestations – Web administration to tweak functionality 14

15. XC Drupal Toolkit Walkthrough Building an XC demo site User Interface – Search and faceted browse – Customization of display elements and facets – Browse UI builder – Circulation status and patron information from ILS – Drupal Themes Live Demo over lunch 15

16. Drupal User Interface 16

17. Faceted browsing of search results 17

18. Faceted browsing of search results 18 facets facet values - Relationships among results set items - Each facet maps to one or more fields - Customizable - Values of metadata fields - Click to limit - Quantity of matches appears in ( )

19. Customize Facets: Facet Mappings 19

20. Edit Authors/Contributors Facet 20

21. Edit Format Facets 21

22. Reorder Facets 22

23. Metadata display 23 - Syndetic Solutions integration - Image cache Image metadata Textual metadata - Defaults include title, contributor, publisher, format - Availability uses NCIP and AJAX - Customizable

24. Configure Metadata Display 24

25. Configure Metadata Display 25

26. Metadata display: Title and Body 26

27. Full Record Display 27

28. WorldCat 28

29. Full Record Display… scrolled down 29 Reviews Related Subjects Similar Items

30. Full Record Display… scrolled down 30 Other Fields

31. Browse Pages 31

32. Find DVDs and Videos 32

33. Find DVDs and Videos – Genre Browse 33

34. Find DVDs and Videos – Genre Browse 34

35. Find DVDs and Videos: Results 35

36. Browse Page Builder 36

37. Browse Page Builder 37

38. Browse Page Builder 38

39. User Accounts Drupal Account types – Local: Optionally linked to ILS credentials – Linked: Automatically created based ILS credentials My Account page – Loaned Items: retrieved from ILS – Requested Items: retrieved from ILS – Saved Items: stored in Drupal Merged lists are possible (from multiple ILSs) 39

40. Circulation, Authentication, Accounts 40

41. Loan Items 41

42. Bookbag 42

43. Bookbag 43

44. Drupal Themes Drupal Themes are collections of templates – Each template themes a particular on-screen element or page – XC Drupal Toolkit includes theme templates Provides out-of-the-box UI Customizable Independent of functional code No graphical identity is provided Kyushu University Library created a theme 44

45. Kyushu University Library – Drupal UI 45

46. Kyushu - Search results Reasons why these items are shown Format icons 46

47. Kyushu - Indexing Implemented Solr/lucene-ja CJK analyzer A unique Tokenizer (originally created) These three enable to search by original scripts : CJK and Japanese pronunciation readings in Katakana and Roman characters. 47

48. Kyushu – Translating Module Search results shown 48

49. Kyushu - Search results in Japanese Reasons why these items are shown Query : America Japan Translated : Faceted navigation 49

50. Kyushu – Development Issues Local Priorities -- reading (880 fields, CJK issues) -- faceted navigation (classification/subject) Data investing -- data on institutional repository, article databases, & library websites Details display NCIP development for NALIS 50

51. Building an XC Community XCO Spring Meeting Session 2

52. XC Begins 52 2004 - Jennifer and Dave applied for an NSF grant for a “front end”. 2006-2007 – Mellon Phase 1 Preliminary Grant with User Research component October 2007 – XC Hiring process starts February 2008 – 1 st Development begins February 2010 – XCO launched

53. Leadership – Changing Roles 53 Jennifer Bowen Nancy Foster David Lindahl

54. Click on a state to change color XC – In the US

55. Orange states represent partner institutions, developers, and advisory committee members. XC - In the US

56. XC - Worldwide

57. Current XC Team Developers Péter Király Drupal Toolkit, OAI Toolkit Sharmila Ranganathan Metadata Services Toolkit Ben Anderson Metadata Services Toolkit Owen Henty NCIP Toolkit MT Wesley Drupal NCIP Module, Website 57

58. Former XC Team Members Eric Osisek – NCIP, MST services Shreyansh Vakil – MST GUI, NCIP, OAI Tejaswi Haramurali – MST GUI and services Steven Dibelius – Deployment Christina Sherman – Community Development Vinay Bangera – MST services RIT Senior Year students – prototype of Authority service 58

59. Other UR contributors 59 Lit list research and general advisor - Judi Briden Technical Advisors - Jeff Suszczynski & Nate Sarr Graphic and design - Sean Morris Desktop & Server support - Andrea Noto & Ralph Arbelo HR - Kelley Kitrinos & Latasha Hill Finance departments – Lois, Tahir, Jim, Natalie UR User Research Team – Kostya, Katie, Melissa, Suzanne Voyager Management team – Stephen & Denise

60. Partner Developers Rick Johnson – Notre Dame – NCIP Rob Fox – Notre Dame – OAI Chris Delis – CARLI - OAI Jon Jiras and students – RIT – NCIP Stephen Westman – UNCC – OAI Mark Ludwig – UB - testing 60

61. Other Interest Cornell, NY King Saud University, Saudi Arabia Denver Public Library, CO Yale, CT Universidad Mayor, Chile Rowen University, NJ Cushing Academy, MA 61

62. Partners Chris Lerch, Director of Information Technology, Wallace Center at Rochester Institute of Technology Pascal Calarco, Head, Library Information Systems, University of Notre Dame Susan Singleton, Executive Director, CARLI 62

63. A Development Partner’s Perspective

64. Reasons to join XCO: We own our data! We want unfettered discovery, display and access. We want alternatives to commercial tools. Opportunities for collaboration with great partners. Opportunities for staff and students.

65. We Own Our Data – So Why Can’t We Have It? Our ILS vendors puts tight restrictions how how we discover and display our collections. We have found most vendor’s “2.0” tools to be lacking.

66. We Want to Support Open Source Initiatives Even though we made the investment in Encore, we want to explore other options. Being involved gives us input.

67. Collaboration: We jumped at the chance to participate with the other partners. We hope for opportunities to partner with these schools on other projects, as well as bring other Connect NY schools on board.

68. Opportunities for Staff/Students: First class development project We were fortunate to have staff looking for this kind of opportunity Great opportunity for students

69. Extensible Catalog Activities At University of Notre Dame Pascal Calarco Rick Johnson Eric Lease Morgan

70. Environment Shared Aleph ILS for ND, three other local private faith- based colleges 21k students, faculty, staff amongst all four Strong commercial vendor orientation: “we buy/license solutions, not build them” Some failures from vended solutions; opens door Collections-oriented library culture Tiny local digitization activity; purchase/license digital collections Risk-adverse, but changing Strong and maturing technology capability in-house Positive working relationship with campus computing (OIT)

71. Why XC @ ND? Interested in 'next gen' discovery systems, engage prior to selection & procurement Excitement and possibility of shared, collaborative, community-based development Strong belief/support in open source within technology units Shake up commercial vendors Confidence in array of Rochester & partners Promising toolkits for local experimentation: diversity of metadata format transformation, enhancement Institutional visibility of activities and collaboration Engage library staff with different perspective on library data, services

72. Outcomes: XC @ ND Tangible OAI project against Aleph; compare vs. integrated functionality New staff: familiarity with library standards, data formats, structures; learning tools Aleph NCIP support poor; provided implementation details back to Ex Libris product manager during implementation Experience and confidence with collaborative development projects, leads to other collaboration, leadership capacity NCIP Toolkit and drivers may enhance Primo functionality for intracampus delivery Drupal: convergence with Fedora DR application needs -> Islandora

73. NCIP Toolkit Aleph Driver Design Relies on Aleph built-in Webservices support called Aleph X-Services Created stand-alone Java library to execute Aleph X-Service calls Aleph Interface vs AlephMediator AlephInterface proxies calls to AlephMediator and translates objects returned into NCIP objects

74. NCIPToolkit Aleph Driver Supported Operations Currently unsupported operations Recall Item Check In/Check Out Create Item Call Slip Request (All other requests supported) All other NCIP Toolkit methods supported including Lookup User Get Availability Renew Item Etc.

75. NCIPToolkit Aleph Driver Version Support Tested Versions Currently just Aleph 18 Adding Aleph 20 support soon More Information http://xcnciptoolkit.googlecode.com/files/NCIP_Al eph_ILS_Support_Design_Implementation.pdf

76. Possible uses of XC at ND Apply authority control processes against vendor- supplied MARC records Collect and normalize content for “Catholic Portal”, Primo, or any other indexer NCIP Toolkit could be leveraged for Primo Create OAI-accessible open access journal article index Aggregate locally produced XML content and expose as OAI Syndicate lists of content to courseware or website Expose “linked data” of Libraries’ holdings

77. Challenges To many, XC still looks like a niche, techie open source project. We need to build out meaningful use cases that clearly demonstrate value to library administration and non-technical areas Functional completion of all components. Right now its “mostly done”; inhibits adoption Lobbying for library monies to join XCO in current budget climate with many competing demands Integration with other systems beyond core ILS; can NCIP toolkit bridge ILS, resource discovery, and document delivery systems, for example?

78. Thanks! Any questions? Contacts: Pascal Calarco pcalarco@nd.edu Head, Library Information Systems Rick Johnson rick.johnson@nd.edu Unit Manager, Library Information Systems Eric Lease Morgan emorgan@nd.edu Head, Digital Access & Information Architecture

79. Lunch XCO Spring Meeting

80. Roadmap for the Future XCO Spring Meeting Session 3

81. Roadmap for the Future Leadership Deliverables Roadmap Governance 81

82. Software Development: the Future of XC Provide strong leadership to guide future development – XCO Board of Managers – organizational leadership – XCO Executive Director – leadership from a dedicated resource – XCO Working Groups – leadership from the community of practice Complete originally planned deliverables Build a technology roadmap 82

83. Complete originally planned deliverables XC Metadata Services Toolkit – Service development platform – Improve performance – Aggregation, Authority and DC services XC Drupal Toolkit – Usability Testing and Refinement – Improve performance – Learning management services – Support XC search on web pages 83

84. Build a Technology Roadmap Input from working groups and executive director Publicly available and fluid Includes: – Architectural design principles – Mapping of requirements to proposed features – Implementation specs – Use cases – Prioritization 84

85. Governance guides core development Core development is development within the roadmap and may be shared via official XCO mechanisms Non-core development falls outside the roadmap – Platforms and standards enable quality pathways for developers to follow – Add-on modules can be distributed separately without requiring a fork in the code 85

86. Engaging the Community: Introducing XCO Working Groups XCO Spring Meeting Session 4

87. Community Source Software Development Initial software development: – Guided by architecture design principles – Carried out by identified partners After software released (as Open Source): – XCO community develops roadmap for future code development and identifies resources – XCO maintains design principles 87

88. Why XCO Working Groups? Develop and maintain roadmap for completing the software, enhancements Provide administrative structure for the XCO Community Take advantage of Community expertise Ensure success of the software 88

89. Proposed XCO Working Groups ILS Connectivity Group – OAI and NCIP Toolkits Commercial Content Group Metadata Group – MST and MST Services Drupal Group Implementation Support Group Others also possible! 89

90. Working Group Charges Develop and maintain roadmap for area of activity Recruit appropriate WG members Identify and solicit resources: – Funding – Development – Expertise 90

91. Working Group Tasks for Today Break up into assigned groups Identify a facilitator and a note taker Discuss questions on handout (front and back!) Fill in 1 copy of handout to turn in Report back to the large group 91

92. Working Groups: Keep in mind… We want your expertise, advice to “kick off” these groups You aren’t committing yourself to join the group you are working on today You are welcome to join one or more groups Please suggest others who you think should be on “your” group (or on other groups) 92

93. Beginning the XC Roadmap Outcomes of today’s WG sessions will become the framework for sections of the roadmap XC Executive Directors will collect and post to the XC Wiki After that, anyone can contribute 93

94. Launching the XCO Working Groups XCO Spring Meeting Session 5

95. Working Group Reporting What is your group? What should this group do as its next three steps? Other comments, observations from group discussions Reporting time limit: 5 minutes per group 95

96. Sustaining XC Software and the XCO Community XCO Spring Meeting Session 6

97. Sustaining the XC Software and XCO Community Survey comments How we go forward 97

98. Sustaining – What you want addressed 1 “Boost participation, brainstorm marketing possibilities” “Sustainability and integration” Institutions may be confused how XC fits into a landscape that now includes Summon and Kuali OLE. What problems does it solve? How to minimize the effort to implement XC at a library Expanding the functionality 98

99. Sustaining – What you want addressed 2 Will the library community support XC going forward? Will there be continuous updates in the future? What are plans for code enhancement? What is needed? What is planned? Ensure a large community of users Ensure library staff have necessary skills/training for XC Plans for long term maintenance of software Successful implementations of XC at institutions to demonstrate why it should be on the radar Funding 99

100. Sustaining – What you want addressed 3 Governance Future planning Lack of availability of commercial support or governance is a common stumbling block for open source software Need for money and programming resources Relationship of XC to standards activities Relationship of XC to Kuali OLE 100

101. Sustaining – What you want addressed 4 Potential to make VUFind an XC front-end in place of Drupal Express current vision (1-2 years) and future vision (3-5 years) How will training be made available? 101

102. Sustaining – Mining your comments 1 Increase use of XC software – Training options needed – Functionality that maps to institutional requirements – VUFind integration – Commercial support options – Early adopters serve a critical marketing need Expressed vision for XC 102

103. Sustaining – Mining your comments 2 Broaden involvement in XC – Ideas, code, institutions using, institutions funding Marketing – Value proposition, differentiators, connections to other efforts Sustainability – Money and programmers for development and maintenance Governance 103

104. How we go forward Governance through technology roadmap development in coordination with XCO board, XCO executive director, and working groups Sustainability through XCO sponsorships, working partnerships, and broadening of institutional deployment. Marketing through XCO website, conference presentations, and broadening deployment. 104

105. Fundraising for Library Initiatives XCO Spring Meeting Session 7

106. Fundraising for XC XCO Spring Meeting Session 8

107. Fundraising for XC Sponsorship Categories Patron - Libraries and other Not-for-Profits Annual library-related operating budget $20 million and higher ($10,000/year) Annual library-related operating budget under $20 million ($5,000/year) Supporter - Libraries and other Not-for-Profits Annual library-related operating budget $20 million and higher ($5,000/year) Annual library-related operating budget under $20 million ($2,500/year) Corporate Sponsor Annual sales revenue $2 million and higher ($15,000/year) Annual sales revenue under $2 million ($7,500/year) 107

108. Fundraising for XC Small Group Discussion – Identify a facilitator and a note taker – Discuss the questions – Prepare one form to hand in – Be ready for a one-minute presentation 108

109. Fundraising for XC Discussion questions 1. What makes XC hard to “sell”? 2. What makes XC easy to “sell”? 3. What will it take to make XC successful? 109

110. Meeting Outcomes and Next Steps XCO Spring Meeting

111. Wrap Up XCO Spring Meeting

112. Download XC software at eXtensibleCatalog.org