Re: [Koha] Upgrede probleme

2015-09-21 Thread Indranil Das Gupta
Hi,

which version are you trying to upgrade from and to which version?

regards
-idg

On Mon, Sep 21, 2015 at 12:11 PM, Vikas Salunkhe  wrote:
> Dear all,
> i dump my old data in mysql  then  i try to login koha following error is
> comming
>
> 1) DBIx::Class::Storage::DBI::_dbh_execute(): Table
> 'koha_library.discharges' doesn't exist at
> /usr/share/koha/lib/Koha/Borrower/Discharge.pm line 32
>
> For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
>
> and i try to rebuild data to command  sudo koha-rebuild-zebra -v -f library
> following erro is comming
>
> 2) error retrieving biblio 446 at /usr/share/koha/bin/migration_tools/
> rebuild_zebra.pl line 679.
> .DBD::mysql::st execute failed: Unknown column 'marcxml' in 'field list' at
> /usr/share/koha/lib/C4/Biblio.pm line 1266.
> DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at
> /usr/share/koha/lib/C4/Biblio.pm line 1267.
> DBD::mysql::st execute failed: Unknown column 'frameworkcode' in 'field
> list' at /usr/share/koha/lib/C4/Biblio.pm line 2167.
> DBD::mysql::st fetchrow failed: fetch() without execute() at
> /usr/share/koha/lib/C4/Biblio.pm line 2168.
> error retrieving biblio 447 at /usr/share/koha/bin/migration_tools/
> rebuild_zebra.pl line 679.
> .DBD::mysql::st execute failed: Unknown column 'marcxml' in 'field list' at
> /usr/share/koha/lib/C4/Biblio.pm line 1266
> ..
> ..
> ...
>
>
> error retrieving biblio 639 at /usr/share/koha/bin/migration_tools/
> rebuild_zebra.pl line 679.
>
> Records exported: 0
> DBD::mysql::st execute failed: Table 'koha_library.zebraqueue' doesn't
> exist at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 414.
> 
> REINDEXING zebra
> 
> 
> CLEANING
> 
> Zebra configuration information
> 
> Zebra biblio directory  = /var/lib/koha/library/biblios
> Zebra authorities directory = /var/lib/koha/library/authorities
> Koha directory  = /usr/share/koha/intranet/cgi-bin
> Lockfile= /var/lock/koha/library/rebuild/rebuild..LCK
> BIBLIONUMBER in : 090$c
> BIBLIOITEMNUMBER in : 090$d
> 
> 
> exporting authority
> 
>
> Records exported: 0
> DBD::mysql::st execute failed: Table 'koha_library.zebraqueue' doesn't
> exist at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 414.
> 
> REINDEXING zebra
> 
> skipping biblios
> 
> CLEANING
> ===
>
>
> I humbaly request  please guide to me  solve the probleme.
>
>
> with regards
>
> vikas Salunkhe
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha



-- 
Indranil Das Gupta

Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC  : indradg on irc://irc.freenode.net
Twitter : indradg

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-
Please exchange editable Office documents only in ODF Format. No other
format is acceptable. Support Open Standards.

For a free editor supporting ODF, please visit LibreOffice -
http://www.documentfoundation.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Upgrede probleme

2015-09-21 Thread Vikas Salunkhe
Dear all,
i dump my old data in mysql  then  i try to login koha following error is
comming

1) DBIx::Class::Storage::DBI::_dbh_execute(): Table
'koha_library.discharges' doesn't exist at
/usr/share/koha/lib/Koha/Borrower/Discharge.pm line 32

For help, please send mail to the webmaster ([no address given]), giving
this error message and the time and date of the error.

and i try to rebuild data to command  sudo koha-rebuild-zebra -v -f library
following erro is comming

