[Workflowtoolkit-l] Routing rules for textbooks in Borrowing

[Stephanie Spires]

Hi Heather,

I was just reading over your routing dilemma and it reminded me of a newsletter article that Kevin at Atlas wrote awhile back - well more than awhile back - in 2004.  But if you find any problems with your current setup you might want to have a look at his article in http://www.atlas-sys.com/products/illiad/Newsletter/archive/OCLCILLiadNewsletterFall2004.pdf on compound routing rules.  The compound rules are certainly more complex in that a table has to be created and included in the database and referenced in the rule.

Just wanted to throw that out there to you in case you need it later.
_________________________________________________________
Stephanie Spires
Custom Services and Training Manager
Atlas Systems - a company promoting library excellence through efficiency
phone: 757-467-7872 x301     fax: 757-467-7875
sspires at atlas-sys.com
http://www.atlas-sys.com/

Registration for the  2010 ILLiad International Conference: Exploring Trends in Resource Sharing is now open.  Pre-Conference is March 24 and the Conference runs March 25 and 26.  The conference is open to everyone with an interest in Resource Sharing.  Learn more at https://www.atlas-sys.com/conference/

Notice:  This e-mail message, including any attachments, is intended only for the named recipient(s) above and may contain confidential information.  If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message from your computer without making any copies or distributing it to any other person.  Thank you.





From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Campbell, Heather
Sent: Tuesday, February 23, 2010 9:13 AM
To: jgrnwood at olemiss.edu
Cc: ILLiad Best Practices Workflow Toolkit
Subject: [Workflowtoolkit-l] Routing rules for textbooks in Borrowing

<sniff> No one would answer my question.... Definitely, not feeling the love here, folks.

We ended up paying over $1200 for a missing textbook this past year, so we needed a better way to identify textbook requests. So----- I looked at the rules I had and figured I could adapt one for the purpose. I called the HelpDesk with questions I had about how this would work.

First some rules of thumb not covered in the documentation:

 *   If you use Direct Request and want these rules to act on requests before Direct Request steps in, your Direct Request rule has to come at the end of all the rules.
 *   Rules that you want to run after the other rules can be put at the end of the rules. The rules go active in numerical order but you don't have to number the rules 1, 2, 3... . You can have rules 1-20, then rule 100, then rule 300. (Our Direct Request rule is #200).
 *   If you use the "like" type instead of "=", you have a keyword search of the requests. So if you have a publishing company like Thomson that may publish with combinations of Thomson and other names (Thomson-Wadsworth, Thomson Educational, et al), the rule will pick up on all requests with the word Thomson in t.LoanPublisher.
 *   I hoped to have one rule dealing with this, but there's a character limit for what you can have in a routing rule.  So I copied the same routing rule, then changed the number and publication name, and moved on to the next one on my list. It didn't take long for me to get through the list.
 *   Of course, avoid any rules with using the keyword University by itself.

My Borrowing clerk preferred that there be a special cancellation queue for textbook requests so I made a custom queue to be used with these rules. My clerk and I recognize that we may snag some requests for non-textbook requests in our queue.  For example, I've already given her heads up that, while Lippincott may publish textbooks now, this was not always the case.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.geneseo.edu/pipermail/workflowtoolkit-l/attachments/20100223/11b955d9/attachment.html>