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

Receive procedure in Acquisition related question
by Henri-Damien LAURENT 05 Aug '05

05 Aug '05

Hi all, table aqorderdelivery seems never to be used in koha-head Acquisition.pm. So I am wondering if one CAN receive books he didnot expect from a supplier with our system or he should go to order, order the erived book and then recieve it, but that doesn't sound a clever way for me. But More, how partial deliveries are managed. For Instance : I ordered 4 books, only 1 was delivered. If system is given a delivery date, it is true I received sthg. But also false my order is not complete. And there should be more than 1 delivery date. I am building a getlateorders function. My main interest is to achieve goal 2-D of Paul's roadmap for 2.2.4 : lateorders management. If aqorderdelivery is never used, maybe we could drop this table in HEAD. Many THX. -- Henri-Damien LAURENT

1 0

feature list for Koha 2.4/3.0 (hdl & paul coding planning)
by Paul POULAIN 05 Aug '05

05 Aug '05

Hi, Here is a list of features that hdl & me will code soon (reminder for thos who didn't follow : hdl & me are working together) All of them will be in next major version, some of them being backported to 2.2.x (that will be specified in this mail. when it's written "backported soon", it means that the backport will be done asap, as it's requested by one of my customers. otherwise, will be backported when hdl/me has time & if requested by someone) *1- Improved multi-branch support* =============================== Some of my libraries have more than one branch for circulation, borrowers, AND for acquisition, cataloguing... In Koha 2.2.x, all librarian have access to everything in a module (if they have the correct login). Some libraries need to have "budget X is for the branch AA", and "budget Y is for the branch BB" or "item must be created/modified only by the library that own them". So we will add the following features : 1-A BUDGET (BOOKFUND) ---------- A new row will be added to the budget, called "branchcode". If branchcode is '', then everybody can acquire using this budget. If branchcode is 'XX', then only a librarian from branch 'XX' can acquire using this budget. This will change : - the parameter >> bookfunds admin screen (adding the list) - the acqui-home.pl script : showing only bookfunds the user can use when placing an order. - in newbiblio, the librarian can choose the bookfund from the limited list. needs only a new row in aqbookfund table. will be in head & backported soon in 2.2.x 1-B SEPARATE BRANCH -------------- in some multi-branch libraries (like in NPL) the branch is only for members/circulation. All acquisition & cataloguing is done in a unique branch. In other multi-branch library, each branch has it's own cataloguing, acquisition... team. So, we need a support for those libraries. I propose to have a new systempreference entry, called "IndependantBranches" (native english, feel free to suggest something better) When not set, the behaviour is as in 2.2.x When set, the behaviour becomes : * in acquisition module, only suggestions made by a user from the same branch as the librarian can be accepted/rejected. * in acquisition module, an order can be modified/recieved/closed only by a librarian from the same branch than the librarian that created the basket. * in catalogue module, an item can be modified/deleted/created only by a librarian from the same branch as item owner branch * in members module, a member can be created/modified only by a librarian from the branch of the member. don't need a change in DB, will be in head & backported soon in 2.2.x *2- OTHER IMPROVEMENTS* ========================== 2-C tracking who does what Koha will save which librarian creates/modify a biblio, and when (but not what he changed ? open question here, as saving what he changed can be very complex) Needs a new table in DB, will be in head only. 2-D late orders in acquisitions, create a new page to see, for a given bookseller the order lines that are still not recieved (+ nice printing of this "late recieve" list using doNotPrint css rule). The page will be like bull/lateissues.pl where you can select a bookseller & see the late serial issues he has. the list will show order info, including basket #, order date,...) No change in DB, will be in head, backported asap in 2.2.x 2-E serial note serials management : add a row to the serial table, for librarian notes (like "phone call to the bookseller on 06/25, should arrive in 10 days") needs a new row in DB. Will be in head, backported in 2.2.x 2-F bookseller history tracker A tool to follow revivals history (in acquisition & in serials module). When you claim a bookseller for a late book or serial, the claim will be stored in an history table. Will be in head, not completly analyzed yet, feel free to suggest how to do this & what to do exactly. 2-G mail contact Adding a "mail contact" in branches table. this mail will be shown in various places (in OPAC for example) and used on some periodic jobs. Needs a row in branches table. Will be in head, backported in 2.2.x 2-H "circulation list" in serials (subscription creation), the librarian will be able to select some users that will recieve the serial issue once after each other. this list will be printed by the librarian when recieving an issue. (then fasten the printed list to the issue, and make it circulate between users). The "reader list" can be ordered by the librarian. In OPAC, users can subscribe & unsubscribe to any "subscription circulation list". A systempref (CirculationList) will activate or un-activate this feature (the OPAC sub/unsub one). will be in head. 2-I "serial issue alert" With this feature, in serials, a user can subscribe the "issue alert". For every issue arrived/missing, a mail is sent to all subscribers of this list. The mail warns the user that the issue is arrive or missing. Will be in head. 2-J return date calculation For instance, the return date does not rely on the borrower expiration date. A systempref will be added in Koha, to modify return date calculation schema : * ReturnBeforeExpiry = yes => return date can't be after expiry date * ReturnBeforeExpiry = no => return date can be after expiry date will be in head & backported soon in 2.2.x -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

6 10

Translation
by Joshua Ferraro 04 Aug '05

04 Aug '05

Hi all, OK ... this one's for the Web Site group and the Documentation Group. In bug 953, MJ requests that we setup a better translator's page complete with links to the latest .po files. Here's an example: http://audacity.sourceforge.net/community/translation Paul then pointed me to his site which is running on Kartouche, a communal translation tool: http://bureau.paulpoulain.com/kartouche/ Given the fact that many translators aren't going to be very tech savvy, I think we should make Koha translation web-based. That is, we should have a site where translators can go, setup a login, assign themselves a translation project, run the .po to get the English, and insert their language in text fields hitting submit when they are done ... so paul, can Kartouche facilitate this? Is there another software app that can? -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

5 9

New feature on koha-fr.org website
by Paul POULAIN 04 Aug '05

04 Aug '05

Hi, I just added a few minuts ago a new category to www.koha-fr.org It is related to Koha OPAC stylesheets. You will find here stylesheets working in Koha OPAC. For instance, there are only 2 stylesheets, the default 2.2.3 and the "bibliotheque de sociologie" one. You now have 2 possibilities : * get an existing stylesheet from this website. * submit another one. You can do this just by sending the stylesheet at paul(a)koha-fr.org, i'll take care of uploading it (with credits) to www.koha-fr.org. You just must release the stylesheet under GPL as Koha itself. (/Don't forget to send me images if you have background url in your stylesheet/) Other koha websites : you can announce this new feature. Direct link to the "opac style" category : http://www.koha-fr.org/rubrique.php3?id_rubrique=19 PS : everything is in french AND english, for your convenience ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Website Homepage
by Joshua Ferraro 04 Aug '05

