- Koha-devel - lists.koha-community.org

Re: [Koha-devel] Please assist: auth values
by Paul A 20 Feb '14

20 Feb '14

Thank you both, Joy and Robin S., for your replies. I had started preparing the explanation below, when I found the solution - 'fl2_rare' must be some sort of a remnant from "pre-production" days, whereas what we deleted (and now restored) is 'fl2_rare ' -- note the space at the end. Reading SSH screens and Firefox browsers did not make it obvious, but in hindsight I've learned a new lesson in querying MySQL; with and without the spaces gives identical results !!! : mysql> SELECT location, COUNT(location) FROM items WHERE location = '2fl_rare'; +-----------+-----------------+ | location | COUNT(location) | +-----------+-----------------+ | 2fl_rare | 920 | +-----------+-----------------+ 1 row in set (0.00 sec) mysql> SELECT location, COUNT(location) FROM items WHERE location = '2fl_rare '; +-----------+-----------------+ | location | COUNT(location) | +-----------+-----------------+ | 2fl_rare | 920 | +-----------+-----------------+ 1 row in set (0.00 sec) Six hours scratching my head, but we're back in business. The only outstanding query I might have is that a search for 'mc-loc=2fl_rare' (with and without trailing space) finds 628 results -- but where is 'mc-loc' finding the 628 ??? And why only 628 of the 920 ??? As an aside, there seems to be some dev.mysql.com documentation on the treatment of trailing spaces in CHAR and VARCHAR types. I think (but could be wrong) that some Koha functions strip trailing spaces. Could this possibly be a point to consider with auth types? Again with my sincere thanks -- Paul Written earlier: This reply covers points you both raised At 05:33 PM 2/19/2014 -0600, Joy Nelson wrote: >Golly Paul! When you say that the volunteer deleted a loc value of >rare book room, are you referring to the authorised value of rare book >room? If so, then you should be able to simply re-add a location of >rare book room to the authorised value list and be ok. Yes, exactly, but an sql query [SELECT * FROM authorised_values WHERE category='loc'] still finds the auth value: id category authorized_value lib lib_opac 1834 loc fl2_rare 2nd floor rare 2nd floor rare so, if I try and "re-add" I get: "Could not add value "fl2_rare" for category "loc" - value already present." But in any case, the drop-down box for cataloguers editing "items" has definitely lost this value (but id=1833 and 1835 are both still there. See <<http://navalmarinearchive.com/ims/koha_staff_edititem.jpg>http://navalmarinearchive.com/ims/koha_staff_edititem.jpg> -- nothing between "2nd floor" and "2nd floor reference".) >When an authorised value is deleted, it does not delete the data in the items >table (items.location) This is what I expected: mysql> SELECT location, COUNT(location) FROM items WHERE location = '2fl_rare'; +-----------+-----------------+ | location | COUNT(location) | +-----------+-----------------+ | 2fl_rare | 920 | +-----------+-----------------+ 1 row in set (0.00 sec) which seems about right -- but they're invisible in the OPAC. E.G. <http://opac.navalmarinearchive.com/cgi-bin/koha/opac-detail.pl?biblionumber…>, but items.location is definitely correct, please see <http://navalmarinearchive.com/ims/koha_staff_biblio_427.txt> ( SELECT * FROM items WHERE biblionumber=427 --- it's too long to paste here.) At worst, if I can restore the auth value to the drop down box, we could go through all 920 items and edit them by hand. >I'm not sure what you mean when you say "so I can't "re-enter" the >auth value which is no longer available for admin editing" >This is not been my experience with the authorised_values list. > >Are you finding data on a query like this? > select barcode from items where location =<enter the code you used >for rarebooks> >or > select distinct(location) from items -which will show you all the >location values in use in the database. > >-joy > >On Wed, Feb 19, 2014 at 5:21 PM, Paul A <paul.a(a)navalmarinearchive.com> wrote: > > Please can one of you assist? > > > > We are in the middle of shelving several hundred boxes of books, and seven > > volunteer cataloguers have spent the day editing items to change the auth > > value "loc" from "box_xyz" to the proper shelf/stack. > > > > At the end of the day, an enthusiastic volunteer instead of deleting an > > empty box from the "loc" values, accidentally deleted our "rare book room" > > (my fault, I gave him superlibrarian credentials instead of doing the job > > myself.) > > > > A search still finds: "628 result(s) found for 'mc-loc=2fl_rare' in NMA > > Catalog" but this is (I think) coming from somewhere other than > > items.location. > > > > An sql query [SELECT * FROM authorised_values WHERE category='loc'] still > > finds the auth value: ... > > 1834 loc fl2_rare 2nd floor rare 2nd floor rare > > ... > > so I can't "re-enter" the auth value which is no longer available for admin > > editing; so "editing" these 628 items is impossible. The OPAC is no longer > > showing the location at all. > > > > The "catastrophe level" is that even if I revert to last nights backup, the > > volunteers tell me they have no way to pull them all (about 3,000 > books) out > > and start over again. > > > > Can anyone, pretty please, suggest a course of action? > > > > Many thanks -- Paul > > > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > >-- >Joy Nelson >Director of Migrations > >ByWater Solutions >Support and Consulting for Open Source Software >Office: Fort Worth, TX >Phone/Fax (888)900-8944 >What is Koha? --- 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

Development meeting - save the date
by Galen Charlton 20 Feb '14

20 Feb '14

Hi, I am calling a development meeting for Tuesday, 25 February 2014, to be held in the #koha IRC channel. All are welcome, but the focus will be on development topics. Tentatively, I would like to discuss the following topics: - DBIx::Class and guidelines for its use in Koha - Search engine work, including enhancements to usage of Zebra and Elastic Search - Pending large enhancements for 3.16 The agenda is being kept intentionally short to permit an in-depth discussion of each item, but if there is a topic that you want to be covered and which requires the participation of most or all of the active developers, please let me know. To permit everybody to participate, I propose that we effectively meet /twice/ that day. 15:00 UTC+0 (http://www.timeanddate.com/worldclock/fixedtime.html?msg=xxx&iso=20140225T15) and 21:00 UTC+0 (http://www.timeanddate.com/worldclock/fixedtime.html?msg=xxx&iso=20140225T21) I will be attending both parts, of course, and will try to act as a bridge between the two sessions. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

5 4

Please assist: auth values
by Paul A 19 Feb '14

19 Feb '14

Please can one of you assist? We are in the middle of shelving several hundred boxes of books, and seven volunteer cataloguers have spent the day editing items to change the auth value "loc" from "box_xyz" to the proper shelf/stack. At the end of the day, an enthusiastic volunteer instead of deleting an empty box from the "loc" values, accidentally deleted our "rare book room" (my fault, I gave him superlibrarian credentials instead of doing the job myself.) A search still finds: "628 result(s) found for 'mc-loc=2fl_rare' in NMA Catalog" but this is (I think) coming from somewhere other than items.location. An sql query [SELECT * FROM authorised_values WHERE category='loc'] still finds the auth value: ... 1834 loc fl2_rare 2nd floor rare 2nd floor rare ... so I can't "re-enter" the auth value which is no longer available for admin editing; so "editing" these 628 items is impossible. The OPAC is no longer showing the location at all. The "catastrophe level" is that even if I revert to last nights backup, the volunteers tell me they have no way to pull them all (about 3,000 books) out and start over again. Can anyone, pretty please, suggest a course of action? Many thanks -- Paul

3 2

RM FYI: index definition patches
by Galen Charlton 19 Feb '14

19 Feb '14

Hi, DOM has been the default indexing mode for bib records for Koha since June 2012, and as of August 2013 is the default mode for instances creating using koha-create. It is desirable that the indexes definitions are not allowed to drift too much between DOM and GRS-1, at least until such time as we fully deprecate GRS-1. Consequently, as of now, for anything new that get submitted, I will decline to push patches that update the GRS-1 index definitions but do not also update the DOM definitions (except, of course, for cases where the purpose of the patch is to repair an issue that only affects the GRS-1 index definitions). This does not apply to any patches that have passed QA or which have been signed off in the past month, although I will retain the right to refer the bug back to the original patch submitter if it turns out to be nontrivial to write a follow-up that updates the DOM configuration. As with any pronouncement of this nature, this is not set in concrete -- if there is a valid reason for a patch to update GRS-1 but not DOM, that's fine -- but patch submitters will have to articulate that reason. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

1 0

Simple bug to test: News by branch
by Mark Tompsett 16 Feb '14

16 Feb '14

Greetings, Okay, it’s a couple months sitting there, and I figure it’s the enhancement status is part of the reason people haven’t gotten to looking at it. The other part being just that everyone is very busy. Bug 7567 has 8 patches which are actually fixes, for the most part (adding testing vs. really insufficient test, updating licenses, cleaning up the sample news data, cleaning up a warning, correcting an incorrect dropdown behaviour, removing finish() calls, fixing the crazy long number of parameters into a hashref), and only the last 2 are the actual enhancements (adding branchcode into the opac_news table, and then actually using it). I intentionally split it into small easily testable pieces. It would nice to see it signed off. Thanks in advance. GPML, Mark Tompsett

1 0

Re: [Koha-devel] [Koha] Kohacon 2014 in Córdoba, Argentina
by Paul Poulain 16 Feb '14

16 Feb '14

Le 09/10/2013 22:35, Luis Maguina a écrit : > Cordoba is in South - America ... Argentina :) In french, we say "lapsus révélateur". Google translate this to "revealing slip" ;-) -- Paul POULAIN - Associé-gérant Tel : (33) 4 91 81 35 08 http://www.biblibre.com Logiciels Libres pour les bibliothèques et les centres de documentation

