Search:

Worldwide (English) Change

WorldCat Resource Sharing support Documentation OCLC ILL Direct Request Planning Guide Comments? Abstract & revision history About This Guide Part 1 -Description and Planning 1. Introducing the OCLC Direct Request Service 2. External System and OCLC ILL Considerations 3. Direct-to-Profile Processing Option 3.1 The Direct-to-Profile Process 3.2 The OCLC FirstSearch/ILL Direct Request Link 3.3 Profiles 3.4 Profile Worksheet and Examples 3.5 Monitoring Direct-to-Profile Processing 4. Direct-to-Lender Processing Option 5. Direct-to-Review File Requirements 7. Signup and Training Part 2 - Technical Specifications 8. ISO-10161 Overview 9. Specifications and Mapping 10. Technical Requirements 10.1 Direct-to-Profile Requirements 10.2 Direct-to-Lender Requirements 10.3 Direct-to-Review File Requirements 11. OCLC Responses Appendix Implementation Checklist ILL Glossary

OCLC ILL ME for Windows software uses slashes (/) to format addresses. Use these guidelines for including slashes within patron address elements.

A patron may have a home address (homeAddressInfo) and a work address (workAddressInfo). You may encode each element either as a string or as a postalAddress. If coded as a string, do not insert slashes. If both a home address and work address are present, then workAddressInfo precedes homeAddressInfo in the PATRON ADDR field, separated by 2 slashes (//).

Do not insert slashes if the data type is string.

If the request contains neither homeAddressInfo or a workAdddressInfo, use multiple strings with a slash after each string:

• streetAndNumber
• additionalInfo
• boxAddress

If coded as a postalAddress, put a slash after the following elements. Existing slashes within these elements are converted to hyphens:

• nameOfPersonOrInstitution
• extendedPostalDeliveryAddress
• streetAndNumber
• postOfficeBox

Back to OCLC ILL Direct Request Planning Guide