Hi Janice,
I am not sure I understand quite well, whether the „no_matchpoint“ problem
occurs when checking out any book or whether it occurs only for one
particular book with the barcode 123285.
If it happens with the one particular book only, I would guess the problem
might be related to
It may be a good practice to put in a catch all policy to prevent
no_matchpoint errors, and perhaps give it an unusual loan period to
give staff a heads-up.
--
Jason Etheridge
| Support Manager
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email:
Did you make any changes to your default circulation policy? I received the
no_matchpoint error when I attempted to modify the loan duration in our default
Circulation Policy Configuration. My solution was to restore the original
policies to their defaults and then create a new policy for
I would like to comment on a couple of the things Dan said.
We are taking something which is fundamentally a website concept (a link
between pages) and applying it to an application, and we need to very
careful that we don't misapply a web-centric mindset to any areas where that
thinking isn't
Dan,
Thanks for all of this. Pushing everyone to think about the broader
context of user interaction types and expectations is /very/
important.
My thoughts on this basically boil down to a few simple rules of thumb
we could follow:
*) if the interface component brings you to a screen that
On Wed, May 21, 2014 at 7:00 PM, Dan Wells d...@calvin.edu wrote:
Hello Bill,
Thanks for the update. I have some thoughts about both of your questions,
but will focus on the link issue for now.
I’m not quite sure how to answer because I feel like we’re not asking the
right question.
On Wed, May 21, 2014 at 5:47 PM, McCanna, Terran
tmcca...@georgialibraries.org wrote:
UI Planning:
I looked through the items listed in Sprint #1 and the only interfaces I
noticed missing were:
Patron - Surveys (Will this not be added until the Local Admin sprint?)
Right, practically
