To german translator of Koha
Hi Friedrich, I see your commits on CVS, and have some comments/suggestions to do : * 1st you speak of "2.2.3", but are commiting on cvs-head. Didn't you make a mistake ? * 2nd, you commit individual templates, where you should just use the .po translator mechanism. I hope you don't edit the templates manually, because you will get mad to follow all the changes we do. look in misc/translator directory in CVS to find all what you need to translate Koha. I hope this makes sense. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Joshua asked me to post a quick note to clarify why NPL uses a MARC 21 952 tag for holdings information instead of the 852 tag. Like many libraries, NPL used commercial ILS(s) that used a 9xx tag for holdings information instead of the 852 tag. (In NPL's case, the previous vendors had used a 952 tag, so it was easiest to continue with the 952 tag when the records were migrated to Koha.) This is pretty common practice, since a library (or ILS vendor) is free to define the subfields of a 9xx tag, while the 852 subfields are controlled by the MARC 21 bibliographic format. Often an ILS wants to save item information that doesn't fit the 852 format, and then the free-form 9xx tags are a good solution. For example, Koha stores home branch and holding branch information for each item. The 852 tag format doesn't have any good subfields for these, unless you use some of the location and/or collection subfields in an abnormal way. Using a 9xx tag, which might be loosely based on the 852 tag, may be a more attractive solution for a library. -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
participants (2)
-
Paul POULAIN -
Stephen Hedges