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

Disambiguating the string "issue"
by lars＠rovaniemelainen.com 02 May '05

02 May '05

I notice in the interface that the term "issue" is used in at least three different contexts: 1) in circulation (i.e. to lend) 2) in journals as part of a host publication 3) in administrivia (i.e. a problem or question) Perhaps this is more suited as a bug report, but would it be possible to pick non-homonymic words for these three concepts? For example, could we say 'lend' or 'loan' for #1, and 'problem', 'question', 'incident', or similar for #3 For #2 the only alternative would be 'number', but that's not an option. -Lars ---------------------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/

2 1

Interesting idea
by Eyler, Patrick 29 Apr '05

29 Apr '05

The link below is about tieing cvs, bugzilla, and rss to help track bug squashing work more readily. Thought it might be of some interest. http://www.pragmaticautomation.com/cgi-bin/pragauto.cgi/Monitor/TrackingBug… -- thanks, -pate ------------------------- We are often unable to tell people what they need to know, because they want to know something else, and would therefore only misunderstand what we said - the Raven (George MacDonald, Lilith)

1 0

Koha 2.2.2 is available for download
by Paul POULAIN 28 Apr '05

28 Apr '05

Hello, The new version of Koha (2.2.2) is available at http://sourceforge.net/project/shownotes.php?release_id=318874 RELEASE NOTES ============= Koha is the 1st Open-Source Integrated Library System. Released at first in New zealand, in 2000 januaray, it is maintained by a team of volunteers from around the globe, the Koha system is a full catalogue, opac, circulation and acquisitions system. Koha 2.2 is more than 247 000 lines of code, developped by more than 30 differents developpers (excluding translators). With the 2.2 version, Koha is now a mature product, with a lot of nice features. It's used in more than 50 libraries, from all kinds (public, schools, search, religious...), of all size (from 1 to 8 branches, from 1000 to 300 000 items). ======== WARNINGS ======== * The librarian interface is tested only with mozilla/firefox. Should work (partially) with IE. OPAC should work fine with any navigator. ======= DIFFS ======= Diff 2.2.1 => 2.2.2 ******************* DB MODIFS : *********** (This new chapter in release notes will be in all new releases. It point any change in the DB. All changes are supposed to be handled by the DB updater, but here for your information) DB structure : none DB content : * new systempref MIME (OPENOFFICE.ORG or EXCEL) and delimiter (;). They are used by the Reports module, when exporting a report to a spreadsheet * new userflags *management* and *tools* to separate systempreferences in 3 differents permissions (see below) BUGFIXES ***** Critical & Minor mixed === ACQUISITION === * 3 bugfixes in suggestions : - major : a suggestion was not shown in acquisition except when ordered by the suggestor itself. - major : the mail to the suggestor was not sent. - minor : the name was not shown in accepted by column, in acquisition * virtual sheves in OPAC : - The user needed to have librarian rights to be able to go to the virtual shelf page. - Adding a book to an existing virtual shelf did not work * when a line was deleted, it was still counted in bookseller number of pending line order (in order.pl). * a non closed basket could be modified even if the supplier was set "inactive" === OPAC === * showing marcnotes in opac-detail (bug #920) === CATALOGUE === * some fixes in authority search (worked, but could fail to return results under certain circumstances) * libopac now works : in Koha >> parameters >> biblioframework >> modify field or subfield. If you set "opac text" to a different value than librarian text, you'll have different headers/text for MARC fields (for example : "1st responsability" for librarians, "author" for end users) * removed a limit to 255 char in field length in MARC editor (the DB can handle much more) * tabs in MARC editor : the active tab is now hilighted & in biblio modif, empty tabs are not shown (as in biblio add) * bugfixes in permissions (some pages required parameters where they should require editcatalogue) * the z3950daemon was buggy (forgotten to port a bugfix in 2.0 branch. It works again) === CIRCULATION === * renewal date was improperly calculated. Now, returndate is calculated from today, not from previous returndate * display waiting status only if item has arrived at pickup branch. Setting 'atdestination' variable if so. Changes are required in the template to take advantage of this. * in circulation, when clicking on member, the member page is opened twice (in main window & in a popup). The popup has been removed. === BORROWERS === * bugfixes in parameters (when modifying a borrower, with alternate address) * members flags (card lost, debarred, gone no address) are back in default template. === ALL === * some fixes for date & currency format IMPROVEMENTS ***** Major === STATS === * The stat module is here !!! In Reports menu, you now have 4 powerful "wizards" (for catalogue, borrowers, issues and acquisitions). You can define 3 things in a report : what you want in columns, what you want in lines, and filters you want on datas. For issues & acquisitions, you also can choose what you want in each cell (count or amount, or loan length). You can get those results in your borwser, or in your spreadsheet (MS-Excel & OpenOffice.org work fine). This module will continue to be improved to get the possibility to retrieve bulk datas in your spreadsheat. It works quite well, but has still some bugs and weaknesses. You also get some nice "top XXX" stats. === CATALOGUE === * catalogue, changed the small "search glass" behaviour. It now appears only on subfields that have a "link" value. Avoid useless glasses and removes nothing. **** WARNING **** : if you don't change you MARC parameters, glasses DISAPPEAR, because no subfields have a link value. So you MUST "reactivate" them manually. If you want to enable the search glass on field 225$a (collection in UNIMARC), just put 225a to "link" field (Koha >> parameters >> framework >> 225 field >> subfield >> modify $a >> enter 225a in link input field (without quotes or anything else) * showing item status in result list. The book status is in items.notforloan (every non 0 value meaning "book not for loan). The item status should be mapped to an item MARC subfield & this subfield should usually be connected to an authorised_value list. * in authorities search forms, adding a "main entry" field ($a), to limit the search. The "anywhere" field is still here. An option has been added to search "contains" or "start by". * item status (opac & librarian interfaces) The item status has been improved : It now can be : - on order (= item has been ordered, but not yet arrived at the library) - not for loan : if the "notforloan" field is mapped to an authorised value list, the right value is shown. Thus, an item can be "lost" or "being repaired", or whatever you put in the authorised values list. (reminder : the "notforloan" field, when 0 means 'ok, book can be issued', and all other values means 'nok, book can't be issued' (whatever the reason, that can be in the authorised value table) * in catalogue search, the user can now order asc or desc. * in catalogue search, the result list now show the itemtype in a column * in catalogue search, if there is only 1 answer, open it directly, don't show a list of results with just 1 line. * added an option to duplicate a biblio * in search before adding a biblio, the search uses the standard Koha API. It means the user don't have to write the title exactly as in biblio.title (empty words are now excluded) * changed behaviour for long fields : if a field contains more than 200 chars, the field will be edited as a textarea, not as a standard input. More conveinent. * in item MARC editor, the item list is hidden if empty. * in item MARC editor, the user can switch easily to the biblio again * UNIMARC plugin for 4xx fields. In UNIMARC, 4xx are related to links. This plugin works like the authority popup, but search in biblio instead of authorities. To set it up, you must : - define a 4xx$9 that will contain the biblio number of the linked biblio. In this 4xx$9 subfield, you must fill the "link to" with the field/subfield that is connected to biblio.biblionumber (090a by default). - define the subfield you want in the 4xx field. This plugins deals "classic link" method (one of the 2 UNIMARC possibilities for links) - choose one subfield and set unimarc_field_4xx.pl as plugin. === TOOLS === * added a tool in misc/merge_authority.pl to merge 2 authorities (and modify biblios using them) This script can also be used to update biblios that use an authority that has been modified. * added a tool in misc/migration_tools/check_marc_definition.pl that can be helpful when you migrate your datas. It compare the datas in the DB and the setting of MARC structure It show all fields/subfields that are in the MARC DB but NOT in any tab (= fields used but not visible) Usually, this means you made an error in your MARC editor. Sometimes, this is something normal. * Useful for translators only : modified tmpl_process to copy files that are not translated (like images, css... previously, they were not copied, it had to be done manually. Errors occurs because changes in english css or images were not reported to the translation directory giving a buggy translation) === ALL === * added a stylesheet for the printer (useful in acquisition basket printing. The doNotPrint style can be used anywhere to remove a part of the screen during printing) * new permissions : management & tools. You now have 2 new permissions : - management : means the user can manage library parameters, but NOT system parameters. - parameters : means the user can manage all parameters (including system parameters : marc structure, authorised values, system preferences. Was the only flag previously existing) - tools : means the user can import/export datas & edit barcodes. note that for compatibility reasons, a user having "parameters" can access everything. * new permission scheme. In every template new variables are available. They are written CAN_user_permission, with permission being one of the permission flag. templates can now show or hidde menu entries depending on user permissions. For example, a user with just circ permissions should have only the "circulation" button on home page. Templates are NOT updated in this version (except for system parameters, as proof of concept), they will be in the next ones. But the scheme is ready. **** Minor === OPAC === * added ISSN to simple biblio detail * added glasses to OPAC marc view, with same behaviour as in librarian interface. * overdues items are more visible on opac-user page * removed menu at bottom of basket page. They are badly shown in some browsers * in biblio basket, showing item info (location, callnumber and barcode) * if a search give only 1 result, the user reach it directly (without a 1 line list) === ACQUISITION === * acquisition, module, adding a button to delete a line in order (was possible by setting qty to 0, but it's more user-friendly) === CATALOGUE === * in authorities, added a "main entry" search field. Will limit the search to the main entry of the main field of the authority (the $a of the tag_to_report field) === BORROWERS === * Show the current borrower in librarian interface, normal view of a biblio (with a link to jump to borrower page) === CIRCULATION === * in circulation, adding a button to edit the borrower & go back to the circ screen directly. === TOOLS === * changes in overdue_notice.pl script : - moving all parameters at start of script => easier to maintain - sending overdues for borrowers without mail to a "koha admin mail". - ignoring borrowers with "overduenoticerequired" set to 0 (= don't send overduenotice) - removing "print" to have a silent script (ie can be put in crontab) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 4

