- Koha - lists.katipo.co.nz

Koha Manual Updates
by Nicole Engard 27 Nov '10

27 Nov '10

Hello all, I have finally integrated the contents of the Wayne State U 3.0 manual, where relevant, into the 3.2 manual. You can see the updates in Git: http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary and soon on the web. Next up I'm going to integrate some docs sent to me directly, if you have comments or suggestions send them my - and as always feel free to send me any patches you may want me to push to the manual. Thanks Nicole C. Engard Documentation Manager

1 0

Re: [Koha] Editing a biblio record
by Paul 27 Nov '10

27 Nov '10

Jared - thanks, that fixed it (but there was no authority found, therefore no hyperlink to remove.) I guess that we are on the "learning curve", and the solution to this glitch was not obvious to newcomers. Somehow I have a feeling that we'll have more questions ;=} Best - Paul "Tired old SysAdmin" At 07:07 PM 11/26/2010 -0500, Jared Camins-Esakov wrote: >Marty and Paul, > >That seems a bit extreme. Very, even. I would suggest a better option >would be to click the three dots next to your erroneous 700s, search for >an authority (any authority... unfortunately you have to do a search >before you can clear a link) and then click the "clear" hyperlink to >remove the authority link. This will allow you to continue using >authorities and remove the unwanted 700 fields. The reason you're unable >to edit the 700$a is that you have BiblioAddsAuthorities set to "don't >allow," but even if you set it to "allow," you'll still be unable to >remove the data from subfield 700$9. See the manual for a little more >information about this system preference:Â >http://koha-community.org/documentation/3-2-manual/?ch=c19#AEN207 > >Regards, >Jared > >2010/11/26 Marty <ontariowolf64(a)yahoo.com> >I suspect authority issues, (is the field grayed out?) >You can edit all of your frameworks to "unlink" MARC fields to authority >types, or if have acces to the database, you could execute: > >UPDATE marc_subfield_structure SET authtypecode = NULL WHERE authtype IS >NOT NULL; > >A bit drastic but it will get rid of all links to authorities in the >frameworks. > >(With thanks to Bernardo Gonzalez Kriegel) > >--- On Fri, 11/26/10, Paul <paul.a(a)aandc.org> wrote: >> >>From: Paul <paul.a(a)aandc.org> >>Subject: [Koha] Editing a biblio record >>To: "koha" <koha(a)lists.katipo.co.nz> >>Received: Friday, November 26, 2010, 5:40 PM >> >> >>We are "experimenting" in preparation for importing some 16,000 *book* >>entries from Excel spreadsheets into Koha (Koha 3.00.06 on Ubuntu Server >>10.10) using MarcEdit. >> >>I have run into a snag editing a MARC biblio record using >><http://koha-admin/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=xxx>. >>We unfortunately got the "Title" of the Author (Sir Max Aitken) (100$c) >>into 700$a as a co-author. >> >>I can add|correct 100$c without difficulty, but cannot in any way delete or >>modify 700$a - I can highlight it with the mouse, but the keyboard is >>totally unresponsive. >> >>Any suggestions warmly welcomed - thanks. >>Paul >>-- >Jared Camins-Esakov >Freelance bibliographer, C & P Bibliography Services, LLC >(phone) +1 (917) 727-3445 >(e-mail) jcamins(a)cpbibliography.com >(web) http://www.cpbibliography.com/

1 0

overdue + circulation
by john smith 27 Nov '10

27 Nov '10

Hi i'm using version 3.2.1 i'm facing a problem in circulation page when patron has long overdue returun his books and he cann't checkout again couse this message Patron has had overdue items and is blocked for 32 day(s). and same problem when try to insert old check out with old date can't chech out couse this massege The due date "27/05/2009" is invalid .. any help that's important .. thanx John Smith International Library of Southiana IT Supports

2 1

need holp on " how to ldap configration on koha "
by tibabu beza 27 Nov '10

27 Nov '10

how to ldap configration on koha. i try to configra ldap on koha like below but it give me the following fantal error. how I can correct it <useldapserver>1</useldapserver>  <ldapserver id="idm"> <hostname>192.168.5.55</hostname> <base>dc=idmdomain,dc=edu</base> <user>cn=kohaadmin,ou=koha,dc=idmdomain,dc=edu</user>  <pass>adama</pass>  <replicate>1</replicate>  <update>1</update>  <auth_by_bind>1</auth_by_bind>  <principal_name>%s(a)my_domain.com</principal_name>  <mapping>  <firstname is="givenname" ></firstname> <surname is="sn" ></surname> <address is="postaladdress" ></address> <city is="l" >Athens, OH</city> <zipcode is="postalcode" ></zipcode> <branchcode is="branch" >MAIN</branchcode> <userid is="uid" ></userid> <password is="userpassword" ></password> <email is="mail" ></email> <categorycode is="employeetype" >PT</categorycode> <phone is="telephonenumber"></phone> </mapping> </ldapserver> Koha error The following fatal error has occurred: No "ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml at /usr/share/koha/lib/C4/Auth_with_ldap.pm line 53. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 44, <DATA> line 275. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 47, <DATA> line 275. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23, <DATA> line 275. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23, <DATA> line 275. Apache Server version: Apache/2.2.14 (Ubuntu) Server built: Apr 13 2010 19:28:27 Koha 3.00.06.010 Koha DB 3.0006010 MySQL mysql Ver 14.14 Distrib 5.1.41, for debian-linux-gnu (i486) using readline 6.1 OS Linux tibabu-desktop 2.6.32-22-generic-pae #33-Ubuntu SMP Wed Apr 28 14:57:29 UTC 2010 i686 Perl 5.010001

