- Koha - lists.katipo.co.nz

Re: [Koha] Koha XSLT Editing - Hyperlinking the Uniform Titles Element
by Paul A 02 Mar '15

02 Mar '15

At 06:20 PM 3/2/2015 +0000, Craig Butosi wrote: >Hi Everyone, > >Thanks to all who have replied regarding XSLT editing in Koha. It appears >that the syntax is the source of my confusion - something to work on! A relatively complete "cheat sheet" can be found at <http://xpath.alephzarro.com/content/cheatsheet.html> -- I have found it useful, YMMV. Paul

1 0

Koha XSLT Editing - Hyperlinking the Uniform Titles Element
by Craig Butosi 02 Mar '15

02 Mar '15

Hi Everyone, 3.18.03 on Linux Ubuntu 3.13.0-45 I'm attempting to learn how to modify XSLT files in order to change the look of the OPAC detail and OPAC result pages. I'm finding this an extraordinarily difficult task. CSS and HTML are much more intuitive to me than XSLT. I might be out of my league on this one. What I would like to start out doing is transforming the Uniform Titles element on the OPAC details page into hyperlinks, so that users can search on UTs from the details page. I've located MARC21slim2OPACResults.xsl and am trying to learn how to add the href attribute, but am lost. Has someone attempted to do this before? If so, and provided my request is not too labor-intensive, would someone on the list be willing to help me out on this? If I perhaps see the correct way of going about this from you, I might be able to more confidently edit other areas of the XSLT pages. Right now I am quite unsure. Happy to be referred to XSLT learning guides that others use too! Many thanks!! Best to all, Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca<https://webmail.rcmusic.ca/owa/redir.aspx?C=b481823b299d45ee94b0016389bb76e…> Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.

3 3

Problem linking authorities
by Pablo Bianchi 02 Mar '15

02 Mar '15

Hi, I have a strange problem. Linking an authority works perfectly with any framework (like "VR", DVDs) but one of them (BKS) doesn't automatically close the popup after linking an authority, neither complete $9 (RLIN) subfield. With this SQL queries* I compare side by side tags 650 (the problem happens with all authorites subfields, 100, 700...) of marc_tag_structure and subfields $9 and $a og marc_subfield_structure table. I update all to set them almost identical but it still have this strange behave. I suspect it have something to do with bug #5093. Javascript console throw *blinddetail-biblio-search.pl:160 <http://blinddetail-biblio-search.pl:160> Uncaught TypeError: Cannot set property 'value' of undefined* "choose" link have last parameter empty: javascript:doauth('15583', 'tag_650_subfield_a_127347_735090', '') This was working some weeks ago, so maybe is related to lastest package upgrades. Using Koha 3.18.4, latest Chromium and Firefox. Things I tried on "BKS" rows: + "defaultvalue" to NULL instead of empty. + "hidden" and "tab" field exactly same values than others frameworks, like "VR". + Empty intranetuserjs syspref. + Removed diacritics from descriptions fields, also from biblio_framework table. + On marc_subfield_structure table, even added nonexistant table "bibliosubject.subject" to kohafield field, as added by default on sample builtin FWs. Thanks! Pablo * SELECT * FROM `marc_subfield_structure` WHERE tagfield="650" AND (tagsubfield="a" OR tagsubfield="9") AND (frameworkcode="BKS" OR frameworkcode="VR") SELECT * FROM `marc_tag_structure` WHERE tagfield="650"

2 2

Bugzilla and other sites outage
by Chris Cormack 02 Mar '15

02 Mar '15

Hi All Linode are rebooting all of their xen servers which will mean the VM that bugzilla and a bunch of other Koha sites and tools run on will disappear for a couple of hours. It will be rebooted at 2015-03-07 6:00:00 PM UTC They have allocated a 2 hour window, but it should not be down that long. Chris

3 2

Re: [Koha] Catalogue - SQL Report Help
by Paul A 02 Mar '15

02 Mar '15