Who knows who is webmaster of
by Paul POULAIN 26 Apr '05

26 Apr '05

http://www.technorati.com/tag/Koha ? same question for http://www.bigballofwax.co.nz/cgi-bin/blosxom/2005/04/24#kohatk I bet chris ;-) (because of WoW I know chris is found of) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Some explanations about release cycle (& 2.2.2b)
by Paul POULAIN 26 Apr '05

26 Apr '05

Hi all, (I write this message to clarify some things after an IRC chat shaun & joshua had yesterday) The release cycle that we have for the Koha project is : * cvs HEAD branch - it's the "commit all what you want, don't be afraid to break things" branch. So every developper can commit what he want, just writing cvs comments during commits. If you commit a great new feature, a mail on koha-devel is always welcomed ;-) - you can modify the DB structure in this branch. $KOHAROOT/updater/updatedatabase is the script where all DB changes should be done. - The CVS, when stabilised, will become the 2.4. Once the Release Manager thinks that the HEAD is stable enough, he will create a new rel_2_4 branch. Then, HEAD become "do what you want" again. the rel_2_4 branch becoming (or expecting becoming) a stable branch. - We don't have a Release Manager for 2.4 yet. We may have a candidate in the next 2-3 weeks, with a large team to add many many features to Koha. I can't officially say who it could be, just keep your fingers crossed. * cvs rel_2_2 branch This is the stable branch. I am the Release Maintainer for this branch, and here are my rules : 1- no changes in DB. I may bypass this rule, but I don't have yet, and don't have anything needing to bypass it. 2- no major feature change. I agree we could consider the change in authenfication that was in 2.2.2 as a major feature change. The bug that needed the 2.2.2b proves we should have ! I will try to be more strict with this rule in the future. 3- new features : any could be OK, if it does not need to bypass the 2 previous one. I prefer to be the only commiter to this branch, but I don't consider being the only owner of this branch. Just commit with extreme care in this branch. You also can commit in HEAD and drop me a mail to request backporting to rel_2_2, i'll do it if possible. Important note : there are a lot of things in rel_2_2 that are not in HEAD for instance. I'll synch ASAP, promised. ABOUT 2.2.2b : this version add NOTHING to 2.2.2 It just fixes the 2 critical bugs introduced by 2.2.1 new features. That's why release note have not been updated, the DL page has not changed. I've modified the 2.2.2 tarball and not CVS to be sure to fix just those 2 bugs. I'll commit ASAP the fixes in rel_2_2 and in HEAD, promised too ;-) HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha 2.2.2b is available
by Paul POULAIN 25 Apr '05

