Library Watch 因應Marshall Breeding 即將在 2014年2月21 日出席2014 圖書館科技與創新服務研討會之特邀演講 (Keynote speech)，繼續針對圖書館自動化產業、圖書館傳統自動化系統與雲端服務系統、雲端系統之共享合作與技術議題進行深入的專訪。
Library Watch: 根據您持續對此產業的觀察，這幾年的產業趨勢有目標方向嗎? 如果有，那是什麼呢?
Library Watch: 您可以提供圖書館員選擇特定圖書館技術的建議嗎?? 相同的，有任何有關於選擇代理代的建議嗎??
Library Watch: 從圖書館員與讀者的角度來看傳統的圖書館自動化管理系統與雲端服務管系統時，最大的差別在哪裡?
為了符合現今圖書館的需求，新型態的資訊科技技術應運而生，這些新的系統我稱之為[圖書館服務平台]，[圖書館服務平台]與傳統的圖書館自動化系統奠基於不同的原則。[圖書館服務平台]設計的目的在於幫助圖書館管理所面對各項不同資源之相對應的詮釋資料。以傳統的圖書館自動化系統為例，編目標準完全根據機讀格式進行設計，而新一代的圖書館服務平台則針對了多樣資料形式相對應的詮釋資料 (包括都柏林核心、VRA、檔案編碼描述格式EAD、ONIX 、ONIX-PL 、鏈結資料和 BIBFRAME 新興書目模式)。新圖書館服務平台可讓館員可能夠全面性的流程進行異質性高資源的採購、描述編目，並能夠依資源的特性與特殊形式提供多樣化的檢索。
理想的圖書館服務平台系統截至目前為止雖尚未完全實現，但目前至少已有產品正持續發展並實現此服務平台的願景，包括 OCLC 的 WorldShare Management Service, Ex Libris 的 Alma 與Innovative 的 Sierra。開放型原始碼 Kuali OLE 與 ProQuest Intota 雖仍持續發展中，但仍是朝此目標邁進。
Library Watch: 由於[協力共享合作] 已被確認為 web-scale 管理系統之核心價值，誰將是此核心價值中的最大受益者? 他們又如何參與?
Library Watch: 針對大陸、臺灣、日本與韓國的資源未能夠完全蒐錄於雲端探索內容服務平台，您有哪些建議或解決方案?
雲端探索服務是奠基於中央知識庫內容蒐集的訂閱服務，中央知識庫會包含圖書館本身的實體紙本館藏資源，圖書館所訂閱的電子資源 (包括全文與索摘資料庫等 )，開放近用資源以及數位典藏與機構典藏資源。
在亞洲地區有許多雲端服務內容提供的國際型廠商，包括 ProQuest, EBSCO, Ex Libris , OCLC 。我希望在共享合作的機會下可以看到更全面性的雲端探索資源的蒐錄並從中學習。
Q1. With your continuing observation of this industry, do you see various trends throughout the years heading toward a coherent direction? If there is one, what is it? If not, why?
I see many different threads and tangents, but in a the broad perspective I see some areas of convergence the library automation industry. Library technologies, to be effective, must align with the work that libraries do in the real world. New formats and publication models continually add to the complexity of library collections. Library technologies must be evolving to handle the increased complexity of library collections and to support the collaborative partnerships in which libraries engage with each other. I have seen a relatively steady advancement in technologies to attempt to adapt to these changing library realities. They often lag behind, but at least I there has been continual progress toward the ambitious goal of providing a technology environment able to support libraries in all of their areas of operational and strategic activity.
Q2. Any suggestions you want to provide to the librarians when they are choosing a certain library technology? Similarly, any special suggestions about choosing a vendor?
Libraries should acquire the technologies that help them do their work in the most responsive manner relative to the needs of serving their patrons. The specific technologies that support this strategic approach will come and go over time. It’s important not to get caught up in the hype that surrounds each new wave of technology or product launch, but to be pragmatic regarding its potential to help the library. Libraries make different choices in the level of risks they can tolerate in the consideration of new technologies. Some may be willing to take on the role of earlier adopters and others may need to follow the path of adopting more proven products and services.
I think that the selection of vendors is as much about partnership as about other business and product considerations. Libraries tend to use their automation systems for very long periods—often more than a decade. The features of a product at the time it is originally acquired represent only a snapshot within its overall development trajectory. It’s important to work with organizations that will be around for the long term, that are committed to developing their products in ways that will evolve in step with the transformation of the library itself. Libraries should press companies not just on the features and capabilities of the current versions of their products, but to articulate their vision of how they plan to develop technology to support libraries and to provide at least an outline their long-term development roadmap. Many companies may have developed products for libraries in a previous iteration but lack the resources to re-develop those products in substantive ways that address the fundamental shifts that libraries have experienced in the nature of their collections and the services that they are expected to provide. Libraries using these products that lack momentum of adequate forward development will be stymied in their ability to operate and provide services effectively. I think that libraries benefit from less complacency and more aggressive movement away from legacy systems tied to concepts of the past and toward those that will better support them relative to current challenges.
Q3. From the perspectives of both patrons and librarians, what would be the major differences between the traditional library management systems and the web-scale library management systems?
The traditional library systems were conceived during an earlier period when libraries were primarily involved with print collections. They offer modules such as circulation, cataloging, serials control, and online catalogs designed to help libraries manage their print collections. They were also developed at a time when technology platforms were generally capable of supporting one library or groups of libraries of limited number. The functionality of these systems focus mostly inwardly, helping the library with managing its own collection and providing access to its own user population. Interlibrary loan or other aspects of resource sharing was handled though other applications.
Libraries today face quite different realities. Their collections include ever higher proportions of content licensed through subscriptions to electronic resources and of digitized materials, such as manuscripts, photographs, audio files and video. Print materials continue to play a part, but one that may diminish over time. Libraries also have greater interest than ever before in collaborative resource sharing arrangements.
To meet the needs of this current vision of libraries, new types of technology infrastructure have been developed. These new systems, which I call “library services platforms” are based on fundamentally different principles than the integrated library systems that came before. Library services platforms are designed to help libraries manage collections comprised of multiple formats of materials with the ability to handle the corresponding metadata standards. Integrated library systems, for example, were entirely centered on the MARC metadata formats. Management of a multi-faceted collection brings the need to support many others, such as Dublin Core, VRA, EAD, ONIX, ONIX-PL, as well as emerging models such as linked data and BIBFRAME. These new systems follow a more comprehensive approach to resource management, automating workflows related to the acquisition, description, and access of materials in ways not closely bound to specific formats of materials.
These new systems tend to be deployed using cloud technologies, such as multi-tenant software-as-a-service that not only result in more efficient models of software development and support, but that are inherently capable of improved collaboration and resource sharing. Rather than focused on the individual solos of automation inherent in integrated library systems installed on local servers, with databases that isolated the collections of each library, library services platforms have the ability to automate large numbers of libraries within the same codebase installation, with the potential to both segregate data as needed for each library organization, but also able to provide shared databases, knowledgebases and indexes that can be collaboratively populated and shared among participating libraries.
This idealized view of library services platforms has yet to be entirely fulfilled, but at least a handful of products have been developed to achieve that vision. Some of the products that incorporate at least some of the major design elements of library services platforms include OCLC’s WorldShare Management Services, Alma from Ex Libris, and Sierra from Innovative Interfaces. The open source Kuali OLE project and ProQuest Intota remain under development, but also fall within this new genre of library systems.
Q4. Since "Collaboration" has been identified as the core value of a web-scale library management system, who are those stakeholders that would be involved in the collaboration? How are they going to be involved with the collaboration?
I see the main stakeholders in collaboration as libraries, librarians and the communities they serve. Naturally the providers of those systems have their own interests, seen in the benefits they receive from successfully providing their products and services to libraries.
The vehicle for collaboration increasingly takes the form of shared technology infrastructure. Rather than each library implementing its own isolated automation system, there is a growing trend for shared automation systems to be provided that serve all the libraries in region or country. In this model of shared infrastructure, each library is able to automate its own operations without the overhead of maintaining its own local integrated library system, while gaining the benefit of providing access for its users to a universe of content vastly beyond what it could acquire on its own. Shared infrastructure comes with the ability to transfer resources among participating libraries as requested by users in much more efficient and less expensive mechanisms than traditional interlibrary-loan.
This model of shared automation has great potential to help libraries as stakeholders to fulfill their services more efficiently and more powerfully than the model of isolated automation systems. Library patrons gain access to more resources as multiple libraries pool their collections of print, electronic, and digital content. Librarians benefit through spending less time maintaining local software and services, focusing their talents on higher-value activities that take better advantage of their core expertise in information-oriented service delivery and are able to provide more immediate benefit to their patrons.
Q5. In a web-scale discovery platform, what are your opinions or solutions about those resources that are not covered in the Central Index pool such as those from China, Taiwan, Japan and Korea?
Web-scale discovery services operate on the basis of a central index populated with content represented by the libraries that use that service. These central indexes ideally would include the records from the library’s local physical collection, the electronic resources to which they subscribe (including full-text, metadata, and A&I terms), open access materials, and metadata from digital collections.
At the current stage of development these Web-scale index-based discovery services have advanced to have effective search and retrieval interfaces, with ever improving relevancy, and that are populated with content from the international publishing arena. English language materials tend to be quite well covered.
The current challenge lies in handling the materials from the many international regions in which these services are deployed, which would include materials from local publishers and in local languages.
Fulfilling the vision of a discovery service to address both international and local materials is where I see the current area of interest and activity. But the challenges are enormous. Not only do the developers of these discovery services have to become involved with content providers in many international regions, but they must also solve serious technical problems inherent in multi-lingual search and retrieval. Given the rising influence of China, Taiwan, Japan, and Korea politically and correspondingly in scholarship, I think that the current discovery services are highly motivated to expand coverage of these materials.
It remains to be seen whether the needs of countries in the Asian region will be well served by the discovery services provided by the current international organizations, such as ProQuest, EBSCO, Ex Libris, and OCLC, or if specialized services will emerge. I hope to learn more about any discovery services underway in Asia that comprehensively cover these Asian materials, and if there are opportunities for collaboration.