VDX Implementation Newsletter

Number 3, June 28, 2002

This is the third in the series of little newsletters designed to provide timely information about VDX implementation status as well as to address questions and concerns. You are encouraged to submit questions for inclusion questions and answers list that will be attached to each newsletter. We continue to make progress toward our "go live" date! Current installation and testing status is:

• Both machines are installed and stable, and failover seems to be working.
• The apache web server is running on the production machine; the following work is still needed:
• • FDI is currently working to incorporate our patron authentication into the patron log on
  • CDL is working to "brand" the screens with the Request project graphics
  
  
• The URL for the web server is http://ucill.cdlib.org:8082/vdx   If you have an ILL account, you may logon and look around. Remember, however, that most of the patron accounts that were created on loihi from requests submitted to the test version of Melweb will not be present in the production database.
• We are continuing to test with OCLC; we are currently working to try to get requests to link to an OCLC profile.
• We now have a draft format for the printed bookbands; Ellen England has communicated with the UCVDX-L list for feedback on the formatting of the printed products.

Some of you have been working on the test system and this has been very helpful to us in identifying parts of the configuration that are not working quite right. If you would like assistance in getting some test requests sent to your VDX location so that you can practice, please contact Ellen England or Mary Heath.

This newsletter is being double-posted to both PIROPS-L and UCVDX-L; apologies to those who have subscribed to both. If you will be working with VDX and have not yet subscribed to the UCVDX-L listserve, send email to listserv@ucop.edu with the message
"SUBSCRIBE UCVDX-L" followed by your name.

The Request Project Team

---

Questions Regarding the Consortial Borrowing System

Southern UC ILL Meeting
March 27, 2002 - UC Irvine
Group 3 Questions

1. How will VDX distinguish between CCG and CCL for purposes of reporting copyright compliance to CCC? Will it be able to pass along this information electronically to CCC? How will we access this information from Crystal Reports?

VDX includes a multi-layered configuration for determining copyright type. This is detailed on pages 67-72 of the "VDX Configuration" manual which I think you all have, but here is a brief overview:

There is a system-level ILL Copyright Policy which sets the following:
• Maximum number of requests that may be made for a particulary journal in a specified period (now set at 5)
• Reset interval for the specified period (now set at 1 year)
• When the reset interval begins (now set at 1 Jan)
• Whether the limit is on a per client or a per unit basis (now set at per unit)
Then, there are defined copyright types; these are:
• F for Fair Dealing
• C for Copyright cleared
• N for No copyright
• CCL defined as fair use (I think that this was created for with no understanding of what it meant and that "F" should be made "CCL")
• CCG (I think that this was created for with no understanding of what it meant and that "C" should be made "CCG")

Each location (in the ILL details tab of the location record) can specify that they will only handle specific copyright types. If no types are specified, it means that the location will handle all types. All of our locations are now set to handle all copyright types. It is also possible to set specific copyright types for specific groups of users and locations, but we have not done this either. VDX tracks copyright by journal title; requests for a title that are under the maximum request limit are set as "Fair Dealing" in copyright type. Once the maximum threshold is reached, the copyright type for a title is set to "Copyright Cleared". I believe that we are responsible for (via Crystal Reports) creating reports to CCC. Ellen will work on creating a report that any of you can use, but I am assuming that this development can wait a couple of months

2. How will VDX distinguish local document delivery requests from ILL requests? These are two parallel work streams; how will they be routed to the correct file and functional work area?

There may be several different streams by which document delivery requests will enter VDX - through a Melvyl or UC-eLinks request, direct keying by an ILL staff member, or through a blank web request form. In any case, these will get processed in the same way that regular requests do: the designated pickup location will be the requesting location and the owning unit (which might be the pickup location or another location on the same campus. Any request where the patron has said they would like to use document delivery will be marked with a "Y" in the "Will Pay Fee" field (on the Details tab of the request, under the Payment section). If there are other issues or special configuration needs, we will try to work them out.

3. How will the VDX system interface with the Minolta 7000 scanners? Web delivery?

VDX will not directly interface with the Minolta scanners. The scanners communicate with Ariel, and Ariel communicates with VDX. When we get version 2.3 of VDX in the late Fall,

4. How will the VDX system interface with UC-eLinks?

Requests that are made from remote databases via UC-eLinks actually get sent to VDX by the Request Resolution Server, so they receive the same processing and validation as requests from the Melvyl system.

5. What will change as far as verifying Borrowing requests during the summer phase of implementation? How will rota be created for requests keyed into VDX by ILL staff?

All requests that are sent to VDX by the Request Resolution Server will be verified by that process; this will not change. Requests that are entered into VDX through a blank web form will need to be manually verified. In late Fall, when we receive version 2.3 of VDX, we will get a process that will automatically search (through a Z39.50 protocol) the Melvyl or any other system (e.g., local OPACs, WorldCat) that a unit designates.

6. Overdues - where will they go?

We think that overdues will be created in a manner similar to the picklist. They can be sent directly to the borrowing patron or to the borrowing unit.

7. Who determines Rushes?

The "need-by-date" that the patron selects determines whether the item is rush; if a patron chooses the shortest need-by-date, the request is set to rush.

8. Can we run a Query on the ISO messages and not the ISO status? Example: Run a search on In Process or Pending.

There is a long list of "message" types, including status, on which a search can be filtered.

9. How will patrons be authenticated when ILL staff receive the request on paper?

ILL staff will need to obtain the patron's barcode number when accepting requests on paper forms. Staff can then use the blank web form to enter the request into VDX.

10. Is it possible to have copy non-returnables be auto-completed when shipped from the lending instutition?

Yes, this is possible. I can be done in the "Location Configuration Defaults" for the unit or the campus. If all campuses are in agreement, this can be done at the system level. Currently, automatic actioning is defined for the following situations:

Location Configuration Defaults
Action	Service type	Authority status	Role of processing unit
Answer Nonsupply	All (="wildcard")	Complete	Responder
Checked In-Indication	All (="wildcard")	Complete	Requester
Check In	All (="wildcard")	Complete	Responder
Received-Indication	Copy Non-Returnable	Complete	Responder
Received Copy	Non-Returnable	Complete	Requester