Centralized management of technical records across an enterprise
First Claim
Patent Images
1. A method for managing technical records, the method comprising:
- controlling, using a data processing system, access to a technical records repository through a centralized technical records security service, wherein the technical records security service controls access to multiple independent technical records repositories for an enterprise, wherein technical records follow a strict naming convention set by the enterprise, and wherein each of the technical records include a specific security classification level set by the enterprise;
setting up and running a multi-server file communication between a client system and the technical records repository;
in response to receiving a request for data, applying an integrity rule to a requested data via a technical records data integrity service that provides details of past transactions between the client system and the technical records repository;
logging a record of interface information previously used when retrieving the requested data;
facilitating integrity verification of an associated communication using the logged record;
in response to validation of credentials of a user, returning a resource bundle containing all resources needed to perform an actual communication being requested, wherein the resources in the returned resource bundle contain details on whether a multi-server communication must take place, the naming and storage conventions that are to be used, which describes exactly how a file is to be named when stored, and exactly where the file is to be stored on a remote repository, including a physical location/address;
authorizing the requested user to access the technical records repository, without identifying a physical name of the server or a physical path way to the technical records repository; and
matching of a name and pathway to the technical records repository for use by a requesting user, wherein the matching is performed by an algorithm from among;
using a lookup table that matches the name of the physical location of the technical records repository with the identifier name;
using a configuration file that points to the technical records repository; and
a coded algorithm that may be unique for the technical records repository'"'"'s storage system, wherein a choice of an algorithm is based on organization naming and storage conventions utilized by the technical records repository.
1 Assignment
0 Petitions
Accused Products
Abstract
A method, system and computer-readable medium for managing technical records across an enterprise are presented. The method includes controlling access to a technical records repository through a centralized technical records security service, wherein the technical records security service controls access to multiple independent technical records repositories for an enterprise, wherein technical records must follow a strict naming convention set by the enterprise, and wherein the technical records must contain a specific security classification level set by the enterprise.
27 Citations
15 Claims
-
1. A method for managing technical records, the method comprising:
-
controlling, using a data processing system, access to a technical records repository through a centralized technical records security service, wherein the technical records security service controls access to multiple independent technical records repositories for an enterprise, wherein technical records follow a strict naming convention set by the enterprise, and wherein each of the technical records include a specific security classification level set by the enterprise; setting up and running a multi-server file communication between a client system and the technical records repository; in response to receiving a request for data, applying an integrity rule to a requested data via a technical records data integrity service that provides details of past transactions between the client system and the technical records repository; logging a record of interface information previously used when retrieving the requested data; facilitating integrity verification of an associated communication using the logged record; in response to validation of credentials of a user, returning a resource bundle containing all resources needed to perform an actual communication being requested, wherein the resources in the returned resource bundle contain details on whether a multi-server communication must take place, the naming and storage conventions that are to be used, which describes exactly how a file is to be named when stored, and exactly where the file is to be stored on a remote repository, including a physical location/address; authorizing the requested user to access the technical records repository, without identifying a physical name of the server or a physical path way to the technical records repository; and matching of a name and pathway to the technical records repository for use by a requesting user, wherein the matching is performed by an algorithm from among;
using a lookup table that matches the name of the physical location of the technical records repository with the identifier name;
using a configuration file that points to the technical records repository; and
a coded algorithm that may be unique for the technical records repository'"'"'s storage system, wherein a choice of an algorithm is based on organization naming and storage conventions utilized by the technical records repository. - View Dependent Claims (2, 3, 4, 5, 6, 13)
-
-
7. A non-transitory computer-readable medium embodying computer program code for managing technical records, the computer program code comprising computer executable instructions configured for:
-
controlling access to a technical records repository through a centralized technical records security service, wherein the technical records security service controls access to multiple independent technical records repositories for an enterprise, wherein technical records follow a strict naming convention set by the enterprise, and wherein each of the technical records include a specific security classification level set by the enterprise; setting up and running a multi-server file communication between a client system and the technical records repository; in response to receiving a request for data, applying an integrity rule to a requested data via a technical records data integrity service that provides details of past transactions between the client system and the technical records repository; logging a record of interface information previously used when retrieving the requested data to facilitate integrity verification of an associated communications; in response to validation of credentials of a user, returning a resource bundle containing all resources needed to perform an actual communication being requested, wherein the resources in the returned resource bundle contain details on whether a multi-server communication must take place, the naming and storage conventions that are to be used, which describes exactly how a file is to be named when stored, and exactly where the file is to be stored on a remote repository, including a physical location/address; authorizing the requested user to access the technical records repository, without identifying a physical name of the server or a physical path way to the technical records repository; and matching of a name and pathway to the technical records repository for use by a requesting user, wherein the matching is performed by an algorithm from among;
using a lookup table that matches the name of the physical location of the technical records repository with the identifier name;
using a configuration file that points to the technical records repository; and
a coded algorithm that may be unique for the technical records repository'"'"'s storage system, wherein a choice of an algorithm is based on organization naming and storage conventions utilized by the technical records repository. - View Dependent Claims (8, 9, 10, 11, 12, 14, 15)
-
Specification