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

Re: [Koha-devel] Keeping Up
by Thomas D 21 Jul '05

21 Jul '05

I do not always keep up. I have too many lists and not enough time to attend to them all. When I take the time, I can always review the archives and find what I should have known months earlier. I will supply some list of lists when I have a bit of time to compose one. Thomas D Quoting Joshua Ferraro <jmf(a)liblime.com> : > ---------------- Beginning of the original message ------------------ > > Hi all, > > How do you keep up with library, technology and Koha news? > What > online resources do you use? > > What Lists, Forums, RSS feeds, Blogs, Wikis, podcasts, etc. do > you use? > > 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 > > > ------------------------------------------------------- > 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

To german translator of Koha
by Paul POULAIN 21 Jul '05

21 Jul '05

Hi Friedrich, I see your commits on CVS, and have some comments/suggestions to do : * 1st you speak of "2.2.3", but are commiting on cvs-head. Didn't you make a mistake ? * 2nd, you commit individual templates, where you should just use the .po translator mechanism. I hope you don't edit the templates manually, because you will get mad to follow all the changes we do. look in misc/translator directory in CVS to find all what you need to translate Koha. I hope this makes sense. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Re: [Koha-devel] z39.50 client: extended services
by Thomas D 20 Jul '05

20 Jul '05

20 July 2005 Quoting MJ Ray <mjr(a)phonecoop.coop> : > ---------------- Beginning of the original message ------------------ > [snip] > > It seems rather fiddly to debug IMO. Basically, one watches > the z3950* > tables and the daemon's logfile and see what it's saying as a > query is > submitted. > > Even so, I still had one of my client libraries banned from a > z3950 > server following undetected problems and repeated requests > that were > more-or-less a denial of service attack. > Being banned from a Z39.50 server could be a very serious problem. I have often wondered about the risks entailed in establishing permanent connections to a Z39.50 server when the process might run unattended. One does not want the query to fail before it is finished fetching the records, however. A user settable timeout function as a fail safe might avoid some risks of an unattended process. One would want to close a Z39.50 connection that had run for too long a time or stop and restart the Z39.50 daemon if a connection had been open too long. [snip] Thomas D --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

1 0

z39.50 client: extended services
by RC Higgins 20 Jul '05

20 Jul '05

I'm interested in utilizing the Extended Services portion of the z39.50 protocol. I understand that some work is being done on koha's client. Are there any plans to implement ES for v3.0's z client? ES does not seem to be implemented in Net::z39.50 or in the zoom api. thanks, Ryan Higgins

3 2

Dewey bug (119)
by Stephen Hedges 19 Jul '05

19 Jul '05

Can anyone think of any reason to keep the biblioitems.dewey column as a DOUBLE(8,6) type? After installing 2.2.3, I still had problems with this bug, so I did: ALTER TABLE biblioitems MODIFY dewey VARCHAR(10) Everything seems to be working fine -- at least I have yet to find any problems created by this change. Is the dewey column ever part of any numeric functions? If we make this change to the biblioitems table, can we close this bug? -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

4 3

Installer for 2.3
by MJ Ray 19 Jul '05

19 Jul '05

For All Koha Hackers: * A new installer is in development. * The start is already in CVS. It doesn't work yet. * I've read old koha-devel posts and I've looked at other projects, so I think I see at least some of the pitfalls. * If you think I will break your code, please warn me now. * I aim to have this working well by the end of August. For Joshua: I've added myself to the 3.0 roadmap. Hope that's OK. For Installer Hackers: Following the installer meeting, I've taken a look at the ExtUtils::MakeMaker and ExtUtils::MakeMaker::Tutorial man pages, as well as some other articles and it looks like this is a reasonable way to go and it might work for koha. I think particularly interesting items on the main man page are: NAME, DISTNAME, VERSION (which are fairly obvious) PREREQS_PM (our dependencies) CONFIGURE (which might do the autodetection and Q&A if wanted) PM (what installs where) and PL_FILES (scripts that write files, perhaps autodetecting) I have started the ball rolling by adding Makefile.PL to the CVS HEAD. I have also removed some other files (Makefile Make.conf.in C4/Makefile.PL C4/MANIFEST) which seemed to be in the way. My next step is to use buildrelease and Install.pm to determine which files in the source tree belong where in the installed tree and write that into the Makefile.PL - at the moment, this will make the Makefile.PL very very big, mainly because of translated templates. I'd rather pack one set of templates and the po files, but which set? I'll do this this week, one way or another. Some other suggested/possible next steps are on a KohaInstaller roadmap at http://www.koha.org/wiki/?page=KohaInstaller - These are ideas and I don't have all the knowledge to decide whether they're possible: if you know more about one or have more ideas, please send comments to the list. If you can do one of the steps already mentioned, please do it and announce it on that page. Until the code is in CVS (or your patch is sent to this list), just hack the installer as you want. I ain't proud. Ultimately, this looks like it might remove buildrelease, installer.pl, Install.pm and possibly some other helper scripts. (What happens to koha.upgrade? An interesting question.) The payoff should be a simpler and more portable installer which is easier to package for every operating system distribution. -- MJ Ray (slef), K. Lynn, England, email see http://mjr.towers.org.uk/ http://www.ttllp.co.uk/koha/

3 3

Advance review on feature list for Koha 2.4/3.0 (hdl & paul coding planning)
by Henri-Damien LAURENT 18 Jul '05

18 Jul '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 This is on CVS version and works. Needs an update in database aqbookfund(additionnal field). > > 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 Still to be done > *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. > Already available on CVS... Needs some fixing though, and maybe some code improvements. But may be of great value. Every other proposed features are still to be done. -- Henri-Damien LAURENT

