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

Bug Squash Meeting Summary
by Joshua Ferraro 01 Aug '05

01 Aug '05

Present: paul hdl thd owen kados We started with 60 bugs (paul had already fixed 5 before the meeting) and ended with 54 bugs. For the entire meeting see the IRC log at koha.org/irc. The following assignments were made: paul 975: serials : renewal of a subscription 790: opac search on 'the' gives internal server error 992: Suggestions doesn't check wether a biblio exists 943: pb accentuations LDAP <=> KOHA 958: Field "notes" becomes empty at receipt 1009: Not all items mapped to MARC 680: Intranet doesn't allow linking of subject headings 1008: Long MARC breaks KOHA 892: data in a closed order appear differently than data before c hdl: 1001: Issuing Rules Error 961: Error message, when deleting an authority kados: 670: "Waiting" status often inaccurate 933: Cancel process results in untemplated dialogue 849: Error when generating barcodes 185: Barcode not auto-calculated when autobarcode is on 836: $auto_install error 682: Move HTML out of addbiblio.pl (WILLNOTFIX) create "authority" in the components on the Koha Bug Tracker owen: 585: Using 'document.forms[0]' notation prevents use of other for 1005: mouse's click doesn't work in submit button 885: Non-ISO8859-1 charset support broken in CSS theme in 2.2 slef: 1002: Error in bulkmarcimport indicates possible permissions probl 984: Bug in installer appears to not correctly escape password chris: 426: Reserving a book (with a reserve fee) results in a hostile m 864: Subject search results not limited, show all results 995: Group Maintenace Looks like it should do something but it do 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

Acquisitions Group Meeting
by Joshua Ferraro 01 Aug '05

01 Aug '05

Hi all, I spoke with HDL today on IRC about Koha's Acquisitions. There are a few concerns: Short-term: 1. Koha's current Acquisitions modules appear to be broken (HDL can expand on this) 2. Koha's simple acquisitions is too simple (does not include budget management for instance) Long-term: 3. Koha should support standards for Acquisitions like EDI, WDDL, SOAP or Web Services. I propose that we discuss fixing Koha's current solutions for the 2.2.x series and also discuss the long-term solution that we hope will be in 3.0 if we can find a sponsor for the development. So who has a vested interest in Koha's Acquisitions asside from HDL and myself? What ideas do you have? When we get some responses we can decide on a meeting time and I'll put together an agenda. 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

3 2

about PROG templates
by Paul POULAIN 30 Jul '05

30 Jul '05

Hi owen & al, I saw your commits on HEAD about PROG templates. they are far from complete (or i missed something). Do you have a timesheet to complete them ? For instance, I still work on default, but once you say prog are ready, i'll swap to them as decided. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

MARC Holdings, Koha, and Migration
by Thomas D 28 Jul '05

28 Jul '05

