- Koha - lists.katipo.co.nz

Re: [Koha] Staging and matching authority records
by Ian Bays 24 Dec '15

24 Dec '15

On 24/12/2015 17:46, Ian Bays wrote: > Hi Joy, > Thanks for this. However I think it works the other way around (use > the xml file to generate the xsl file). I had a clue that the xsl > file was being used for rebuild when I introduced a syntax error in > the xsl file and rebuild threw an error. > The command to recreate the xsl (as per comments in header) is roughly: > > xsltproc ../../../xsl/koha-indexdefs-to-zebra.xsl > authority-koha-indexdefs.xml > authority-zebra-indexdefs.xsl > > but that does not put the normalize-space around the 010$a. So I > suspect I need to inspect the koha-indexdefs-to-zebra.xsl to see when > and why it inserts the normalize-space stanza. > > If anyone else has this problem with dom indexing on dev install at > roughly this version I would be happy to raise a bugzilla entry for it. > > Strangely if I do an authority search and capture the URL, then change > the "mainentry" to be "LC-card-number" and the search term to be "n > 90628286" and resubmit the changed URL it will find the correct > record. This leads me to think that the search request from the staff > client and the search interface from the matching algorithm is asking > zebra for different things. Here is (most of) the changed URL as I > don't know of any way in the staff client to search authorities for > contents of LC-card-number: > > /cgi-bin/koha/authorities/authorities-home.pl?op=do_search&type=intranet&authtypecode=PERSO_NAME&marclist=LC-card-number&and_or=and&excluding=&operator=is&value="n > 90628286"&orderby=HeadingAsc > > Thanks again. > > Ian > > On 24/12/2015 15:14, Joy Nelson wrote: >> Hi Ian- >> If you are editing the .xsl file be sure to use xsltproc to recread >> the indexdefs.xml file also. (then reindex your auths, naturally :-) ) >> >> I suspect that you are correct that there is some stripping of >> spaces, but not to the extent you are looking for. i.e. Koha is >> removing 1 space, but not multiple spaces If this is the case, >> someone with some more expertise would need to weigh in on the behind >> the scenes code. >> >> If you have some perl proficiency you can use perl scripts to pull >> out, modify the 010$a (stripping out spaces) from your authority >> records in Koha if that would help make them match the incoming >> records. But from a true catalogers perspective you want the 010$a >> in your system to be the 'right value' spaces or no spaces, so using >> a script to modify your 010$a's may or may not be desirable. >> >> joy >> > > -- > Ian Bays > Director of Projects, PTFS Europe Limited > Content Management and Library Solutions > -- Ian Bays Director of Projects, PTFS Europe Limited Content Management and Library Solutions

2 1

Koha 3.20.7 Release
by Frédéric Demians 24 Dec '15

24 Dec '15

It is with great pleasure that we announce the release of Koha 3.20.7, a maintenance release of the Koha open source integrated library system. The Koha community dedicates its version 3.20.7 to the memory of 31-year old Santu Mandal, Santu Mandal, an Indian who was a committed Koha user, as well as a Koha translator into Bengali, passed away on December 15th. Our warmest support goes to his fiancée, and to his parents. See the full release notes here: https://koha-community.org/koha-3-20-7/ Download: http://koha-community.org/download-koha/ Merry Christmas,

1 0

Koha 3.20.7 Released
by Frédéric Demians 24 Dec '15

24 Dec '15

It is with great pleasure that we announce the release of Koha 3.20.7, a maintenance release of the Koha open source integrated library system. The Koha community dedicates its version 3.20.7 to the memory of 31-year old Santu Mandal, Santu Mandal, an Indian who was a committed Koha user, as well as a Koha translator into Bengali, passed away on December 15th. Our warmest support goes to his fiancée, and to his parents. See the full release notes here: https://koha-community.org/koha-3-20-7/ Download: http://koha-community.org/download-koha/ Merry Christmas, -- Frédéric DEMIANS http://www.tamil.fr/fdemians

1 0

Staging and matching authority records
by Ian Bays 24 Dec '15

24 Dec '15

Hi. We are trying to stage some authority records to match existing authority records to overlay them. We have used the matching for bibliographic records successfully before but are having difficulty with matching authority records. The version of Koha is 3.20.01.000 and we are MARC21 using dom indexing and icu chains. Before getting into the details, can I ask if anyone has any experience of matching authorities (staging and managing) with any success? We are trying to match on the 010$a and looking at the matching rules documentation in: http://manual.koha-community.org/3.20/en/catadmin.html#recordmatchingrules Thanks in advance. Ian -- Ian Bays Director of Projects, PTFS Europe Limited Content Management and Library Solutions

6 12

Koha 3.18.13 Released
by Liz Rea 24 Dec '15

24 Dec '15

