Matthew Hale from the Kings Fund provided an interesting talk about how they implemented Hyku - an open source online archive solution and how it integrates with Koha

1. Implementing an open source online archive solution (Hyku) - interaction and comparisons with Koha
Matthew Hale

2. Digitised publications and first solution
• The King's Fund publications from 1898.
• 2013 - 1,771 documents digitised (in 2 batches) @ 30,000 images.
• Digital Archive and Repository Team at ULCC (CoSector) to
• implement ePrints with Wellcome Player embedded.
• TIFFs for Wellcome Player; JPEG2000 for archive copy; OCR’d for
• search; metadata from Koha.

3. Need for new solution
• Search poor; little ePrints functionality used; not good fit.
• Hybrid solution, poor admin interface - reliant on custom scripts.
• Upgrades and development issues; use of Wellcome Player.
• New pricing model January 2017.

4. The solution
• Samvera (known as Hydra 2008-2017) platform.
• Fedora Commons repository software; Solr indexing and searching;
• Blacklight facets; Ruby plugins ("gems") (i.e. IIIF search.)
• "Heads" for applications, user interfaces - technical, dependencies.
• Need for packaged, simpler solution - Hyku, easy implementation.
• Universal Viewer embedded; improved searching; modern admin

5. A familiar situation
• Similarities to Koha 9 years ago:
• open source;
• opportunity, but no other comparable examples;
• trusted supplier;
• remote hosting, SaaS;
• mutual learning process, ongoing development;
• trailblazing (with community responsibility);

6. Implementing Hyku
• New version of Archive successfully launched June 2018.
• First live Hyku instance in world – https://archive.kingsfund.org.uk
• Integrating with Koha:
• biblionumber;
• Koha metadata (Tools - Export);
• styling;

7. Linking from Koha results
• Example search
• MARC21slim2OPACDetail.xsl:
• <xsl:variable name="bibnumber">
• <xsl:value-of select="marc:datafield[@tag=999]/marc:subfield[@code='c']" />
• </xsl:variable>
• <a href="http://archive.kingsfund.org.uk/biblionumber/{$bibnumber}/">
• <img id="imageArchiveLink" src=
• "https://archive.kingsfund.org.uk/biblionumber_thumbnail/{$bibnumber}"
• height="120" width="90" onerror="this.style.display='none'" title="Digital copy" />
• </a>
• Jquery for any that are problematic.

8. Comparison of communities
• Unique requirements, local development and solutions.
• Decentralised, shared ethos rather than single product. Toolkit.
• Flexibility rather than cost: Brown, Columbia, Cornell,
• Harvard, Princeton, Stanford, Yale. In UK: Oxford, Durham, LSE, York.
• Anglo-US rather than global: HEA ; Samvera partners, developers and users.
• Reliance on local development teams.
• Branding issues, support monetisation, organisation, funding central
• developer.

9. Future work
• Collections for online exhibitions (Spotlight).
• Born-digital: as PDFs, native support in Universal Viewer; tesseract-
• ocr for OCR?; PDF/A archiving format with OCRmyPDF?
• Other formats – video, image, sound, web.
• Commitment to open source project - CoSector feeding code back
• to community. What will others develop? (Warburg, British Library.)
•

10. © The King's Fund 2018
www.kingsfund.org.uk
m.hale@kingsfund.org.uk
● https://samvera.org