Test records for Summit: Patron records

Alliance members keep test patron records in the local system, to help with

... testing the local circ system (a variety of patron types, with and without expiration dates and other fixed and variable fields to test loan rules, printing notices, etc.);

... testing Summit Borrowing; and

... testing Summit Borrowing with new members.

Members also have "Loaner" patron records for other Alliance members to use in testing Summit Borrowing (requesting, etc.).

Testing Summit Borrowing

To test Summit Borrowing (SB), members make at least one test record, and may identify additional test records already prepared for local circ testing, as long as they can be used to demonstrate SB allowed and not allowed for patrons based on PType code (eligible vs. not eligible for SB). However, it is strongly recommended that each member create several new test records that are used specifically for testing SB.

1. Allowed to request via SB. Several test records should have a local PType code that is mapped to allow Summit Borrowing, testing student, faculty, and staff codes.

2. Not allowed for SB. Identify or make at least one record for a patron with a PType that is not eligible for Summit Borrowing.

Test records: For security, we do not post the file of test patron records, numbers, and access information. If you need to use a test record, please contact Alliance office.

Testing with a new member

This special record will work when testing with a library that is otherwise off limits for making and receiving requests—for example, a new member.

When a new member [new] joins the Alliance, all current members remain active with SB while new is finishing table set-up and other work for making SB publicly available. Although the data has been loaded into the union catalog, new isn't ready to make SB available to its patrons, or to make its materials available to other Alliance members. Until new is ready, their items in the union catalog are "off limits", as well as their patrons.

So how does Summit allow some requests and not others? PType code "210" is set up to be a local ptype and a Summit PType. A "210" patron may belong to any Alliance member and make a request from new, and "210" may be a patron at the new member site and request materials from other members. The system will reject all other requests from new's patrons, and for its materials.  (note: "240" is also set up for testing, to be used only for institutions with direct CRL membership)

Every member also has a Loan Rule for PType 210 (or 240), and the rule is identical at every site.

requirements for each test record

Example, set of test patron records for Summit

It's easy to find the Summit test patron records when they all begin with the same "last name" for example:

xSummit, Angel test undergrad 1

xSummit, Bernard test undergrad 2

xSummit, Cesar test undergrad 3

xSummit, Darlene test undergrad 4

xSummit, Ernestine test grad student 1

xSummit, Filipi test special patron 1

xSummit, Gertie test faculty 1

xSummit, Hortense test staff 1

xSummit, Ichiro test town patron 1

Loaner Patron records

Each Alliance institution also creates and keeps in their local database patron records that will be used by, or "loaned to", other Alliance institutions. In other words, any institution may test Summit Borrowing in the Summit union catalog acting as a patron at any other member institution. Having these loaner records facilitates Summit Borrowing committee or small group and Alliance staff testing new features, etc. ("Patron test records", on the other hand, are used by the institution owning the patron record.)

updated: September 7, 2007