Let's talk about this at the 8/12/04 TS Aleph Implementation Group meeting. Betsy
-----Original Message-----
From: Rich Bennett
Sent: Tuesday, August 10, 2004 2:53 PM
To: LMS Steering Committee
Cc: Martha Hruska
Subject: Connecting to Other SUL Using the UF Client
FCLA is looking at the issue of being able to "Connect to" other SUL catalogs (read-only) when using our own UF client.
Because of the way permissions work in Aleph, the most reasonable approach is likely to mean that any user wanting to see info in another catalog will need to login using another userid that all staff would use for this read-only purpose. They would not be able to connect while logged on to their own userid. They would right-click on the "key" in the lower right corner to login as this other read-only user when necessary.
Does this seem problematic? (It may really be the only option).
Has there been a lot of use of this capability in NOTIS by our staff?
What specifically has this capability been used for in NOTIS -- and what would it likely be used for in Aleph by our staff? (Or what would it be desirable to use this capability for?)
Thanks. Rich
P.S. In order for a UF staff member to be able to connect to UNF, etc. when
logged on with their own userid, permissions require that the UF userid would
also need to be included in the UNF, etc. permissions. This is why it seems
that the only reasonable way to approach this will be for all staff to use a
generic userid that can be included in all of the separate SUL password files.