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

Several RFCs for 3.2 added
by Danny Bouman 11 Sep '08

11 Sep '08

" I have added several new RFCs for 3.2 to http://wiki.koha.org/doku.php?id=en:development:rfcs3.2. Most of these RFCs will need more detail, but I would like to get the ideas added so that they can be discussed if needed. Here is a summary of the new RFCs: Advanced cataloging search Add the same advanced search options that you find under the "Search" link on the Koha staff side to the Cataloging search accessible under the "More" menu. In addition to all of those fields it is also necessary to search by the biblio# and control# (001 tag). Fast add capability When staff is checking out an item to a customer that does not exist in the database, they need the ability to temporarily create a biblio and item, so that it can be checked out to the customer. Alert staff when unsaved changes have been made Anytime a staff person has modified data in any form on the staff side of Koha and then attempts to leave the page by either clicking on another link or using the browser back button, they should be alerted that they have made changes that have not been saved. The alert box should give the staff the option to either "Continue without saving" or "Cancel". Place a hold on multiple items I would like to propose adding the ability to select and place a hold on multiple items placed in the Cart. Tag multiple items I would like to propose adding the ability to select and tag multiple items at a single time from the Cart. Support for Syndetics Similar to how the Amazon and Baker and Taylor enhanced content is supported, the enhanced content provided by Syndetics should also be supported. -- Danny Bouman Web Programmer Howard County Central Library 10375 Little Patuxent Parkway Columbia, MD 21044 410.313.7924

1 0

ibdata1
by David Schuster 10 Sep '08

10 Sep '08

As I watch this file grow I am wondering how to clear it. I saw this on a mysql list, but wanted to get developer insight... March 2007 Location: Sweden Senior Member A very cumbersum way: 1.mysqldump all databases 2.Remove the ibdata1 file. 3.Start the mysqld process. It will now recreate the ibdata1 table space since it recognizes that it is missing. 4.Import the sql dump from step 1 and you are back again. -- View this message in context: http://www.nabble.com/ibdata1-tp19400910p19400910.html Sent from the Koha - Dev mailing list archive at Nabble.com.

2 1

Clearing log files best way?
by David Schuster 09 Sep '08

09 Sep '08

As I have been playing around and reloading records deleting files etc... some of my Log files have gotten rather large. What is the best way to clear them without screwing things up? Thanks for your hints! You all are doing a great job and I hope to be able to "observe" on Friday! David Schuster -- View this message in context: http://www.nabble.com/Clearing-log-files-best-way--tp19392790p19392790.html Sent from the Koha - Dev mailing list archive at Nabble.com.

3 2

Position announcement - Koha application developer (US or Canada)
by Galen Charlton 08 Sep '08

08 Sep '08

[Apologies for cross-posting] LibLime has a full-time Perl application developer position that we're looking to fill immediately. The responsibilities will center on adding new features to the Koha ILS (http://www.koha.org/) but may include working on other open-source library projects such as the ‡biblios metadata editor (http://www.biblios.org/) Applicants should be based in the United States or Canada. REASONS YOU'LL LOVE WORKING AT LIBLIME 1. Our customers. Working at LibLime you'll have the opportunity to work directly with libraries who have a real vision for where they want their library technology to go, and the resources to take it there. 2. Flexible, distributed environment. We have a central management office, but most of our employees work from home offices. Hours are flexible; you can listen to your own music and work in your pajamas (if you want to!). 3. It's all Open Source. We're geeks about open source; every piece of code you create is licensed under the GPL. We tell our customers that means no vendor lock-in, but it applies to employees too -- your code follows you to your next job. 4. Competitive compensation and benefits package. Excellent group health plan, 401(k) retirement account with employer matching, and support for travel to professional development opportunities such as the Code4Lib conference. 5. Upward mobility. LibLime is a growing company with lots of opportunities to advance your career. QUALIFICATIONS 4+ years of application development experience in Perl including SQL and web services. Experience working with an existing codebase, including good refactoring skills. Experience on the command line in Unix/Linux environment. PREFERRED QUALIFICATIONS Domain knowledge in library workflow in one or more areas such as acquisitions, authority control, serials, cataloging, or circulation. Knowledge of library-speciﬁc standards/protocols such as MARC, MODS, Dublin Core, Z39.50, other Z39.* standards, NCIP, SIP2. JOB DESCRIPTION The complete job description and qualifications can be found at http://liblime.com/about/careers/software_engineer_koha HOW TO APPLY Send a resume and cover letter to careers(a)liblime.com. -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Indexing authorities
by Marcel de Rooy 08 Sep '08

08 Sep '08

Hi All, I have a small zebra [2.0.26] indexing question, while working with Koha (3.00.00.107). When reindexing authorities with rebuild_zebra, I noticed the warning Index 'any' not found in attset(s). Some research shows that the record.abs in marc_defs/marc21/authorities contains a line "all any". But the attsets bib1, gils and explain for authorities do not contain a line for 'any'. Please note that the bib1.att for biblios does contain a line "att 1016 Any". (The warning is not repeated for reindexing biblio.) Do you have the same warning? Could this warning simply be ignored? Should the "all any" line in the record.abs be removed for authorities or should the 1016 line be added to the record.abs for authorities? Any comments are welcome. Regards, Marcel de Rooy

