Aligning Reasons for Cancellation/Rejections

One of the easiest ways to improve the performance of DOCLINE in ILLiad is by limiting the number of times human intervention is required in the system. Harmonizing the syntax of your “reasons for no” is a good example of this. Usually, this means case matching.

An ILLiad library filling requests from DOCLINE probably has a lending volume which requires batch updating, and selecting Filled As Requested By Borrower. This is a setting adjusted inside DOCLINE.

Batch updating means statistics for how a library fills requests may be inaccurate in DOCLINE’s reports, but ILLiad libraries using DOCLINE already receive inaccurate reports from DOCLINE for a variety of reasons.

syntaxmatchIn the batch update screen, you have a number of reasons for rejection. In ILLiad’s customization manager, these have to match DOCLINE’s syntax to work effectively and not create errors. For example, if I reject due to poor condition, ILLiad’s customization manager must say POR, not por. Not found as cited must be INC*, not inc or INC. DOCLINE is not a system which allows for guessing.

syntax2  

Once your Reasons for Cancellations are updated in ILLiad to match DOCLINE’s, batch updating will be much easier. Because DOCLINE has a limited number of reasons compared to OCLC, you can align other scenarios to the most appropriate reasons.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s