1 0

charge 0
by Jonson philip 27 Nov '10

27 Nov '10

hi in circulation.pl when patron has fines , charges column details of each book appears 0 , in total gives a right value . why ? if there any way to appear each fine of each book . thank's , i'm using version 3.2.1

1 0

session timeout
by Lori Bowen Ayre 27 Nov '10

27 Nov '10

Could someone explain how to set the session timeouts such that the staff stay logged in for the day without timing out but the OPAC times out after 15 minutes? Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant The Galecia Group // www.galecia.com (707) 763-6869 // Lori.Ayre(a)galecia.com <Lori.Ayre(a)galecia.com>Specializing in open source ILS solutions, RFID, filtering, and automated materials handling (AMH) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

3 4

Re: [Koha] Editing a biblio record
by Marty 27 Nov '10

27 Nov '10

Thanks Jared, Thanks, I didn't know that, but for me clicking the 3 dots and then searching only results in "no results found" if I keep the search term that's automatically entered in "Main entry" or a 500 error if I leave it blank... Probably something else wacky in my database... Marty --- On Fri, 11/26/10, Jared Camins-Esakov <jcamins(a)cpbibliography.com> wrote: From: Jared Camins-Esakov <jcamins(a)cpbibliography.com> Subject: Re: [Koha] Editing a biblio record To: "Marty" <ontariowolf64(a)yahoo.com> Cc: "koha" <koha(a)lists.katipo.co.nz>, "Paul" <paul.a(a)aandc.org> Received: Friday, November 26, 2010, 7:07 PM Marty and Paul, That seems a bit extreme. Very, even. I would suggest a better option would be to click the three dots next to your erroneous 700s, search for an authority (any authority... unfortunately you have to do a search before you can clear a link) and then click the "clear" hyperlink to remove the authority link. This will allow you to continue using authorities and remove the unwanted 700 fields. The reason you're unable to edit the 700$a is that you have BiblioAddsAuthorities set to "don't allow," but even if you set it to "allow," you'll still be unable to remove the data from subfield 700$9. See the manual for a little more information about this system preference: http://koha-community.org/documentation/3-2-manual/?ch=c19#AEN207 Regards,Jared 2010/11/26 Marty <ontariowolf64(a)yahoo.com> I suspect authority issues, (is the field grayed out?) You can edit all of your frameworks to "unlink" MARC fields to authority types, or if have acces to the database, you could execute: UPDATE marc_subfield_structure SET authtypecode = NULL WHERE authtype IS NOT NULL; A bit drastic but it will get rid of all links to authorities in the frameworks. (With thanks to Bernardo Gonzalez Kriegel) --- On Fri, 11/26/10, Paul <paul.a(a)aandc.org> wrote: From: Paul <paul.a(a)aandc.org> Subject: [Koha] Editing a biblio record To: "koha" <koha(a)lists.katipo.co.nz> Received: Friday, November 26, 2010, 5:40 PM We are "experimenting" in preparation for importing some 16,000 *book* entries from Excel spreadsheets into Koha (Koha 3.00.06 on Ubuntu Server 10.10) using MarcEdit. I have run into a snag editing a MARC biblio record using <http://koha-admin/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=xxx>. We unfortunately got the "Title" of the Author (Sir Max Aitken) (100$c) into 700$a as a co-author. I can add|correct 100$c without difficulty, but cannot in any way delete or modify 700$a - I can highlight it with the mouse, but the keyboard is totally unresponsive. Any suggestions warmly welcomed - thanks. Paul _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Jared Camins-EsakovFreelance bibliographer, C & P Bibliography Services, LLC(phone) +1 (917) 727-3445(e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 1

Editing a biblio record
by Paul 27 Nov '10

27 Nov '10

We are "experimenting" in preparation for importing some 16,000 *book* entries from Excel spreadsheets into Koha (Koha 3.00.06 on Ubuntu Server 10.10) using MarcEdit. I have run into a snag editing a MARC biblio record using <http://koha-admin/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=xxx>. We unfortunately got the "Title" of the Author (Sir Max Aitken) (100$c) into 700$a as a co-author. I can add|correct 100$c without difficulty, but cannot in any way delete or modify 700$a - I can highlight it with the mouse, but the keyboard is totally unresponsive. Any suggestions warmly welcomed - thanks. Paul

3 3

Cataloguing disappears after updatedatabase runs
by Marty 26 Nov '10

26 Nov '10