Things that you were afraid to ask about for MARC holdings and why it mostly does not matter yet for Koha, with a MARC 21 holdings mapping supplement. UNIMARC and MARC 21 holdings are considered below in a rather tedious manner. A mapping of common standard MARC 21 subfields to a single local use field for linking to the Koha items table is presented in the last section for migration purposes. Please comment and offer corrections, etc., especially about the migration mapping. Even if you would ignore the tedium of the previous sections, please comment about the migration mapping if you have an interest in migration issues for Koha. I have not tested this mapping in an actual implementation and may even be mapping MARC 21 to orphaned columns in the items table. If the migration mapping may be useful, it should form part of a migration how-to document. STATEMENT OF REASSURANCE Let me state at the outset, that I am satisfied that the current limitation for linking the Koha items table to one and only one MARC field is not a problem restricting Koha from functioning in any important way for its current likely users. Development resources should be concentrated elsewhere. At some suitable point in the future, it would be appropriate to revisit this issue. I have brought this issue forward previously with a less complete understanding of how and why Koha holdings works the way that it does. CURRENT KOHA HOLDINGS MODEL Koha has adopted a holdings implementation modelled on the French Recommendation 995, http://www.adbdp.asso.fr/outils/infogestion/r995.htm . Using this model, holdings information for one record is retained in one and only one local use field. Using Koha with MARC 21, any single field may be adapted for that purpose. 952 is the Koha default implemented at NPL. UNIMARC HOLDINGS UNIMARC had omitted holdings support from the bibliographic format. Implementers used local use fields or some other means for holdings information. The French government supported recommendation 995 for public libraries. The IFLA recently approved a UNIMARC holdings format as a separate record from the linked bibliographic record, http://www.ifla.org/VI/8/projects/UNIMARC-HoldingsFormat04.pdf . Paul Poulain reports the UNIMARC holdings format as not yet adopted by any ILS that he knows. Related bibliographic control number 004 in UNIMARC holdings identifies the control number 001 for the corresponding UNIMARC bibliographic record on the same system. Other system control number 035 in UNIMARC holdings matches 035 in UNIMARC bibliographic on the same system for identifying the control number 001 for a bibliographic record obtained from another system. In accordance with the approval of the UNIMARC holdings format, two fields are being added to the UNMARC bibliographic format. Location and call number 852 is being added to UNIMARC bibliographic to match the corresponding 252 field in UNIMARC holdings. Electronic location and access 856 is being added to UNIMARC bibliographic to match the corresponding 252 field in UNIMARC holdings. Within UNIMARC holdings, copy number $t is the linking subfield for identifying the particular copy across multiple fields. UNIMARC SERIALS HOLDINGS The UNIMARC holdings format allows storing complex serials holdings information in a format that is easy for machines to parse, although, difficult for humans to read. Display presentation and complementary textual holdings fields allow for easy human readability of complex serials holdings. Complex serials holdings can be stored in the following fields. aptions and patterns fields 500-502 are optional. Enumeration and chronology - basic bibliographic unit 510 is mandatory if applicable. The other enumeration and chronology fields 511 and 512 are optional. The simpler textual holdings fields 520-521 are optional. 500-502, 510-512, and 520-521 are linked together by interfield linking data $6. Recommendation 995 only allows for simpler format textual holdings that are easy for humans to read but difficult for machines to parse. At some future time, when Koha needs to support more complex needs of academic libraries or other libraries with complex serials holdings, to provide for the configuration of OpenURL resolvers this issue should be addressed. MARC 21 HOLDINGS MARC 21 bibliographic has always provided multiple holdings fields. MARC 21 holdings format for storing holdings information in a separate record linked to the bibliographic record has become more popular in recent years. Despite the holding standard for MARC 21, some systems have implemented nonstandard local use holdings fields and subfields. Certainly, some information often not considered to apply well to standard holdings fields or not provided in the standard at all requires local use field or subfield implementation. Koha's use of a local use field for holdings is certainly not exceptional. At the beginning of the year, OCLC announced their plan to implement holdings in separate holdings format records by year's end. In the the MARC 21 bibliographic format, as in the MARC 21 holdings, format, copy number $t is the linking subfield for identifying the particular copy across multiple holdings fields. For those cases where a subset of the copy is required, materials specified $3 is the linking subfield for identifying the subset. Control number for related bibliographic record 004 in MARC 21 holdings identifies the control number 001 for the corresponding MARC 21 bibliographic record on the same system. System control number 035 in MARC 21 holdings matches 035 in MARC 21 bibliographic on the same system for identifying the control number 001 for a bibliographic record obtained from another system. MARC 21 SERIALS HOLDINGS MARC 21 holdings fields from both MARC 21 bibliographic records and MARC 21 holdings records allow storing complex serials holdings information in a format that is easy for machines to parse, although, difficult for humans to read. Display presentation and complementary textual holdings fields allow for easy human readability of complex serials holdings. Complex serials holdings can be stored in the following fields. Captions and patterns fields 853-855. Enumeration and chronology fields 863-865. The simpler textual holdings fields 866-868. 853-855, 863-865, 866-868, and item information fields 876-878 are linked together by field link and sequence number $8. If the enumeration and chronology fields 863-865 are not used, then location 852 or textual holdings fields 866-868 are linked to item information fields 876-878 by $3. The all holdings in one local use field model that Koha uses based on Recommendation 995 only allows for simpler format textual holdings that are easy for humans to read but difficult for machines to parse. At some future time, when Koha needs to support more complex needs, of academic libraries or other libraries with complex serials holdings, to provide for the configuration of OpenURL resolvers this issue should be addressed. DEVELOPMENT OF KOHA HOLDINGS MODEL An account of the development of the Koha holdings model can be found in the "Koha diary" along with much other useful history. Hedges, Stephen. A Koha diary : implementing Koha at the Nelsonville Public Library. kohadocs.org. 2005. http://www.kohadocs.org/koha_diary.html . The diary describes part of how the default Koha table linkings to MARC fields had originated. Poulain, Paul. Re--dumpmarc : date--Wednesday May 21, 2003, 10:02 AM ; to--shedges / from--paul.p. Stephen is quoted. "We've been discussing our item information. There is _so_ much valuable information in our old system about each item that we don't want to lose, but which doesn't fit into a MARC tag. Things such as date last seen (which is also in Koha items table) or date last borrowed (also in Koha). We're very tempted to just write a script to read the item information from our old system and load it directly into the Koha items table." Paul replied. "Why don't you add specific non-standard marc tags in the parameters table and map them to the corresponding koha fields ? Note that I agree to say that there are only a few 852 subfields code that are free in MARC21 (1,4,5,7,9,d,o,u,v,w,y if my table is right), but it may be enough." Local use field 952 had been used for holdings by the ILS that NPL had been using prior to migrating to Koha and was retained for the Koha to MARC items linkings and presented as a default for Koha. The substitution of a local use field avoids the risk of some possible future assignment of unassigned subfields for those items table columns that are not part of the MARC standard. MARC 21 TO KOHA HOLDINGS MAPPINGS 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. 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 items.copynumber. (If you have been using $3, you should find some way of combining $t with $3 to form a unique whole number.) 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 $r for items.replacementprice. 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 boolean. Map 876 $j, 877 $j, and 878 $j to 952 $1 for items.itemlost. Be sure to convert to an integer boolean. Map 876 $j, 877 $j, and 878 $j to 952 $w for items.withdrawn. Be sure to convert to an integer boolean. Map 852 $k, 852 $h, 852 $i, and 852 $m concatenated together sequentially to 952 $h for items.itemcall number. Map 506 $a, 876 $j, 877 $j, and 878 $j to 952 $4 for items.restricted. Be sure to convert to an integer boolean. Map 852 $c, 856 $u, 876 $l. 877 $l, and 878 $l to 952 $c for items.location. Migrating MARC 21 holdings to Koha would certainly be easier if Koha supported multiple fields for holdings. However, as stated above, that is an issue best left for a future time. Thomas D --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

