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

Got Git? We do!
by Joshua M. Ferraro 19 Aug '07

19 Aug '07

Hi folks, Well, it's official, we've moved the version control for Koha from CVS, hosted on Savannah, to a fully distributed system, running Git (http://git.or.cz/) Git is the same version control system used by the Linux Kernel and was originally developed by Linus himself. Koha 3.0 will be the first release of Koha to be managed using Git. There's never been a better time to get active in Koha development, submitting patches is now a cinch. Here's a basic overview of how the process works: http://wiki.koha.org/doku.php?id=en:development:git_usage If you'd like to track development changes, feel free to view our git-web: http://git.koha.org and take note of the available RSS feeds. Thanks to everyone who's helped us through this transition, most notably MJ Ray (who I believe was the first to recommend Git), and Chris Cormack for doing most of the heavy lifting. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Version numbering & updating
by Paul POULAIN 17 Aug '07

17 Aug '07

Hello world, with Koha 3.0 we will have a new web installer, that can take care of database updating. hdl has added a Version systempref, that contains the database version. for instance there is a <kohaversion> number in the koha.xml file. When a user authentify itself, Koha checks that kohaversion and Version are the same, otherwise, the user is automatically redirected to the web installer for database update. I think we can improve a little the behaviour (mainly for libLime & us : it will be an improvement only on a multi-koha setup). I would suggest to move the <kohaversion> in the code itself. Thus, when you install a new version, all your database will automatically go to update the 1st time the user logs in, on each virtual host / library. How can we handle database updates during development stages ? If I add a systempref, of a column, how to have LibLime and other devs handle that ? I suggest that version could be a long number, like in Perl : N.SSTTVVV : N is 3 (until it becomes 4 ;-) ) SS is the version number (00 for instance) TT is the 3rd level version number (00 for instance too) VVV is the developper subrelease number. An example, based on koha 2.2.9 (but I propose this method for Koha 3.0 only, of course) We are currently in Koha 2.0209001 I add a column to the table items, it's called mycolumn, it's a date. I will add to updatedatabase : if ($DBversion < 2.0209002) { $dbh->do("BEGIN TRANSACTION"); $dbh->do("ALTER TABLE `items` ADD `mycolumn` DATE NOT NULL"); $DBversion = 2.0209002; $dbh->do("UPDATE systempref set value=$DBversion where parameter='Version'"); $dbh->do("COMMIT"); } Once it is in the public code, every developper will automatically be redirected to the updatedatabase page, without having to take care of what I have commited ;-) What do you think of this idea ? -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

4 8

a new reserves system
by Joann Ransom 16 Aug '07

16 Aug '07

Hi Kyle, I wonder if it is worth considering which bits of the current reserves module are 'broken', as in not working as well as they could, and which 'bits'are new or enhancements. Are you looking at doing a whole rewrite / reengineering, or developing the existing reserves code? cheers Jo. *Joann Ransom* Deputy Head of Libraries. Horowhenua Library Trust.

3 3

systempreferences (partial) cleaning
by Paul POULAIN 16 Aug '07

16 Aug '07

