- Koha - lists.katipo.co.nz

Re: [Koha] Fixing Default Item Types - Conversion Question
by Chris Cormack 11 Oct '10

11 Oct '10

On 11 October 2010 12:02, Chris Hobbs <chobbs(a)nhusd.k12.ca.us> wrote: > On 10/10/10 2:54 PM, Chris Cormack wrote: > > 2010/10/9 Chris Hobbs <CHobbs(a)nhusd.k12.ca.us>: > > Is there a way for me to fix the Default item types for our biblios en > masse? Our biblioitems records have the correct item type from our > conversion, but every time we add a new item type it defaults to our '0' > type (Art Print). > > There are 2 places where itemtype is set, either at > biblioitems.itemype or items.itype > There is a systempreference which controls which one is used. > > I would recommend using the item level itemtypes. > > That is our setting, but I think I did a poor job of explaining our problem. > The real issue is that I didn't populate the 942c (or 942n) sub-fields when > I imported our MARC records, so those are unset. If somebody edits an > existing MARC record, 942c is defaulting to our itemtype 0, which is Art > Print, unless the cataloger is paying attention and edits 942c in addition > to whatever else she went in to edit. Later, when they go to add a new item > of that biblio, the item-level itype becomes Art Print unless they notice > and change it. > > Since we have no biblios with multiple item types associated with them (we > create a different biblio for each media type of a title), I'd like to set > the 942c sub-field based on an example item attached to that biblio. *If* > there were an itemtype in the biblio table, the pseudo-SQL might look > something like this: > > update biblio set itemtype=(select top 1 itype from items where > items.biblionumber=biblio.biblionumber) > Ah right, I getcha... ok, we the problem there is, you wont get it into the MARC, just into the biblioitems table (itemtype is in biblioitems not biblio), So while UPDATE biblioitems, items SET biblioitems.itemtype = items.itype WHERE biblioitems.biblioitemnumber = items.biblioitemnumber would mostly fix your problem, it sill wouldnt get the value into the marc. Heres some perl im typing free hand,so the chances of it actually working are fairly slim but it might put you on the right path #!/usr/bin/perl use strict; use warnings; use C4::Context; use C4::Biblio; my $dbh = C4::Context->dbh(); my $items_sth = $dbh->prepare("SELECT itype FROM items WHERE biblioitemnumber = ? LIMIT 1"); my $biblioitems_sth = $dbh->prepare("SELECT biblionumber,biblioitemnumber FROM biblioitems"); $biblioitems_sth->execute(); while (my $biblioitem = $biblioitems_sth->fetchfow_hashref()){ $items_sth->execute($biblioitem->{biblioitemnumber}; if (my $item = $items_sth->fetchrow_hashref())){ my $marc = GetMarcBiblio($biblioitem->{biblionumber}); my $field = MARC::Field->new('942,'','','c' => $item->{itype}); my @old_fields = $marc->field('942'); $marc->delete_field($_) foreach (@old_fields); $marc->append_fields($field); ModBiblio($marc, $biblioitems->{biblionumber}, ''); } } Back up your db, and it probably has at least 2 syntax errors in there, but the theory should work :) Chris

2 1

Bug found on purchase suggestion, koha 3.00.06.
by sinthya angel 09 Oct '10

09 Oct '10

hi , Im using koha 3.00.06. There is bug found on purchase suggestion. 1.First i logged as a opac user, then i send purchase suggestion to libray. 2. Then i logged as a admin on staff client, then set a library, then click "more › Acquisitions " , then i saw the "1 pending suggestion waiting" at there. 3. But when i click the "manage suggestion" link there is no suggestion was displayed in that page. Thanks in Advance. Regards Angel

3 2

email setup and documentation
by Msgr. Marion J. Makarewicz 08 Oct '10

08 Oct '10