At 11:00 AM 2/26/2015 +0530, SATISH wrote: [snip] >And am looking for help for generating unique records (biblio) after >merging both BK and BB. I am trying with following sql, but throwing >errors. Can you please help me over here. >---------------------------------------------------------------------------------------------------------------------------- > >SELECT DISTINCT b.biblionumber, b.title, b.author, t.editionstatement, >t.publishercode, t.isbn, i.ccode, count(i.itemnumber) FROM biblio b LEFT JOIN >biblioitems t USING(biblionumber) LEFT JOIN items i USING(biblionumber) >WHERE items.itype='BB' AND items.itype='BK' GROUP BY b.biblionumber >--------------------------------------------------------------------- > >Error: >The database returned the following error: >Unknown column 'items.itype' in 'where clause' Two points: First, after you define "JOIN items i" you refer to 'items' as 'i'. Second, itype cannot have two values -- it is either BB or BK... Try your last line as: WHERE i.itype='BB' OR i.itype='BK' GROUP BY b.biblionumber; Best -- Paul

3 4

Re: [Koha] Catalogue - SQL Report Help
by Paul A 28 Feb '15

28 Feb '15

At 10:10 AM 2/28/2015 +0530, SATISH wrote: >Hi, >I found one solution, but it is not through Koha. >I exported unique records generated by both the item type BB and BK and >put it in a single excel file and applied conditional formating and >applied filter ( to ISBN column, since it is unique) by colour and found >the duplicate biblionumber/titles generated between BB and BK (not among >BB or BK) and removed manually. But, still I expect, automated software to >perform this using sql. >When fetching unique records from particular item type is possible means, >merging both the items types results, creating a view for that and >eliminating duplicate records should also be possible using sql. But I am >not good in mysql. > >Since my library requirement is to maintain "book" and "book bank" as >separate item types for accommodating more than one circulation rules and >also facilitate searching with-in particular item type. You write "separate item types" and "eliminating duplicate records" -- but "item type" is a *biblio* attribute (942$c, not repeatable), so if you want 2 item types, you must have 2 bibliographic records, each with its own biblionumber even if they are otherwise identical. Perhaps what you are looking for is two "branches" -- one "books", one "book bank", where you might be able to set different policies... Best -- Paul >I request this forum to help me for doing this within koha using sql not >manually (using excel) please or someone already did similar exercise >please help me. > >Hoping to get some solution. > >With thanks. > >Satish MV >Librarian >Govt. Engineering College, Hassan. >Karnataka. > > >On Fri, Feb 27, 2015 at 11:06 AM, SATISH ><<mailto:lis4satish@gmail.com>lis4satish(a)gmail.com> wrote: >Thank you Paul, I made corrections, but the purpose is not solved. >By using "OR" it populates duplicate record. > >By maintaining only one kind of item type, I can not make varied >circulation policies (but can generate unique records report for books), >and in this case, for the same user I have to provide two different kind >of ID cards for issue books from BK and BB, since no provision to create >different circulation policy. > >And if I make two kinds of Item Type, then unique report won't come ? (can >make varied circulation policies, that is, by using single ID, I can issue >books of different item types). > >Is there any way to generate a report either separately for each item type >orÂ as indicated by you using "OR" between BK/BB and then apply some >query to eliminate duplicates within Koha. > >or any other way, koha team could help me ?? > >Hoping to get some solution. > > >Thank You >Satish MV >Librarian >Govt. Engineering College, Hassan. >Karnataka. > > > >On Thu, Feb 26, 2015 at 8:04 PM, Paul A ><<mailto:paul.a@navalmarinearchive.com>paul.a(a)navalmarinearchive.com> wrote: >At 11:00 AM 2/26/2015 +0530, SATISH wrote: >[snip] >And am looking forÂ help for generating unique records (biblio) after >merging both BK and BB. I am trying with following sql, but throwing >errors. Can you please help me over here. >---------------------------------------------------------------------------------------------------------------------------- > >SELECT DISTINCT b.biblionumber, b.title, b.author, t.editionstatement, >t.publishercode, t.isbn, i.ccode, count(i.itemnumber) FROM biblio b LEFT JOIN >biblioitems t USING(biblionumber) LEFT JOIN items i USING(biblionumber) >WHERE items.itype='BB' AND items.itype='BK' GROUP BY b.biblionumber >--------------------------------------------------------------------- > >Error: >The database returned the following error: >Unknown column 'items.itype' in 'where clause' > > >Two points:Â First, after you define "JOIN items i" you refer to 'items' >as 'i'.Â Â Second, itype cannot have two values -- it is either BB or >BK...Â Try your last line as: > >WHERE i.itype='BB' OR i.itype='BK' GROUP BY b.biblionumber; > >Best -- Paul >_______________________________________________ >Koha mailing listÂ <http://koha-community.org>http://koha-community.org ><mailto:Koha@lists.katipo.co.nz>Koha(a)lists.katipo.co.nz ><http://lists.katipo.co.nz/mailman/listinfo/koha>http://lists.katipo.co.nz/mailman/listinfo/koha > > > > >-- > > > > > > >-- > >

