Present: Deb Lamb-Deans, Carmen Blankinship, Joanne Leary, Pat Schafer, Howard Raskin, Susan Currie

Bursar interface testing
Susan distributed copies of the bill data extract report from Voyager. This report lists all the test fine and fee records created in the Voyager patron accounting files. Library Systems plans to test the interface with the Bursar to see how the program actually closes the bill records in Voyager but before doing so, they would like us to verify that the bill information is accurate. Lydia provided a handout which outlines the basics of the bursar program and some expected field changes. Committee members should review this handout for any questions we have about the data exchange. One thing that is different is that instead of student ID number, the Voyager program uses the institution ID number from the patron record. Unit summary reports should probably have the student's bar-code number on it as well. Everyone should notify Susan when the bill report has been verified.

The committee reviewed the list of fine and fee reasons in Voyager. Some are system supplied and won't be discussed for use until we implement the media booking client. For Budget and Accounting as well as for the Bursar, we currently have 3 subcodes, based on combinations of fine and fee reasons and service units. In NOTIS, we have used only 5 fine/fee reasons but we have more that are used. For a list of subcodes used by the endowed libraries, see the website at http://www.library.cornell.edu/Adminops/burlisting.html Right now, we have defined overdue, lost book fine, recall fine, rush recall and lost book cost as fine/fee reasons that transfer to the Bursar and are assigned a subcode. We also have a miscellaneous, a binding cost, a damage and repair cost and a miscellaneous cost, none of which currently can be transferred to the Bursar via the interface. If we want these charges to transfer to the Bursar, we need to decide which subcode to use. The committee decided to recommend the use of the subcode for overdue fines. We also discussed the rush recall reason which has not been used. We decided to eliminate this fine/fee reason. One very important thing about fine/fee reasons is that because they are given a unique number in Voyager (e.g. F1 overdue, F11 binding cost), once we set the fine/fee reason, we cannot change the unique number or the charges will not map correctly to the bursar interface.

Although every one tried to create a system generated replacement bill using the backdating feature, no replacement bills were created. We will need to create an overdue and let the 27 day cycle take its course to see if a bill is generated. We also had questions as to whether fines we create for students will pass and if we take partial payments, will the unpaid remainder pass. These questions will be forwarded to Library Systems.

A significant change in the Voyager Bursar interface is that unlike NOTIS, where we send student overdue fines nightly to the bursar and replacement bills 50 days after the date due, we cannot set different intervals for overdues and replacement bills to be transferred to the bursar. We will have to send all bills to the Bursar at the same time. This means students will have 10 days after being billed to pay at the library before the bill is sent to the bursar. This will be an important piece of publicity for students.

Operator Security Profiles
Pat reviewed the security profiles set for this phase of testing and asked for feedback. There was much discussion about what is needed for the circulation, cataloging and acquisitions modules for access services staff. We also discussed differences for student and staff sign-ons, which are important for overrides in order to check materials out from the annex. The ability of patrons to place recalls through the opac also makes a difference in operator profiles. We decided upon naming conventions and profile values for circulation. Pat will make changes in system administration to reflect our discussion so that we can do further testing. She will be presenting our recommendations to the Security Committee this week.

Templates for creating reserve records
One of the technical services workflow committees has begun discussing setting up bibliographic and holdings templates to be used for course reserve. The Voyager Circulation Manual outlines choices on pages 66-71. Everyone should review these pages and send feedback to Susan. We will be discussing course reserve processing in more detail in one of our next meetings.

The next meeting of this committee will be Friday, March 17 in Olin 603. Lydia Pettis will be meeting with us for a reports discussion. Susan will organize another meeting sometime the week of 3/20/00. We will also need to discuss the next data migration and testing.