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

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

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

02 Aug '05

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

1 0

opac-user & opac-userdetail
by Paul POULAIN 02 Aug '05

02 Aug '05

Hi, in opac, there is opac-user & opac-userdetail perl scripts. They seem to be highly similar, except that opac-user has more informations it seems (current reserves & history, fines & debts) Note that opac-userdetail don't work in css templates, as opac-userdetails.tmpl is undefined. BUT : NPL uses opac-userdetail.pl & has a .tmpl so, should we drop opac-userdetail & use opac-user or did I miss something ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Patron controlled passwords
by Joshua Ferraro 02 Aug '05

02 Aug '05

Hi all, I just committed some code that Andres sent me: opac-passwd.pl opac-passwd.tmpl and one line to opac-user.tmpl This script allows a patron to change their password from the OPAC. The template needs to be translated into English and merged into HEAD. Cheers, -- 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

2 1

Business Readiness Rating
by Joshua Ferraro 02 Aug '05

02 Aug '05

Hi all, Check out: http://www.openbrr.org/ "Business Readiness Ratings (BRR) is being proposed as a new standard model for rating open source software. It is intended to enable the entire community (enterprise adopters and developers) to rate software in an open and standardized way." We'll have to see how widely this proposed standard is adopted, but in the meantime, there are some very good points made in the White Paper (http://www.openbrr.org/docs/BRR_whitepaper_2005RFC1.pdf) about the characteristics of a mature open source project. We're doing pretty well but there are areas where we could improve. Cheers, -- 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

1 0

thanks for your bug reports
by Paul POULAIN 02 Aug '05

02 Aug '05

Hi Tumer, I just want to thank you for your bug reports : very clear, and usually with the solution. Don't hesitate to continue "bugging" us ;-) I go back to solve 1009 ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0