OCLC Oddments: Updates & Status Reports

Here are three recent posts of relevance to CFLC members from the OCLC Resource Sharing List:

Subject: OCLC Update: ISO-ILL Status 7/15

ISO-ILL Testing Status
OCLC recognizes the seriousness of the ISO-ILL system outage and has a senior development team working seven days a week to resolve this problem. In addition quality assurance and product staff, as well as experts from other divisions of OCLC, are assisting and trouble shooting and testing. Resolution of this problem is a top priority at all levels in OCLC.

Progress
Here is an update of where OCLC stands with testing:
* Lending - nearly all messages and workflows are succeeding.
* Borrowing - incoming requests are successfully getting into OCLC but we have not successfully taken an entire borrowing workflow to completion
* Data integrity -data transferring between OCLC and test systems appears to be solid

Success
We are happy to report that testing of lending functionality with CISTI (OCLC symbol: CAI) has been successful. As of Saturday morning, CISTI will be able to receive and process new requests. Libraries that sent requests to CISTI prior to their non-supplier designation on July 9, may begin to see responses to these requests sooner than Saturday morning, as CISTI begins processing their backlog.

We continue to test with four outside systems in parallel and have tested through most weekends including the July 4th holiday weekend.

We apologize again for this extended downtime, and thank our testing partners as we continue to resolve these problems.

Subject: OCLC: ILL Fee Management Program Borrower/Lender Reports (7/14)

With the change in numbering to WorldCat Resource Sharing request identifier numbers, the ILL Fee Management Program Borrower and Lender Reports are incomplete.

When we migrated the system we added an extra digit to the request number. Previously, if we hit request 999,999 we started over with request number 1. Now, we roll over to 10,000,000. The IFM reports only display 7 digits, so this is resulting in missing data.

For example:
A library has IFM data in request numbers:
10,000,001 and
10,000,002 and
10,000,003

The only request appearing in their report is: 10,000,00 (lopping off the last/8th digit in the request number) which actually indicates the first request in that string, but the other two are then being dropped from the report.

We have no reason to believe that the monetary transactions were affected, just that the report information is inaccurate. OCLC Usage Statistics are being revamped to accommodate the 8th digit of request identifiers. We expect this process to be corrected in 2-3 weeks.

We apologize for any inconvenience this is causing our users and will post a message when these reports are corrected. . This problem is not related to the previous problem with IFM reports related to data missing from June 2-30.


Subject: OCLC: Lender Local Data Record (LDR) Display in Requests (7/14)

OCLC regrets to inform users of an open issue regarding lender LDR routing. The following text outlines how lender LDR routing is currently working.

Lender LDR always appears on first lender of a lender string. Lender LDR appears on second/third/fourth/fifth lender IF the previous lender actively responds NO. If a request ages/advances to the next lender automatically, lender LDR data does not appear for the next lender in the string. You will need to check your local holdings manually to fill the request.

Here is an example of how this will work for a request with four lenders:

Lender 1 does not respond, request automatically ages and advances to next lender in the string
Lender 2 does not see LDR information, responds NO, request advances to lender 3
Lender 3 sees LDR information, responds NO, request advances to lender 4
Lender 4 sees LDR information and fills the request

We do not believe that the majority of our users will be affected by this.

This issue will be addressed in a future install, however no date has been determined.

SUBJECTS: OCLC ODDMENTS