I have been able to go through all the steps for a Koha 3.0 install on Ubuntu. Catalogue and circulation are all set up, imported from an existing Follett ILS. I am so impressed with this excellent software and a great user community. One remaining issue is getting the email notifications to work on my network. I can find minimal postings in the lists and no specific how to in the documentation as to setting up email. This is a school environment and I have an email server already running (Dovecot) handling all the local faculty and student email accounts. My Koha box is distinct. How do I get the email notifications to relay to the mail server? I've tried it with sendmail configured on the Koha machine. I can deliver to local users. I'm trying to understand MX entries, relays, and wondering if I have to set up a DNS server. I do have all the machines figured to static IP addresses and host names. Any pointers in the right direction? A recent thread seemed to be solved with Postfix, but not knowing the network configuration, I'm not sure what's next. One suggestion was nullmailer. Perhaps it's just that sendmail is so challenging in its setup. I have had experience with sendmail and that's why I've tried it first. In many respects this may be off topic, but considering that Koha is available as a turn-key solution, it seems that a little more clarity on what else is needed to configure to enable it to use full functionality, much like the documentation is clear on how to set up the MySQL database, and then you can forget about it. Thanks for all the help. Marion

1 0

how to up grade from 3.00 to 3.2 help me
by Yatheesh Y 08 Oct '10

08 Oct '10

hello we are planing to use 3.2 version at present I have 3.00 on ubantu o/s cd till now I did not have any data in that koha3.00. I would like to upgrade please send me if u have any step by step process thank you

1 0

Koha - migrating items' circulation history from current ILS
by Linda Culberson 07 Oct '10

07 Oct '10

Is there documentation and/or methodology of migrating the circulation history of items from our current ILS into Koha? I know there is a field for how many times an item has been checked out, and I know there is offline circulation, but what I'm unclear about whether it is the best method to use to migrate our current circulation history information into Koha. Thanks in advance. -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

3 3

Services for Peru
by Alfonso de la Guarda 07 Oct '10

07 Oct '10

Hello, My company needs a professional with experience in implementing Alfresco and Koha for a library in Peru. This candidate must have previously implemented similar solutions and train some people in such solutions. Our team is very good but we need to reduce self-learning time for implementation, and - most importantly, get suggestions or ideas to a successful performance. According to the qualifications we can offer from $ 5000 to U.S. $ 10000 for such advice, plus travel and stay (and if there is a remarkable work: a tour to Macchu Picchu!). Please send inquiries about this to: alfonsodg(a)ictec.biz Notice: We prefer a professional Spanish language skills, however, this is not mandatory Regards, -------------------------------- Alfonso de la Guarda Gerente de Investigación y Desarrollo ICTEC SAC http://www.ictec.biz Telef. 991935157 1024D/B23B24A4 5469 ED92 75A3 BBDB FD6B 58A5 54A1 851D B23B 24A4

1 0

3.2.0 release candidate available
by Galen Charlton 07 Oct '10

07 Oct '10

Hi, I have uploaded the release candidate for Koha 3.2.0. Changes since the beta include: * fixes to the upgrade of acquisitions data from 3.0 * various bugfixes, particularly to acquisitions, serials, and label creation * improvements to test case coverage * all required test cases now pass * adding back the ability to save and manage local system preferences * the rotating collections feature is now deferred to 3.4.x * security fixes * translations Pending confirmation of successful installations and upgrades, this will become the general release of 3.2.0. At this point, string changes, enhancements, and non-super-critical bugfixes will not be accepted for 3.2.0; only truly critical bugfixes, improvements to upgrade and installation processes and documentation, and translations will be pushed. The tarball can be retrieved from: http://download.koha-community.org/koha-3.02.00-rc.tar.gz Checksum and signature files for verifying the package can be retrieved from: http://download.koha-community.org/koha-3.02.00-rc.tar.gz.MD5 http://download.koha-community.org/koha-3.02.00-rc.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.00-rc.tar.gz.sig Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

3 3

Koha manual for 3.2 in pdf format?
by Linda Culberson 06 Oct '10

06 Oct '10