1 0

Barcode
by Partha Mukhopadhyay 28 Jul '05

28 Jul '05

Hello friends, I'm running koha for the last one year and recently upgraded to 2.2.3. As it requires PDF::API2, I have installed the version 0.44 (the latest available version). But it is not working. Then I came to know the version dependency of barcode.pl of koha 2.2.3. It requires a bit older one 0.3r77. I downloaded the required one. But the question is how to uninstall the previous one i,e, 0.44 from site_perl. Is it necessary to uninstall 0.44 before installation of 0.3r77? P S Mukhopadhyay Lecturer, Deptt. of LIb. & Inf. Sc, Vidyasagar University, W.B., India -- India.com free e-mail - www.india.com. Check out our value-added Premium features, such as an extra 20MB for mail storage, POP3, e-mail forwarding, and ads-free mailboxes!

3 2

2.2 => new submenus
by Paul POULAIN 28 Jul '05

28 Jul '05

Hi, i've just commited some stuff to make Koha more user friendly. 2 things : * some css rules changes (in buttons for example) * a dynamic submenu for each menu (getting rid with submenu) To test you can : * update your cvs copy (done only for default templates in english) * http://bureau.paulpoulain.com:9019/cgi-bin/koha/acqui/acqui-home.pl (login test/test), or any other Koha page. Any suggestion welcomed -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

new "letter" system in HEAD
by Paul POULAIN 28 Jul '05

28 Jul '05

Hi developpers, I'm pleased to introduce the new "Letters" system : Letters will be used everytime you want to sent something to someone (through mail or paper). For example, sending a mail for overdues use letter that you can put as parameters. Sending a mail to a borrower when a suggestion is validated uses a letter too. the letter table contains 3 fields : * code => the code of the letter * name => the complete name of the letter * content => the complete text. It's a TEXT field type, so has no limits. My next goal now is to work on point 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. (see mail on koha-devel, 2005/04/07) The "serial issue alert" will be the 1st to use this letter system that probably needs some tweaking ;-) Once it will be stabilised default letters (in any languages) could be added during installer to help the library begin with this new feature. To test those features, 2 ways : * http://127.0.0.1:8080/cgi-bin/koha/admin/letter.pl (login test/test) * update your CVS copy, run updatedatabase and go to letter.pl Enjoy. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Website / ID Progress
by Joshua Ferraro 27 Jul '05

27 Jul '05

Hi all, Could all the folks contributing to the Website / Interface Design Group send progress report summarys to koha-devel so we know where we're at? Also, I'd like to hold another meeting within a couple of weeks to outline the next phase of our project, so if you've got suggestions for times send 'em my way. I'm thinking either Wednesday, August 3th at 20:00 GMT (http://tinyurl.com/7eq6d) or Wednesday August 10th at 20:00 GMT (http://tinyurl.com/dbueu) I'll put up an agenda on the wiki when I get your progress reports. 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

Bug Squash Mtg
by Joshua Ferraro 27 Jul '05

27 Jul '05

Hi all, Time to schedule another Bug Squashing meeting. How's Monday, August 1st at 15:00 GMT work for everyone? Here's the time in your area: http://tinyurl.com/7sfhv I count 64 bugs in 2.2 and HEAD: http://tinyurl.com/as66z We'll be working through the bugs, assigning the tough ones and fixing the easy ones. If you can attend, please do (even if you can only attend briefly). Let me know if you'd like the time changed. 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

To change koha password
by Rajam S 27 Jul '05

27 Jul '05

Sir, I have installed Koha in my institution. Can you please tell me how we can change the password of kohaadmin. Regards Rajam S -- Chinmaya Institute of Technology, Govindagiri, Chala, PO Thottada, Kannur 670007 Phone: (0497) 2822923, www.chintech.org

3 3