2) error retrieving biblio 446 at /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl line 679.
.DBD::mysql::st execute failed: Unknown column 'marcxml' in 'field list' at
/usr/share/koha/lib/C4/Biblio.pm line 1266.
DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at
/usr/share/koha/lib/C4/Biblio.pm line 1267.
DBD::mysql::st execute failed: Unknown column 'frameworkcode' in 'field
list' at /usr/share/koha/lib/C4/Biblio.pm line 2167.
DBD::mysql::st fetchrow failed: fetch() without execute() at
/usr/share/koha/lib/C4/Biblio.pm line 2168.
error retrieving biblio 447 at /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl line 679.
.DBD::mysql::st execute failed: Unknown column 'marcxml' in 'field list' at
/usr/share/koha/lib/C4/Biblio.pm line 1266
..
..
...


error retrieving biblio 639 at /usr/share/koha/bin/migration_tools/
rebuild_zebra.pl line 679.

Records exported: 0
DBD::mysql::st execute failed: Table 'koha_library.zebraqueue' doesn't
exist at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 414.

REINDEXING zebra


CLEANING

Zebra configuration information

Zebra biblio directory  = /var/lib/koha/library/biblios
Zebra authorities directory = /var/lib/koha/library/authorities
Koha directory  = /usr/share/koha/intranet/cgi-bin
Lockfile= /var/lock/koha/library/rebuild/rebuild..LCK
BIBLIONUMBER in : 090$c
BIBLIOITEMNUMBER in : 090$d


exporting authority


Records exported: 0
DBD::mysql::st execute failed: Table 'koha_library.zebraqueue' doesn't
exist at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 414.

REINDEXING zebra

skipping biblios

CLEANING
===


I humbaly request  please guide to me  solve the probleme.


with regards

vikas Salunkhe
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] System generated field 001 control number

2015-09-21 Thread David Cook
Sorry for the delay. Pulled in a few different directions at the moment.

 

Thanks for the clarification Pablo. I haven’t looked at that record yet (just 
about to leave for the day), but I imagine the number was from OCLC or some 
other system. 

 

I think Katrin has responded more recently mentioning that cataloguing plugins 
might be helpful. I suspect that she’s correct.

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St, Ultimo, NSW 2007

 

From: Pablo Bianchi [mailto:pablo.bian...@gmail.com] 
Sent: Tuesday, 15 September 2015 11:45 PM
To: David Cook 
Cc: Koha-org - List 
Subject: Re: [Koha] System generated field 001 control number

 

Hi David,

​​On Mon, Sep 14, 2015 at 10:37 PM, David Cook  > wrote:


While I agree that the 001 should be populated with a unique bibliographic 
control number, it's not the way that Koha is typically set up.

 

Yet for example on Koha demo of Catalyst IT Ltd. (New Zealand) we can find this 
record 

  with biblionumber=999$c=999$d==20895 but control number 001==30908. Maybe 
they take 30908 from OCLC, but that is not what we are looking for, we want 
just an incremental system generated number like barcode.pl  
 plugin builder does for items, but for biblios, with no relation with Koha 
biblionumber.

In theory, it's configurable, but there are parts of Koha that expect the 
biblionumber to be in the 999$c field (e.g. MARC21slim2OPACResult.xsl).

 

I know 999 is used internally by Koha, so I don't wish to touch nothing about 
biblionumber/999$c/999$d.

 

Cheers,

Pablo

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Disable displaying items from other locations (independent branches)

2015-09-21 Thread Mirko Tietgen
Hi Gregor,

Le-grex schrieb am 20.09.2015

> "Staff Client Catalog Search: By default, items from other
> locations are displayed catalog searches."
> 
> But i don't get how to change this default behaviour?

I don't think there is an equivalent to the OPAC limitation options
in the staff client. You can manually limit searches to a single
branch in advanced search, I assume that is meant here.

If you do not want the libraries to be connected at all, multiple
Koha instances may be a better choice than independent branches.
Have you looked into that?

HTH,

Mirko


--

Mirko Tietgen
mi...@abunchofthings.net
http://koha.abunchofthings.net
http://meinkoha.de



signature.asc
Description: OpenPGP digital signature
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] koha authorities update linking authorities in subfield 0

2015-09-21 Thread schnydszch
Thanks Katrin! I will file a enhancement bug for this. Just in case for those
interested, I used MARCEdit's MARC Tools and added the following XSLT to
transform the MARCXML into MARCXML adding the desired Control Nos.:

