Be reassured, your cataloguing done since last week is not lost. You
should be able to dump the records in a MARC file and reimport it in the
newer version rather easily.
As well, having very recently done an upgrade from 3.0.2 simply using
the Koha upgrade tool, I'd be very optimistic about y
Hi Luisa
I would stop now, the last 3.4 release was 7 years ago, it is very very
out of date. And upgrading from a version that old will be very hard.
If you haven't catalogued much already I would start with a new install
of 18.11.04 and start with that.
Chris
On 2/04/19 11:17 am, Luisa Korodr
Dear Koha Community,
Need help. I have only just been appointed as Librarian to a Theological
library and we have just installed Koha 3.4 to automate the collection and
as of last week I have started cataloguing the 15,000 resources that we
currently have.
I need technical advise whether I should
Right now, the packages for Koha 3.4.2-1 are uploading to the
repository. Versions of this were in the squeeze-dev repository for a
while with no complaints, so I assume that means everything was OK.
(Also, we've been running them here for a while with no real issues.)
One important thing to note
Mahesh T Pai wrote:
> MJ Ray writes:
> > using koha_perl_deps.pl which does show what is required and
> > what is optional. Splitting debian.packages in two would be
> > a bigger job and I'm not sure if it's worthwhile, but have a
> > go if you think it is.
>
> How about a .deb metapackage a
MJ Ray writes:
> using koha_perl_deps.pl which does show what is required and
> what is optional. Splitting debian.packages in two would be
> a bigger job and I'm not sure if it's worthwhile, but have a
> go if you think it is.
How about a .deb metapackage as a part of the koha tarball, whi
Mahesh T Pai wrote:
> I would certainly appreciate if the dependencies were grouped by
> "absolutely required"; and "X is required if you enable (or want
> functionality kX) kX", where kX is an option within Koha.
I've submitted a patch for INSTALL.debian which will suggest
using koha_perl_deps.pl
On 20 Jun 2011 18:16, "Mahesh T Pai" wrote:
>
> aj...@maxenna.com writes:
>
> > Initially I added the following lines to ports.conf.
> >
> > Listen 80
> > Listen 8080
> > NameVirtualHost*:80
> > NameVirtualHost*:8080
>
> "NameVirtualHost" is not configuration to be set in ports.conf
>
> It sh
aj...@maxenna.com writes:
> Initially I added the following lines to ports.conf.
>
> Listen 80
> Listen 8080
> NameVirtualHost*:80
> NameVirtualHost*:8080
"NameVirtualHost" is not configuration to be set in ports.conf
It should be set in koha-httpd.conf; and the installer would have done
it
Hi Ajesh,
I experience the exactly the same problems as described in the points 1 and
2. Have you solved it and how?
Sincerly Alen
--
View this message in context:
http://koha.1045719.n5.nabble.com/Koha-3-4-on-Ubuntu-tp4333084p4503118.html
Sent from the Koha - Discuss mailing list archive at Na
2011/6/8 Robin Sheat :
> Also, is this filtering powered by zebra, in which case a reindex (or at
> least a regular index) may be needed?
I tried that :) a reindex.
Nicole
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://l
Nicole Engard schreef op wo 08-06-2011 om 08:55 [-0400]:
> And I have a very small collection since it's a test system and so
> every bib with an item attached is a BK. I do have EBK but they don't
> have items attached. Do we know if this is looking at the biblio item
> type or the item item typ
I do have BK in my itemtypes table:
mysql> select * from itemtypes;
+--+--+--++--+-+
| itemtype | description | rentalcharge | notforloan |
imageurl | summary |
+--+
Nicole,
I'm sure that you have an entry in your itemtypes.itemtype that is 'BK'
and I'm positive you have a branchcode that is "NIC" as well as having
an items.itype=BK and a items.homebranch=NIC. Do you have something you
could do a test with that isn't the majority of your items? Maybe if
Okay I tried it on my system with just
itype: [BK]
And nothing was hidden.
I tried it with
itype: [BK]
homebranch: [NIC]
And still everything showed
So I'm at a loss here.
Nicole
On Tue, Jun 7, 2011 at 7:57 PM, Nicole Engard wrote:
> It might :) I'll have to re-read it tomorrow when m
It might :) I'll have to re-read it tomorrow when my brain has refreshed :)
Thanks!
On Tue, Jun 7, 2011 at 6:26 PM, Linda Culberson
wrote:
> Nicole,
> Does this help?
> My OpacHiddentems looks like:
>
> itype: [07, 10]
> location: [STAFF, ISO]
>
> In items my items.itype 07 is defined in Item
Nicole,
Does this help?
My OpacHiddentems looks like:
itype: [07, 10]
location: [STAFF, ISO]
In items my items.itype 07 is defined in Item Types Administration as
Staff Assigned
My items.itype 10 in Item Types is Archival Copy
The locations STAFF and ISO
are in Authoritized Values for categor
Can you give us a sample with your data in it, cause that document
really isn't helpful to me at all, I'm not following what it wants me
to do.
Nicole
On Tue, Jun 7, 2011 at 5:55 PM, Linda Culberson
wrote:
> I got the information from docs/opac/OpacHiddenItems.txt and just took at
> stab at it.
I got the information from docs/opac/OpacHiddenItems.txt and just took
at stab at it.
Those item types (itypes) I listed no longer appear in the opac - so I
think it works. like
in OpacHiddenItems.txt
It indicates you can use any field in the items table:
> The OpacHiddenItems syspref allow the
I also did not get any responses when I asked on list after the
feature was pushed to Koha ... this is why it's not in the manual
either :(
Nicole
On Tue, Jun 7, 2011 at 5:41 PM, Linda Culberson
wrote:
> Sharon,
> I didn't get a response, but I seem to have gotten it to work in Koha 3.4.
> Mine
Sharon,
I didn't get a response, but I seem to have gotten it to work in Koha 3.4.
Mine is like:
itype: [07, 10, 14, 15]
location: [STAFF, ISO]
because those are the item types and locations we don't want to
appear in the OPAC
Hope that helps.
On 6/7/2011 4:05 PM, Sharon Moreland wrote:
> Hi
Hi Linda and Koha folks,
Was the mystery of the OpacHiddenItems syspref ever solved?
We opened the associated document and added the necessary items and
values (http://screencast.com/t/YEpkHriOQ) but our Withdrawn items
remained visible in the OPAC.
I didn't find any open bug tix related to this
Hi!
I think your problem is described here:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5667
There is a signed off patch for this, so hopefully it will be fixed in 3.4.1.
Basically, if you want to fix it yourself, you need to *copy* this
part of the config:
...
...
and change
Hi
I've installed Koha 3.4. I want to enable my server as public z39.50
server. I have the following config file:
===
tcp:@:
tcp:@:9998
tcp:@:
/var/lib/koha/zebradb/biblios
/etc/koha/zebradb/zebra-biblios.cfg
/etc/koha/zebradb/pqf.propert
Dear Koha Community
I have upgraded to Koha 3.4 but I'm unable to use the Label Creator.
Whenever I create new batch or manage existing batch it says:
*WARNING:* An error was encountered and items(s) not added, the error was:
Branch is not set, you please set your branch before adding items to a
Please, create a new mail thread for each topic you want to discuss,
with a proper subject, so people interested in that specific topic
knows in its mailbox what it is about.
regards
To+
On Mon, Apr 25, 2011 at 11:29 AM, wrote:
> Hi All,
>
> Thanks to everyone for the support so far.
>
> I ha
Hi All,
Thanks to everyone for the support so far.
I have successfully installed Koha3.4.0 on Ubuntu.
I have a query. Is there a starter's guide available(any links or pdf's).
Like how to start using Koha step by step. Something that might be a
little simpler than
http://koha.org/documentat
On Sun, Apr 24, 2011 at 4:03 AM, wrote:
>
> Initially I added the following lines to ports.conf.
>
> Listen 80
> Listen 8080
> NameVirtualHost*:80
> NameVirtualHost*:8080
Spaces are needed between 'NameVirtualHost' and the rest of the lines
(i.e. *:80)
NameVirtualHost *:80
NameVirtualHost *:8080
You are much better off using the INSTALL files that come in the tarball,
INSTALL.ubuntu in your case.
That error you are getting looks like you haven't set up the mysql user to
match the username and password you chose when running perl Makefile.PL
Chris
On 24 Apr 2011 19:50, wrote:
> Proceedin
Proceeding further and after carefully executing the last few steps
mentioned at
http://wiki.koha-community.org/wiki/Koha_on_Ubuntu
when I try to open http://127.0.1.1:8080/, I am seeing this
***
Software error:
Access denied for user 'k
Initially I added the following lines to ports.conf.
Listen 80
Listen 8080
NameVirtualHost*:80
NameVirtualHost*:8080
Then on executing the command
>> sudo apache2ctl restart
*
Syntax error on line 10 of /etc/apache2/ports.conf:
Invalid command
Hi,
On Apr 22, 2011, at 10:43 AM, aj...@maxenna.com wrote:
> I am not sure why, could somebody let me know why I am getting this error.
In addition to double-checking the steps that Arturo mentioned, if Koha is the
only web app on your server, you may also want to disable the default site:
sudo
Looks like you need this commands :
sudo ln -s /etc/koha/koha-httpd.conf /etc/apache2/sites-available/koha
*
# sudo gedit /etc/apache2/ports.conf
*
*add*
*
*
Listen 80
Listen 8080
NameVirtualHost*:80
NameVirtualHost*:8080
*
then
# sudo a2enmod rewrite
# sudo a2enmod deflate
# sudo a2ensi
Hi,
I am trying to install Koha3.4 on Ubuntu OS.
I believe I was successfully able to complete the installation, following
the steps at
http://wiki.koha-community.org/wiki/Koha_on_Ubuntu
But when I try to access the below address, I am getting error
http://127.0.1.1/
***
I'm terribly sorry, we had an alarm go off, and I apparently hit send
before I finished my message. We need to know about OpacHiddenItems in
3.4 because in 3.2 we are using Lost to hide items in the opac. We
don't like having something marked "LOST" when we know it isn't and and
are very deter
35 matches
Mail list logo
