On 2/25/08, Chris Cormack <[EMAIL PROTECTED]> wrote: > Yeah, we cant use these variables in the templates, as what is in them is > controlled by sysprefs, ie itemcallnumber is going to be empty unless people > are using item level callnumbers item-level callnumbers are really the only valid type of callnumber, since callnumber refers to shelf location and bibs don't have shelf location. There's a separate concept of 'classification' that can appear at the bib level, but it's really not used very much in practice in libraries, other than as a reference point. Shelf browse lists, etc., are generated from the item-level itemcallnumber, which should always be populated for every item.
> Its a tricky one as Nicole says, some libraries use dewey and LC .. so we > need to display both. The fields dewey and classification don't exist anymore, we now have: itemcallnumber (combined full call number at the item level) and we have cn_source and cn_sort (for sorting rules based on the cn_source value as defined in Administration->Classification Filing Rules) At the bib level we have biblioitems: cn_source cn_class cn_item cn_suffix cn_sort dewey and classification no longer exist and should be replaced at the bib level with a concatenation of cn_item . cn_item . cn_suffix and at the item level with itemcallnumber. Please see the following reference: http://wiki.koha.org/doku.php?id=en:development:callnumbers Hope that helps. -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS [EMAIL PROTECTED] |Full Demos at http://liblime.com/koha |1(888)KohaILS > Chris > > > On 2/26/08, Owen Leonard <[EMAIL PROTECTED]> wrote: > > As far as I can tell, call number handling is generally broken in 3.0, > with > > no realy standard for how to display call numbers. Some templates use > > <!--TMPL_VAR NAME="itemcallnumber" -->, some use <!--TMPL_VAR > > NAME="classification" -->, some use <!-- TMPL_VAR name="dewey" -->. > > > > Which is correct, or is there a better way to handle call numbers in a > more > > generalized way? > > > > -- Owen > > > > -- > > Web Developer > > Athens County Public Libraries > > http://www.myacpl.org > > > > > > _______________________________________________ > > Koha-devel mailing list > > [email protected] > > http://lists.nongnu.org/mailman/listinfo/koha-devel > > > > > _______________________________________________ > Koha-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/koha-devel > > _______________________________________________ Koha-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/koha-devel