Hello world, I have reviewed all the systemprefs, and the following ones seems now useless : - acquisitions - printcirculationslips - ReadingHistory - checkdigit : not used anymore. we can clean Input.pm sub checkdigit (unless chris & HLTers want to reintroduce it) - memberofinstitution : SANOP = this systempref seems unconsistent. Could you explain what it is done for ? - patronimages - opacheader -disable_dictionnary - the 2 ldap* ones I have changed nothing on git, just to let you know. I have updated the french version of the systempreferences (misc/sql-datas/fr/mandatory/), but not the english ones Reviewing them I see some systemprefs that are unknown to me : intranetuserjs, IntranetmainUserblock, item-level_itypes, kohaspsuggest, OpacMainUserBlock, opacuserjs, SpecifyDueDate (seems some of them are used, but would be nice to have all of the usefull ones in updatedatabase : LibLimers, the ball is your's ;-) ) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

2 2

Automation Survey
by Joshua M. Ferraro 15 Aug '07

15 Aug '07

Hi folks, Just thought I'd pass along this survey from Marshall Breeding, in case anyone in the Koha community would like to participate. See the forwarded message below. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ----- "Marshall Breeding" <marshall.breeding(a)vanderbilt.edu> wrote: > I am conducting a survey on library automation trends. The survey > aims to measure how well libraries are satisfied with their > automation systems and the companies or other organizations that > support them. It also attempts to get some indication of whether > libraries are looking favorably on open source software for their > automation system. > > The survey works through the lib-web-cats directory within the > Library Technology Guides web site. This approach eliminates the > need to retype any demographic information regarding your library. > You will just need to navigate to your library in lib-web-cats. > > Here are the instructions on how to complete the survey: > > http://www.librarytechnology.org/lwc-survey-2007.pl > > I am hoping to get a very large response to this survey. I will > publish the results of the study in an upcoming article, provided I > get enough responses to ensure its validity. > > Thanks in advance for taking the time to participate in the survey. > > Please contact me directly if you have any problems accessing or > completing the survey. > > -Marshall Breeding > > > ----------------------------------------------------------------- > Marshall Breeding > Director for Innovative Technologies and Research > Vanderbilt University Library > 615-343-6094 > > Editor, Library Technology Guides > http://www.librarytechnology.org > > _______________________________________________ > Web4lib mailing list > Web4lib(a)webjunction.org > http://lists.webjunction.org/web4lib/

1 0

New Feature planned : Automatically adding/linking authorities when creating biblios
by Henri-Damien LAURENT 14 Aug '07

14 Aug '07

Hi there, We are planning to add a new feature with a new System preference (BiblioAddsAuthorities). When set to One, in addbiblio.pl when saving a new biblio, or modifying one, For each used field linked to an authority, unless there is already a $3 or a $9, we search authorities for a similar one (same subfields). If found, we add a $9 to the first authority number (supposed to be stored in 001 field) (or maybe we should display all results to select the authority to link to ?) Else, we create a new authority of the type linked to current biblio field, so that heading contains all subfields of the current biblio field We add a $9 to that biblio field which points to authid. End End Comments and remarks welcome. -- Henri-Damien LAURENT

1 0

Re: [Koha-devel] Database structure, some cleaning
by Waylon Robertson 10 Aug '07

10 Aug '07

http://katipo.co.nz/gallery/koha2-4/search_ideas_1, right hand search column shows how these tables were to be used... and i did implement usage of these tables, showed Rachel a working version of this idea. Thought i committed it all.... guess not. Found the work though. as i recall, categorytable was a table of 'adult, child' and mediatype like 'cd, dvd, book, pamplet, newspaper', and subcategory like 'fiction, nonfiction, so on. My code included the search within option. should i recheck my work and commit? (to 2.9)? Waylon categorytable : ========== this table is filled by admin/itemtypecategory.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. mediatype : ========== This table is filled by admin/mediatype.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. subcategorytable : =========== this table is filled by admin/itemtypesubcategory.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. Send instant messages to your online friends http://au.messenger.yahoo.com

1 0

A New Reserves System
by Kyle Hall 09 Aug '07

09 Aug '07

Hey all, I've been talking with Kados and Chris about revamping the current Reserves system, which will in the future be known as the Holds system to distinguish it from Academic Reserves. I've set up a page on the Koha Wiki with a list of requirements my librarians have given me, and I would like to get suggestions and input from the rest of the Koha community before I begin this undertaking. The wiki page can be found at http://wiki.koha.org/doku.php?id=en:development:ideas_for_a_new_reserves_sy… Thanks, Kyle -- IT Tech Crawford County Federated Library System

1 0

Database structure, some cleaning
by Paul POULAIN 08 Aug '07

08 Aug '07

Hello world, I have reviewed the DB schema : ***** QUESTIONS ****** accountoffsets : ========= The accountoffsets table seems to be filled sometimes (C4/Circ.pm, line 1399 for example), but I see only some INSERT. It is SELECTEd or UPDATEd nowhere in the code On all my user database, this table is empty. So : can we remove the accountoffsets table & the code refering to it ??? aqorderdelivery : ========== the table is never filled by anyone, but used in acquisition_stats.pl under certain circumstances. I think acquisition_stats is buggy here, and we can remove the table categorytable : ========== this table is filled by admin/itemtypecategory.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. mediatype : ========== This table is filled by admin/mediatype.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. subcategorytable : =========== this table is filled by admin/itemtypesubcategory.pl script, commited by genjimoto on 2005-05-02, but we do nothing with this table. So I propose we remove the table and the script. ******* ALREADY DONE *********** just to let you know, but i'm 99.99% sure of what has to be done, so I did it already. aqorderbreakdown : ============= the branchcode, linenumber and allocation rows are never used. I've removed them from default structure. auth_subfield_table, marc_biblio, marc_blob_subfield, marc_subfield_table, : ============= useless in koha 3.0, will be important for libraries migrating from 22 to 3.0, but not for a fresh install. table removed from default structure. biblioanalysis, uploadedmarc, charges, itemsprice, sessionqueries, users, borexp, borrowers_to_borrowers, catalogueentry, marcrecorddone, websites, z3950queue, z3950results : ========= Tables not used in 3.0, removed from default structure. It can either be a koha 1.0 table that is useless, sometimes since years, or a test table. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

2 1

Fw: Community perl survey
by MJ Ray 06 Aug '07

06 Aug '07

-- forwarded text begins Take part in the 2007 Perl Survey! The Perl Survey is an attempt to capture a picture of the Perl community in all its diversity. No matter what sort of Perl programmer you are, we'd love to hear from you. The survey can be found at: http://perlsurvey.org It only takes about 5 minutes to complete. The survey will be open until September 30th, 2007. After that, we'll be reporting on the results and making the data freely available. Please feel free to forward this email to anyone other Perl programmers you know. Thanks for your help! Yours, Kirrily "Skud" Robert The Perl Survey info(a)perlsurvey.org

1 0