Hi Beda,
a similar problem was reported on Bugzilla:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13396
Hope this helps,
Katrin
Am 10.12.2014 um 18:57 schrieb Chris Cormack:
> Hi Beda
>
> What version did you upgrade from. 3.18.x uses DOM not GRS1 for indexing, I
> suspect that is
Hi Lenora,
I have filed bug 13436 to add more options to the list:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13436
Could you take a look and maybe add the options you think are missing in
a comment?
Thanks,
Katrin
Am 11.12.2014 um 01:41 schrieb Lenora Oftedahl:
> In 3.18, there
Hi Chris
Am 10.12.2014 18:57, schrieb Chris Cormack:
> Hi Beda
>
> What version did you upgrade from. 3.18.x uses DOM not GRS1 for
> indexing, I suspect that is your problem
Mirko suggested to add:
grs1
grs1
/var/lock/koha/__KOHASITE__
1
at the end of koha-conf.xml. After a new reindexing koha
Op 10/12/14 om 18:01 schreef Robin Sheat:
> I expect this to happen tomorrow, though I'll be conferencing then so I
> can't promise exactly when it'll happen.
3.16.05 packages are now available in the 'oldstable' repo.
--
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FE
Kerrie, to select by homebranch, you just need to add a branch parameter,
i.homebranch=<>
So the statement will now look like
SELECT DISTINCT b.biblionumber, b.title, b.author, t.editionstatement,
t.publishercode, t.isbn, i.ccode, count(i.itemnumber) FROM biblio b LEFT
JOIN
biblioitems t USING(bi
Hi Paul & Heather,
The report you developed for Satish below is very helpful, but I'd like to
tweak it a little differently - I've tried every variation I can think of with
no luck (I don't have very much SQL experience)... how can I get it to select
by branch, rather than collection code?
SE
In 3.18, there's a system preference under Administration for Sharing anonymous
usage statistics. Unfortunately, we can't choose a library type because we are
neither a public library under the usual definition or a university. We are a
special or government library. How can we add that?
Le
Dear all,
We have recently upgraded to 3.18 and I just noticed the following warning
found in staff client under About > System Information:
The entry is missing in your configuration file. Falling
back to legacy facet calculation.
How do we resolve this issue?
Thank you in advance for your he
Dear all,
We have successfully upgraded to 3.18 and encountered a problem when tried
to add daemon mode to rebuild_zebra.pl (bug# 6435, from 3.16). Our IT
person has supplied the following:
[9:50:24 AM] Alexey - Neo Universe:
root@ip-172-31-0-233:/usr/share/koha/bin/migration_tools# ./rebuild_ze
> How can we activate z39.50 in Koha
> In order to obtain records from the World catalog and other libraries
You don't need to "activate" anything, you just need to have some
Z39.50 servers added to Koha, which would normally have been done
during the installation process.
http://manual.koha-comm
Thank you both Heather and Paul, for helping me on sql report,
This will help many librarians here.
On Thu, Dec 11, 2014 at 12:43 AM, Paul A
wrote:
> At 12:09 AM 12/11/2014 +0530, SATISH wrote:
>
>> [snip] how to achieve for the same tables,
>> for each collection ( as per collection code).
>> B
Hello
How can we activate z39.50 in Koha
In order to obtain records from the World catalog and other libraries
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
At 12:09 AM 12/11/2014 +0530, SATISH wrote:
[snip] how to achieve for the same tables,
for each collection ( as per collection code).
Because, at various time intervals, library inspection team here is most
interested in
knowing how many unique titles and counts as a whole library and also by
co
Hi Heather Braum,
The result is amazing.
Thank you very very much, for the SQL and for your explain, this is what I
was looking for.
Here, I have one more related query, how to achieve for the same tables,
for each collection ( as per collection code).
Because, at various time intervals, library i
That's a very encouraging and affirmative recommendation.
Thank you Elaine.
On Wed, Dec 10, 2014 at 1:12 PM, Elaine Bradtke wrote:
> Our system is run in the cloud. We felt this was more secure/reliable than
> running it from our internal server. We recently shifted from one virtual
> machin
Our system is run in the cloud. We felt this was more secure/reliable than
running it from our internal server. We recently shifted from one virtual
machine to another, including a change in the version of Linux we run. Of
all the online services we have, Koha was the easiest one to move, and had
I find the guided reports wizard, frankly, to be very unhelpful, especially
since I work with 50 branch locations in our consortia. I usually write my
own custom reports, as a result, for much more granular control.
To get this kind of data you gave as an example, you have to query and join
three
Hi Beda
What version did you upgrade from. 3.18.x uses DOM not GRS1 for indexing, I
suspect that is your problem
I am going to be in a conference all day so hopefully someone else can help
Chris
On 11 December 2014 6:27:58 am NZDT, Beda Szukics
wrote:
>Hallo
>
>I upgraded today to koha 3.1
Hi Elaine
It's in the 3.18.01 release notes
http://koha-community.org/koha-3-18-01-security-release/
You won't be able to see it in bugzilla the bug is still private until a 3.16.x
release is done but you can cherry pick the code from the 3.18.x branch in git
Chris
On 11 December 2014 6:33:
Could someone let us know what bug number this is?
Thanks
On Wed, Dec 10, 2014 at 5:01 AM, Robin Sheat wrote:
> Chris Cormack schreef op wo 10-12-2014 om 12:46 [+1300]:
> > I have reported the bug, and I am just uploading a couple of patches,
> > (one for master/3.18 which is bootstrap) and one
Hallo
I upgraded today to koha 3.18.1 using the debian packages.
I noticed that the links between authority records and bibligraphic
records weren't updated using koha-rebuild-zebra
So I tried a full reindex:
koha-rebuild-zebra -f kb
I get:
16:41:54-10/12 zebraidx(4827) [warn] Couldn't open c
You have discovered one of the quirks of the system. For biblios with
multiple items it will produce the same information (title, etc.) for each
item. I don't know how to work around that. Maybe someone else does?
Elaine
On Wed, Dec 10, 2014 at 5:12 AM, SATISH wrote:
> Hi,
>
> I would like to
You could set-up the MySQL server containing coha as a linked server in MS
SQL Server. You could then perform queries against it from within the MS
SQL Server environment, update it - strongly NOT advisable - and/or copy
its contents to a local (MSSQLSRV) DB.
On Sunday, December 7, 2014, Sina Stew
Hi Michal,
We were running 3.16 and just upgraded to 3.18.
As for the logs, I will have to check with our IT person, as I don't have
access to that area. Unfortunately I'm not familiar with the operating
system side of things.
Thanks for the advice on "koha-conf.xml" and I will forward it to
24 matches
Mail list logo