1 0

Koha project meeting on #koha, 12 September 2008 at 19:00 UTC
by Galen Charlton 05 Sep '08

05 Sep '08

Hi, The Koha developers will be holding a meeting on the #koha IRC channel on Friday, 12 September 2008 at 19:00 UTC. The agenda is currently: 1. Confirm the release manager, translation manager, and documentation manager for Koha 3.2. Each of these positions has one candidate at present: Release Manager: Galen Charlton, LibLime Translation Manager: Chris Cormack, Catalyst Documentation Manager: Nicole Engard, LibLime, 2. Decide on the release maintainer for Koha 3.0 The two candidates are currently Joshua Ferraro (LibLime) and Henri-Damien Laurent (BibLibre). 3. Discuss options for filling the position of QA manager for 3.2. 4. Discuss the features planned for Koha 3.2. All Koha users, developers, and other interested parties are welcome to attend. The meeting will be logged, and I will also send a summary to the koha and koha-devel mailing lists. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 2

community structure (RMaint, translation manager, QA manager...)
by Paul POULAIN 05 Sep '08

05 Sep '08

Hi, Back from my august vacation, it seems that we have reach the 3.0 official release, and that's good to see. IMO, the next step is to organize the next months team we need a 3.2 Release Manager, and we have one candidate (galen, LibLime). we need a Release Maintainer, and we have 2 candidates (hdl, BibLibre & kados/joshua, LibLime) we need a Translation Manager, and we have 1 candidate (chris C., Catalyst) we need a QA manager and we had some thoughts about that on irc, although no decision afaik. we need a Doc manager, and we have one candidate (nicole, LibLime). Previously, we always have choosen the guys (sorry Nicole, you're the 1st woman in the game on this matter ;-) ) by IRC general applause (ie: no formal vote, but an evidency that the candidate is the best we will have). We always have had only 1 candidate, except once, for 3.0 RM, were we had joshua & Pierrick. (Seems we had choosen the good guy as Pierrick/Ineo disappeared some time after ;-) ) So : - What about having an IRC meeting to nominate officially all Koha positions ? and announce them everywhere. - What about 3.0RMaint ? hdl is still candidate & will devote some time on that specifically (with BibLibre growing, things should be better for him). Looking at recent head commits, some are bugfixes that should be cherry picked to 3.0 branch. The plan, if he is accepted as RMaint, is to release a version once every 3 months (except if there is a blocking bugfix : "immediate" release in this case) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08

7 10

Koha 3 Advanced Search
by zang＠zang.co.za 04 Sep '08

04 Sep '08

I have a very basic problem with my Koha 3 test installation. If I use the "Limit type to" selection, my search does not show anything. My Items are set as "Books, Booklets, Workbooks", but if I set the "Books, Booklets, Workbooks" checkbox, I get "No results found". If I unset the checkbox, it finds my search. Is this a known issue? Your help will be appreciated.

3 2

Re: [Koha-devel] To maintain a 'dev installation with rep 3.0.x
by Zeno Tajoli 03 Sep '08

03 Sep '08

Hi, At 14.54 03/09/2008, Galen Charlton wrote: >On Wed, Sep 3, 2008 at 3:36 AM, Zeno Tajoli <tajoli(a)cilea.it> wrote: > > get checkout my3.0.x > >You may want to do > >git checkout -b my3.0.x > >in order to create a new 3.0 working branch, unless my3.0.x exists already. in fact I have done an error on cut & paste. The instruction that I thin to use are: git fetch git branch --track kohaclone origin/3.0.x ['kohaclone' is the name of my local branch] get checkout kohaclone get pull I want only to update an existing branch. Thank you Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

To maintain a 'dev installation with rep 3.0.x
by Zeno Tajoli 03 Sep '08

03 Sep '08

Hi to all, I have little experience with git so I ask you a confirm of my thoughts. Date: Mon, 11 Aug 2008 16:05:53 -0500 From: "Galen Charlton" <galen.charlton(a)liblime.com> Subject: [Koha] Koha 3.0.x Git branch created >If you are running a dev-mode installation of Koha 3.0 and you *don't* >want your installation to start following the 3.1 developments, you >should fetch, create the tracking branch, and check out that branch >BEFORE rebasing and going through the database update. I have a dev-mode installation, last update 26-Jul-2008, so I don't have the exact 3.0 stable version. I want to have the last maintaining version, the branch called '3.0.x'. I think that I need to do those operation with git: git fetch git branch --track kohaclone origin/3.0.x ['kohaclone' is the name of my local branch] get checkout my3.0.x get pull With those operation I will have a dev installation with the last maintaining version ? Thank you for everything Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1