Browse Prior Art Database

System for Sharing Documents in a Single Data Base

IP.com Disclosure Number: IPCOM000059871D
Original Publication Date: 1986-Feb-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 3 page(s) / 85K

Publishing Venue

IBM

Related People

Carpenter, ME: AUTHOR [+2]

Abstract

An arrangement is described to share documents, residing on a single data base, among specified subsets of enrolled operators in such a way as not to disturb the way documents have previously been stored. All documents in the IBM 5520 administrative system have "Document Owners" which are in fact the operators' IDs. For private documents only, the owner may view, modify, or print the document content. While many techniques are available to logically partition data bases, or limit document access, the described arrangement does not require any changes to document profile information associated with each document. The system security administrator has the option to use or not use the capability as a configuration option.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

System for Sharing Documents in a Single Data Base

An arrangement is described to share documents, residing on a single data base, among specified subsets of enrolled operators in such a way as not to disturb the way documents have previously been stored. All documents in the IBM 5520 administrative system have "Document Owners" which are in fact the operators' IDs. For private documents only, the owner may view, modify, or print the document content. While many techniques are available to logically partition data bases, or limit document access, the described arrangement does not require any changes to document profile information associated with each document. The system security administrator has the option to use or not use the capability as a configuration option. Since all documents have 'Owners' as part of their document profiles, lists are created by the security operator which consist of operators who are to have affinity. Before document access is granted to a shared document, a check is made to determine if the requestor has the proper authority. If the requestor is not the document owner, and the document is not 'globally shared', the requestor must have affinity to the document owner via a specified affinity list, called the User Access List. Operators must associate themselves with a User Access List before they can gain access to 'Shared' documents owned by others. Operators may exist in multiple User Access Lists, thereby having affinity to more than one group of operators/owners. Thus, they may gain access to 'Shared' documents across multiple groups and these multiple groups may gain access to their 'Shared' documents. Provision to allow all operators on the system to have access to a 'Shared' document is accomplished by specifying a Document Charge Number, such as "9999." User Access Lists may be made effective or not by operators having Security Authority. This will allow those installations which do not wish to use User Access to do so. Since when User Access Lists are in effect, only operators having Security authority may Display List All Documents in a single step. An operator may determine which User Access List they have most recently selected by performing Display Document Status. The following are examples of how one might use Access Lists.

(Image Omitted)

Example 1: Non-int...