Borrow Direct Implementation Notes

This site contains a record of decisions made during the Dartmouth implementation of Borrow Direct.

Patron access


I forgot to mention one important systems-related issue when we spoke yesterday, and that has to do with patron authentication for entry into the system.

All three existing sites authenticate patrons for entry into the Borrow Direct system. The standard method is to require patrons to enter their barcode, institutional id, library id, or ssn (whichever you use as the key to the patron record) on a Borrow Direct login screen, and URSA (Borrow Direct) connects to the patron file and determines that the patron is in good standing and eligible for the service.

The service agreement among the current partners allows all current faculty, staff, and students of each institution to use Borrow Direct. "Courtesy borrowers" or other categories of patrons are not eligible for the service, although they may log in as "guests" and search the catalogs, but not place requests. We generally have agreed that anyone locally eligible for ILL services is eligible for Borrow Direct - and this varies somewhat at each campus. Bottom line - You will have to provide epixtech with a list of codes that correspond to the eligible patron categories. This is how Penn patrons currently are authenticated for Borrow Direct use.

Columbia uses a campus-wide authentication system for all restricted services built on Kerberos that works a little differently, but with the same result. I'm sure there is some local programming required, as well as some customization from epixtech. Yale is also implementing a similar campus authentication system.

We can talk in greater detail about this issue later, but I just wanted to bring it up for your consideration.


Materials Lent

Overall the type of material lent is books. More specifically, BD partners lend oversize and folio materials if they are in good condition and in a circulating location. Office copies and Permanent Reserve (class dups) copies are not lent.

Non-book materials shelved in the same "location" as book materials

The BD system excludes non-books on the assumption that their OPAC location would indicate their type. [Excepting for serials/journals which are sliced off the top based on the mat type in the MARC record leader byte.] It also excludes based on the OPAC STATUS value. From my notes "The URSA software uses z39.50 to connect to the catalog and identify materials for possible loan. The information it can consult as to whether an item can be lent is limited to that which displays in a regular OPAC display. Hence, our restriction to using OPAC Location and OPAC Status."

We had a concern that some "stacks" locations would have books and other stuff. For instance Evans Map Room as an OPAC location is applied both to books and maps shelved at that location.

Howard Pasternack at Brown writes

We have the same problem with oversize art books. The location is Rock for both regular size and oversize, but the oversize don't circulate. We were thinking of tinkering with the location symbol and putting something innocuous like a period at the end of the location so that we would have both "Rock" and "Rock." Other than a status message which no one here is happy with, there doesn't seem to be anything else to do. Another option would be to just let things alone and say no the request.

The DHMC decision

The problem

Though there are 2,000 potential DMS faculty, many have not registered with the library for Inno privileges - they have no need or desire to do so unless they are checking material out of the Libraries. Since we don't deliver books to users, they are only in Inno if they are here and using the Libraries in person. If they have registered for check-out privileges, they are supposed to be entered like any other Dartmouth faculty member. No special coding in Inno, indistinguishable from other College faculty. (The 900 full-time faculty (included in the 2,000) are automatically put in Inno, I believe, through the HR dump each term.)

Residents (house staff) and Post Docs registering at Matthews-Fuller get coded with the Stat Cat of "F" for faculty, but with a descriptor of "H". This is a group that should be considered Dartmouth graduate students, but would be deleted if you automatically "not out" the H category. Again, they'll only be in Inno if they are using the Libraries for check-out - it's unlikely for the very few non-Lebanon-based residents to be a factor here.

Other professional staff (nurses, pharmacists, administrators) without DMS faculty appointments are coded with a Stat Cat of "A" and a Descriptor of "H". They would be deleted from BorrowDirect in your scenario.

Non-professional staff are coded with a Stat Cat of "S" and a Descriptor of "H". They would be deleted from BorrowDirect in your scenario.

Assuming that the basis for your BorrowDirect eligibility list is Inno, and that you are going to use the descriptor "H" to "not out" "DHMC" users, the biggest issue for us are the residents, and the occasional mis-coded faculty member.

The solution

Create new PTYPES in Innopac for ineligible DHMC borrowers. Create new patron record templates to support the new ptypes and instruct Biomedical circ staff on which templates apply to which patrons.

Jennifer added two new ptypes to Innopac to support Borrow Direct.

035 > DHMC Faculty/AP-I
036 > DHMC AP-II/ServicePlease modify the Loan Rule Determiner table as follows:

Add ptype 35 to any rule that includes ptype 2.
Add ptype 36 to any rule that includes ptype 5.

Circ will modify the Patron Blocks table as follows:

Create an entry for ptype 35 by copying the entry for ptype 2.
Create an entry for ptype 36 by copying the entry for ptype 5.

In the coming days we will be modifying the patron records for some DHMC folks to use the new ptypes. We'll do this via a batch update. Debra and Bethany Bryden will be working on creating new record templates to support the new ptypes and will distribute instructions to Biomed staff who create patron records on how to choose the right template.

The batch loads from HRMS and SIS are not affected by the new ptypes.

Last Updated 4/16/03 JKM