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

Website / ID Group Meeting Reminder
by Joshua Ferraro 09 Aug '05

09 Aug '05

Just a reminder that our Website / ID meeting is tomorrow (Wed, Aug 10) at 20:00GGMT (time in your area: http://tinyurl.com/dbueu) I've put up a basic agenda on the wiki, please feel free to add or expand on your items: http://tinyurl.com/d7de3 Hope to see you tomorrow! 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

about leader management
by Paul POULAIN 08 Aug '05

08 Aug '05

Hi koha devs, I'm working on leader support atm. It works quite well now (on rel_2_2 cvs branch) I'm waiting for some feedbacks from joshua. I'm working on 2 plugins that will help the library to fill it. I work on UNIMARC as well as on MARC21 plugin. I have some questions to make them as powerful as possible : * the default values, when the biblio is created. I suggest : - n (new/creation) for byte 5 - a (printed material) for byte 6 - m (monography) for byte 7 all other bytes being empty. * when biblio is modified, is it interesting to set byte 5 to c (Corrected or Revised) automatically ? * any other suggestion or interesting idea ? (link to marc21 : http://www.loc.gov/marc/bibliographic/ecbdldrd.html) (note : the leader will be in MARC editor in a "virtual field", named 000@, field 000, subfield @, but it's handled as the leader in the MARC record, of course) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 1

Authorities reporting to one tag only?
by Tümer Garip 08 Aug '05

08 Aug '05

I am using koha2.2.2b on a windows machine. It took me while to figure out how to work the authority file with MARC21 and may be I am still not very clear. I want to use an Authors authority table to report to MARC 100 field OR Marc 700 field That is if I am filling the 100 field (that field being set to be filled by authority table) searching for an author from the authority table and getting it works. However I cannot do the same with 700 field. This I believe is because the authority-file checks for ‘tag_to_report’ which can only be set to one tag only. Is this to mean that for each tag I have to recreate an authority table which does not sound logical as I will be just duplicating all the same data? Am I missing something here? Or is this what is ment to be? Tumer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/53 - Release Date: 20/07/2005

2 1

Alert / letter system done
by Paul POULAIN 05 Aug '05

05 Aug '05

Hi, I think the Letter system is ready, as well as the Alert one (although it will have to be improved with some other alerts) I have successfully : - defined a letter for serials. - in Serials modules, - selected this letter for alert - been in OPAC, and put an alert on this subscription - been back in librarian interface, and recieved an issue for the subscription. Few seconds later, I got a mail in my mailbox, everything worked fine. what has to be done : 1- I need at least 1 "letter" in english, to include it in CVS, for inclusion during install stage. 2- Ideas to extend the Alert system. I think we could create alerts for Virtual shelves (= be warned when a virtual shelf is modified). Does anyone have an idea. This system should be working for any module (acquisition/cataloguing/members/circulation/authorities/...) (I also plan to modify mails sent on suggestions to use the letter system. Most of my libraries want to have their own letter ;-) ) Next week should be used to play with Zebra & 3.0 version and begin point 2-H circulation list. (Will use Letters system probably ;-) ) (+ ending a data migration) Have nice week-end koha fans. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

LOG and USERENV specific information
by Henri-Damien LAURENT 05 Aug '05

05 Aug '05

Adding Log Facility. Needs Two Update in database... On more table (action_logs) And One more syspref Activate_Log, with YesNo values. Maintainance has been sweeped of previous Log functions addbiblio.pl contains a sample of code using Log.pm Could be generalized to Authorities, acquisitions, members soon. Adding page to display log views. can be called by admin/viewlog.pl Works with C4/Log.pm uses action_logs table using C4::Log, you have access to : - logstatus, a simple Boolean Function which returns True if Activate_Log is set false if off. - logaction that takes : * usernumber returned by gettemplateanduser * modulename a string (acquisition, catalogue, asoasf) * actionname a developper defined string (add, modify, delete) * objectnumber, primary key of object modified * infos, if needed (not a DELETE action) should contain the informations stored) - displaylog takes a modulename and a list of filters (list of hashes with keys name and value) and returns a result list of hash-record and a count of records returned. the information returned by displaylog should be different whether you modify a book or an order. That's Why a modulename is needed. The userenv cookie is set in Auth.pm. To get the userenv information, you must FIRST gettemplateanduser, which verifies whether the user is granted access to the demanded page, and set informations with decoding the cookie. Then you can get : $ bornum, $ userid, $ cardnumber, $ firstname, $ surname, $ branchcode, $ userflags of the active user calling the C4::Context->userenv which returns a hash with number, id, cardnumber, firstname, surname, branch, and flags keys. Any further information can be provided if needed. Enjoy. -- Henri-Damien LAURENT

2 1

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