Re: [Koha] Russian Language characters in public catalog
To see the ligatures in the catalog at the Library of Congress, see
https://lccn.loc.gov/84174397
On 26-Jan-20 19:04, Eric Phetteplace wrote:
Ineed after asking on Twitter, I discovered the arch is not an accent, but
a ligature meant to indicate that two latinate characters are representing
one Cyrllic one. It's apparently an idiosyncrasy of library cataloging:
"Yup, left ligature and right ligature. It's because library
transliteration values absolute precision over readability. Just writing ia
could be, in theory, either иа or я, so the ligatures signify that it's all
one letter under there."
https://twitter.com/marccold/status/1220858664560529408
Honestly though, it doesn't matter what language or meaning the symbol has,
it doesn't render correctly in our catalog so I'm still stuck. I wonder if
anyone else has a solution that doesn't involve simply using Arial. I see a
lot of catalog records with this ligature and yet not every catalog is
forced to use one of the small selection of fonts that support it, I hope.
Best,
ERIC PHETTEPLACE Systems Librarian (he/him)
ephettepl...@cca.edu | o 510.594.3660
5212 Broadway | Oakland, CA | 94618
:(){ :|: & };:
On Sun, Jan 26, 2020 at 4:15 AM le-grex wrote:
Am 26.01.20 um 12:54 schrieb le-grex:
*snip*
So his latin Name is M. Saryan. Or in russian, М. Сарьян. I would not
expect to see this pronounciation signs in a book search, since they are
not part of his name. But i'm not a Librarian in the way that i know
what the demands of these things are.
Excuse me, i meant "М. Сарьян" without the pronounciation sign ;)
*snip*
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] LC Name Authorities - Bulk upload LC database file into Koha Authorities module?
On 1/27/2016 11:19 PM, Craig Butosi wrote: I've been curious for a while now if anyone has successfully bulk-uploaded into Koha (3.20 or newer) one of the free LC Name authority database files available through the Library of Congress:http://id.loc.gov/download/ I wonder if it's even possible given the file formats in which these files are available (n-triples, rdf/xml, Turtle, etc). It looks like some sort of conversion would be required before uploading into the Koha authorities module. It would be lovely to bulk upload a Name authority file direct from LC rather than Z39.50'ing individual authorities. This would be very positive. One of the problems is that the downloads available are not MARC, but are either MADS or SKOS. It seems as if converting these records to MARC would lose information, but I am not sure. To see what this means, look at the record "United States--History--Civil War, 1861-1865--Bibliography" http://id.loc.gov/authorities/subjects/sh2007100437.html. If you select RDF/XML (MADS and SKOS) (http://id.loc.gov/authorities/subjects/sh2007100437.rdf) this is what would need to be translated into MARC. The guidelines for mapping MARC to MADS are at http://www.loc.gov/standards/mads/mads-mapping.html, and it says "This mapping gives equivalencies between the MARC 21 Authority Format and MADS, but is not intended to be a crosswalk that allows for bi-directional conversions without some loss of data. Where there is no equivalent MARC 21 element, this mapping says "no MARC 21 equivalent". Therefore, I assume there are some problems. I don't know if anybody has experience with this, but I don't think the problems would be trivial. James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] LC Name Authorities - Bulk upload LC database file into Koha Authorities module?
Yes. It seems as if this would be a tremendous step toward the future and would help everybody. Jim On 1/29/2016 4:21 PM, Joy Nelson wrote: Agreed Tomas. I would love to see Koha have the ability to be 'format' agnostic when it comes to the data. On Fri, Jan 29, 2016 at 9:14 AM, Tomas Cohen Arazi <tomasco...@gmail.com <mailto:tomasco...@gmail.com>> wrote: There are (at least) two options: - Make Koha handle more metadata formats (for authority records / thesaurus) and have the tools extract the needed heading for the bibliographic records - Make Koha handle importing SKOS-core packages into its authority database. Those could work IMO. 2016-01-29 12:11 GMT-03:00 James Weinheimer <weinheimer.ji...@gmail.com <mailto:weinheimer.ji...@gmail.com>>: > On 1/27/2016 11:19 PM, Craig Butosi wrote: > >> I've been curious for a while now if anyone has successfully >> bulk-uploaded into Koha (3.20 or newer) one of the free LC Name authority >> database files available through the Library of Congress: >> http://id.loc.gov/download/ >> >> I wonder if it's even possible given the file formats in which these >> files are available (n-triples, rdf/xml, Turtle, etc). It looks like some >> sort of conversion would be required before uploading into the Koha >> authorities module. It would be lovely to bulk upload a Name authority file >> direct from LC rather than Z39.50'ing individual authorities. >> > > This would be very positive. One of the problems is that the downloads > available are not MARC, but are either MADS or SKOS. It seems as if > converting these records to MARC would lose information, but I am not sure. > > To see what this means, look at the record "United States--History--Civil > War, 1861-1865--Bibliography" > http://id.loc.gov/authorities/subjects/sh2007100437.html. If you select > RDF/XML (MADS and SKOS) ( > http://id.loc.gov/authorities/subjects/sh2007100437.rdf) this is what > would need to be translated into MARC. > > The guidelines for mapping MARC to MADS are at > http://www.loc.gov/standards/mads/mads-mapping.html, and it says "This > mapping gives equivalencies between the MARC 21 Authority Format and MADS, > but is not intended to be a crosswalk that allows for bi-directional > conversions without some loss of data. Where there is no equivalent MARC 21 > element, this mapping says "no MARC 21 equivalent". Therefore, I assume > there are some problems. > > I don't know if anybody has experience with this, but I don't think the > problems would be trivial. > > James Weinheimer weinheimer.ji...@gmail.com <mailto:weinheimer.ji...@gmail.com> > First Thus http://blog.jweinheimer.net > First Thus Facebook Page https://www.facebook.com/FirstThus > Personal Facebook Page https://www.facebook.com/james.weinheimer.35 > Google+ https://plus.google.com/u/0/+JamesWeinheimer > Cooperative Cataloging Rules > http://sites.google.com/site/opencatalogingrules/ > Cataloging Matters Podcasts > http://blog.jweinheimer.net/cataloging-matters-podcasts > The Library Herald http://libnews.jweinheimer.net/ > > [delay +30 days] > > ___ > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> > https://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha -- Joy Nelson Director of Migrations ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/> James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Marc21 uniform-title and koha
On 9/22/2015 6:48 PM, Gaetan Boisson wrote: So we would have this in the bibliographic record : 100 0\ $9authid $aHomer. 240 10 $9authid $aIliad And this in the authority record : 001 authid 100 $aHomer $tIliad I would have thought that the 240 should be linked to an uniform title record (with the header in 130), but this kind of authority cannot have an author name. http://www.loc.gov/marc/bibliographic/bd130.html From what i understand, we should be filling both 100 and 240 in the biblio from the 100 in the authority in this situation, with subfields from the authority going in different subfields in the bibliographic record (namely the $t will end up in a $a). As far as i know, Koha really doesn't do that. As far as how it works in Koha, I haven't got a clue--in Koha or any other ILS. In my own opinion, MARC21 has been wrong for a long, long time because it splits the 100$a$t in the authority records into 1xx/240 in the bibliographic records. I have been told that the reason is very old (from the 1960s) that it was the only way to allow search and display of authors and titles separately. This was from the card catalog, where you could search for the author as main entry or the main title. In the added entries, it was always a matter that you had to search the author's name and the title did not work. Of course, we are well into the second decade of the 21st century, and these things should be taken care of. In short: I don't know. Other, wiser heads will have to help! James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Marc21 uniform-title and koha
On 9/22/2015 4:32 PM, Gaetan Boisson wrote: as a non specialist in marc21 i am being asked how to fill field 240 properly. What i understood from what was explained to me today, is that when 240 refers to a uniform title that doesn't have a clearly defined and unique author, a uniform-title authority will be used, with the header in 130. But if the title has one unique and unambiguous author, a person for instance, a personal name authority should be used, with the title in 100$t. Seeing how authorities work in Koha this doesn't seem feasible, as the subfields will be copied from the specified header to the bibliographic record, and this would involve copying a 100$t to a 240$a while the 100$a of the authority is copied to the 100$a of the bibliographic record. Can anyone confirm this understanding of the marc21 standard and give me a better clue of how it is supposed to be implemented in Koha? Concerning the MARC format, when you have a uniform title, and it is main entry, e.g. "Beowulf" it goes into a 130. 130 \0 $aBeowulf If you have a uniform title and it has an author, the author's heading will go into the 1xx field (a person's name in 100, a corporate name in 110, etc.) and the title goes into 240, not into 100$t. So, you have 100 0\ $aHomer. 240 10 $aIliad This works differently if there is a uniform title for another work. So, if Homer's Iliad is one part of a book, e.g. the title is "Masterpieces of Greek literature" and one part is Homer's Iliad, it works: 245 00 Masterpieces of Greek literature ... 700 02 $aHomer.$tIliad. I don't know if this helps or just makes it more confusing... I have noticed that a lot of this does not seem to display in the default public view of Koha and if you want it to display, you have to implement it with your style sheet. James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] What to use, UNIMARC or MARC21 ?
On 9/15/2015 5:55 PM, Curtis Rempel wrote: L4U exports in MARC format which should be easy enough to import, however, during koha config, I had to choose between UNIMARC or MARC21. Full disclaimer: I’m a Linux guy, I wouldn’t know a UNIMARC or a MARC21 record if one fell out of the sky and knocked me out cold.:-)How would one know what to choose here? Would I somehow be able to determine what MARC flavour the L4U export is? Does it even matter? Yes, it matters a lot, but primarily to the people who will be inputting into the catalog. There are a few library formats, various flavors of MARC based more or less on nationality: there is MARC21 (which is used primarily by the Anglo-American community) but there are all kinds of others. UNIMARC is popular in Europe. Normally when a librarian wants to catalog something, they look to see if another library has already made a record for it, then the librarian can download that record into the local catalog, saving a lot of time and labor. Obviously for this to work, the formats have to be the same. So, the format makes a difference when you import these records. In the US, you can expect to download records in MARC21, but in Europe, you will expect to download in UNIMARC but there are exceptions everywhere. The inputters should know where they want to get the records--if they don't, then they need to figure it out. James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Slash (/) following title
On 12/08/2015 14.19, Owen Leonard wrote: It may be standard, and it may be correct as far as cataloging is concerned, but that doesn't mean it necessarily looks right to the general public using the catalog. As happens so often, when you take something out of its native habitat it can look strange. In the older (obsolete?) ISBD display the slash and other punctuation are OK. E.g. Transports : travel, pleasure, and imaginative geography, 1600-1830 / edited by Chloe Chard and Helen Langdon. - viii, 341 pages : illustrations ; 26 cm. I never met anyone who was bothered by the punctuation or even noticed any of it. But, when you change the environment you see: Transports : travel, pleasure, and imaginative geography, 1600-1830 / by Chard, Chloe; Langdon, Helen. the hanging slash is a punch in the face, although probably nobody would really care about the : (colon) between the title-subtitle. But if the display was: Transports : travel, pleasure, and imaginative geography, 1600-1830 / by Chard, Chloe; Langdon, Helen. people would notice the hanging : and think that was weird too. The Belgian painter Rene Magritte was really good at taking normal, everyday things and putting them in strange situations, so that they become weird. http://www.mattesonart.com/Data/Sites/1/magritte/Hegel's%20Holiday.jpg or http://www.renemagritte.org/images/paintings/personal-values.jpg The punctuation is similar. When not in an ISBD display, it should probably be removed. James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Cataloguing in Koha
On 19/02/2015 10.48, Diana Haderup wrote: I'm new to the list and have a question concerning cataloguing in Koha (version 3.16.04). It pertains to the MARC fields 110/111 or 710/711 respectively. All of them have the First Indicator in common, which is defined as follows: First Indicator Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order (see:http://www.loc.gov/marc/bibliographic/bd110.html) The LOC examples did not help much to interpret the meaning of the first indicator. Can somebody shed light on how to understand the numbers' descriptions and when to choose which number? I'd be grateful for examples as well. I don't know if this is the list for regular cataloging questions. Most of those go to lists such as Autocat. To answer your question: The 2 is used in most cases. The 1 is used with some kind of government agency where the government agency controls a jurisdiction (national, down to local such as a city). Therefore, you will see in the examples: 1101#$aUnited States.$bNational Technical Information Service 1101#$aMinnesota.$bConstitutional Convention because the US and Minnesota are jurisdictions, while any non-jurisdictional agency will have a 2, e.g. 1102#$aInternational Labour Organisation.$bEuropean Regional Conference because while the ILO is a inter-governmental agency, it is not a jurisdiction. But note. There is also 1102#$aCatholic Church.$bConcilium Plenarium Americae Latinae where the Catholic Church gets a 2 because it is not a jurisdiction, but 110 1_ |a Papal States. |b Congregazione del buon governo and 110 1_ |a Vatican City. |b Comitato centrale del grande giubileo dell’anno duemila these get a 1 because they are jurisdictions. This also goes for references, e.g. 110 2_ |a New York Public Library has a reference 410 1_ |a New York (N.Y.). |b Public Library as a subbody of the jurisdiction of New York City. Determining whether bodies should be entered subordinately to larger bodies or not can be difficult. It can be especially tough for government (jurisdictional) bodies. The rules for AACR2 are 24.17-24.19, plus the RIs at https://sites.google.com/site/opencatalogingrules/library-of-congress-rule-interpretations Whenever I explain these things, I have to stop and discuss why cataloging rules can be so complicated. Often it makes sense but in this case, I have never in my life seen how a 1 or 2 makes any difference in searching or display (I have never run across a 0). In theory, I guess you could have the 1 file differently from the 2 so that you could--in theory--get government bodies filed separately (if anybody would want it), but it wouldn't work anyway because the rules for determining the form of name of a subordinate body are so obscure it would be almost totally arbitrary. For instance as we saw, New York Public Library is *not* considered a subbody of the jurisdiction of New York! Although it is! It's only a reference. Explain that to a member of the public! And how these forms will be at all relevant in the world of linked data, I really cannot imagine. These are some of the issues I have hoped the world of cataloging would address, but they haven't. Oh well, back to work! -- James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts [delay +30 days] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Library Herald App - Beta testers wanted
Apologies for cross-posting Hello everyone, I would like to announce a new Android app for librarians to keep up with the latest news, The Library Herald App available at https://play.google.com/store/apps/details?id=com.library.herald.wo.jobs I have put it as a Beta version (meaning it needs testing), and I would *really appreciate* testers. I have set up a Google Community for that purpose: https://plus.google.com/communities/108527211796112252514 Anybody can join, and the app is free. Right now, it works only on Android, but if there is a good response, it could entice me to make it work on other devices. It has already been an interesting learning experience, and I even made a promotional video. For more explanation, here is my opening post on the Google Community site: I began this project as a learning experience for myself. First, I wanted to learn how to make an app, so I made one that I thought would be useful for my own purposes, and it turned out to be better than I expected and I wanted to share it. It turned out that if you want to share apps, it is best to use Google Play so that you do not have to sideload anything. So now I am learning the process of putting the app into the marketplace and how development can take place. To have a development process, you need to make a Google Community! By the way, you will see ads in this app, but the money does not go to me. It goes to the project that helped me create this app. Now I want to learn how to build apps from scratch. If people like this app, it will be an incentive for me to learn! Maybe we can all learn together, while we improve the app for everyone! Please share this post with anyone who may be interested. James Weinheimer weinheimer.ji...@gmail.com First Thus http://blog.jweinheimer.net First Thus Facebook Page https://www.facebook.com/FirstThus Personal Facebook Page https://www.facebook.com/james.weinheimer.35 Google+ https://plus.google.com/u/0/+JamesWeinheimer Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts The Library Herald http://libnews.jweinheimer.net/ The Library Herald App https://play.google.com/store/apps/details?id=com.library.herald.wo.jobs ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] JS bookmarklet for non-Z39.50 copy-cataloging.
On 5/27/2014 10:01 PM, Mccallum, Charles wrote: snip Hi: I'm not sure how useful this will be for other folks, but I've just put up a demo of a JS bookmarklet that can make copy-cataloging in Koha easier from non-Z39.50 data sources. A demo of Koha integration is here: http://firuta.huh.harvard.edu:8080/fp-koha-demo/ and a more complete readme and checkout instructions are here: http://sourceforge.net/p/filteredpush/svn/HEAD/tree/trunk/FP-DataEntry/ This project initially targeted the museums community where the idea of copy-cataloging isn't as familiar: Thinking about it, there seemed to be a number of cases that were analogous. This plugin tries to be generic so that it could be used anywhere there is an authoritative source of information, and a web form that needs to be filled in. /snip Thanks for that. It is really cool. Could it be changed to allow adding materials for websites coded with schema.org? -- James Weinheimer weinheimer.ji...@gmail.com First Thus http://catalogingmatters.blogspot.com/ First Thus Facebook Page https://www.facebook.com/FirstThus Cooperative Cataloging Rules http://sites.google.com/site/opencatalogingrules/ Cataloging Matters Podcasts http://blog.jweinheimer.net/p/cataloging-matters-podcasts.html ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] CDS/ISIS to MARC21 (Koha) issue
Are you sure you want to merge everything into a single 100? MARC21 works otherwise. If you did have 100 1\ $aSmith, John;$aEdwards, Mary;$aJackson, Ann It would seem to be more difficult to prevent a search for a specific John Jackson or Mary Smith *not* to pull up this record. This is one place I would do a lot of thinking about, because once they are merged, they could be very difficult to unmerge if necessary. Jim On 13/05/2013 12:29, Alexandru Constantin wrote: Dear colleagues, I'm trying to convert (using MARCEdit) my approx. 10 000 entry ISIS database to MARC21 for import in Koha. I'm encountering the following problem: Some of the tags for each book are duplicate; for example, for multiple authors, the record will look smth like this: ... =702 John =702 Mary =702 Ann ... I would like to merge this fields into the MARC21 100 field like this: ... =100 \\$a John, Mary, Ann ... Unique fields haven't posed problems, but those duplicates do. I would really appreciate some help. Best regards ^_^, -- *James Weinheimer* weinheimer.ji...@gmail.com *First Thus* http://catalogingmatters.blogspot.com/ *First Thus Facebook Page* https://www.facebook.com/FirstThus *Cooperative Cataloging Rules* http://sites.google.com/site/opencatalogingrules/ *Cataloging Matters Podcasts* http://blog.jweinheimer.net/p/cataloging-matters-podcasts.html ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Can any one help me
On 11/04/2013 13:08, Dagne Woldie, MS/HS Library Assistant wrote: snip If koha enable us to catalog Ethiopian collection. That books written in Amharic language. Please if any one who has such experience. please, please/ /snip There are two options you can use. Koha can use the unicode character set so therefore, you should be able to enter the characters in Amharic. There are various options for entering Unicode characters. The other option is to use what is called transliteration, as is done in most libraries. The Library of Congress uses this transliteration table http://www.loc.gov/catdir/cpso/romanization/amharic.pdf. If you want to see if another library in Worldcat http://www.worldcat.org has already cataloged an item in Amharic, you will use these transliteration tables to search, e.g. http://www.worldcat.org/oclc/745610236 I am sure that other countries use other transliteration tables, but these are the ones that I know. I don't know anything about Amharic, though. -- *James Weinheimer* weinheimer.ji...@gmail.com *First Thus* http://catalogingmatters.blogspot.com/ *Cooperative Cataloging Rules* http://sites.google.com/site/opencatalogingrules/ *Cataloging Matters Podcasts* http://blog.jweinheimer.net/p/cataloging-matters-podcasts.html ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