25 Apr '05

http://sourceforge.net/project/showfiles.php?group_id=16466&package_id=1361… Only 2 differences with 2.2.2 : * identified OPAC users can still use Koha ! * When dealing with serial issues, there are no more empty lines added in the issues list. This also fixes the problem with special issues that could not be typed. Don't hesitate to send any remark on this mailing list. PS : don't be surprised if this version still appears as 2.2.2 and not 2.2.2b. If you can log on OPAC and it still works, then it means you have got it ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

New document on kohadocs
by Stephen Hedges 24 Apr '05

24 Apr '05

New on http://www.kohadocs.org: Set Parameters and Migrate Your Data to Koha 2.2, English translation of Paul Poulain's Paramétrer et migrer, by Regula Sebastiao. Look in section "2.2 Migrating Data." -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

1 0

z39.50
by Ben Goodger 24 Apr '05

24 Apr '05

Hi, What is the status of z39.50 support in 2.2.2? I have been so far unable to get it to work and it is more or less vital for the application I intend to use Koha for. -- ~ Ben Goodger ~ Please remember to FLOSS daily. ~ www.getfirefox.com

3 3

Translation wiki for jargon?
by lars＠rovaniemelainen.com 21 Apr '05

21 Apr '05

It would be nice to have a glossary of jargon used in the Koha interfaces. Is there a translation wiki for help with a glossary of terms and jargon found in Koha? If not, I am willing to add as a starting point the list of terms and scope notes that I have come up with if someone can start a wikipage for it and send me the URL. -Lars ---------------------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/

3 3

-no subject-
by Jochen Geiser 19 Apr '05

19 Apr '05

Hi ! Could any body help me I installed the koha 2.2.1 succesfully, but when I open it on my Browser on linux 9.2 , the following message is coming:"Access forbidden you don't have permission to access the requested object. It is either read-protected or not readable by the server ! What could I do..? gReezes Jochen Geiser

1 0