<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi all:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I was just wondering… what’s the biggest library collection you’ve heard of? What’s the biggest Koha collection you’ve heard of?<br><br><o:p></o:p></p><p class=MsoNormal>Most recently, I recall there being a mention of 13-14 million bibliographic records in a Turkish public library consortium: <a href="http://koha.1045719.n5.nabble.com/KOHA-with-PostgreSQL-td5856359.html">http://koha.1045719.n5.nabble.com/KOHA-with-PostgreSQL-td5856359.html</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I did some Googling and arrived at this list: <a href="https://en.wikipedia.org/wiki/List_of_largest_libraries">https://en.wikipedia.org/wiki/List_of_largest_libraries</a>. The two biggest are the British Library with 170+ million items and the Library of Congress with 160+ millions. Library and Archives Canada come in third with 54 million, and the New York Public Library comes in fourth with 53 million.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It drops off pretty fast after that… 2 in the 40s, 4 in the 30s, 6 in the 20s, and 3 in the teens. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think the largest Koha I’ve managed had a little over 1 million items and 1 million biblios.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m guessing that many cases of “large” libraries must be in the 1-10 million range, which doesn’t actually seem that bad. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I sometimes wonder about the merit of a table that stored something like (“id”,”type”,”metadata”). The primary key has an index by default I believe and then maybe add one to “type” if we find necessary although it might only ever need to be accessed after the row is already retrieved… <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Just thinking about adding different metadata formats to Koha. In theory, Zebra can handle any XML metadata format we throw at it. I think you can index different record types into Zebra. We’d need to change how the indexing runs and add some XSLTs for indexing/retrieving those metadata formats, but I think it’s doable.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There’s a few ways of handling the results afterward… you could add templates to the existing XSLTs so you could feed the metadata to the same XSLT regardless of format. Or we could adopt an intermediary data format (when retrieving data from Zebra, we can define our own XSLTs per record type I believe) and do our displays based on that intermediary format.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The remaining troubles would then be with other places in Koha that use the MARCXML directly… such as cataloguing, which relies on mappings between the relational database and MARC and items which are composed/decomposed to/from MARCXML. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But I think that’s all achievable.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Of course, I don’t have a project at the moment that would involve adding metadata formats. Thinking more about RDF, but I think that’s a bit of a barrel of monkeys. While I think RDF has merit when it comes to browsing records, I still don’t see how you could effectively retrieve an RDF record from a local triplestore if you’re relying on data stored on a remote server. Your RDF record might have the title you want to find, but what if you want to find a record by author? There’s no local data referring to the author. You just have a triple in the record that contains an IRI pointing to the author record on another server. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I don’t have a lot of experience with RDF or triplestore or linked data in general… but I assume that there must be some sort of local caching of data in search indexes? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>David Cook<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>Systems Librarian<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>Prosentient Systems<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>72/330 Wattle St, Ultimo, NSW 2007<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>