Re: proxy rewrite and consortium question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Fri, 20 Jun 2003 15:15:03 -0700
- From: "David Jones" <DJones@xxxxxxxxxx>
- Subject: Re: proxy rewrite and consortium question
>>> Yi.Kong@xxxxxxxxxx 06/13/03 06:37AM >>>
The problem is those databases subscribed by only one or partial libraries. For example, db 1 was subscribed by only library a, but in library b, a user can go to library a's page and click the link.
<<<
Yi,
As was mentioned, you may have to go the multiple-IP route (#105455), but you may be able to get away with just using the HOME column in the forward table ( http://csdirect.iii.com/faq/wam.shtml#homfld ) provided that:
1) you force verification on the affected databases
2) databases that are affected are not part of aggregator collections that multiple libraries have different databases from, unless those databases have distinct elements to their URLs.
Granted, that can be very limiting and you may have to go for the multiple-IP route, but for many small consortiums, this can be the less expensive route. Also, the HOME column can be used in conjunction with the multiple-IP route to really limit use of specific databases to patrons from specific campuses even when they are visiting a different campus...
Let's say we have three libraries: Lib1, Lib2 and Lib3. Lets say they have the following subscriptions:
1)
Only Lib1 subscribes to database A from Vendor Z and the URL is like
www.vendorZ.com/dbA
2)
Only Lib2 subscribes to database B from Vendor Z and the URL is like:
www.vendorZ.com/dbB
3)
Only Lib1 also subscribes to database C from Vendor Y and the URL is like:
www.vendorY.com
4)
Both Lib1 and Lib2 subscribe to database D from Vendor X and the URL is like:
www.vendorX.com
As long as the "db*" part of the URL is always present in #1 and #2, these entries will work:
1 > Token dbA
2 > IP Address/Host Name *.vendorZ.com
3 > Port 80
4 > Service Level 0
5 > Verify Y
6 > Valid Patron Types 0-255
7 > Valid Patron Home Libs Lib1
8 > Database Identifier dbA
9 > Database Name DBA from Vendor Z
1 > Token dbB
2 > IP Address/Host Name *.vendorZ.com
3 > Port 80
4 > Service Level 0
5 > Verify Y
6 > Valid Patron Types 0-255
7 > Valid Patron Home Libs Lib2
8 > Database Identifier dbB
9 > Database Name DBB from Vendor Z
1 > Token dbC
2 > IP Address/Host Name *.vendorY.com
3 > Port 80
4 > Service Level 0
5 > Verify Y
6 > Valid Patron Types 0-255
7 > Valid Patron Home Libs Lib1
8 > Database Identifier dbC
9 > Database Name DBC from Vendor Y
1 > Token dbD
2 > IP Address/Host Name *.vendorX.com
3 > Port 80
4 > Service Level 0
5 > Verify Y
6 > Valid Patron Types 0-255
7 > Valid Patron Home Libs Lib1,Lib2
8 > Database Identifier dbD
9 > Database Name DBD from Vendor X
HTH,
David