I know that the Koha manual for 3.2 is a work in progress, but what is the status of having the manual available in pdf format? My post earlier today about the no-longer used GranularPermissions setting is a good illustration of the pitfalls of working from outdated documentation :-[ Thanks! -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

1 0

Koha v. 3.2 GranularPermissions
by Linda Culberson 06 Oct '10

06 Oct '10

In the documentation for version 3.2 there is a GranularPermissions setting. I can't find where to set it in the Koha Administration System Preferences. Thanks in advance for your help. -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

2 2

Koha license upgrade ballot option summaries
by Thomas Dukleth 06 Oct '10

06 Oct '10

[The timeline of developing a ballot on the issue of upgrading the license has been significantly delayed by my accidentally breaking my primary computer; a severe bug in the program which I used to prepare an improved replacement computer; the time I generously offer to everyone I know; and allowing a cold to overtake me while I foolishly attempted to make up for lost time by not sleeping enough. Please accept my apologies all round. Providing some badly fatigued version of myself to the Koha community would not have served any good purpose. Any work I do should be from my best self to the extent possible and not merely what I can manage to provide on a particular day or week.] Upgrading the copyright license for Koha 3.4 is being considered for a ballot. Koha 3.4 is currently under development and will follow the forthcoming stable version. The question would not affect Koha 3.2, the immediately forthcoming stable version, nor any current or previous version. Koha has always used the GNU General Public License version 2 (GPL 2), invoked with the user's option of choosing a later version of the license from the Free Software Foundation (FSF), http://www.gnu.org/licenses/gpl-2.0.html . In 2007, the FSF finalised two options to which software licensed as GPL 2, invoked with an or later version option, may be upgraded. Those licenses are the GNU General Public License version 3 (GPL 3), http://www.gnu.org/licenses/gpl-3.0.html , and the Affero General Public License version 3 (AGPL 3), http://www.gnu.org/licenses/agpl-3.0.html . See the transcript linked from the meeting page in the wiki for the large number votes about how we should prepare and conduct the presently delayed ballot on the question of upgrading the software license, http://wiki.koha-community.org/wiki/License_Upgrade_Vote_IRC_Meeting,_13_Ju… . I need to take the time to summarise the votes to help put us back on track. gmcharlt "item: by two weeks from now, brief descriptions of the ballot options to be prepared; where brief = 150 words in English + link to koha-community.org wiki; descriptions to be written by a known proponent(s) of the option" Suggestions for summary text reasons for Koha license options follow. Brief summaries are much more difficult for me to compose than more complete summaries will be for the wiki. 1. RETAINING GPL 2, INVOKED WITH AN OR LATER VERSION OPTION: REASONS FOR KOHA 3.4. I do not recommend retaining GPL 2. There are some good reasons for retaining GPL 2 but I think that they outweighed by the benefits of upgrading to a newer version of the license. Advocates of GPL 2 will suggest their own text summarising the benefits of retaining GPL 2. 2. UPGRADING TO GPL 3, INVOKED WITH AN OR LATER VERSION OPTION: REASONS FOR KOHA 3.4. I do not recommend adopting GPL 3 over AGPL 3, however, I find both preferable to staying with GPL 2. The following barely fits the 150 word limit imposed on a summary. * A lengthy open, even if imperfect, comment period for multiple drafts before the license was finalised. * Substantially the same copyleft license as GPL 2 with protections for users over issues identified subsequent to the 1991 publication of GPL 2 and greater clarity of language. * Greater international legal compatibility for terminology and aspects of software copyright law. * Greater compatibility with other free software licenses would allow more code from other projects to enhance Koha. Compatibility includes GPL 2 code, invoked with an or later version option; code from newer projects using GPL 3; and greater compatibility with other non-GPL free software licenses. * Attribution rights for contributing authors even when not copyright holders. * Other protections including greater protection from aggressive use of patents, controlled by modifiers and conveyors of the software, covering some aspect of the software functionality. * Still upgradable. See wiki.koha-community.org/Some_Appropriate_Page for more detail. 3. UPGRADING TO AGPL 3, INVOKED WITH AN OR LATER VERSION OPTION: REASONS FOR KOHA 3.4. The following also barely fits the 150 word limit imposed on a summary. * AGPL 3 text is identical to GPL 3 except for the reciprocal section 13. Thus AGPL 3 has all the advantages included within GPL 3 with a vital addition. * Section 13 ensures that any user of the software remotely over the network, the typical case for Koha, has the right to download the complete source code for the particular modified version being used. Users avoid vendor lock-in over software. * Code from other AGPL 3 projects could be used to enhance Koha in addition to the compatibility provided by GPL 3. * Compliance mistakes are protected by the 30 day cure provision allowing first time violators to have their rights automatically restored. Advice from the Software Freedom Law Center suggests a means for a copyright holder to reinstate the first time protection to reassure a party believed to have innocently violated the license. See wiki.koha-community.org/Some_Appropriate_Page for more detail. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

1 0