The Koha team is pleased to announce the happy holiday release of Koha 3.18.13. Please refrain from putting down your holiday beverage of choice to install this version, it will be waiting for you when you get back from your time away. :) As always, the release notes are available at https://koha-community.org/release-notes-for-koha-3-18-13/ Have a very jolly holiday period, stay safe, and we'll see you all back in the new year, when I know you are all going to be refreshed and ready to contribute patches, signoffs, opinions, and good humour to the Koha community. Liz

1 0

Searching using Z39.50/SRU
by Boulier, Jack 23 Dec '15

23 Dec '15

Can anyone explain to me why I am getting connection errors for the Z39.50/SRU option when attempting to catalog new materials? My connection options are Columbia University, Smithsonian Institution Libraries and the Library of Congress. All three give me a connection failed error. The system is connected to the internet, I am able to connect to the system using http. And the server will connect to loc.gov. Thanks for your assistance. Jack Boulier, LRC Director 5221 Madison Ave. Sacramento, CA 95841 (916) 339-4370 Direct (916) 339-0305 FAX (916) 339-1500 Main jboulier(a)mticollege.edu

2 1

Re: [Koha] Searching using Z39.50/SRU
by Paul A 23 Dec '15

23 Dec '15

At 08:34 PM 12/23/2015 +0000, Boulier, Jack wrote: >Can anyone explain to me why I am getting connection errors for the >Z39.50/SRU option when attempting to catalog new materials? My connection >options are Columbia University, Smithsonian Institution Libraries and the >Library of Congress. All three give me a connection failed error. The >system is connected to the internet, I am able to connect to the system >using http. And the server will connect to loc.gov. How have you got them set up? LoC are pretty bullet-proof and fast set up as: Hostname/Port--Database--Userid--Password--Checked--Rank--Syntax--Encoding--Timeout lx2.loc.gov:210--LCDB--blank--blank--Yes(or no)--17(your choice)--USMARC--utf8--0 The Smithsonian is oddball (siris-libraries.si.edu:210, default, USMARC, utf8) -- fast but "choosey" e.g. their own Smithsonian Miscellaneous Collections Vol. 93 No 4 (that I have in front off me) finds it using the author (Randers-Pehrson), but "nothing found" with the title "Pioneer wind tunnels" or even more odd, Title + Author also gives "nothing found"... Columbia most often seems to work efficiently: clio-db.cc.columbia.edu:7090, VOYAGER, USMARC, utf8 -- but only if they have it "on-site" e.g Butler stacks -- if it's "off-site" (whatever that means) it works about 50% of the time. Best -- Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

1 0

Re: [Koha] [ByWater Partners] [Koha North America] Your suggestions for a new name of Koha NA
by Paul A 23 Dec '15

23 Dec '15

At 03:47 PM 12/21/2015 -0700, Christopher Davis wrote: >The Koha NA officers are please to see to much discussion of this >topic on the listservs. Some sanity please: KohaUS or KohaUSA. Going back a century and a half: Yankee Koha went to town Riding on an email; He stuck a feather in his hat, And called it MARCaroni. Yankee Koha keep it up; Yankee Koha dandy, Mind the coding and the bugs, And with the git be handy. ... or something like that. Best -- Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

5 4

Your suggestions for a new name of Koha NA
by Christopher Davis 22 Dec '15

22 Dec '15

Good Day Everyone, During its first annual meeting, the scope of the Koha North America Users Group (Koha NA) was to form an organization to discuss and support Koha issues native to the U.S. Although everyone is cordially invited to every Koha NA meeting, all face-to-face meetings will be held within the contiguous U.S. to ensure that U.S. Koha users have a better chance to attend them (for many, travel outside of the U.S. is prohibited). In light of recent discussion on the Koha listservs regarding its extent, the Koha NA has voted to change its name to reflect its scope and we are asking for your help. Please reply to this message with your name suggestions and then join us at our next online meeting to vote for them (Wed, Jan 13th, 2016 @ 11 am Central Time). All the best, Christopher Davis Secretary, Koha NA

21 28

Re: [Koha] [ByWater Partners] [Koha North America] Your suggestions for a new name of Koha NA
by Stebbings, Wade 22 Dec '15

22 Dec '15