(Was: In koha-3.02.00 where is the cataloguing?) After installing koha 3.02.00.004 again, this time from scratch on my test box, everything works fine. However, after putting my backup database in, and it runs updatedatabase.pl it fails miserably (and that's also where my cataloguing page disappears, among other things) Backups are made with mysqldump, is there a way to restore my backup in the new version another way? Or any way where updatedatabase won't fail? I have tried other installs (3.02.005) but I keep having things disappear. See below for the errors. Thanks, Marty 1 updatedatabase.pl: DBD::mysql::db do failed: Table 'hold_fill_targets' already exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 1969. 2 updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'item_level_request' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 1988. 3 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AllowRenewalLimitOverride' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2035. 4updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'reserves-HOLD' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2049. 5 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry '4' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2053. 6 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry '4-sms-0' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2054. 7 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry '4-email-0' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2055. 8 updatedatabase.pl: DBD::mysql::db do failed: Duplicate key name 'issn' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2062. 9 updatedatabase.pl: DBD::mysql::db do failed: Table 'branch_transfer_limits' already exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2098. 10 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2117. 11 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2118. 12 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AllowHoldPolicyOverride' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2151. 13 updatedatabase.pl: DBD::mysql::db do failed: Table 'branch_item_rules' already exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2152. 14 updatedatabase.pl: DBD::mysql::db do failed: Table 'default_branch_item_rules' already exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2163. 15 updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'holdallowed' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2171. 16 updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'holdallowed' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2175. 17 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'OPACAmazonCoverImages' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2260. 18 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AmazonCoverImages' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2262. 19 updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'smsalertnumber' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2298. 20 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AmazonReviews' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2377. 21 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AllowNotForLoanOverride' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2395. 22 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'RenewalPeriodBase' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2412. 23 updatedatabase.pl: DBD::mysql::db do failed: Can't create table './koha/#sql-7d6_6f.frm' (errno: 150) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2421. 24 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'viewISBD' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2455. 25 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'viewLabeledMARC' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2456. 26 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'viewMARC' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2457. 27 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'AWSPrivateKey' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2501. 28 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2680. 29 updatedatabase.pl: DBD::mysql::db do failed: Table 'fieldmapping' already exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2695. 30 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2744. 31 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2745. 32 updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'finedays' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 2752. 33 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3070. 34 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3182. 35 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3298. 36 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3339. 37 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3385. 38 updatedatabase.pl: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''YesNo')' at line 2 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3449. 39 updatedatabase.pl: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''YesNo')' at line 2 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3453. 40 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3550. 41 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3552. 42 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'reserves-HOLDPLACED' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3561. 43 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3663. 44 updatedatabase.pl: DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`koha/permissions`, CONSTRAINT `permissions_ibfk_1` FOREIGN KEY (`module_bit`) REFERENCES `userflags` (`bit`) ON DELETE CASCADE ON UPDATE CASCADE) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3672. 45 updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'HomeOrHoldingBranchReturn' for key 1 at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3754.

1 1

bulk import of authorised values?
by Peter Huerter 26 Nov '10

26 Nov '10

Is there a way to do a bulk import of "authorized values"? I have not been able to find KOHA user interface support for this. If there is no user interface support for this, then can I *safely* add new authorised values to the SQL authorised_values table directly? I am wondering if I can do something like this: In MYSQL, to add a new "MILITARY" authorised value to LOC: 1. SELECT * from authorised_values; And determine the next 'id' available, call it <id> in what follows. 2. INSERT INTO authorised_values VALUES (<id>, 'LOC', 'military', 'MILITARY', NULL); Thanks, Pete. Context: Specifically, I'm interested in adding "LOC" authorized values. I've added two such values manually using the KOHA interface (Home › Administration › Authorized values). They are called "RARE", and "MILITARY". These values are making it into the following SQL table: (To dump all LOC authorised values I do this ..) mysql> select * from authorised_values where category = "LOC"; +----+----------+------------------+----------------------+----------+ | id | category | authorised_value | lib | imageurl | +----+----------+------------------+----------------------+----------+ | 12 | LOC | FIC | Fiction | NULL | | 13 | LOC | CHILD | Children's Area | NULL | | 14 | LOC | DISPLAY | On Display | NULL | | 15 | LOC | RARE | Rare book collection | | | 16 | LOC | STAFF | Staff Office | NULL | | 17 | LOC | GEN | General Stacks | NULL | | 18 | LOC | AV | Audio Visual | NULL | | 19 | LOC | REF | Reference | NULL | | 31 | LOC | military | Military | | +----+----------+------------------+----------------------+----------+ 9 rows in set (0.00 sec) (To dump the structure of authorised_value table I do this ..) mysql> show columns from authorised_values; +------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | category | varchar(10) | NO | MUL | | | | authorised_value | varchar(80) | NO | | | | | lib | varchar(80) | YES | | NULL | | | imageurl | varchar(200) | YES | | NULL | | +------------------+--------------+------+-----+---------+----------------+ 5 rows in set (0.00 sec) mysql> -- View this message in context: http://koha.1045719.n5.nabble.com/bulk-import-of-authorised-values-tp328151… Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 1