DIE ÖSTERREICHISCHE BIBLIOTHEKENVERBUND UND SERVICE GMBH
EDOC UND ALMA
STATUS QUO UND ÄNDERUNGEN MIT ALMA
VICTOR BABITCHEV
AGENDA
eDOC current status
From Aleph to Alma changes in eDOC architecture
Changes and the consequences for librarians
New Web-tool for librarians
Next steps
Conclusion
eDOC current status – 1
Since autumn 2004 eDOC has been used as the central OBV catalogue enrichment tool (CE) for free accessible objects
The eDOC strong side is its efficient and librarian-friendly workflow
With Primo introduction in 2009 eDOC began losing its search engine role (SWISH-e) in favor of more powerful Primo
eDOC became important part of OBVSG workflow integrating objects from various systems and sources and preparing full texts for Primo
indexing
eDOC current status – eDOC Institutions and “the sharing effect” (18) – 2
Institution eDOC objects transfer Objects: own.-prod. / from others
Akademie der bildenden Künste, Wien eDOC-Light 158/50,308
Arbeiterkammer Wien - // - 2,932/1,6286
Fachhochschule Wirtschaft, Wien - // - 2,810/1,6286
Fachhochschule der Wirtschaft Campus02 Graz - // - 128/1,3159
Medizinische Universität Wien eDoc Batch client 8,479/35,392
Oberösterreichische Landesbibliothek eDoc Batch client 5,015/88,642
Parlament eDOC-Light 9,061/16,195
Technische Universität Wien eDoc Batch client 50,114/83,826
Universität Graz eDoc Batch client 48,638/200,145
Universität Innsbruck eDoc Batch client 27,682/224,772
Universität Linz eDOC-Light 4,045/126,578
Universität Salzburg eDoc Batch client 28,247/241,742
Universität für Bodenkultur Wien eDoc Batch client 10,750/45,257
Universität für Musik und darstellende Kunst Wien eDOC-Light 1,346/10,888
Verbund für Bildung und Kultur eDoc Batch client 20,853/47,720
Veterinärmedizinische Universität Wien eDoc Batch client 10,678/7,882
Wienbibliothek im Rathaus eDOC-Light 159,579/37,062
Wirtschaftsuniversität Wien eDoc Batch client 11,768/125,600
Note. TOC PDF-objects in eDOC from DNB: 182,000, May 2017
eDOC current status – 3
The eDOC objects repository is constantly growing and it will reach soon one million objects (2004-11: 5,000, 2017-05: 975,000 objects)
eDOC current status – 4
eDOC contains considerable number of electronic objects containing full texts and they are searchable in Primo
Full texts
From Aleph to Alma - changes in eDOC architecture – 1
With introduction of Alma cloud architecture the fully automated eDOC local workflow should be changed considerably
During the Alma concept design phase OBVSG prepared requirements and worked out with Exl approaches enabling local processing to start and monitor Alma jobs
However eDOC ability to ingest thousands objects per evening and update thousands of catalogue records was a challenge for Alma in part of its API calls limits
Nevertheless we were optimistic and set the goal to implement eDOC with very similar performance characteristics in Alma like we have it now!
From Aleph to Alma - changes in eDOC architecture – 2
In our Alma solutions we implemented optimal data access mechanisms returning blocks of Alma records per single access and thus reducing API calls considerably
New special Exl APIs enabled starting Alma jobs from our local applications and monitor their execution – and this provided a
fundament for building of Alma integration into our local processes!
virtually Alma could be used as it were running locally…
The above factors provided necessary prerequisites for adjusting and re- factoring of eDOC for Alma
The redesign works brought considerable changes in eDOC but still left its core – the data model and main functions remained unchanged (as we planned)!
From Aleph to Alma - changes in eDOC architecture – 3
eDOC & Alma Flows
Get objects
Get BIB records from Alma (convert XML to ASEQ)
Process objects & update BIBs with URLs (ASEQ)
Start Alma import job to update BIBs and monitor it … Objects
BIB Aseq file eDOC
Repository
Alma
OBV eDOC
Visual Library DNB
Springer etc.
. . . .
Changes and consequences for librarians – 1
With reaching large volumes of text objects in eDOC - SWISH-e search engine began showing its limits and needs to be stopped (after 12.5 years of operation vs the expected 5!)
Its dismounting would also release our considerable machine and maintenance resources
Planned for Q 1. 2018
The most radical change in new eDOC is the entire absence of
bibliographic data, only ACNr left in Bib.-record to keep the data model intact
all eDOC objects are linked to their Bib.-record and making it extreme “slim”
was nevertheless sufficient to perform furher its “parent” role …
The above also means that librarians would lose access to control over the qualilty of objects (for those who used SWISH-e) …
Changes and the consequences for librarians – new eDOC Web tool – 2
We developed a new Web tool enabling simple control for librarians over eDOC objects via ACNr and objects IDs as the access points
Selected eDOC internal fields will now be also displayed enabling librarians to more straightforward control over their objects
among them are: types of objects, dates, notes, size etc.;
support to building of aggregate objects could be more friendly now
The text extraction quality check for PDF-objects is shown now using a
“traffic lights” approach
“green” – ok!, “red” - problem (and “grey” – not relevant)
Changes and the consequences for librarians – new eDOC Web Tool – 3
Click line on
online test
Changes and consequences for librarians – 4
TOCs from DNB
PDF-TOCs from DNB is a large part (182,000) of objects searched in Primo, and they save considerable scan resources in libraries
in 2016 over 46% of all TOCs came from DNB
With Alma we plan to change “harvesting” of data from ACC02 and switch to more efficient Alma methods - such as direct OAI-PMH access to DNB (tested already…)
no “memo” records will be used for that new eDOC is prepared already
Next steps
Although eDOC core components already adapted for Alma it is still a lot of adjustments to be done in other workflows and tools!
In our plans stays bringing some advanced eDOC-light features to eDOC
“Batch-Client” institutions (e.g. in treatment of erroneous objects)
After implementation of OAI-PMH access to DNB we may retro-actively add further thousands of TOCs to eDOC
Some Alma implementation tasks will provide further improvements in eDOC integration with other services
eDOC will remain the “central click point” for about 1 million objects without bottlenecks in the data base performance
eDOC either returns objects from its repository or redirects accesses to other systems storing their objects remotely …
Conclusion
With considerable re-work of eDOC for Alma, removal of bibliographic
contents and redesigned Web service, we believe that eDOC will serve equally good at times of the new ILS like it does now!
We are proud that eDOC became a solid part of our services, provides a reliable and librarian-friendly workflow, does a good job for libraries and end-users and last but not least - it shares and saves our resources
And we would like to thank all institutions contributing to its growth and all who are using it!
and this year eDOC will reach one million objects!
_
This is the end - thank you!
VB/2017-05-16
eDOC objects acceses
eDOC objects daily accesses
