I'm not the most knowledgeable on this subject, but since it's later in the day
you might be hanging until tomorrow waiting for the experts
Our OPAC is at ___our hostname__/eg/opac/home
If that helps, great. If not, someone else will get your over this hurdle but
it might be tomorrow!
-Hol
Hello,
First of all thanks everyone for the support.
The installation of Evergreen 2.10 went smoothly on Debian 8.
After which the ejabberd services and Evergreen have been started successfully.
There were not any errors after running the autogen.sh script and after
restarting apache2.
Afte
Josh,
Have you considered using a different status for the ILL items?
We have the library setting "Selfcheck override events list" configured to
automatically override the COPY_NOT_AVAILABLE block. But we also have the
library setting "Block copy checkout status" configured to prevent checkout
of
For reference:
I had thoughts about creating a "origin type" like field in the circ
matrix "Staff", "OPAC", "Selfcheck", etc. Then you could set rules
based on that to say "Staff can renew this, but you can't OPAC renew
this" and "this can't be checked out at a selfcheck,". Add in an
opti
Josh,
I don't think this is a problem for a software solution. I think it is
best solved by ILL workflow changes and staff education.
In PINES, ILL staff are instructed to check the item out to the patron when
they create the pre-cat record so that the due date is set correctly. As
you mentioned
Thanks for the idea been. I am referring to the web based self check, I should
have clarified that.
Josh
Josh Stompro - LARL IT Director
-Original Message-
From: Open-ils-general
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Ben
Shum
Sent: Wednesday, April
Josh,
As far as I know that feature does not exist.
We (MVLC) would welcome it as we've had a request for this capability in
the past but have had the tuits to implement it.
The trick would be making this work with SIP2 self check clients as well
as Evergreen's own self check.
Cheers,
Jaso
Presuming you mean the Evergreen web selfcheck, I could only think of
a workaround approach like follows:
If you were to designate the workstation for the selfcheck to be a
different org unit (like an opac invisible child unit of the parent
library), then include a circ policy in circ_matrix_match
Hello Everyone,
My coworker is working on an issue with out of state ILL items, that we always
want to have due on a specific date, even when the customer doesn't pickup the
item right away. And she has been trying to figure out if there is a way to
block a specific item from being checked out
Hi,
It is time to elect the Release Manager for the next Evergreen release.
The Release Manager does not have to be a core committer, but does
need to be familiar with Git and have contributed something to the
Evergreen project whether it be code or documentation.
Nominations (including self-nom
10 matches
Mail list logo