2 1

Call for news for February newsletter
by Koha Newsletter 14 Feb '14

14 Feb '14

Fellow Koha users ~ We're collecting news for the February newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- * News items can be of any length. We can link to longer entries. * Anything and everything Koha. * Submit by the 26th. Thank you! -- Chad Roseburg Joanne Dillon Editors, Koha Newsletter

1 0

wiki page about the creation of a new authority type
by Fabio T. 12 Feb '14

12 Feb '14

Hi everyone, some weeks ago I thought of a page in the Koha wiki dedicated to the creation of new autority types. I also sent a mail to the list but I realized just today that the address I wrote from wasn't registered to Koha-devel (the list was forwarded from another address of mine)... The idea came up mainly for two reasons. First, to shed some light on the procedure (I'm not even 100% sure to know all the pieces involved!); second, the manual lacks this kind of information (it just says to create a new framework as for the biblio ones, omitting any edit on the Zebra side for example). This way the community would benefit from having a standard and approved procedure for creating a fully working new authority type; the wiki format would ease the review and update of the information... then maybe some of the contents could make it to the manual (those not directly targeted to system administrators I guess). So, here's the page: http://wiki.koha-community.org/wiki/Create_new_authority_type I'm not sure it is entirely complete and correct, so any review could be crucial for the users (should I add a note on top of the page stating it is still a work-in-progress yet to be verified from the developer community?). Thank you in advance for any thoughts or contributions. Regards, Fabio -- View this message in context: http://koha.1045719.n5.nabble.com/wiki-page-about-the-creation-of-a-new-aut… Sent from the Koha-devel mailing list archive at Nabble.com.

1 0

FYI: CVE numbers for recent security update
by Galen Charlton 10 Feb '14

10 Feb '14

Hi, I requested CVE numbers for the issues fixed in the security releases; here's what was assigned: CVE-2014-1922: absolute path traversal issue in tools/pdfViewer.pl CVE-2014-1923: directory traversal issues in edithelp.pl and member-picupload.pl CVE-2014-1924: MARC framework import/export did not require authentication CVE-2014-1925: MARC framework import/export could be used to perform unexpected SQL commands Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

1 0

Wiki page update question
by Mark Tompsett 10 Feb '14

10 Feb '14

Greetings, http://wiki.koha-community.org/wiki/Developer_handbook Handy little page, but as I have noted on the discussion, the QA Testing Tools are missing from the list. Who? Where? How? Et cetera, et cetera – do I get the QA Testing Tools onto the page? That little macro-y {DevBook} is too magical for a wiki newbie like myself. GPML, Mark Tompsett

3 2