When I travel to Asia where language barriers become more of an issue, and I inevitably get asked, “Where are you from?” I often try to respond “correctly” by saying US or USA or some variant, but I will continue to get a blank stare until I speak the word “America,” and then they understand. For a lot of us, we like to think of the Americas as two continents, but for a large part of the world the denotation for America is the US. But I digress. I really appreciate the link from Mr Davis (http://koha-na.org/index.php/Minutes2015-12-09 section “Is Koha for U.S. users only or for everyone in North America?”). While this helps the context, somewhat, it still does not really elucidate the supposition behind “the problem” and “hot water” as I’ve seen used to refer to the basis for this decision. In particular, item 3 of the meeting notes mentions that holding an annual meeting outside the US would hurt the organization. Is there evidence of this, or is this a perception? The note goes on to say certain employers would prohibit employees from traveling to another country. Do you really mean prohibit? If I worked with one of these organizations and offered to pay my own way, even do this on my own time, to travel abroad to a Koha meeting, they would still stand in my way? I’m guessing what was meant was cost-prohibitive (for the organization to pay for it). Well, guess what? Budgets shifted this year at my organization and I cannot travel next spring to Los Angeles—uh, that’s in the US, too. Let’s use precise language if it’s going to be the determiner for big decisions that result in moving sites, redirecting URLs, maybe 404s, etc. I agree with the sentiment expressed by Mr Brannon and Ms. Rogers regarding wasting time in coming up with a name. —wade From: <partners-bounces(a)bywatersolutions.com<mailto:partners-bounces@bywatersolutions.com>> on behalf of Lee Jamison <ldjamison(a)maryu.marywood.edu<mailto:ldjamison@maryu.marywood.edu>> Date: Tuesday, December 22, 2015 at 10:59 AM To: "BRANNON, CHRISTOPHER" <CBRANNON(a)cdalibrary.org<mailto:CBRANNON@cdalibrary.org>> Cc: Francis Devadason <Francis.Devadason(a)doc.ks.gov<mailto:Francis.Devadason@doc.ks.gov>>, partners <partners(a)bywatersolutions.com<mailto:partners@bywatersolutions.com>>, KohaNA <kohana(a)bywatersolutions.com<mailto:kohana@bywatersolutions.com>>, Koha <koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>> Subject: Re: [ByWater Partners] [Koha North America] Your suggestions for a new name of Koha NA I just went back to check the correct translation, and in Māori, Merika or Amerika both translate to mean the USA. Their word for North America is Amerika Te Tai Tokerau so there appears to be a clear distinction between the two, though I do acknowledge you make an excellent point Christopher! On Tue, Dec 22, 2015 at 11:18 AM, BRANNON, CHRISTOPHER <CBRANNON(a)cdalibrary.org<mailto:CBRANNON@cdalibrary.org>> wrote: Some would argue that “America” is more vague than “North America”, and would make the problem bigger. ___________________________ Christopher Brannon IT Coordinator [CDAL-color (Signature Size)] 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456<tel:%28208%29769-2315%20Ext.%20456> cbrannon(a)cdalibrary.org<mailto:cbrannon@cdalibrary.org> www.cdalibrary.org<http://www.cdalibrary.org/> Keep tabs on us at: [Coeur d'Alene Public Library is on Facebook!]<http://www.facebook.com/pages/Coeur-DAlene-ID/Coeur-dAlene-Public-Library/7…> [Coeur d'Alene Public Library is on Twitter!] <http://twitter.com/cdalibrary> From:partners-bounces@bywatersolutions.com<mailto:partners-bounces@bywatersolutions.com> [mailto:partners-bounces@bywatersolutions.com<mailto:partners-bounces@bywatersolutions.com>] On Behalf Of Lee Jamison Sent: Tuesday, December 22, 2015 8:02 AM To: Christopher Davis Cc: Koha; Francis Devadason; partners; KohaNA Subject: Re: [ByWater Partners] [Koha North America] Your suggestions for a new name of Koha NA Hello everyone (I'm representing a newly-partnered institution), I've been reading the dialog between everyone and it made me ask myself "Why not bring the name back to Koha's original Māori roots?" So I thought of KohaMerica (could perhaps even be called KM for short) as Merica is the Māori word for America. It seems to roll off the tongue while still being unique and easy to identify. On Dec 21, 2015 5:47 PM, "Christopher Davis" <cgdavis(a)uintah.utah.gov<mailto:cgdavis@uintah.utah.gov>> wrote: Wade, et al, The Koha NA officers are please to see to much discussion of this topic on the listservs. If you want to learn the context of why Koha NA is changing its name, please visit <koha-na.org/index.php/Minutes2015-12-09<http://koha-na.org/index.php/Minutes2015-12-09>>. In short, Koha NA's original scope was the U.S. and we do not want our name to indicate North America when we are not able to physically meet outside of the U.S. FYI: Our monthly meetings (you're all invited to our next meeting: Jan 13, 2016) are held online and so international boarders typically do not pose any obstacle like they do when meeting face-to-face. Merry Christmas, Christopher Davis Secretary, Koha NA On Mon, Dec 21, 2015 at 10:56 AM, Stebbings, Wade <Wade.Stebbings(a)walkerart.org<mailto:Wade.Stebbings@walkerart.org>> wrote: > I agree, the frequency of face-to-face meetings can be reduced if it’s too > expensive. However, there is nothing like the serendipity offered by a > face-to-face meeting or conference. And maybe that luxury is something > done infrequently, or maybe with regional chapters. > > But I go back to what I said previously: what problem are we trying to > solve? > > If it’s about cost, then this new line of discussion has value. > > —wade > > On 12/21/15, 11:37 AM, "Francis Devadason" <Francis.Devadason(a)doc.ks.gov<mailto:Francis.Devadason@doc.ks.gov>> > wrote: > >>Why do we have to travel? We can have online conferencing. >> >>-----Original Message----- >>From: Koha [mailto:koha-bounces@lists.katipo.co.nz<mailto:koha-bounces@lists.katipo.co.nz>] On Behalf Of >>Stebbings, Wade >>Sent: Monday, December 21, 2015 10:14 AM >>To: Owen Leonard; Koha >>Cc: KohaNA; partners >>Subject: Re: [Koha] [ByWater Partners] [Koha North America] Your >>suggestions for a new name of Koha NA >> >>Owen, >> >>Christopher said ³for many, travel outside of the U.S. Is prohibited,² >>which sounds more like travel constraints due to policy reasons, not due >>to cost. If we¹re really talking about cost-optimization, then the focus >>on contiguous-US is misplaced: cost has more to do with location than >>distance, some locations are simply much higher cost to stay. For >>example, my recent conference trip to Chicago (c. 400 miles), flying and >>driving were close to the same cost, but the cost of accommodations by >>far exceeded everything else. Chicago is expensive, New York is >>expensive, San Francisco is expensive, Winnipeg is not. It has nothing to >>do with political boundaries. The majority of Canadian population lives >>relatively close to the Canadian-US border, Edmonton being the most >>egregious outlier. >> >>Agreed, we need to step back and rethink, What problem are we trying to >>solve? ŒHot water¹ doesn¹t say much. >> >>If that answer drives the shape and expanse of the organization, or >>chapter, then fine. But not until that is decided do we name something. >>It is now obvious to me the exercise of naming something is way too >>premature. >> >>‹wade >> >>On 12/21/15, 8:02 AM, "partners-bounces(a)bywatersolutions.com<mailto:partners-bounces@bywatersolutions.com> on behalf of >>Owen Leonard" <partners-bounces(a)bywatersolutions.com<mailto:partners-bounces@bywatersolutions.com> on behalf of >>oleonard(a)myacpl.org<mailto:oleonard@myacpl.org>> wrote: >> >>>I think everyone needs to pause and reflect on what the goal of this >>>process is, because we seem to be continuing to dig this hole deeper >>>instead of climbing out. >>> >>>> all face-to-face meetings will be >>>> held within the contiguous U.S. to ensure that U.S. Koha users have a >>>> better chance to attend them (for many, travel outside of the U.S. is >>>> prohibited). >>> >>>The goal of this process is to define the terms of a Koha user group >>>which meets within the contiguous United States. This narrow definition >>>is of the location of the meetings, not of those who are welcome in the >>>group. >>> >>>This rule about meeting locations is not made in order to be >>>exclusionary, but in order to create more opportunities for U.S. >>>members to participate. The United States is big, travel is expensive, >>>and libraries don't like to spend money. >>> >>>I would encourage everyone to make suggestions which don't have "North >>>America" or "America" as a basis. Both terms include areas which are >>>outside the contiguous United States and thus explicitly excluded. >>>Take a look at the maps: >>> >>>https://en.wikipedia.org/wiki/North_America >>>https://en.wikipedia.org/wiki/Americas >>> >>>Terms like "North America" and "America" are WHY we're hot water in the >>>first place. >>> >>> -- Owen >>> >>>-- >>>Web Developer >>>Athens County Public Libraries >>>http://www.myacpl.org >>>_______________________________________________ >>>Partners mailing list >>>Partners(a)lists.bywatersolutions.com<mailto:Partners@lists.bywatersolutions.com> >>>http://lists.bywatersolutions.com/mailman/listinfo/partners >> >>_______________________________________________ >>Koha mailing list http://koha-community.orgKoha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> >>https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > Partners mailing list > Partners(a)lists.bywatersolutions.com<mailto:Partners@lists.bywatersolutions.com> > http://lists.bywatersolutions.com/mailman/listinfo/partners _______________________________________________ Partners mailing list Partners(a)lists.bywatersolutions.com<mailto:Partners@lists.bywatersolutions.com> http://lists.bywatersolutions.com/mailman/listinfo/partners -- Lee Jamison Field Support Technician Verizon Wireless SPOC Marywood University 570-961-4586 ldjamison(a)marywood.edu<mailto:ldjamison@marywood.edu>

1 0