Record Load Request Confirmation and Service Agreement:

In submitting a record load request, you agree to the following terms:

1. Record load requests are handled on a first-come, first serve basis, with routine record loads taking priority. Additionally, certain requests may be expedited based on extenuating circumstances.

2. Requests will not be acted upon until records are submitted to Production Systems (PST) and Catalog Management (CMT).

3. Once records are received and analysis is completed by Catalog Management, the records will be test-loaded to TOrbis by Production Systems. PST will submit the test-load results to you for approval, and you will have **2 weeks** to approve the test load or to request corrections. If you are not comfortable evaluating the test load results, please designate a colleague who will do it for you and let PST and CMT know in advance. CMT will also sign off on the test load results within the 2 week period. If you will need more time due to scheduling conflicts, please let us know as soon as you recieve the test results.

4. If you or a designated colleague cannot approve the test load results within the 2 week time frame or fail to ask for more time, your request will drop the the bottom of the record load request queue (see http://www.library.yale.edu/%7Elso/databaseadmin/eresource/E-resourceRecordLoadQueue.xls) and we will move to the next request.

5. Once the test load results are approved, CMT will decide whether to send the records out for authority control. Once the bibs records are returned from Backstage with an associated file of auth records (ususally takes about 3 days), PST will schedule a time to load the both bibs and auths to production Orbis. When the records are fianlly loaded, you will receive load stats plus any additional information necessary to the load (duplicate bibs, clean-up required, errors, etc.). An announcement will be posted to Yulib and to our blog (http://blogs.yale.edu/roller/page/eresourcerecords).