On Tue, Mar 3, 2009 at 11:17 AM, Karen Collier <[email protected]>wrote:
> Bill, > > The "no op" checkin you're describing sounds to me like it would be perfect > for offline checkin. > > Regarding transits, I'd say it would be preferable for offline check-ins > NOT to automatically go to transit. Like with holds, staff would have no > way to know which books are going somewhere other than shelving (unless they > were physically labeled as belonging to another branch, but they wouldn't > always be labeled and the home library wouldn't always be the destination, > so even that's unreliable). > > I assume that if the item wasn't immediately transited in the system, it > would show up on the pull list? So there might be a little extra delay > while staff tracks the book down, but the item would reliably get where it's > going, rather than languishing on the shelf while staff thinks it's > transiting. > Not necessarily. An item will transit for 2 basic reasons: it's captured for a hold or it's trying to "go home". In the case of holds, the item will show up on the pull list if it happens to be targeted. Of course, there's no guarantee of that. If the item just needs to "go home", there will be no indication to staff that the item _should_ have transited. It will just be in the "reshelving" status and it won't go into transit until it's checked in again. This situation, in particular, is why I'm concerned about the "no op" checkin with offline. -b -- Bill Erickson | VP, Software Development & Integration | Equinox Software, Inc. / The Evergreen Experts | phone: 877-OPEN-ILS (673-6457) | email: [email protected] | web: http://esilibrary.com