1 0

Converting to dom indexing
by Steven Nickerson 28 Feb '15

28 Feb '15

Hello all, I've recently upgraded a package install environment on Debian to 3.18.04 and have the 'symptoms' of not being able to find anything in the OPAC search and also seeing the "couldn't open collection.abs" error when trying to rebuild the zebra indexes. I'm trying to follow the "Switching to dom indexing" instructions at the <http://wiki.koha-community.org/wiki/Switching_to_dom_indexing> http://wiki.koha-community.org/wiki/Switching_to_dom_indexing Wiki but have a few questions. Can someone please help me understand: - The first step is to add some lines after the "" line, but what if I don't find that line in my /etc/koha/sites/<sitename>/koha-conf.xml file currently? I don't have any lines with "maximumrecordsize" in them at all, so where exactly do the new lines about 'retrieval-info-bib-dom.xml'' need to be added? - The next step is to add 2 "/xi" lines after the "</retrievalinfo>" line, but which "</retrievalinfo>"? I kind of assume this is all referring to the whole stanza that starts with "" but I don't want to be wrong with my assumption - The next step says "Do the same thing for authorities and the retrieval-info-auth-dom.xml file". Where/what is the "authorities" file, and where in that file do I make the additions? Finally, I find the retrieval-info-auth-dom.xml file at /etc/koha/zebradb, but again, where inside that file do I make the additions? Thanks in advance! Hope these haven't all already been answered before. Steve

2 1

'mixed materials' showing up as 'book' item types
by Heidi Addy 27 Feb '15

27 Feb '15

I have a number of items that are cataloged at 'mixed materials' both in the 000 field and the 008 field, but they are showing up as 'book' item types on the original search results page. If I click on the item title or item details it shows correctly as 'mixed materials.' I heard this was a bug in the old Koha version and I think these records must have carried over. The mixed material records I create in the new version display correctly. Any suggestions on how I can fix the records carried over from the old Koha version with the bug? Thanks, Heidi

1 0

Where do I find the batch code and category code.
by ChristyThomas 27 Feb '15

27 Feb '15

Hi, I am not able to speak with the person that did the installation who can tell me the batch code and category code. Is there a way for me to get them logged in as the administrator? Thanks for all your help. I appreciate this forum. Christy -- View this message in context: http://koha.1045719.n5.nabble.com/Where-do-I-find-the-batch-code-and-catego… Sent from the Koha-general mailing list archive at Nabble.com.

2 2

Plugins for RDA for 336, 337, 338 $a
by Mike D. 27 Feb '15

27 Feb '15

Hello, can I ask community how libraries solve subfiels $a at fields 339, 337, 338? It can't be solved by Authorized values because they cant' contain any spaces or national characters. But texts are too long for manual writing isnt' it? How you solve this? Thanks Mike

1 0