> A copy item that has Circulate "No" (for in-house only) is Holdable but > does *not* appear on the Pull List. Dead end.
This is because Evergreen assumes Circulate "No" implies Holdable "No". > So: we tried Circulate "Yes" and then "Reference" is "Yes" - but to our > surprise, such an item can be checked out. Oops. I don't think Reference has any behavior by default, though I've seen circ scripts (prior to the in-db circ that 1.6 uses) configured to stop circulation based on it. It looks like the in-db circ matrix is able to look at the item level Reference flag, so you should be able to create a rule to stop circulation based on this. > Anybody an idea how to tackle this ? Correct me if I'm understanding, but you have "closed stacks", which means only staff has access to them, so patrons have to make "stack requests" for staff to go fetch those items. Do the patrons need to know at the time of a stack request whether the item may be used in-house only or may leave the building? Why not let a checkout occur on the patron's account to show that the item is in their possession, but otherwise tell them when an item may not leave the building? -- Jason Etheridge | VP, Tactical Development | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com Please join us for the Evergreen 2010 International Conference! It is being held April 20 - 23, 2010 at the Amway Grand Hotel and Convention Center, Grand Rapids, Michigan. http://www.evergreen2010.org/
