home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: bit.listserv.notis-l
- Path: sparky!uunet!darwin.sura.net!uvaarpa!murdoch!poe.acc.Virginia.EDU!jlc5f
- From: jlc5f@poe.acc.Virginia.EDU (Jean L. Cooper)
- Subject: work unit security
- Message-ID: <1992Jul27.132334.18294@murdoch.acc.Virginia.EDU>
- Sender: usenet@murdoch.acc.Virginia.EDU
- Organization: University of Virginia
- Date: Mon, 27 Jul 1992 13:23:34 GMT
- Lines: 23
-
- In the LSYS Enhancement Ballot that was distributed to LIB1s
- last week, one of the proposed enhancements is:
-
- LSYS Work Unit Security--"Currently, to give access to check in
- (R statements) one must also give access to create vendor and order
- scope. This defeats the purpose of restricting access."
-
- Maybe I'm on the wrong track here, but I think I've found a
- way around this. When giving access only to M,N,R statements,
- I totally delete any Default OrdUnit Code. For some reason,
- this allows me to put "N" in the vendor and order scope fields.
- It seems odd to me that the Default OrdUnit Code, the vendor,
- order scope, and R statements are connected, but experimentation
- is an incredible thing! <grin>
-
- Jean L. Cooper
- Assistant Systems Librarian
- LIB2
- University of Virginia
- --
- Jean L. Cooper (BITNET: JLC5F@virginia.edu CIS: 70253,1114)
- "The true University of these days is a Collection of Books."
- --Carlyle
-