<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi David,</p>
<p>I wonder if pulling this information from the MARC record could
slow us down in some places where usually the information is only
pulled from biblio/biblioitems. <br>
</p>
<p>I like the idea of making the display configurable, but maybe not
only using CSS, but having a multi-select system preference to
choose where to display.</p>
<p>Also in testing we should probably consider both LTR and RTL
scripts.</p>
<p>Hope this helps,</p>
<p>Katrin<br>
</p>
<div class="moz-cite-prefix">On 22.12.22 05:18, David Cook wrote:<br>
</div>
<blockquote type="cite"
cite="mid:01fb01d915bc$812f3590$838da0b0$@prosentient.com.au">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}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;}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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The MARC21 880 field allows you to provide
alternative graphical representations for pretty much any
other MARC field. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Typically, in Koha (and perhaps other
library systems), we display these alternative graphical
representations on the “detail page”. You can see the roman
script, the Arabic script, the Chinese script, etc. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In Koha, we also show some data in the
search results, and that’s more problematic… because the
search results should take up a limited amount of space on the
screen, but hypothetically you can include many different
scripts via the 880. I used to work in a government library in
Canada where many of our bibliographic records contained quite
a few different 880s. So it does happen.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have a library that has catalogued
records using the roman alphabet (ie using Pinyin) and
provided Chinese versions via the 880. They’d like to show
both the romanized and Chinese versions throughout Koha (e.g.
in the cart, checkout screens, course reserves, etc.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve coded some of those customizations,
since they only have 880s in Chinese, but I’m increasingly
reluctant to make these changes. I don’t want to carry these
customizations locally, but I don’t know that the Koha
community would accept these changes. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What do you all think about this? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Should we include every 880 title and
author in every screen? Should we maybe include them but hide
them by default using CSS and then allow certain libraries to
just show particular languages used by their patrons or by
checking the current language?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know I can go faster on my own, but I
rather go farther with all of you, so please let me know your
thoughts : )<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David Cook<o:p></o:p></p>
<p class="MsoNormal">Senior Software Engineer<o:p></o:p></p>
<p class="MsoNormal">Prosentient Systems<o:p></o:p></p>
<p class="MsoNormal">Suite 7.03<o:p></o:p></p>
<p class="MsoNormal">6a Glen St<o:p></o:p></p>
<p class="MsoNormal">Milsons Point NSW 2061<o:p></o:p></p>
<p class="MsoNormal">Australia<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Office: 02 9212 0899<o:p></o:p></p>
<p class="MsoNormal">Online: 02 8005 0595<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="https://www.koha-community.org/">https://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="https://git.koha-community.org/">https://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="https://bugs.koha-community.org/">https://bugs.koha-community.org/</a>
</pre>
</blockquote>
</body>
</html>