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

[QA] QA break between tonight and the beginning of the hackfest in Marseille
by Fischer, Katrin 26 Feb '14

26 Feb '14

Hi QA team, as a result of yesterday’s developer meetings we are going to take a short break from QAing in order to give Galen the opportunity to clean out the Passed QA queue before the hackfest in Marseille. Please focus on sign offs and kitten rescue (looking at bugs in Failed QA, Doesn’t apply) during this and next week instead. Thank you! Katrin

1 0

Database in specific directory & backup
by Andrea Furin 26 Feb '14

26 Feb '14

hi to all. two questions: 1. is it possible to save the koha database in a specific directory, like in home directory in a second hard drive? 2. for making regular backups is it better to have only one partition in an hard drive (system + data) and create an image file of the hard disk and save it in other storage devices instead of having an hard disk for system and another for data? (i noticed that config files are in different places in system partition) tia andrea furin --

1 0

FW: [Koha] 3.14 Koha (Pie)
by Marcel de Rooy 26 Feb '14

26 Feb '14

"Cherry picked" from Koha ML. Compliments for Brendan and Galen. As well as for the March 14 option from Heather :) ________________________________________ Van: koha-bounces(a)lists.katipo.co.nz [koha-bounces(a)lists.katipo.co.nz] namens Hernandez, Heather [heather_hernandez(a)nps.gov] Verzonden: dinsdag 25 februari 2014 23:10 Aan: Brendan Gallagher CC: koha(a)lists.katipo.co.nz Onderwerp: Re: [Koha] 3.14 Koha (Pie) Hey, Brendan-- You didn't wait until Mar. 14?:) I hope he enjoys his Pi Pie! Cheerio! --heather ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian Cultural Resources and Museum Management Division San Francisco Maritime National Historical Park heather_hernandez(a)nps.gov 415-561-7032 (voice) 415-556-3540 (fax) http://www.nps.gov/safr/historyculture/library-collections.htm "The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Proposal of a new development for Marseille hackfest, feedback needed
by Paul Poulain 24 Feb '14

24 Feb '14

Hi koha-devel, There are sometimes debates about how and who is using Koha, how it is setup, which decision is of general interest. I had 2 ideas that could be developed during the hackfest. 2 of BibLibre developers are very motivated by the idea, anyone else can join us ;-) **** 1st idea : collecting -anonymous- data on staff interface usage We sometimes are wondering whether librarians are running an old version of IE, or if they have a large screen, or if the page X is often run or not. There's a tool that could let us know: piwik (BibLibre already has an offer on Piwik for the OPAC) The idea here would be to add piwik for staff interface, and collect all datas on a single piwik instance. We made something (quick) for one of our current supported library, just to see what kind result we could get. We're quite happy with the performances, datas are interesting (which browser is used, which screen size, which pages. [ For example, the library runs an average of 40 times "reports/catalogue-stats.pl" every day (yes, that's crazy ;-) ). This page is worth being optimized !!! ] The only caveat we've seen for now is that it can be tricky to have many websites pointing to the same piwik database. We also are not completely peaceful with having 10 000 librarians calling the server. We could face a heavy load... But that's worth investigating imo. (for those who don't know what is piwik, it's like google analytics, but respect your privacy ;-) Ah, and it's a software developed by a frenchy, living in new zealand, that has office hosted by catalystNZ afaik) If the community likes the idea, we will ask him for any advice on the 2 caveats we fear. [ PS: please avoid starting a troll about piwik collecting anonymous data or not because of the IP. Anyway, the feature will be trigger-able by the library. ] **** 2nd idea : collecting nominative datas. We very often face the question "how many libraries are using Koha" So the idea is to have a form that let the library declare itself. Library name, type (academic, public,...), country,... We could also collect other data, like catalog size, systempreferences values to be able to make statistics. Example of answers we could get: * how many libraries are using Koha in Africa ? * What's the average catalog size ? Which library is the largest one ? * Is someone/how many libraries are using the "insecure" mode (syspref=insecure set to "Yes") ? [ If no, we can drop it ! ] Each library could choose to share or not the data (and maybe which level of data. One could accept to declare itself & share sysprefs, but not appear on nominative listings for example) A specific website could be made to display informations, either nominative or not. Do you like those ideas ? PS: BibLibre is of course willing to host piwik and "statistics" servers. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

5 5

foss4lib webinars about OpenSource in libraries
by Paul Poulain 24 Feb '14

24 Feb '14

Not really a developer thing, but I see that foss4lib organise some webinars about "OpenSource". Does anyone from this mailing list plan to attend one of them or know what they'll talk about ? ( https://foss4lib.org/content/free-webinars-introducing-foss4lib ) -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Install Koha 3.14.03 with Single Command in Ubuntu 12.04 LTS
by DP Tripathi 22 Feb '14

22 Feb '14

Dear Library Professionals! Install Koha 3.14 with single command in Ubuntu 12.04 LTS. Download and keep the file wherever you wish to keep in the server. (For ex: someone keeps the file at Desktop) then run the following command. This script assumes that you have Apache and MySQL pre-installed in your system. Login as root: sudo su (Enter) Enter the password: Run the following command: *root@localhost:/home/library/Desktop# *chmod +x install_koha.sh *root@localhost:/home/libraryDesktop# *./install_koha.sh Ensure that your system is connected with Internet. Follow the Instruction. Add the port 8080 (Listen 8080) when it asks to add and save & close the file. It will install Koha 3.14 in your system. To open the Interface, use the following user id and password. User ID : koha_library Password: (please note down the password from terminal, it appears like 10ImCcKq3QHpfdx7) Enjoy! Feel free to contact at dptkvs(a)gmail.com, if you face any problem. Download the File at http://librarianguide.in/install_koha.sh Thanks! -- ********************* D. P. Tripathi Assistant Librarian Biju Patnaik Central Library NIT Rourkela Odisha - 769008 India www.librarianguide.in **********************

1 0

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