04 Aug '05

Hi all, I propose that we immediately replace the first paragraph on the Koha homepage. I've gotten several winks from library professionals that the current language makes Koha sound like a homebrew project rather than an enterprise-level ILS. Here's what I propose: Koha (Maori for "Gift") is the first open-source Integrated Library System (ILS). Developed initially in New Zealand by Katipo Communications Ltd. and first deployed in January of 2000, it is currently maintained by a team of software providers and library technology staff from around the globe. Koha offers a full-featured ILS including a catalog, OPAC, circulation, cataloging and administration components. etc ... How does that sound? -- Joshua Ferraro VENDOR SERVICES 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

3 3

sourceforge CVS down once again => moving to another CVS server ?
by Paul POULAIN 04 Aug '05

04 Aug '05

Hi, Sourceforge CVS is down once again today. I use savannah cvs for another project. it's really very very fast (no comparison possible with sf in fact !) Shouldn't we plan a move to savannah of our cvs ? (I don't know if we can move with all our cvs history, but probably) (note i don't want to speak once again of another version tool, as we have decided that CVS is not the best tool, but it's well known by everybody, so we stay with CVS) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 1

bug in module c4/circulation/circ2 sub renewals
by osilvestro＠cpcipc.org 03 Aug '05

03 Aug '05

We found an error in the procedure renewals. When to make renovations, it gave the error us "are not allowed but renovations", to correct the error the following change is due to make in/the C4/circulation/circ2.pl line 1602: my ($$env, $bornum, $itemno); original code my ($$env, undef, $bornum, $itemno); corrected code Omar F. Silvestro - Universidad Nacional de Cordoba

1 0

Structure of action_logs table
by Tarallo, Andres 03 Aug '05

03 Aug '05

I'm doing some work with C4::Logs. I've ported to this module a function for doing logs to a file that we've developed locally. I've noticed that if your koha system doesn't have an action_logs table logactions complains about it and does nothing. So I've added some code to create the table automagically and record to it. I need the "Official" structure of this table, since I created it with my best guess. I plan to contribute this back to the project. Andres

2 1

Re: [Koha-devel] MARC Holdings, Koha, and Migration
by Thomas D 03 Aug '05

03 Aug '05

MARC 21 TO KOHA HOLDINGS MAPPINGS draft 0.02 Corrected generally, and with reference to information about Koha tables that Chris Cormack and Paul Poulain gave me over IRC. Thank you Chris and Paul. Yes this is missing mapping for other tables that might be part of the migration process. Mapping to the Koha items table for MARC 21 holdings is the only issue treated here. Mapping existing standard data to a MARC 21 local use field is necessary when migrating holdings to Koha. If using the default local use field 952, the following may be a common mapping. Be sure to construct unique 952 fields populated from the corresponding $t, if present. Mappings with multiple subfields listed should have all listed subfields mapped to the corresponding local use 952 subfield where the last populated subfield value would overwrite any previous populated value for that local use 952 subfield. Map 852 $t, 876 $t, 877 $t, and 878 $t to 952 $t for a nonexistent items.copynumber column. (If you have been using $3, you should find some way of combining $t with $3 to form a unique whole number.) Do not link items.itemnumber to a MARC subfield, not even 952 $t in the MARC to Koha links to avoid possible loss of data. Koha will assign a unique itemnumber to your items with no help from your old records. If you need to maintain your existing copy numbers in a Koha table, create a new column in Koha for representing that information, such as items.copynumber, and program a solution. You could append copy numbers to an appropriate subfield accompanied by a text label 'copy ' within an existing value such as call number, given below, and suppress appending in cases where only one copy exists. Map 852 $p, 876 $p, 877 $p, and 878 $p to 952 $p for items.barcode. Map 541 $d; or 876 $d, 877 $d, and 878 $d to 952 $d for items.dateaccessioned. Map 850 $a, 852 $a, or 852 $b to 952 $b for items.homebranch. Be sure to convert to the 4 character all caps code as defined for Koha branches. Map 541 $h; or 876 $c, 877 $c, and 878 $c to 952 $o for items.price. Map 365 $b; or 876 $c, 877 $c, and 878 $c to 952 $u for items.replacementprice. Map 365 $f to 952 $r for items.replacementpricedate. Map 852 $b to 952 $d for items.holdingbranch. Be sure to convert to the 4 character all caps code as defined for Koha branches. Map 506 $a, 876 $h, 877 $h, and 878 $h to 952 $y for items.notforloan. Be sure to convert to an integer where NULL or 0 is for loan and 1 is for loan. Map 876 $j, 877 $j, and 878 $j to 952 $1 for items.itemlost. Be sure to convert to an integer where NULL or 0 is not lost, 1 is lost and paid for by the party responsible for losing the item, and 2 is lost with no payment yet. Map 876 $j, 877 $j, and 878 $j to 952 $w for items.withdrawn. Be sure to convert to an integer where NULL or 0 is not withdrawn and 1 is restricted. Map 852 $k, 852 $h, 852 $i, and 852 $m concatenated together sequentially to 952 $h for items.itemcallnumber. Map 506 $a, 876 $j, 877 $j, and 878 $j to 952 $4 for items.restricted. Be sure to convert to an integer value where NULL or 0 is not restricted and 1 is restricted. Map 852 $c, 856 $u, 876 $l. 877 $l, and 878 $l to 952 $c for items.location. Thomas D --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

1 0

Re: [Koha-devel] Website Homepage
by Thomas D 03 Aug '05

03 Aug '05

Sorry, I had failed to test my first suggestion until after posting. I wish I could have retracted it moments after it had been sent. My first paragraph would have needed to be divided into multiple paragraphs and even then would not have looked presentable or led the eye quickly enough to the elements appearing afterwords. There is too much empty space at the top of the page and the style sheet is not flexible enough for most of my first paragraph to have come close to working even if subdivided. I retract the mini feature list and other verbose elements of my original first paragraph suggestion. As I had written originally, there would be better way to convey this information in a new website design. Additionally, my non-breaking spaces were attached to the wrong end of adjacent words. Here is my suggested revised first paragraph. I do stand by my previous suggestions for everything prior to and after the first paragraph. <p> Developed initially in New Zealand by Horowhenua Library Trust and Katipo Communications Ltd. and first deployed in January 2000.  It is currently maintained and continuously developed by a team of software providers and library technology staff from around the globe.  Koha offers a full-featured ILS including integrated acquisitions, cataloguing, online public access catalogue (OPAC), circulation, and administration modules.  Control the power and freedom of Koha and open source software yourself at your library. </p> Thomas D Quoting Thomas D <koha(a)alinto.com> : > ---------------- Beginning of the original message ------------------ > > 1. PROBLEM > > What were the winks for exactly? The salient difference that > I see is , > aside from the derivation of koha, is that Joshua has > substituted "software > providers and library and technology staff" for "volunteers" > in the > original. Is 'volunteers' the concept at which the library > professionals > were winking? > > I would suggest that the colour scheme, graphics, and other > elements of > appearance are as likely to contribute to contribute to the > 'homebrew' > impression as the actual text. There is an aspect of the > graphics adjacent > to the Koha logo images that does seem a little out of place > for a > significant application intended to reliably run the most > vital operations > of a library. The way that the "download koha" balloon is > presented on the > home page is one example. The way the logo image at the > bottom with the > background colouration and hard outline edges appears > disjointed from the > page at the bottom of the home page is another example. I > would not expect > the graphical presentation to be adjusted until it is > presented as part of a > coherent new website design. > > People's expectation of web page appearance has been corrupted > by the glut > of poorly designed corporate websites and their imitators. > High bandwidth > consumption as an advertisement for shareholders at the > expense of > functionality and usability is a distinguishing characteristic > of far to may > corporate websites. Thankfully, that problem does not plague > any Koha > related website. > > I have noticed a form of possible redundancy in the original. > Although, > perhaps it is clarifying redundancy. When is an OPAC not a > catalogue? > > > 2. REVISED TEXT > > I would suggest the following amendment of of your proposed > text with the > consideration that Chris had suggested for HLT. My suggestion > tries to > provide a minor feature summary and compelling motivation for > adopting Koha. > The importance of development options in addition to > installation and > support is emphasised. > > There would certainly be better ways to convey this > information in a new > website design. This is my brief attempt at the current one. > > 2.1. BODY > > <h1><span class="heading">Koha </span> (Maori for 'Gift') is > the first > open-source Integrated Library System (ILS).</h1> > > <p> > Developed initially in New Zealand by Horowhenua Library Trust > and Katipo > Communications Ltd. and first deployed in January 2000. >  It is > currently maintained and continuously developed by a team of > software > providers and library technology staff from around the globe. >  Koha > offers a full-featured ILS including integrated acquisitions, > cataloguing, > online public access catalogue (OPAC), circulation, and > administration > modules.  Koha is multilingual and uses MARC 21, UNIMARC, > or non-MARC > records.  It contains integrated Z39.50 client and server > services. >  It supports the latest advances in patron accessiblity > and self > checkout circulation.  It is fully customisable from > template options > down to every line of open source code.  New features are > being added > constantly.  Control the power and freedom of Koha and > open source > software yourself at your library.  Do not be dependent > on one vendor. >  Available for free download and free use at your > library.  Many > installation, support, and feature development options are > available from > providers locally and internationally. > </p> > > <h1>that's right ... it's free</h1> > > <p> > Koha is released under the <a > href="http://www.gnu.org/copyleft/gpl.html">GNU General Public > License</a> > and is available to <a href="/download/">download</a>. > </p> > <p> > If you would like a quote for <a > href="/installation/support.html">installation and support, or > additional > feature development</a>; there are providers available > throughout the world. > </p> > > > While there are modest overlaps at the end of my suggested > first paragraph > with the preexisting second paragraph, the emphasis is > different. I do not > believe that it is redundant. > > Check the existing tags. The current paragraph tags do not > have valid > opening and closing tags which is not a significant problem > for browsers. > My valid tags may not provide properly rendered spacing. > > I would also suggest removing the possible implication that > Koha may be > difficult to install from the final paragraph. It might be > depending on the > installer and the system but the installation script works > quite well aside > from some minor glitches and the installation process is well > documented. > > <p> > We've put up a <a href="http://www.cafepress.com/koha/">Koha > store</a>, so > that even if your library is not ready for Koha yet, you can > still wear it > proudly. > </p> > > > 2.2. SPELLING AND USAGE CONVENTIONS > > Whether international (British) English or American English > spelling and > usage is used, I have no definite preference. The IFLA uses > and > international English as do many international bodies > including the UN in > New York. I presume that people at Katipo and Horowhenua > Library Trust use > New Zealand English spelling and usage. > > My own preference, as a US national, in my own use is for > international > English where that seems generally appropriate and American > English where > that seems appropriate following Fowler's example. Sidewalk > is a more > sensible contemporary term than pavement when most roads in > well developed > countries have been paved. American English spelling and > usage dominates > widely exchanged computer applications and the internet. I > use program for > computer applications but programme for events. I also follow > the sensible > practise of using spelling that is the same in a maximum > number of dialects, > when appropriate. I use dramatic arts instead of theatre or > theater, when > appropriate. > > American English spelling and usage have increasingly tended > to dominate > library science. The initiative and greater financial > resources of the > Library of Congress have brought the world's largest library, > MARC, and > Library of Congress Subject Headings (LCSH). DDC, like > Library of Congress > Classification, is also US based. Many other examples could > be given of > American English dominance in library science. UDC uses > international > English but is less detailed and less well updated than DDC. > Other English > language subject thesauri competing with LCSH and based on > more carefully > considered designs have fallen out of use and been replaced by > LCSH; because > of the high cost of maintaining competing thesauri and > disadvantage from the > greater difficulty of international cooperative record > exchange and use with > multiple thesauri. While international English spellings are > included in > LCSH authority records as references, the American English > form is the > authorised form. American English has become the dominant > English dialect > for the exchange and interoperation of library records in > English and the > point to which major non-English systems have been paired. > > > 2.3. HEADER > > Whatever spelling and dialect choice is taken alternate > spelling and > language forms for important terms should be include at least > in the > keywords meta tag. > > <meta name="keywords" content="Koha, ILS, acquisitions, > cataloging, > cataloguing, online public access catalog, on-line public > access catalog, > online public access catalogue, on-line public access > catalogue, > circulation, administration, MARC 21, UNIMARC, Z39.50, open > source, GNU, > customisable, customizable, templates"> > > I will leave it for others to suggest what would be > appropriate keywords for > other languages than for me to use mistaken forms outside my > native language. > > > Thomas D > > Quoting Joshua Ferraro <jmf(a)liblime.com> : > > ---------------- Beginning of the original message > ------------------ > > > > Hi all, > > > > I propose that we immediately replace the first paragraph on > > the > > Koha homepage. I've gotten several winks from library > > professionals > > that the current language makes Koha sound like a homebrew > > project > > rather than an enterprise-level ILS. > > > > Here's what I propose: > > > > Koha (Maori for "Gift") is the first open-source Integrated > > Library > > System (ILS). Developed initially in New Zealand by Katipo > > Communications > > Ltd. and first deployed in January of 2000, it is currently > > maintained > > by a team of software providers and library technology staff > > from around > > the globe. Koha offers a full-featured ILS including a > > catalog, OPAC, > > circulation, cataloging and administration components. > > > > etc ... > > > > How does that sound? > > > > -- > > Joshua Ferraro VENDOR SERVICES 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 > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward > > articles, > > informative Webcasts and more! Get everything you need to > get > > up to > > speed, fast. > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/koha-devel > > > > ------------------- End of the original message > --------------------- > > > > > --------------------------------------------- > Protect your mails from viruses thanks to Alinto Premium > services > http://www.alinto.com > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > from IBM. Find simple to follow Roadmaps, straightforward > articles, > informative Webcasts and more! Get everything you need to get > up to > speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel > > ------------------- End of the original message --------------------- --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

1 0