1 0

[Fwd: [koha-Infos] Documentation Koha]
by Henri-Damien LAURENT 18 Jul '05

18 Jul '05

Here comes along a french email relating a new document on Koha installation on Gentoo Distribution and gives a link onto a page which compares Koha to some Open-Source Softwares and gives it quite a good mark. Translation of the email follow : Hi, I am writing this little e-mail to announce the publication of a documentation on Koha (Install, Setup, and use under Linux Gentoo) on http://logiciels.bib.free.fr website (Koha page) This doc was written during my training period in LabSAD, a research lab at Pierre Mendes France University in Grenoble. My work there was to introduce Koha into the library. Documentation is primarily devoted to laboratory members but I had it published in case ot other could be interested. Hoping I didn't make too many mistakes. May the original sender forgive me if I did. :) Have a nice day.

1 0

Re: [Koha-devel] switching from marc_words to zebra [LONG]
by Thomas D 18 Jul '05

18 Jul '05

7 July 2005 Quoting Paul POULAIN <paul.poulain(a)free.fr> : > ---------------- Beginning of the original message ------------------ [snip] > >>It should really not be a pain to move to zebra with this > >>structure : > >>every call with a MARC::Record (NEWxxxxyyyy subs) manages > the > >>storing of > >>the MARC::Record in marc_* tables. We could replace this > code > >>with a > >>zebra insert/update, using biblio.biblionumber as primary > key. > >>How to manage biblios and items ? My idea here would be to > >>store biblio > >>+ all items informations in zebra, using a full > MARC::Record, > >>that > >>contains biblio and items. > > > > > > For MARC21, would you use the 852 holdings location and > other fields in MARC > > bibliographic? MARC21 has a MARC holdings format as a > separate record type > > from MARC bibliographic, > http://www.loc.gov/marc/holdings/echdhome.html . > > UNIMARC now also has a UNIMARC holdings format as a separate > record type, > > > http://www.ifla.org/VI/8/projects/UNIMARC-HoldingsFormat04.pdf > . I would > > certainly advocate moving towards full use of the available > formats but > > perhaps one should approach the question by degrees to > preserve development > > resources. > > In UNIMARC, there is also what we called "recommandation 995" > (http://www.adbdp.asso.fr/outils/infogestion/r995.htm, in > french). > I know no ILS using HoldingsFormat04.pdf description. All uses > "reco > 995", that simpler by far. > I have found a helpful summary of some French UNIMARC issues. Lahary, Dominique. UNIMARC as a cataloguing format in France : 64th IFLA General Conference. IFLA, 1998, http://www.ifla.org/IV/ifla64/111-161e.htm . Recommendation 995 is not an IFLA standard but as long as it is supported as a standard for French public libraries that is fine. My concern was adhering to a recognised standard. Preferably a simple one at first. Recommendation 995 does not seem to offer a means for machine parsing of holdings enumeration for serials. On that account and a few others, it has strong disadvantages for academic libraries. Machine parsing of serials holdings is very important for reducing the administrative burden of OpenURL link resolvers. I expect that the UNIMARC holdings format is too new to have many adopters yet. Although OCLC will be adopting the MARC21 holdings format this autumn, much of what is useful in the holdings format already has a place in MARC bibliographic. The Koha MARC21 framework is missing some of the most helpful fields for enumerating serials holdings in a machine parsable manner. This is correctable by the user and may be most significantly a problem for most easily administering OpenURL link resolvers. There are other omissions from the default framework such as the leader and the fixed fields that are much more significant but can also be corrected by the user and can be addressed by the model change for Zebra. > > Curiously MARC21 and its predecessors seem to have left this > out of the > > format. Only the thesaurus is given in the MARC21 record. > The method of > > matching a thesaurus control number is left to the system > implementation. > > That's exactly what we do in Koha, as we use the $9 (system > implementation ;-) ) > This lack makes hard to exchange biblio between libraries. > Why would you need to use $9 in UNIMARC when you have $3 in the UNIMARC specification? I have asked on other lists about how standard implementations address this authority control problem for MARC21 bibliographic and I am awaiting any answers. Unfortunately, my recent posts to the MARC list seems to have fallen into the moderator's black hole. There is a recent discussion on the MARC list with the usual negative answer about the recurring question of MARC in relational databases. A similar negative view has been expressed about XML really offering a way around the problem. There is a mention how existing systems represent MARC data from the ever well informed and insightful Karen Coyle. She gives a similar description to the one Joshua had given me about how this may be implemented. Coyle, Karen. Re: Marc in relational databases : MARC. (July 6, 2005). http://listserv.loc.gov/cgi-bin/wa?A2=ind0507&L=marc&T=0&F=&S=&P=957 . It would be fantastic if Karen could be persuaded to take an active interest in Koha. She is retired from the California Digital Library but I imagine she has plenty to keep herself busy. > -- > Paul POULAIN > Consultant indépendant en logiciels libres > responsable francophone de koha (SIGB libre > http://www.koha-fr.org) > > > ------------------------------------------------------- > 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_idt77&alloc_id?492&op¿ick > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel > > ------------------- End of the original message --------------------- Thomas D --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

2 1

another university in egypt using Koha
by hatem ibraheem 13 Jul '05

13 Jul '05

there is another university in egypt using Koha MSA university (Modern Sience and Arts university) http://www.msa.eun.eg/library.htm and u can see in opac koha system open always in the morning i am hatem ibraheem library exective in the university hope to add our university --------------------------------- Start your day with Yahoo! - make it your home page

1 0