http://www.loc.gov/MARC21/slim;
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#; 
xmlns:dc="http://purl.org/dc/elements/1.1/;  
xmlns:xsl="http://www.w3.org/1999/XSL/Transform;
exclude-result-prefixes="rdf dc marc">
 
 

 
   
   
 
 
   
 
   
  

 

 
  
   
  
 




--
View this message in context: 
http://koha.1045719.n5.nabble.com/koha-authorities-update-linking-authorities-in-subfield-0-tp5852941p5854033.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Disable displaying items from other locations (independent branches)

2015-09-21 Thread le-grex
Am 21.09.2015 um 08:53 schrieb Mirko Tietgen:
> Hi Gregor,

Hello Mirko,
> 
> Le-grex schrieb am 20.09.2015
> 
>> "Staff Client Catalog Search: By default, items from other
>> locations are displayed catalog searches."
>>
>> But i don't get how to change this default behaviour?
> 
> I don't think there is an equivalent to the OPAC limitation options
> in the staff client. You can manually limit searches to a single
> branch in advanced search, I assume that is meant here.

Mh, maybe if i can make this fix for the common search in staff-client,
that would be a way.

> 
> If you do not want the libraries to be connected at all, multiple
> Koha instances may be a better choice than independent branches.
> Have you looked into that?

Yes, indeed and it makes sense, but: There are some dozens of libraries
of this organisation (In fact it is one organisation, but they are more
or less independent from eachother). Each one does not have s many
items (books etc.)... The Problem is not so much, that i can find items
from other libraries, but that i can see how often which item has been
borrowed etc.

So i hoped, having one instance with a lot of branches on a "nice"
server, is more suitable than having... let's say 20 Koha Instances on
one Server or 20 VMs ;)

> 
> HTH,
> 
> Mirko
> 

Ya, thank you.

Ciao,

grex
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Kohacon 2016 location

2015-09-21 Thread schnydszch
Congratulations Greece! Better luck next time Philippines!



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Kohacon-2016-location-tp5853623p5854040.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] koha authority plugin adding choose aside from related headings

2015-09-21 Thread schnydszch
In current iteration of Koha ILS, when authority plug-in is switch on in
Cataloging and catalogers can only choose from controlled
vocabularies/authorities/lists, the cataloger has to go through adding
authorities/subjects through this plug-in. The cataloger is shown the
authority plug-in search interface. When a user search for a particular term
through the authority plug-in search interface, he/she is presented with the
Topical term and all other related headings (Broader and Narrower heading
and used/for see from) with clickable links for the Broader and narrower
headings if only these headings were properly linked in the authorites. A
user has the option to choose the topical term or heading searched and can
also scroll down further for related headings (those in 15x) (see
screenshots) but can not choose outright the broader or narrower headings
referred to by the Main heading (55x) (see screenshot 1). 

authorities_choose.png
  
 

If the topical term (Main heading) is chosen or click by clicking the
'choose' link, the term is added in the cataloging (Add biblio) module.
While in order for the user to add the other narrower and broader headings,
the user must search again for the previous search query in the authority
plug-in and have to go to through the process of scrolling further for these
terms and choosing them again in the authority plug-in. This task of adding
authorities is tedious for the catalogers. I feel that this is not yet
doable in Koha default installation, but I'm posting here to confirm if this
really is the case. The ideal case here is to put a clickable 'choose'
beside the linked terms (55x $wg or $wh) and when these clickables are
clicked, these terms are put in a temporary table. A clickable 'Move to
Record' then will add these terms in the Cataloging - Add Biblio module. I
don't if this even doable in jquery, or if not it should be an enhancement
to Koha ILS.


go through the process of searching it again in the authority plug



--
View this message in context: 
http://koha.1045719.n5.nabble.com/koha-authority-plugin-adding-choose-aside-from-related-headings-tp5854045.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] System generated field 001 control number

