170 likes | 178 Views
Explore the collaborative model of SFX service provision in a library consortium setting, emphasizing shared resources and centralized support for efficient management. Learn about the implementation timeline, administrative roles, policy guidelines, and technological advancements in SFX operations. Discover the EZB system integration, data reloading processes, and enhancement of service workflows through centralized development. Gain insights into DataLoaderTable functionalities and the consolidation of resources for effective use of SFX in consortia.
E N D
Consortial SFXCommon Gain ...and Common Pain Dr. Mathias Kratzer Bavarian State Library, Munich (Germany) - Bavarian Library Network (BVB) Head Office - IGeLU 2009 - Helsinki
Where is ... Helsinki IGeLU 2009 - Helsinki
... Bavaria? IGeLU 2009 - Helsinki
sfx.bib-bvb.de 17 universities of appl. sciences 10 universities 1 Bavarian State Library 1 shared / “guest” instance __________________________ 29 productive instances running on one server IGeLU 2009 - Helsinki
4 8 15 16 23 42 • 2003-03-28: installation of SFX2 by ExL • 2003-11-05: start of production with SFX2 • 2005-07-01: start of migration to SFX3 • 2005-12-12: switch of live system to SFX3 • 2008-11-14: move into Solaris 10 zone on Sun Fire V1280, 8+4 UltraSPARC III CPUs, 48 GB RAM, 380 GB Disk Space • 2008: first instance broke the 2 Mrpy limit IGeLU 2009 - Helsinki
3 2 4 1 Consortia Model 2 shared instance SFX menu service A1 service A2 service S1 service S2 service A3 SFX menu service B1 service B2 service S1 service S2 Consortia API Consortia API instance of Library A instance of Library B OpenURL IGeLU 2009 - Helsinki
Central Admins • 2 people at ~ 60% of their time • take care of KB and software (general monitoring, applying monthly revisions) • develop and provide consortia services (update activations for most e-journals & consortially acquired e-books, create and configure targets on shared instance etc.) • co-ordinate contact to popular sources • train local administrators IGeLU 2009 - Helsinki
Local Admins • 0 - 4 contact persons from each library • conceptual design of the SFX menu (what services, colloquial display logic, …) • graphical design of specific menu layout • end user training & 1st level support • (de-)activation of aggregator sub-targets • (de-)activation of locallyacquired e-books • contact to sources of only local interest IGeLU 2009 - Helsinki
From Our Policy • UNIX access is restricted to Central Admins. • Certain sections of the SFX Admin Center (e.g., Administrator Tools and Submission of SIs) are restricted to Central Admins. • Statistics data are moved from online to offline tables every night before a workday. • Statistics data are moved from offline tables to archive files every March. • E-journal activations are updated quarterly. IGeLU 2009 - Helsinki
EZB • hosted by University Library of Regensburg • back end: central database for cooperative cataloguing of e-journals and subscriptions • also open for freely available e-journals • very strong support for consortia • front end: end-user interface for searching and browsing in a library-specific view • conceptually quite similar to SFX’ A-Z List • famous for its traffic light icons: IGeLU 2009 - Helsinki
SFX Reloaded 1 exports data (quarterly) EZB corrects erroneous data Targetauswahl 28 lokale Instanzen Laden der Daten verify/edit(?) the Local Admins “DataLoaderTable” Datensplitting Verbund- zentrale Fehlerevaluation map to targets Central Admins update & evaluate automatic workflow in development! via CRM??? additions & changes to the SFX KnowledgeBase Ex Libris IGeLU 2009 - Helsinki
SFX Reloaded 2 • workflow and programs developed by BVB Head Office (uses Perl, sh, and MS-EXCEL) • avoids double maintenance of e-journal subscriptions in EZB and SFX • core components: • Perl hash mapping host and domain names to targets or to interfaces (only if inevitable) • DataLoaderTable, an EXCEL sheet readable by humans and parseable by a Perl script IGeLU 2009 - Helsinki
DataLoaderTable 1 • input files are pairwise disjoint parts of the EZB export file: titles mapped to the same target • each table row is converted to a sh-script line: „run batch version of DataLoader on input file for the following target service(s)...“ IGeLU 2009 - Helsinki
DataLoaderTable 2 • input files are maximal disjoint parts of the EZB export file: titles covered by the same set of interface subtargets • decision for one set is stored for next quarter! • What if monthly revision brings IFC_X_F, …??? IGeLU 2009 - Helsinki
Some further • central development of • shared Source Parsers (e.g. BVB’s library information portal Gateway Bayern) • shared Target Parsers (e.g. ILL, eBooks on Demand, Manuscripta Mediaevalia, …) • even libraries with few human resources can offer SFX to their users and rely on • centrally managed default configurations • central expertise in 1st level support IGeLU 2009 - Helsinki
One further big Admin Center Only Configurations • Display logic rules: no more symbolically linked default set since migration to SFX3 • Translation of certain standard phrases like “Full Text For Related Object” since introduction of simplified menu templates • Want to fix an incorrect Parse Param? – Takes 5 mouse clicks for a single instance but in a consortium like ours: 145(!) IGeLU 2009 - Helsinki
Thank you ... ... for your attention and/or patience! Feel free to contact us: sfx@bib-bvb.de IGeLU 2009 - Helsinki