Fellow friends, suddenly we have a problem with one Patron. When we
want to check out for this Patron the system is coming up with Cannot
Check Out! Lost: Patron's card is lost.
We have no clue as to what has caused this and how to resolve it. Plse
help asap. We just recorded her checkout
Colleagues, I have just spotted that our assistant Librarian had the
Patron's profile with Lost Card checked to Yes which was wrong. We
have reversed that to No and it is fine now.
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Hi, I'm just starting a thread to discuss this topic so we make some
decisions and we can continue improving Koha in this aspect. As far as
I can remember there are a few issues with this:
1) The use of ENV vs. koha-conf.xml vs. DB/systempreferences to store
memcached configuration.
I introduced
Hello,
I have a new site running 3.06.02. I have configured LDAP as
authentication and it seems to connect, authenticate and create the new
patron correctly. The problem is though, that once the user logs in for the
first time (and hence creates the Patron record) they are met with a
I have noticed this exact same behavior.
The expiration date is the most disconcerting to me.
After users log in successfully 1 time, all is well, but the first initial
login is a bit confusing.
-S
Barry Cannonba...@oslo.ie 2/8/2012 12:32 PM
Hello,
I have a new site running
Does anyone successfully use the Anonymize Checkout History tool in
Koha? We have found it not to work as we would expect and I'm not sure
if we are attempting to use it improperly or the tool just does not work.
Thanks,
Tom
--
Could you please include exact error message including line number?
There is no line number mentioned in the log as the problem is with the
header which is generated by the template file (or rather, the included
header file). All that is logged is the referer URL
LDAP mappings can have
All,
We have had an instance using rebuild_zebra.pl -b -x -r -v where it
emptied the zebra bibliographic database but didn't rebuild it. Has
anyone else had that happen before? Know the reason or the solution?
We have compared the scripts and the configuration files with the other
Hi,
We have been on Koha for about 8 months now and are still refining the way we
deal with acquisitions.
The crux of the problem is that the way Koha wants to deal with Orders ie. A
status On order (Not for loan) does not allow reserves to be placed against it.
Yet we definitely want to let
Hello David,
You probably have an answer already, but once you access tools, and than import
patrons function, it should give you the option on what to do with duplicate
records:
(If matching record is already in the borrowers table: Ignore this one, keep
the existing one, or Overwrite the
I configured Circulation, fines rules and circulation in System preference
the same way in Koha 3.6.2 and Place hold works good.
Thx
--
View this message in context:
http://koha.1045719.n5.nabble.com/Problem-with-place-hold-tp5429552p5468757.html
Sent from the Koha-general mailing list archive
11 matches
Mail list logo