<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> Are you talking about the results screen or the details display? Do you have the XSLT displays on (More -> Administration -> Global System Preferences -> XSLTDetailsDisplay and XSLTResultsDisplay -> On) ?<div><div><br></div><div>If you don't care about "correctness in cataloging" you could put your local call numbers in the 050 field (the LC Call number field) which *will* show in the OPAC results display. (incidentally, I think it's actually kind of ludicrous to display the LC call for our consortium, as all call numbers are local to their individual branch, but I digress...)</div><div><br></div><div>See this example with XSLTResultsDisplay On: <a href="http://screencast.com/t/ZmE3MzBiZj">http://screencast.com/t/ZmE3MzBiZj</a> Notice the LC call number field is shown, in addition each item is shown with it's local call number after the owning location. Of course, your catalog would be different since you probably don't have multiple branches (I admit I'm ignorant of the structure of your organization, apologies if I'm making an incorrect assumption).</div><div><br></div><div>This example, with XSLTDetailDisplay <a href="http://screencast.com/t/OTllZmFk">http://screencast.com/t/OTllZmFk</a> shows that the 050 doesn't seem to show anywhere on the main detail display, an interesting omission, considering it's inclusion in the results display. Of note here is that every item shows it's local call number in the items table, indicating that you would need 952 + subfields to denote items to show the local call number on the detail view. I'm not sure why a lack of barcodes would change the item display here, I'll have to do some playing around to test it. Absolutely the XSLTDetailDisplay preference would change this display, though perhaps not in a way that helps you. </div><div><br></div><div>I hope this helps answer your question, or leads you to an acceptable solution. :)</div><div><br></div><div>(I'm sure that someone will suggest editing your XSLT stylesheets to show the 852, a valid option, but that is currently out of the bounds of my expertise)</div><div><br></div><div>Liz Rea</div><div>NEKLS</div><div><br></div><div><div><div>On Dec 18, 2009, at 9:52 AM, Cynthia M. Van Ness wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi, all,<br><br>We're trying to get Koha Express running (version 3.00.02.012) and we found that the OPAC will not display call numbers in the 852 tag, so we found a utility to transfer call numbers to the 952 tag. Bib records still won't show call numbers, so we are trying to add individual items. Only Koha isn't taking them. Our collection is not barcoded; is that the problem?<br>
<br>Any advice out there?<br><br>========================<br><br>Neh-ko, gah-gis-dah-yen-duk.<br>[Other council fires were here before ours.]<br><br>Cynthia M. Van Ness, MLS<br>Director of Library & Archives<br>Buffalo & Erie County Historical Society<br>
25 Nottingham Court<br>Buffalo, NY 14216-3199<br>Voice: 716-873-9644 x 305<br>Fax: 716-873-8754<br>Email: <a href="mailto:bechslibr@bechs.org">bechslibr@bechs.org</a><br>Web: <a href="http://www.buffalohistory.org/library/index.htm">www.buffalohistory.org/library/index.htm</a><br>
* Search our catalog at: <a href="http://www.wnylibraries.org/">www.wnylibraries.org</a><br><br>
_______________________________________________<br>Koha mailing list<br><a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>http://lists.katipo.co.nz/mailman/listinfo/koha<br></blockquote></div><br></div></div></body></html>