2015-09-21 Thread Iming Chan
Does this mean we can use MARC 999$c or 999$d for record matching and merging
purpose during import, as it didn't seem to work properly when we first
start to use Koha a while back.  

At this moment, we manually enter Koha record number found in 999$c into
001, while OCLC number is swapped to 035 in MARCedit.

Iming



-
Iming Chan
Translib Information Service
Melbourne, Australia
http://opac.translib.com

Phone: +61 3 9801 5097
Fax: +61 3 9801 4024
E-mail: im...@translib.com
--
View this message in context: 
http://koha.1045719.n5.nabble.com/System-generated-field-001-control-number-tp5853323p5854116.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Question about Koha Item types.

2015-09-21 Thread Jesse Lambertson
Thank you Katrin.

Your suggestion with the 942 does clear up what I was beginning to suspect.

And yes, definitely, these informational pieces between the 942 and the 952
must be IDENTICAL.
Experience has taught me this for sure.

Thank you much.

Jesse



On Sun, Sep 20, 2015 at 6:00 AM, Katrin Fischer 
wrote:

> Hi Jesse,
>
> I don't quite understand what you are trying to do, but maybe I can
> still help out with some general information about the item types in
> 942$c and 952$y.
>
> The pull downs for both are populated from the list of item types
> configured in your Koha installation, independent from the values that
> might appear in your data. So in order for this to work correctly, your
> configured item type codes should match exactly the information in your
> imported records. Be careful: the spelling needs to be exactly the same
> (case-sensitive). It's also a good habit to have your item type codes be
> only alphanumerical, without spaces, underscores, hyphens or similar, as
> that might affect searching later.
>
> The item type codes from both fields are indexed together into the same
> index. I'd run a few tests with one or two manually added records -
> checking the advanced search and also the item type facet.
>
> Hope this helps,
>
> Katrin
>
> Am 17.09.2015 um 16:52 schrieb Jesse Lambertson:
> > Hello everyone.
> >
> > I am doing a bunch of record editing right now and I have a question
> about
> > the Koha item-types as defined in 942 Vs. 952.
> >
> > I know we can edit items and define holdings according to defined item
> > types in what is the 952 via the edit function.
> >
> > But if I have a bunch of records that were imported with $ y already
> coded
> > in 952 as a BOOK, for instance, or a VISUAL MATERIAL, it seems those are
> > NOT being listed and able to be added to search restrictions at the
> outset
> > (because I had not defined item-types before I started importing). But
> all
> > the ones I imported AFTER I defined item-types are (I think).
> >
> > My question is, if I edit the 942 in the cataloging module by choosing to
> > attach an item-type to records, will those then become part of an
> item-type
> > search capability? Or do I then need to ALSO edit the attached 952
> holding
> > fields too?
> >
> > In my mind, this seems redundant, but I do want to know.
> >
> > Curious.
> > No rush, but I want to make sure I am layering as much usability and
> nuance
> > into our catalogue as I am able.
> >
> > Thank you much.
> >
> > Jesse
> >
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
Jesse A Lambertson
Librarian
Sultan Qaboos Cultural Center
1100 16th St, NW
Washington, DC 20036

Ph: (202)-677-3967 Ext. 104
jlambert...@sqcc.org
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Newly imported users all get booked the enrollment fee

2015-09-21 Thread Michael Kuhn
I had an empty Koha database with a user type "Adults" where enrollment 
period is set to 12 months, enrollment fee set to 10 Euro. Using menu 
"Tools > Import patrons" I loaded a number of users with user type 
"Adults" into the database, which went OK. Only the next day when the 
script "fines.pl" had run I saw that all these users had a fee of 10 
Euro booked on their account. It seems like Koha thought all these users 
were newly enrolled so it booked the fee.


All these users were migrated from another system and had already paid 
their fees, so there is no reason to book these 10 Euro. How can I 
prevent this behaviour?


Or, if I can't prevent it - will it be enough to delete the respective 
lines in Koha table "accountlines"?


I did not find much information about how the process of enrolling and 
the booking of the fee works. Basing on what date will the next fee get 
due etc.


I appreciate any help!

Kind regards, Michael
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha