Commit | Line | Data |
---|---|---|
ae8b9281 RJ |
1 | <?xml version="1.0" encoding="utf-8"?>\r |
2 | <chapter xml:id="ill" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r | |
3 | xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r | |
4 | <info>\r | |
5 | \r | |
c169396d | 6 | <title>Interlibrary Loans</title>\r |
ae8b9281 RJ |
7 | \r |
8 | </info>\r | |
9 | \r | |
10 | <para>\r | |
c169396d | 11 | <emphasis role="bold">Sitka Support Team <?linebreak?>Revised April 2016</emphasis>\r |
ae8b9281 | 12 | </para>\r |
a0d37b98 JP |
13 | \r |
14 | <para>Interlibrary loans can be handled in part or in whole within Evergreen using the different \r | |
15 | methods outlined here.</para>\r | |
16 | \r | |
ae8b9281 | 17 | \r |
c169396d | 18 | <!--\r |
ae8b9281 RJ |
19 | <section xml:id="ill-issue">\r |
20 | <title>The Issue</title>\r | |
21 | <para>Pre-catalogued items (pre-cats), currently used for interlibrary loan (ILL) items at\r | |
22 | most Sitka libraries, are created at the time of the loan to the patron, and thus cannot\r | |
23 | be used to manage transit status when ILL items are received at a central location for a\r | |
24 | patron at a branch location. Further, some Sitka libraries need to use brief records for\r | |
25 | borrowed ILL items based on job descriptions and established workflows. Pre-cats do not\r | |
26 | create catalogue records in the Sitka database, but brief MARC records do. In order to\r | |
27 | facilitate workflow and maintain database integrity in a shared environment, it is\r | |
28 | recognized that policy is required on brief record standards and recommended procedures. </para>\r | |
29 | \r | |
30 | \r | |
31 | <simplesect>\r | |
32 | <title>Possible Solutions</title>\r | |
33 | <orderedlist>\r | |
34 | <listitem>\r | |
35 | <para>Track incoming interlibrary loan items, including transits between the\r | |
36 | receiving location and branches, outside the Evergreen system. Circulate ILL\r | |
37 | items as Evergreen pre-catalogued items at each branch as per current\r | |
38 | practice within Sitka. </para>\r | |
39 | </listitem>\r | |
40 | <listitem>\r | |
41 | <para>Create a fixed set of brief bibliographic (MARC) records, with a single\r | |
42 | attached volume record, and single attached copy from a fixed set of\r | |
43 | barcodes from library’s range of barcodes. Library staff will manage which\r | |
44 | barcodes are associated with which MARC record and determine optimal\r | |
45 | workflow in order to do this. </para>\r | |
46 | </listitem>\r | |
47 | </orderedlist>\r | |
48 | </simplesect>\r | |
49 | \r | |
50 | <simplesect>\r | |
51 | <title>Recommended Solution</title>\r | |
52 | <para>Sitka support team recommends future sites, and possibly existing sites, consider\r | |
53 | both solutions. Sitka support team will provide future libraries with information on\r | |
54 | both options and request that they make a decision at the time of migration. </para>\r | |
55 | </simplesect>\r | |
56 | </section>\r | |
57 | \r | |
58 | <section xml:id="ill-technical-note">\r | |
59 | <title>Technical Note for Implementing Solution #2</title>\r | |
60 | <para>This technical note will outline a proposal on how to use a fixed set of bibliographic\r | |
61 | records and Sitka support’s proposed technical recommendations. The Circulation and\r | |
62 | Cataloguing Working Group, and the Business Function Group, will all have input to the\r | |
63 | proposal and recommendations, and it is expected that policy and recommended workflow\r | |
64 | will be developed as a result. </para>\r | |
65 | \r | |
66 | <simplesect>\r | |
67 | <title>Record Requirements</title>\r | |
68 | \r | |
69 | <para>We recommend the following as potential requirements for a fixed set of records to\r | |
70 | be used for ILL. Some sites may use all fields, while some may not. Some sites may\r | |
71 | input actual title and author data for each resource, while some sites may create\r | |
72 | fixed records with fixed generic bibliographic data. For example, as actual\r | |
73 | bibliographic data is retained in Outlook, a Sitka library may choose to create\r | |
74 | their ILL brief records using a generic title such as BFN Interlibrary Loan Book,\r | |
75 | where BFN is Fort Nelson’s LAC code. (See Appendix for information about LAC\r | |
76 | codes)</para>\r | |
77 | \r | |
78 | <itemizedlist>\r | |
79 | \r | |
80 | <listitem>\r | |
81 | <para>Bibliographic records could include the following fields and text could be\r | |
82 | in upper case to further identify as a brief record:</para>\r | |
83 | <itemizedlist>\r | |
84 | <listitem>\r | |
85 | <para>100 $a for author's full name</para>\r | |
86 | </listitem>\r | |
87 | <listitem>\r | |
88 | <para>245 $a for title, and 245 $b for sub-title, and\r | |
89 | <emphasis>ILL</emphasis> designation</para>\r | |
90 | </listitem>\r | |
91 | <listitem>\r | |
92 | <para>850 $a, or $590a, with representation of originating library,\r | |
93 | either the LAC library code (meets the MARC standard) or a full text\r | |
94 | representation of the library’s name. If using generic bibliographic\r | |
95 | data Sitka support recommends the 590 or 850 contain LAC code of\r | |
96 | library that created brief record</para>\r | |
97 | <mediaobject>\r | |
98 | <alt>MARC view of brief record</alt>\r | |
99 | <imageobject>\r | |
100 | <imagedata scalefit="0" fileref="media/practice-1.png"/>\r | |
101 | </imageobject>\r | |
102 | </mediaobject>\r | |
103 | \r | |
104 | </listitem>\r | |
105 | \r | |
106 | </itemizedlist>\r | |
107 | <para>An ILL MARC record template will be created by Sitka support containing\r | |
108 | final, approved fields. This template will be available by selecting <menuchoice>\r | |
109 | <guimenu>Cataloguing</guimenu>\r | |
110 | <guimenuitem>Create New Marc Record</guimenuitem>\r | |
111 | </menuchoice> >and choosing appropriate template from drop down menu.</para>\r | |
112 | </listitem>\r | |
113 | \r | |
114 | <listitem>\r | |
115 | <para>Volume record can contain a dummy 'ILL' call number that does not need to\r | |
116 | be changed on a per-loan basis.</para>\r | |
117 | <itemizedlist>\r | |
118 | <listitem>\r | |
119 | <para>Owning library/call number will be the designated ILL branch at a\r | |
120 | library system.</para>\r | |
121 | </listitem>\r | |
122 | </itemizedlist>\r | |
123 | \r | |
124 | \r | |
125 | </listitem>\r | |
126 | \r | |
127 | <listitem>\r | |
128 | <para>Copy is assigned a shelving location 'ILL', which is holdable, but not\r | |
129 | OPAC visible. This will prevent patrons from discovering these brief\r | |
130 | records. Shelving location can be library system specific, or a Sitka wide\r | |
131 | shelving location meant to be used by all sites using brief records for\r | |
132 | ILL.</para>\r | |
133 | <itemizedlist>\r | |
134 | <listitem>\r | |
135 | <para>Sitka support team will create the Sitka - wide shelving location\r | |
136 | with required attributes upon final formalization of policy.</para>\r | |
137 | </listitem>\r | |
138 | <listitem>\r | |
139 | <para>o Copy is assigned a library system specific, or one agreed upon\r | |
140 | by Sitka consortia or library federation, circulation modifier that\r | |
141 | has correct circulation parameters associated with it. </para>\r | |
142 | </listitem>\r | |
143 | <listitem>\r | |
144 | <para>o Library staff can create a cataloguing item record template with\r | |
145 | all required attributes pre-loaded, thereby facilitating data entry\r | |
146 | and consistency when creating fixed set of records.</para>\r | |
147 | </listitem>\r | |
148 | </itemizedlist>\r | |
149 | </listitem>\r | |
150 | </itemizedlist>\r | |
151 | \r | |
152 | </simplesect>\r | |
153 | \r | |
154 | <simplesect>\r | |
155 | <title>Workflow Proposal</title>\r | |
156 | <procedure>\r | |
157 | <step>\r | |
158 | <para>Create fixed set of brief bibliographic records, with attached volume and\r | |
159 | copy records.</para>\r | |
160 | </step>\r | |
161 | <step>\r | |
162 | <para>As ILL items are received at central branch, staff key in basic\r | |
163 | bibliographic data into MARC record in capital letters and flag as\r | |
164 | <emphasis>ILL</emphasis> in title statement. If using generic\r | |
165 | bibliographic data this is not required.</para>\r | |
166 | </step>\r | |
167 | <step>\r | |
168 | <para>Staff place a title level hold on MARC record for requesting\r | |
169 | patron.</para>\r | |
170 | </step>\r | |
171 | <step>\r | |
172 | <para>Staff check item in to put it in transit to branch, or to capture hold if\r | |
173 | patron is at central branch. </para>\r | |
174 | </step>\r | |
175 | <step>\r | |
176 | <para>Staff send item to branch or to holds/ILL shelf at main branch.</para>\r | |
177 | </step>\r | |
178 | <step>\r | |
179 | <para>Branch staff checks in item to capture hold and contact patron.</para>\r | |
180 | </step>\r | |
181 | <step>\r | |
182 | <para>Branch staff checks out item to patron.</para>\r | |
183 | </step>\r | |
184 | <step>\r | |
185 | <para>Patron returns item and staff check it in to either put it in transit back\r | |
186 | to main branch, or if returned at main branch to close transaction.</para>\r | |
187 | </step>\r | |
188 | <step>\r | |
189 | <para>Staff at main branch check item in to close transaction and return item to\r | |
190 | originating library.</para>\r | |
191 | </step>\r | |
192 | <step>\r | |
193 | <para> As new ILL items are received staff replace existing bibliographic\r | |
194 | data (title and author)with new bibliographic data and repeat cycle. If using generic bliographic data this step is not required.</para>\r | |
195 | </step>\r | |
196 | \r | |
197 | \r | |
198 | </procedure>\r | |
199 | \r | |
200 | \r | |
201 | </simplesect>\r | |
202 | \r | |
203 | <simplesect>\r | |
204 | <title>Summary</title>\r | |
205 | <para>When the ILL item is returned, none of these records are deleted. The\r | |
206 | bibliographic record is edited with the title, author, and originating library of\r | |
207 | the new item when the corresponding barcode is reused. If generic bibliographic data\r | |
208 | is used, editing is not required.</para>\r | |
209 | <para>Solution #2 allows the item to be tracked from receipt, through any transfers\r | |
210 | between branches, and eliminates the need for circulation staff to key in any data\r | |
211 | when the circulation occurs.</para>\r | |
212 | <para>Solution #2 is best for multi-branch libraries, or at single branch sites where\r | |
213 | circulation staff are not responsible for keying in item information.</para>\r | |
214 | <para>Solution #2 allows for email notification to patron when hold is captured.</para>\r | |
215 | \r | |
216 | <note>\r | |
217 | <para>One issue with Solution #2 using actual bibliographic title and author data is\r | |
218 | that returned ILL items with outstanding fines will display on the patron record\r | |
219 | with the current title of the MARC record under which their ILL circulated. For\r | |
220 | example, if a barcode is re-used while a patron still has fines attached to that\r | |
221 | copy, patron’s record will be updated and contain the new title information, not\r | |
222 | the information for the item they originally borrowed. </para>\r | |
223 | <para>Sitka support team recommends ILL and circulation staff be aware of this and\r | |
224 | adopt procedures to manage fines on ILLs at time of check-in if using actual\r | |
225 | bibliographic data in brief MARC records. This could include voiding the\r | |
226 | circulation fine and creating a “grocery” bill with all relevant details in\r | |
227 | note, or collecting payment at time of check-in when possible. </para>\r | |
228 | <para>Sites using generic data will not have to manage this as fines on patron\r | |
229 | account would reflect title BFN Inter Library Loan Book, for example. </para>\r | |
230 | </note>\r | |
231 | \r | |
232 | </simplesect>\r | |
233 | <simplesect>\r | |
234 | <title>Appendix</title>\r | |
235 | <formalpara>\r | |
236 | <title>LAC Code</title>\r | |
237 | <para>Library and Archives Canada <link\r | |
9906b6c5 JP |
238 | xlink:href="http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1"\r |
239 | xlink:title="http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1"\r | |
240 | >http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1</link></para>\r | |
ae8b9281 RJ |
241 | </formalpara>\r |
242 | \r | |
9906b6c5 JP |
243 | <para>Quick and easy list for BC here <link\r |
244 | xlink:href="https://bc.libraries.coop/support/institution-codes/"\r | |
245 | xlink:title="https://bc.libraries.coop/support/institution-codes/"\r | |
246 | >https://bc.libraries.coop/support/institution-codes/</link></para>\r | |
ae8b9281 RJ |
247 | </simplesect>\r |
248 | \r | |
249 | \r | |
250 | \r | |
251 | \r | |
c169396d | 252 | </section> -->\r |
ae8b9281 | 253 | \r |
9f25c74c JP |
254 | <section xml:id="ill-pre-cats">\r |
255 | <title>Interlibrary Loans via Pre-cats</title>\r | |
a78657f8 JP |
256 | \r |
257 | <para>\r | |
a0d37b98 JP |
258 | Pre-cats, also known as pre-catalogued items, are temporary records created at the time of check out.</para>\r |
259 | <para>Pre-cats can be used for incoming interlibrary loans that are not between two Interlibrary Connect \r | |
260 | libraries.</para> \r | |
a78657f8 | 261 | \r |
a0d37b98 JP |
262 | <simplesect xml:id="ill-pre-cats-workflow">\r |
263 | <title>Workflow</title>\r | |
a78657f8 JP |
264 | <para>The workflow for receiving interlibrary loans using pre-cats is:</para>\r |
265 | \r | |
266 | <procedure>\r | |
267 | <step>\r | |
268 | <para>Follow your normal procedures for receiving the item in your interlibrary loan system, such as Outlook or fILL.\r | |
269 | </para>\r | |
270 | </step>\r | |
271 | <step>\r | |
272 | <para>\r | |
273 | Contact the patron manually.\r | |
274 | </para>\r | |
275 | </step>\r | |
276 | <step>\r | |
277 | <para>\r | |
26530137 | 278 | When the patron comes to check out the item retrieve the patron’s account.\r |
a78657f8 JP |
279 | </para>\r |
280 | </step>\r | |
281 | <step>\r | |
282 | <para>\r | |
283 | Scan the barcode for the pre-cat. A pop up will appear.\r | |
284 | </para>\r | |
285 | </step>\r | |
286 | <step>\r | |
287 | <para>\r | |
26530137 | 288 | Click <guibutton>Pre-catalogued</guibutton>.\r |
a78657f8 JP |
289 | </para>\r |
290 | </step>\r | |
291 | <step>\r | |
292 | <para>\r | |
293 | Fill in the fields as per your library’s policies.\r | |
294 | </para>\r | |
295 | <para>\r | |
296 | Title and Circ Modifier need to be filled in.\r | |
297 | </para>\r | |
298 | <para>\r | |
26530137 JP |
299 | Some libraries enter the title all in CAPS so staff can see at a glance in the <guilabel>Items Out</guilabel>\r |
300 | screen that the item is an interlibrary loan. You will need to know which circ modifier(s) your library uses.\r | |
a78657f8 JP |
301 | </para>\r |
302 | </step>\r | |
303 | <step>\r | |
304 | <para>\r | |
26530137 | 305 | Click <guibutton>Check Out</guibutton>.\r |
a78657f8 JP |
306 | </para>\r |
307 | </step>\r | |
308 | <step>\r | |
309 | <para>\r | |
26530137 | 310 | The item is now checked out to the patron. If you use barcodes on cards, attach the barcode to the item and give the item to the patron.\r |
a78657f8 JP |
311 | </para>\r |
312 | </step>\r | |
313 | <step>\r | |
314 | <para>\r | |
26530137 | 315 | When the item is returned scan the barcode in the <guilabel>Check In</guilabel> screen. \r |
a78657f8 JP |
316 | </para>\r |
317 | <para>\r | |
26530137 | 318 | If you use barcode cards have a designated spot to put returned cards so they can be reused.\r |
a78657f8 JP |
319 | </para>\r |
320 | </step>\r | |
321 | <step>\r | |
322 | <para>\r | |
26530137 JP |
323 | If you don’t re-use the barcode, scan the barcode into the <guilabel>Item Status</guilabel> screen.</para>\r |
324 | <para>Highlight the item and select <menuchoice><guimenu>Actions for Cataloguers</guimenu>\r | |
325 | <guimenuitem>Delete Items</guimenuitem></menuchoice>.</para>\r | |
326 | </step>\r | |
327 | <step>\r | |
328 | <para>\r | |
a78657f8 JP |
329 | Return the item using your normal procedures via Outlook, fILL etc.\r |
330 | </para>\r | |
331 | </step>\r | |
332 | </procedure>\r | |
333 | \r | |
a0d37b98 JP |
334 | <note><para>When using pre-cats we recommend that you have a set of barcodes that you recycle to avoid creating hundreds of pre-cats in the system. \r |
335 | These pre-cat barcodes may take the form of barcoded cards that are scanned and attached to the \r | |
336 | interlibrary loan while it circulates.</para></note>\r | |
337 | \r | |
338 | </simplesect>\r | |
339 | \r | |
340 | <simplesect xml:id="ill-pre-cats-tips">\r | |
341 | <title>Tips</title>\r | |
342 | \r | |
a78657f8 JP |
343 | <para>Some important things to remember about pre-cats are:</para>\r |
344 | <itemizedlist>\r | |
345 | <listitem>\r | |
346 | <para>\r | |
26530137 | 347 | They are temporary and not visible in the OPAC\r |
a78657f8 JP |
348 | </para>\r |
349 | </listitem>\r | |
350 | <listitem>\r | |
351 | <para>\r | |
26530137 | 352 | A pre-cat only really exists as long as it is checked out\r |
a78657f8 JP |
353 | </para>\r |
354 | </listitem>\r | |
355 | <listitem>\r | |
356 | <para>\r | |
26530137 | 357 | Make sure you chose the correct circulation modifier to ensure that the item follows the correct circulation policy\r |
a78657f8 JP |
358 | </para>\r |
359 | </listitem>\r | |
360 | <listitem>\r | |
361 | <para>\r | |
26530137 | 362 | Don’t use the barcode on the item. This causes problems if the item belongs to another Sitka library.</para>\r |
a78657f8 JP |
363 | </listitem>\r |
364 | </itemizedlist>\r | |
a0d37b98 | 365 | </simplesect>\r |
a78657f8 | 366 | \r |
9f25c74c | 367 | </section>\r |
ae8b9281 | 368 | \r |
9f25c74c JP |
369 | <section xml:id="ill-brief-records">\r |
370 | <title>Interlibrary Loans via Brief MARC Records</title>\r | |
371 | \r | |
372 | <para>Items received through interlibrary loan can be circulated to patrons through the use of brief MARC records. This method enables a library to assign data entry associated with interlibrary loans\r | |
373 | to a particular staff member or members as well as taking advantage of Evergreen's automatic email and text message notifications. </para>\r | |
374 | \r | |
375 | \r | |
376 | <simplesect xml:id="ill-record-req">\r | |
377 | <title>Record Requirements</title>\r | |
378 | \r | |
379 | <para>We recommend the following best practice for creating a fixed set of records to\r | |
380 | be used for interlibrary loans. Some sites may chose to enter bibliographic information for the particular item in the fields while others may prefer to use generic data as the actual data is retained in \r | |
381 | their 3rd party interlibrary loan software.</para>\r | |
382 | \r | |
383 | <itemizedlist>\r | |
384 | \r | |
385 | <listitem>\r | |
386 | <para>Bibliographic records should include the following fields and text should be\r | |
387 | in upper case to further identify the record as a brief ILL record:</para>\r | |
388 | <itemizedlist>\r | |
389 | <listitem>\r | |
390 | <para>100 $a for author's full name</para>\r | |
391 | </listitem>\r | |
392 | <listitem>\r | |
19b30e91 | 393 | <para>245 $a for title, and 245 $b containing <emphasis>ILL</emphasis></para>\r |
9f25c74c JP |
394 | </listitem>\r |
395 | <listitem>\r | |
396 | <para>599 $aILL with a $9 containing the Library Archives Canada code of the library who created the record.</para>\r | |
397 | <mediaobject>\r | |
398 | <alt>MARC view of brief record</alt>\r | |
399 | <imageobject>\r | |
400 | <imagedata scalefit="0" fileref="media/practice-1.png"/>\r | |
401 | </imageobject>\r | |
402 | </mediaobject>\r | |
403 | \r | |
404 | </listitem>\r | |
405 | \r | |
406 | </itemizedlist>\r | |
407 | <para>These records can be created using the <guilabel>sitka_book_rda</guilabel> MARC template.\r | |
408 | This template is available by selecting <menuchoice>\r | |
409 | <guimenu>Cataloguing</guimenu>\r | |
410 | <guimenuitem>Create New Marc Record</guimenuitem>\r | |
19b30e91 | 411 | </menuchoice> and choosing appropriate template from the drop down menu.</para>\r |
9f25c74c JP |
412 | </listitem>\r |
413 | \r | |
414 | <listitem>\r | |
19b30e91 | 415 | <para>Volume records should use 'ILL' for the call number. This call number does not need to\r |
9f25c74c JP |
416 | be changed on a per-loan basis.</para>\r |
417 | <itemizedlist>\r | |
418 | <listitem>\r | |
419 | <para>In multi-branch systems with centralized interlibrary loan the Owning library/call number should be the branch handling interlibrary loan.</para>\r | |
420 | </listitem>\r | |
19b30e91 JP |
421 | </itemizedlist>\r |
422 | </listitem>\r | |
423 | <listitem>\r | |
424 | <para>Copy records should use either be a real barcode affixed to a card that is used for checkout or a barcode that can be easily written onto a \r | |
9f25c74c | 425 | card or wrapper that circulates with the item.</para>\r |
19b30e91 | 426 | <itemizedlist>\r |
9f25c74c | 427 | <listitem>\r |
26530137 JP |
428 | <para>A shelving location called ILL should be created and assigned to copies attached \r |
429 | to these MARC records. This shelving location should be set up to be holdable, but not\r | |
9f25c74c | 430 | OPAC visible. This will prevent patrons from discovering these brief\r |
26530137 JP |
431 | records in the OPAC. Multi-branch systems with centralized interlibrary loan \r |
432 | should created a system level shelving location</para>\r | |
9f25c74c JP |
433 | </listitem>\r |
434 | <listitem>\r | |
435 | <para>Library staff can create a cataloguing item record template with\r | |
436 | all required attributes pre-loaded, thereby facilitating data entry\r | |
19b30e91 | 437 | and consistency when creating fixed set of records.</para>\r |
9f25c74c | 438 | </listitem>\r |
19b30e91 JP |
439 | </itemizedlist>\r |
440 | </listitem>\r | |
441 | <listitem>\r | |
9f25c74c | 442 | <para>If interlibrary loans should follow a circulation policy that is different from the library's default circulation policy library staff should ensure that a policy exists and contact Support \r |
19b30e91 JP |
443 | if a policy needs to be created. Support recommends using the circulation modifiers \r |
444 | "ill-no-renewal" and/or "interlibrary-loan".</para>\r | |
9f25c74c | 445 | </listitem>\r |
19b30e91 JP |
446 | <listitem>\r |
447 | <para>Staff can keep track of which records are available for use by putting all of the \r | |
448 | items into a copy bucket. COPY BUCKET LINK HERE</para>\r | |
449 | </listitem>\r | |
9f25c74c | 450 | </itemizedlist>\r |
19b30e91 | 451 | \r |
9f25c74c JP |
452 | \r |
453 | </simplesect>\r | |
454 | \r | |
126cacd5 | 455 | <simplesect xml:id="ill-record-workflow">\r |
9f25c74c JP |
456 | <title>Workflow</title>\r |
457 | \r | |
458 | <para>Once a set of brief MARC records have been created, with volumes and copies attached, this workflow should be followed:</para>\r | |
459 | \r | |
460 | <procedure>\r | |
461 | <step>\r | |
462 | <para>As ILL items are received at central branch, staff key in basic\r | |
463 | bibliographic data into MARC record in capital letters in the 245 field. If using generic\r | |
464 | bibliographic data this is not required.</para>\r | |
465 | </step>\r | |
466 | <step>\r | |
467 | <para>Staff place a title level hold on the MARC record for the requesting\r | |
468 | patron ensuring to select the correct pickup location and the notification option requested by the patron.</para>\r | |
469 | </step>\r | |
470 | <step>\r | |
471 | <para>Staff check the item in using the barcode associated with the correct MARC record. Staff should never use the barcode assigned to the item by home library as the item may exist in the Sitka database.</para>\r | |
472 | <para>A hold slip will be generated and the item status will change to <guilabel>On holds shelf</guilabel>. If the patron has requested notification via email or text the notification will be sent; patrons \r | |
473 | requesting notification via phone need to be contacted. The item is placed on the Holds/ILL shelf.</para> \r | |
474 | <para>If the patron has requested pickup at a different branch a transit slip will be generated and the item status changed to <guilabel>In transit</guilabel>. The item should be shipped to the \r | |
475 | appropriate branch.</para>\r | |
476 | </step>\r | |
477 | <step>\r | |
478 | <para>Branch staff checks in item to capture hold. If the patron has requested notification via email or text the notification will be sent; patrons \r | |
479 | requesting notification via phone need to be contacted. The item is placed on the Holds/ILL shelf. </para>\r | |
480 | </step>\r | |
481 | <step>\r | |
482 | <para>Staff checks out the item to the patron and ensures that the ILL barcode is attached to the item or written on the wrappings that circulate with the item.</para>\r | |
483 | </step>\r | |
484 | <step>\r | |
485 | <para>When the patron returns the item staff check it in using the ILL barcode. The item may be sent into transit back to the branch that handles interlibrary loans where it will be checked in again.</para>\r | |
486 | </step>\r | |
487 | <step>\r | |
488 | <para>Staff return the item to its originating library via their 3rd party interlibrary loan software.</para>\r | |
489 | </step>\r | |
490 | <step>\r | |
491 | <para> As new ILL items are received staff replace existing bibliographic\r | |
26530137 | 492 | data (title and author) with new bibliographic data and repeat cycle. If using generic bibliographic data this step is not required.</para>\r |
9f25c74c JP |
493 | </step>\r |
494 | \r | |
495 | </procedure>\r | |
496 | \r | |
497 | <note><para>One issue with using actual bibliographic title and author data is\r | |
498 | that returned ILL items with outstanding fines will display on the patron record\r | |
499 | with the current title of the MARC record under which their interlibrary loan circulated. For\r | |
500 | example, if a barcode is re-used while a patron still has fines attached to that\r | |
501 | copy, patron’s record will be updated and contain the new title information, not\r | |
502 | the information for the item they originally borrowed. </para>\r | |
503 | <para>Support recommends ILL and circulation staff be aware of this and\r | |
504 | adopt procedures to manage fines on ILLs at time of check-in if using actual\r | |
505 | bibliographic data in brief MARC records. This could include voiding the\r | |
506 | circulation fine and creating a <guilabel>grocery</guilabel> bill with all relevant details in a\r | |
507 | note, or collecting payment at time of check-in when possible. </para>\r | |
508 | <para>Sites using generic data will not have to manage this as fines on patron\r | |
509 | account would reflect the title as Interlibrary Loan Book, for example. </para>\r | |
510 | \r | |
511 | </note>\r | |
512 | \r | |
513 | \r | |
514 | </simplesect>\r | |
515 | \r | |
516 | <simplesect>\r | |
517 | <title>Appendix</title>\r | |
518 | <formalpara>\r | |
519 | <title>LAC Code</title>\r | |
520 | <para>Library and Archives Canada <link\r | |
9906b6c5 JP |
521 | xlink:href="http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1"\r |
522 | xlink:title="http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1"\r | |
523 | >http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1/d=1</link></para>\r | |
9f25c74c JP |
524 | </formalpara>\r |
525 | \r | |
9906b6c5 JP |
526 | <para>Quick and easy list for BC here <link\r |
527 | xlink:href="https://bc.libraries.coop/support/institution-codes/"\r | |
528 | xlink:title="https://bc.libraries.coop/support/institution-codes/"\r | |
529 | >https://bc.libraries.coop/support/institution-codes/</link></para>\r | |
9f25c74c JP |
530 | </simplesect>\r |
531 | \r | |
532 | \r | |
533 | \r | |
534 | \r | |
535 | </section>\r | |
536 | \r | |
537 | <section xml:id="ill-connect">\r | |
538 | <title>Interlibrary Loans via Interlibrary Connect</title>\r | |
539 | \r | |
a78657f8 JP |
540 | <para>Interlibrary Loan Connect uses Evergreen’s hold and transit functionality to facilitate interlibrary \r |
541 | loans without requiring 3rd party software to track the interlibrary loans. </para>\r | |
542 | \r | |
543 | \r | |
3f683d2f JP |
544 | <simplesect xml:id="ill-connect-workflow">\r |
545 | <title>Workflow</title> \r | |
546 | \r | |
a78657f8 JP |
547 | <procedure>\r |
548 | <para>Borrowing Library</para>\r | |
549 | <step>\r | |
550 | <para>A patron searches the OPAC and places a hold.\r | |
551 | </para>\r | |
552 | </step>\r | |
553 | <step>\r | |
554 | <para>\r | |
555 | The patron specifies the Pickup library and how they would like to be notified.\r | |
556 | </para>\r | |
557 | </step>\r | |
4fb51276 | 558 | </procedure>\r |
a78657f8 | 559 | \r |
4fb51276 | 560 | <procedure>\r |
a78657f8 JP |
561 | <para>Lending Library</para>\r |
562 | <step>\r | |
563 | <para>\r | |
564 | Libraries in the zone print their hold pull list. You can tell by the Pickup Library column which items are being \r | |
565 | pulled for local holds and which ones are to fill interlibrary loans with pickup.\r | |
566 | </para>\r | |
567 | </step>\r | |
568 | <step>\r | |
569 | <para>\r | |
570 | Staff check in the items which generate hold slips for local holds and hold in transit slips for interlibrary loans.\r | |
571 | </para>\r | |
572 | </step>\r | |
573 | <step>\r | |
574 | <para>\r | |
575 | The interlibrary loans are set aside/give to an ILL clerk to be packed and sent to the appropriate library.\r | |
576 | </para>\r | |
577 | </step>\r | |
4fb51276 | 578 | </procedure>\r |
a78657f8 | 579 | \r |
4fb51276 | 580 | <procedure>\r |
a78657f8 JP |
581 | <para>Borrowing Library</para>\r |
582 | <step>\r | |
583 | <para>\r | |
584 | Staff receive and unpack interlibrary loans.\r | |
585 | </para>\r | |
586 | </step>\r | |
587 | <step>\r | |
588 | <para>\r | |
589 | Connect loans are checked in which generates a hold slip, changes the item status to\r | |
590 | “On holds shelf”, and automatically notifies the patron if they requested notification via email or text.\r | |
591 | </para>\r | |
592 | </step>\r | |
593 | <step>\r | |
594 | <para>\r | |
595 | The item is placed on the hold shelf.\r | |
596 | </para>\r | |
597 | </step>\r | |
598 | <step>\r | |
599 | <para>\r | |
600 | Item is checked out as normal to the patron.\r | |
601 | </para>\r | |
602 | </step>\r | |
603 | <step>\r | |
604 | <para>\r | |
605 | When the item is returned, staff check in the item normally. A prompt to create a slip will appear. \r | |
606 | It is very important to read the prompt carefully as there are three possible prompts. One, the system is generating a transit \r | |
607 | slip to send the item home, two, the system is generating a new hold in transit slip to send the item to another library to fill \r | |
608 | an interlibrary loan, or three, the system is generating a new hold slip to fill an interlibrary loan for another of your patrons.\r | |
609 | </para>\r | |
610 | </step>\r | |
611 | <step>\r | |
612 | <para>\r | |
613 | Package and ship the item to its new destination or place it back on your hold shelf if there is a hold for a new patron.\r | |
614 | </para>\r | |
615 | </step>\r | |
4fb51276 | 616 | </procedure>\r |
a78657f8 | 617 | \r |
4fb51276 | 618 | <procedure>\r |
a78657f8 JP |
619 | <para>Owning Library</para>\r |
620 | \r | |
621 | <step>\r | |
622 | <para>\r | |
623 | Receive and unpack the item.\r | |
624 | </para>\r | |
625 | </step>\r | |
626 | <step>\r | |
627 | <para>\r | |
628 | Check the item in. If the item has not been requested to fill another interlibrary loan or hold it will be changed to the \r | |
629 | status of reshelving and can be reshelved.</para>\r | |
630 | </step>\r | |
631 | </procedure>\r | |
a0d37b98 JP |
632 | </simplesect>\r |
633 | \r | |
634 | <simplesect xml:id="ill-connect-tips">\r | |
635 | <title>Tips</title>\r | |
a78657f8 JP |
636 | \r |
637 | <para>Some important things to remember about Interlibrary Connect are:</para>\r | |
638 | <itemizedlist>\r | |
639 | <listitem>\r | |
640 | <para>\r | |
26530137 | 641 | You determine what items from your library will participate \r |
a78657f8 JP |
642 | </para>\r |
643 | </listitem>\r | |
644 | <listitem>\r | |
645 | <para>\r | |
26530137 | 646 | Your hold policies can be set up to use Age Hold Protection to prevent your brand new items from being used for interlibrary loans\r |
a78657f8 JP |
647 | </para>\r |
648 | <para>\r | |
26530137 | 649 | Let Support know if items are allowing Connect holds or not allowing Connect that should, your policies may need to be tweaked\r |
a78657f8 JP |
650 | </para>\r |
651 | </listitem>\r | |
652 | <listitem>\r | |
653 | <para>\r | |
26530137 | 654 | Your OPAC will allow patrons to search all libraries in your Connect zone\r |
a78657f8 JP |
655 | </para>\r |
656 | </listitem>\r | |
657 | <listitem>\r | |
658 | <para>\r | |
26530137 | 659 | The item follows the policies of the check out library when it is checked out\r |
a78657f8 JP |
660 | </para>\r |
661 | </listitem>\r | |
662 | <listitem>\r | |
663 | <para>\r | |
26530137 | 664 | Pre-due and overdue notices are generated from the check out library\r |
a78657f8 JP |
665 | </para>\r |
666 | </listitem>\r | |
667 | <listitem>\r | |
668 | <para>\r | |
26530137 | 669 | To ensure your statistics are accurate the only time a transit on an interlibrary connect item should be aborted is if the lending library decides not to lend the item after sending it in transit in Evergreen\r |
a78657f8 JP |
670 | there are a number of report templates under SITKA_templates -> Intra-federation ILL stats that you can run to get your ILL stats\r |
671 | </para>\r | |
672 | </listitem>\r | |
673 | <listitem>\r | |
674 | <para>\r | |
675 | You may also want to run some of the reports found under SITKA_templates -> Holds to catch holds that are not being filled. \r | |
676 | </para>\r | |
677 | </listitem>\r | |
678 | <listitem>\r | |
679 | <para>\r | |
680 | You must use the barcode on the item. \r | |
681 | </para>\r | |
682 | </listitem>\r | |
683 | </itemizedlist>\r | |
684 | \r | |
3f683d2f JP |
685 | </simplesect>\r |
686 | \r | |
a78657f8 JP |
687 | <simplesect xml:id="ill-connect-closure">\r |
688 | \r | |
3f683d2f | 689 | <title>ILL Closures</title>\r |
a78657f8 JP |
690 | \r |
691 | <para>If libraries wish to close interlibrary loans for a period of time you need to submit a ticket to Support. \r | |
692 | Support will update your hold policies to prevent your patrons from placing holds on items belonging to other libraries as \r | |
693 | well as block patrons from other libraries from placing holds on items belonging to your library. Patrons will be able to place \r | |
694 | holds if they select the owning library of the item as the pickup up library. Currently it is not possible to post a message \r | |
695 | on the OPAC to indicate to patrons that interlibrary holds are temporarily unavailable. Patrons are able to search the entire \r | |
696 | zone but if they attempt to place an interlibrary loan hold they will get a message indicating that the hold cannot be placed.</para>\r | |
697 | \r | |
698 | <para>Alternatively, staff can simply not pull items from the pull list with a pickup library other than their own.\r | |
699 | The hold will be re-targeted to another copy when the hold targeter next runs (assuming your library doesn’t own the only copy.)\r | |
700 | </para>\r | |
701 | </simplesect>\r | |
702 | \r | |
703 | </section>\r | |
704 | \r | |
705 | <section xml:id="ill-library-accounts">\r | |
706 | <title>Patron Accounts for Libraries</title>\r | |
707 | \r | |
26530137 JP |
708 | <para>The patron permission profiles for ILL (PL ILL, Post-Sec ILL, etc.) are intended for accounts\r |
709 | created for other libraries. These accounts allow staff to check out items going to that library \r | |
710 | so the items show as checked out in Evergreen and staff can easily follow up with a library about\r | |
711 | all of the items that have been sent to them via interlibrary loan. If their ILL email is set in the \r | |
712 | account the system will send them pre-due and overdue email notifications.</para>\r | |
713 | \r | |
a78657f8 | 714 | \r |
26530137 JP |
715 | <simplesect xml:id="Workflow">\r |
716 | <title>Workflow</title>\r | |
a78657f8 | 717 | \r |
26530137 | 718 | <para>Once accounts have been created this workflow can be followed for outgoing interlibrary loans.</para>\r |
a78657f8 | 719 | \r |
26530137 JP |
720 | <procedure>\r |
721 | <step>\r | |
722 | <para>Follow the normal procedures through your 3rd party ILL system to identify the items \r | |
723 | that need to be pulled to be sent to other libraries.\r | |
724 | </para>\r | |
725 | </step>\r | |
726 | <step>\r | |
727 | <para>\r | |
728 | Pull the items from the shelf.\r | |
729 | </para>\r | |
730 | </step>\r | |
731 | <step>\r | |
732 | <para>\r | |
733 | In Evergreen retrieve the patron account for the library.\r | |
734 | </para>\r | |
735 | <para>You may want to have a naming convention so you can easily retrieve the accounts via \r | |
736 | the barcode or patron search.</para>\r | |
737 | </step>\r | |
738 | <step>\r | |
739 | <para>\r | |
740 | Check the applicable items out to library account.</para>\r | |
741 | <para>The system will follow general patron circulation policies unless the library has had Support \r | |
742 | set up specific policies for ILL. You may also want to set up ILL specific group penalty thresholds \r | |
743 | to allow more checkouts to an ILL account than to a normal patron account.\r | |
744 | </para>\r | |
745 | </step>\r | |
746 | <step>\r | |
747 | <para>\r | |
a78657f8 | 748 | Follow the normal procedures through your 3rd party ILL system to send the item to the borrowing library.\r |
a78657f8 | 749 | </para>\r |
26530137 JP |
750 | </step>\r |
751 | <step>\r | |
752 | <para>\r | |
753 | When the item is sent back follow your normal procedures through your 3rd party ILL system to receive the item.\r | |
754 | </para>\r | |
755 | </step>\r | |
756 | <step>\r | |
757 | <para>\r | |
758 | The item will either have the status of checked out or in-transit in Evergreen. Check the item in to set\r | |
759 | the status to Reshelving.\r | |
760 | </para>\r | |
761 | </step>\r | |
762 | </procedure>\r | |
763 | </simplesect>\r | |
a78657f8 | 764 | \r |
9f25c74c | 765 | </section>\r |
ae8b9281 RJ |
766 | \r |
767 | \r | |
768 | \r | |
769 | </chapter>\r |