US20020010708A1 - Defining a uniform subject classification system incorporating document management/records retention functions - Google Patents

Defining a uniform subject classification system incorporating document management/records retention functions Download PDF

Info

Publication number
US20020010708A1
US20020010708A1 US09/778,029 US77802901A US2002010708A1 US 20020010708 A1 US20020010708 A1 US 20020010708A1 US 77802901 A US77802901 A US 77802901A US 2002010708 A1 US2002010708 A1 US 2002010708A1
Authority
US
United States
Prior art keywords
user
document
null
code
class
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09/778,029
Inventor
Lowrie McIntosh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US09/778,029 priority Critical patent/US20020010708A1/en
Publication of US20020010708A1 publication Critical patent/US20020010708A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99951—File or database maintenance
    • Y10S707/99952—Coherency, e.g. same view to multiple users
    • Y10S707/99953—Recoverability

Definitions

  • the present invention provides a reliable mechanism to accomplish this task.
  • the “type” of document must also be determined. Different types of documents within the same subject matter area may have different retention requirements. The system must be able to determine the type of document at the outset. This “type” information specifies whether a particular document is “official” or “informational” and whether it is also “vital” or “sensitive.” The type of document determines the level of protection afforded and has a direct impact on determining the life-cycle of the document. Additionally, document type impacts the decision as to the media selected to store it, whether electronic, paper or film.
  • Informational documents (largely copies) have their own destruction schedule based on need. They are not archived and their life cycle must not exceed official documents of the same subject. They are destroyed at the office level when their usefulness is over. Normally, informational documents have a substantially shorter life-cycle than official documents pertaining to the same subject.
  • Sensitive documents contain, for example:
  • a system for providing a true interlingual mechanism to achieve uniformity when classifying documents by subject to assist in the management, complying with retention requirements and long term storage of documents of an organization.
  • the term document includes, without limitation, the hard copy and digitally stored version of the output of a computer program such as a wordprocessor, microfilm or microfiche, correspondence of all types and office folders which themselves may contain documents.
  • objects such as furniture and the like may also be classified by creating a label (in this case, the document) which contains all of the relevant classification information for the object.
  • Using generic terminology in a hierarchical structure use of the system directs a user of the system to a single classification for any document.
  • the system captures acronyms, vernacular and industry specific terms as well, as foreign terms, into a thesaurus that can be modified and appended as classification needs change.
  • the system learns as synonyms are added to the hierarchical structure capturing differences in individual perception.
  • the invention includes the capability of searching for the location of a particular document.
  • a descriptive term is entered at a query prompt that the user believes best describes the subject matter of the document in question. If this entry results in a hit, all information pertaining to the document is then available to query.
  • An example of a screen display in which such a query may be made is shown in FIG. 3.
  • entry of a descriptive term produces a particular subject classification (i.e., a class code as described below).
  • attribute filters include location (physical location such as file cabinet or work station), acronym (class codes, alpha and/or numeric references, i.e., form numbers, department IDs), organizational unit (cost center number, department number), subject description (i.e., class code), label description (e.g., three line description for a particular tangible asset as shown in FIG. 1. If the entry term does not find a match in the hierarchical structure, the system will search a synonym database for a match. If the search of the synonym database also does not yield the desired document, it must be concluded that the desired document has not been classified.
  • the system is able to specify a physical location for a hard copy of a document by office, box, in draw and folder, or of a document on magnetic or similar media by diskette location, hard disk drive location (i.e., computer) or network drive location (i.e., server) and file name.
  • hard disk drive location i.e., computer
  • network drive location i.e., server
  • FIG. 1 is a screen display showing a query screen for performing a search.
  • FIG. 2 is a screen display showing a list of synonyms.
  • FIG. 3 is a screen display showing a query screen for performing a search.
  • FIG. 4 is a screen display showing the results of a query of the type shown in FIG. 3.
  • FIG. 5 is a screen display showing a query screen for performing a search.
  • FIG. 6 is a screen display showing the results of a query of the type shown in FIG. 5.
  • FIG. 7 is a screen display showing the results of a query of the type shown in FIG. 5.
  • FIG. 8 is a block diagram showing a high level view of the functions performed by the invented system.
  • FIG. 9 is a block diagram showing the store documents function.
  • FIG. 10 is a block diagram showing the maintain inventory function.
  • FIG. 11 is a block diagram showing the maintain system function.
  • FIG. 12 shows the layout for the entity relationship diagram shown in FIGS. 12 A- 12 F.
  • FIGS. 12 A- 12 C show the first row of Figures forming the entity relationship diagram.
  • FIGS. 12 D- 12 F show the second row of Figures forming the entity relationship diagram.
  • FIG. 13 shows the layout for the logical database model shown in FIGS. 13 A- 13 L.
  • FIGS. 13 A- 13 D show the first row of Figures forming the logical database model.
  • FIGS. 13 E- 13 H show the second row of Figures forming the logical database model.
  • FIGS. 13 I- 13 L show the third row of Figures forming the logical database model.
  • FIG. 14 shows the layout for the physical database model shown in FIGS. 14 A- 14 L.
  • FIGS. 14 A- 14 D show the first row of Figures forming the physical database model.
  • FIGS. 14 E- 14 H show the second row of Figures forming the physical database model.
  • FIGS. 14 I- 14 L show the third row of Figures forming the physical database model.
  • This invention is a computer based system which provides a reliable structure to properly identify and track documents used by an enterprise throughout their life cycle to provide an efficient and easy to use mechanism to ensure that document retention requirements are complied with while enabling the orderly destruction of documents once their retention requirements have been satisfied.
  • Classification is performed when the document is created. There are a number of reasons for developing software that makes retrieval easier and control and tracking a bi-product of the processing which of necessity is already being performed.
  • One factor which leads to performing document classification at document creation is placing the responsibility for classifying the document on the individual creating the document. The individual creating the document is in the best position to provide its proper classification. The time it takes to learn proper classifications for the subject areas involved for the normal user is relatively short, typically a matter of hours. This small investment in time substantially reduces the time required for searches to locate documents for retention schedule compliance and for retrieval. Learning to classify at the time a document is “saved” enables the use of the same procedure when a search needs to be performed.
  • the invention also employs the intelligent use of synonyms, i.e., a synonym database, as pointers. Synonyms are used to direct the user to the “official” term for the appropriate classification. To populate the synonym database, a document inventory is taken to collect the local terms being used to describe documents. It should be noted that a detailed inventory of document descriptions currently existing (i.e., prior to implementation of the invention) is not needed. However, when a system implementing the invention is initially used, it is preferable that there be some inventory of terms (synonyms) in use be available to the new users of the system to improve acceptance of the system and productivity. This inventory or synonym database can be created manually, i.e., by manual entry as part of the Browse Synonym function shown in FIG. 9. The synonym database contains all or a subset of terms in use by the organization to refer to a particular document instead of the “official” term used to classify that document. A screen display used for this purpose is shown in FIG. 2.
  • Synonyms are assigned to each level of the hierarchy. This enables anyone to use a term that they perceive is related to the subject matter and be directed to a unique official classification.
  • One of the important aspects of this invention relates to its record retention components which create a records retention linkage. This includes tracking and providing a direct linkage to the terminology used in the U.S. Code of Federal Regulations and to similar legislative retention requirements of any other country. In addition to identifying the media, it also catalogs the type of record.
  • the document type determines the essential security requirements for these documents.
  • Use of the invention provides a system that ensures uniformity by all users when classifying documents by subject, i.e., a uniform subject classification system.
  • This invention provides a hierarchically structured, subject oriented database, populated with terms in current use by the enterprise (i.e., chart of accounts and organizational chart) and by legislative references which pertain to the retention of documents.
  • a typical set of class codes names with class code acronyms in a uniform subject classification is shown in Appendix I.
  • search process is the reverse, where the search word (subject description) is entered into the system and the classification tools lead the user to the proper classification and then to the document being sought.
  • Supplemental databases containing synonyms are available for each line of the classification scheme. These databases can be added to by the user and in this way translate acronyms, local vernacular, abbreviations and foreign terms that reveal the user's perception of the subject being sought.
  • the invention provides a tracking mechanism to enable protecting, finding and retrieving a document, or group of documents (file series) when needed and to ultimately locate and destroy them when their life-cycle has been completed, as specified by an official retention schedule.
  • class levels can be adjusted to fit local conditions.
  • the document would be a label affixed to the artwork or the desk.
  • labels may also be affixed to a document or folder or box containing documents and/or folders. Additional data appearing on the label, referred to as “label lines,” providing specific descriptions beyond the class itself. Label line descriptions are extensions of the class code and are searchable using well known automated search techniques. Labels are a part of the record when attached with the same retention value as the record which normally is then case when the label is associated with a particular folder. It should be noted that labels do not have a retention value when attached to an asset such as a desk.
  • a typical response to the query provides the acronym of “HRJD”, or “ H uman R esources, J ob D escriptions” as shown in the screen display of FIG. 3.
  • the display would show the contents of the class table for the item located by the search as containing:
  • steps I-III it is possible to generate a report for each classification with the information shown in Table I.
  • the information in the Med Typ, Rec Typ, Start After, Off Ret and RC Ret columns is initialized for each new document added to the system based on the class code. That is, for each class code, this information is stored in a class table and is predetermined based on business and government regulations.
  • the information in the RCopy CC# column is obtained from a location table and is preset with a location code based on the workstation from which the data for the record was entered. By changed the data in the class table or location table, all documents associated with that class code or location would be changed as well.
  • the column labeled “No.” contains a unique computer generated numbers used to represent each file series.
  • the column labeled “Med Typ” represents media type, i.e., paper, magnetic, microfiche, etc. Each media type in the example is represented by a number, for example, 0 for paper, 1 for magnetic, 2 for microfilm, 3 for microfiche, 4 for CD-ROM.
  • the column labeled “Rec Typ” represents record type, i.e., Vital (V), Informational (I), Official (O), Sensitive (S).
  • the column labeled Start After contains the date starting the retention, e.g., annual review (AR), completed (CT), superseded (SU), current year (CY) and final audit (FA).
  • the retention start date marks the beginning of the “clock” as related to “upon the completion of the audit” when the record is superseded, or beginning when the contract has been completed, or when a license has expired.
  • AR annual review
  • CT completed
  • SU superseded
  • CY current year
  • FA final audit
  • the column labeled “RCopy CC#” represents record responsibility copy cost center number. This is the cost center number as identified in the Chart-of-Accounts for the organization. This cost center is the only cost center which can send documents in this file series to a long term storage facility (for archival). All other holders of copies of such documents (i.e., informational copies) would have been instructed to destroy such copies at the office level according to a predefined schedule for destruction of such documents, which as previously noted, would predate scheduled destruction of the official copy of the document. An expanded example of a retention schedule appears in Table II.
  • the system automatically identifies the “owner” of the document and the location of all copies, both Official and Informational. Such ownership is determined by virtue of the ownership of the file series of the document which in turn is determined by the functional responsibility of the cost center in the Chart-of-Accounts (organizationally). As noted above, the system captures the location and the cost center when the user “saves” a created (or modified) document based on information in the class table and location table.
  • a report may be produced identifying the selected document's key attributes allowing the “owner” to review the document and authorize the purge process, or any other access to or modification of a file series and records in the file series.
  • ERS is a client/server application to assist in the management of valuable corporate information.
  • ERS maintains a record retention schedule detailing how information ought to be stored, where, and for how long.
  • the application helps the user classify documents into groups of similar information.
  • ERS provides document security. It can prevent unauthorized reading of. or writing to official corporate information.
  • ERS provides a means to search for documents pertaining to a specific subject, date range, author, etc.
  • the system acts as a pointer to direct users to where information is stored.
  • the ERS application has four categories of user. Each group of users and their responsibilities are described below.
  • the Records Manager is responsible for the overall performance of the system. The manager has the greatest amount of authority and access. The responsibilities of the Records Manager are the following:
  • Information Services will be responsible for maintaining the technical environment. This includes setting up databases, insuring that all users and servers are configured properly, etc.
  • the Department Coordinator is sometimes referred to as a ‘Super User’. They have more authority and system access than a normal user, but less than the Records Manager. The responsibilities of the Department Coordinator are the following:
  • Each class has attributes. There attributes are retention period, record type (official, informational), sensitivity, and vital flag, etc. Users can not override these values with their own when storing a document. If they need different attribute values than what is associated with a given class, then they should contact the Record Manager. The Record Manager may then create a sub class having the attribute values desired by the user.
  • a classification will no be the responsibility of two or more cost centers.
  • the cost center the owns a classification is responsible for all the documents that have been assigned to that classification.
  • the cost center must insure that the inventory of documents is correct and properly maintained.
  • a document is assigned a classification at the major level, then it can not be located in any archive facility. For example, if a document is classified as ‘AC’ for accounting, then it can not be stored at a off site storage facility. If the same document was classified as ‘ACAP’ for accounting, accounts payable, then it could be stored at a warehouse.
  • a user can have access to several ERS databases. One for production work and one database for training, for example. However, no user will have write access to two production databases. There will be no support for across production database searches.
  • the user will have the ability to retrieve and open a document by searching for its classification, synonym, or other attributes such as author, title, and/or date. If multiple documents are found that satisfy the users search criteria, a list of these documents will be displayed for the user to pick from.
  • the documents being searched may be found on the users hard drive, shared network drive, or archive facility (Mezzanine).
  • the users will have the ability to store at document on their hard drives, shared network drives, or archive facility (Mezzanine). Regardless of where the user stores the document, they will have the ability to manage their documents with ERS classifications and synonyms.
  • ERS will assign the classification associated with the corporate synonym to the document. Also, the user may wish to assign one of their own synonyms to the document. ERS will automatically translate from the user's synonym to the appropriate corporate synonym and assign the classification to the document.
  • Users will have the ability to add, change, or delete their own synonyms. They may create synonyms different than the corporate synonyms. However, user created synonyms must be related to corporate synonyms. User synonyms will be children of a corporate synonym.
  • This update function would allow a users to change information the system stored about them. Such information as phone number, mail stop, spread sheet directory name, and location would be fields a user could change. The function would not allow them to change their user group or create a new user.
  • the Department Coordinator would have access to the same functions as the normal user. However, in their stand alone ERS application they would access to these additional functions.
  • a media request is a note to Information Services that items found on hard disk need to be moved to CD.
  • This report is to display those items in inventory that are approaching the end of their office retention period and starting their center retention period. These inventory items may require a media change and/ or location change.
  • This report would be used to issue inventory requests for media change. This report would help the Department Coordinator manage the logistics of moving records to and from a storage facility.
  • the purpose of these reports are to display where classifications may be mis used.
  • the reports should list (1) the documents assigned classifications that are not approved by the Departmental Coordinator for application by the user, and (2) the documents only assigned a major classification.
  • the purpose of this report is to display the documents that need to be (1) placed in a off site storage facility, (2) retrieved from an off site storage facility, and/or (3) under go a media change.
  • Information Services organization needs some of the same functions of the Department Coordinator, but not all. Information Services needs to be able to maintain inventory locations and media. They will also need the same inventory reports and media life reports available to the Department Coordinator. In addition, the following functions would be available to only Information Services users.
  • ERS will record who is running what, when, and for how long. This usage activity can create a large volume of data in a short period of time. For this reason, there will be a batch job available to remove usage activity prior to a certain date. In this fashion, the Records Manager can select to keep usage information for only one quarter, for example.
  • the Records Manager would have access to all the functions available to the normal user and the Department Coordinator. However, the Records Manager would have access to the following additional functions in their stand alone ERS application.
  • Static tables would include record type, sensitivity codes, retention start codes, synonyms, classes, users, user groups, companies, departments, and cost centers, media types, buildings, aisles, and locations, etc.
  • the purpose of the catalog of functions is to display a summarized list of all the update and reporting capabilities of the system by type, subject, name, and description.
  • ERS920 Media Type Maintenance.
  • ERS930 Organization Type Maintenance.
  • ERS935 Record Type Maintenance.
  • ERS945 Retention Start Maintenance.
  • ERS950 Sensitivity Maintenance. Utilities Inventory ERS010 Application Package, File Open. ERS020 Application Package, File Close. ERS030 Application Package, File Save.
  • Any system is made up of functions.
  • Functions are software that produce menus, reports, updates, interfaces, and utility activities.
  • Features are the capabilities of each function.
  • reporting functions have the capability to output their information to the screen, the printer, or to an extract file for easy entry into a spread sheet. These output routing capabilities are all features of a reporting function.
  • menus The purpose of menus is to provide access to all other functions of the system. Pull down menus are placed at the top of each window. The features of all menus are described below:
  • a bar of push buttons will be located just below the menu at the top of the window.
  • the push buttons will contain icons symbolizing frequently used functions or menu options. Thereby a user can access a function one of two ways. The first method is by pulling down the appropriate menu and clicking on the option desired. The second means of accessing a function would be to click on the icon for the function found on the button bar.
  • the pull down menus will show all functions planned for the application at all times. However, some of the functions will appear in gray letters. These will be the functions that are not completed and are not available for use. As the system development effort continues, more and more of these functions will be enabled and will appear in black letters. In this fashion, a user can see all the functions of the system, and what is available for use today.
  • Reports are functions used to output information. Reporting functions can produce output in tabular listings, graphs, or spread sheets formats. This output can be sent to the screen, a printer, or a file directory.
  • the features of reporting functions are the following:
  • the user will have the option to create their own report sub heading that will appear at the top of each page.
  • the sub heading can be used to document the items selected or their purpose for running the report.
  • the user will have the ability to limit the size of the report. They will be able to select one or more columns on the report and state what values they would like to have retrieved for those columns. For example, if department number is a column on a report, then a user will be able to state which departments should appear on the report. For inventory related reports, users will have the ability to do string search on the title and description of items.
  • Each report can have more than one method of sorting.
  • the user will have the ability to select, from a pre-set list, how the information should be sorted.
  • Each report can be routed to one of three different places.
  • the report can be viewed on the screen, sent to a printer, or placed in comma delimited file.
  • the comma delimited file can be read by Lotus or Excel spread sheet software.
  • Every report routed to the screen will have the ability to be printed. This feature will allow the users to view the first several pages of a report, and then print it, if they desire.
  • Every object of the window used to specify report sub-headings, selection criteria, sorting, and routing will have a help message associated with it.
  • the help message will offer a one line description of the object.
  • reporting function Just prior to exiting a reporting function, the system will post to the database the name of the reporting function run, rows retrieved, the user's ID, date, and time. In this fashion, tracking of reporting function usage and charge back activities can be supported.
  • Update functions provide the ability to add, change, or delete records in the database.
  • the features of update functions are the following:
  • a single update function will allow the user to add new records, change existing ones, or delete records from a table. The user will not have to select three different update functions from a menu to maintain one table.
  • the user will not have to know key field values such as department numbers, building numbers, or document numbers.
  • they will be shown a list of records that can be updated. Then, they can point to an existing record to change it, or delete it.
  • a code field value is asked for on a data entry window, it will be displayed in a drop down list box along with its description. For example, if a user must input an cost center number, then they will be given a drop down list box containing cost center number and names to choose from.
  • ERS will allow the user to drag an object on to a command button to signal that they wish to perform the command.
  • an update function could consist of three windows.
  • the first could be a list of documents to update.
  • the second window could be all the descriptive information about the document.
  • the third window could be used to input key words or phases about the document. The user would not be forced into going from the first, to the second, and then to the third window. They would be given push buttons to jump from the first window to the third, and from the third to the second window. In this fashion, the user would not be forced into traversing through several windows in a pre-set pattern to enter the data.
  • Each field will be validated at the time the user moves the cursor from one field to another on a data entry window. This will prevent the user from entering several fields of erroneous information before realizing that any of it is wrong.
  • buttons At the bottom of each data entry window, in an update function, would be several push buttons. These buttons would be used to signal the computer to write the transaction out to the database, or cancel the transaction. Each time one of these buttons is pressed, the user will see a message a the bottom of the window confirming the computer's actions.
  • Each object and field in a data entry window will have a help text associated with it. This one line of help message will appear at the bottom of the screen when the object or field is clicked on.
  • the purpose of a business process model is to show the relationship between people, systems, data, office policy and procedures, and documents.
  • a component of a business process model is a node tree diagram.
  • FIG. 8 shows the major activities associated with an application.
  • FIGS. 9 through 11 show the node tree diagrams for ERS.
  • the application will store its information in a set of relational tables.
  • the total size of the database is expected to be approximately 500 Megs of disk space for a 300,000 inventory items. There will be roughly 1,200 total users, about 300 will be activity at any point in time.
  • Entity Name Entity Definition Access The purpose of this entity is to store the access codes and descriptions. Access codes are select, update, insert, and deleted. Class The purpose of this entity is to store the all the information about a classification. This information contains classification code, title, retention periods, record type, sensitivity, etc. Data Dictionary The purpose of this entity is to store entity, attribute, and physical column information. This entity is used to support data dictionary reporting. Function The purpose of this entity is to store a valid list of system functions. System functions are window objects such as reports, updates, inquiries, interfaces, etc. Function Column The purpose of this entity is to store a valid list of columns than can be used to limit retrieval of a reporting function.
  • Function Column Last Used The purpose of the last used function column entity is to record the selection criteria chosen by a specific user when a report was run. This entity supports storing the last query parameters applied by a user for a given report.
  • Function Data Window Function Sort The purpose of this entity is to store a valid list of storing options that can be applied to a reporting function.
  • Function Sort Last Used The purpose of the last used function sort entity is to record what sort sequence a user requested the last time they ran a specific report. This entity support recalling the last query for a report and user.
  • Function Subject The purpose of this entity is to define what area of interest, for the user, the function relates to.
  • Function Type The purpose of this entity is to store a valid list of function types. Function types are used to group functions together.
  • Function types are reports, updates, interfaces, etc.
  • Function Usage The purpose of this entity is to track who has accessed a function of the system and when. This entity could be used as a basis for activity analysis and usage charge back costing.
  • Inventory The purpose of this entity is to store information about an item in inventory. The information includes title, date stored, media, classification, etc.
  • Inventory Abstract Inventory Request The purpose of this entity is to store requests to move inventory from one form of media to another. For example, request to move documents from disk to tape. Once the media has been moved, the request is deleted. No past history of media requests are stored.
  • Inventory Statistics The purpose of this entity is to store the quantity of items in inventory for each class, record type, level one location, and month. These statistics can be used to determine if classifications are being properly applied.
  • Location The purpose of this entity is to store a valid list of locations. Locations can be storage areas, buildings, property, shelves, drawers, etc.
  • Location Type The purpose of this entity is to store valid location types. Location types are building, floor, aisle, storage area, shelf, property number, drawer, etc. The location type also denotes what level of the hierarchy the location can be found.
  • Media Type The purpose of this entity is to store a valid list of media types and descriptions. Media are hardcopy, disk, tape, CD, microfiche, etc.
  • Object Identification The purpose of this entity is to store the last identification number assigned to a table. For example, the last class identification assigned to the class table.
  • Organization The purpose of this entity is store a valid list of companies, departments, and cost centers.
  • Organization Type The purpose of this entity is to store a valid list of organization types. For example, company, department, cost center are all organization type. This entity also defines what level of the organization hierarchy the organization will be found on. Record Type The purpose of this entity is to store the valid record types and their descriptions. Valid record types would be official and informational. Request Type the purpose of this entity is to store a valid list of inventory request type codes and descriptions. Inventory request types are to change media or to move to or from offsite storage. Retention Reference The purpose of the retention reference entity is to store the text of the law or regulation that governs a set of classes and their retention periods. Retention Start The purpose of this entity is to store a valid list of retention type codes and descriptions. Retention types define when a record's retention period begins.
  • Sensitivity The purpose of this entity is to store a valid list of sensitivity codes and descriptions. Sensitivities are confidential, secrete, etc. Synonym The purpose of this entity is to store alternative names for a classification. A synonym may be a classification code, a portion of the classification name, or a commonly used alternative to the classification name. User The purpose of this entity is to store a list of valid users for the system. User Class The purpose of this entity is to store every classification the user has access to and may assigned to documents. The classes are initially set up by the Departmental Coordinator.
  • FIG. 12 is the entity relationship diagram. Its purpose is to provide a high level view of the database and its structure. The diagram shows each table in the system and how it relates to other tables. The solid lines between entities denotes identifying relationships. The dotted lines denotes non-identifying relationships.
  • Attributes are the columns that can be found in each entity or table within the database. The definitions are sorted by entity name and attribute name.
  • Class Identification System assigned identification number The class identification is the unique identifier for the classification. This integer is a system assigned value, not user assigned.
  • Abstract Description of classification The abstract is the legal definition of the classification.
  • Class Code User assigned identification code The class code is a 10 character user assigned classification code. The first two characters of the class code are the major class. The third and fourth characters are the primary class. The fifth and sixth characters are the secondary class. Characters 7-8 represent the next relationship level. Characters 9-10 represent the last relationship level.
  • Classification Title Long name or title for class. The classification title is the name of the class code. Classification Title Class title and all parent class Extended titles. The extended classification title contains the titles of all the parent classifications plus this classification's title.
  • this classification code is ACAP
  • the extended classification title is ‘Accounting, Payables’.
  • Center Retention Quantity of months in offsite Months storage The center retention months is the quantity of months an inventory item is held in a records center or off site storage facility. The office retention plus the center retention months equals the total retention period for a classification.
  • Organization System assigned identification Identification number The organization identification is the unique identification for a company, department, or cost center. The integer value is system assigned, not user assigned. Organizations own users and classifications. Created By User ID of person who created the class. The created by column contains the user identification of the Records Manager who created the classification.
  • Media Type Code User assigned identification code for media type. The media type code defines what form the inventory item is stored in.
  • DISK hard disk
  • FLOPPY floppy disk
  • CD CD ROM
  • TAPE magnetic table
  • FICH microfich
  • PAPER hardcopy.
  • Retention Reference User assigned identification number The retention reference column is used to store the identification number for the reference document or law governing a set of classes and their retention periods. For example, ‘26 CFR 1.6001.1’ is a document defining how checks ought to stored.
  • Retention Start User assigned identification code Code The retention start code defines when the retention period of the document starts. The quantity of months an inventoiy item is held may start when the document first created, or it may start when the document is moved to an off site storage facility.
  • the vital flag is a yes/no column denoting if the classification involves vital documents.
  • Vital documents are those records whose loss would have a financial impact on the organization.
  • Last Changed Date Last Changed By Timestamp
  • Entity Name Entity or long table name The Dictionary name of the entity in the logical data model. In most cases, the entity name is similar to the long name for the table in the database.
  • Attribute Name Attribute or long column name The attribute name from the logical data model. In most cases, this is the long name for the column.
  • Column Name SQL column name The column name is the physical name for the attribute in the SQL database. Datatype SQL column datatype.
  • the datatype is the physical format of the column in the SQL database.
  • Entity Definition Entity description or meaning The entity definition contains the description, meaning, or purpose of the entity.
  • Null Option SQL null option The null option is a flag denoting if a column must always contain data or not. If the null option equals ‘Yes’ then the column does not have to contain data all the time. If the null option is set to ‘No’ then the column must always have data in it.
  • User Defined Data- type Name Last Changed Date Last Changed By Timestamp Function Function Number User assigned identification number. The function number is the unique identification of a function of the system. Function numbers are assigned by programmers. For example, ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • Function Subject User assigned identification code. Code The function subject code defines what area of interest, for the user, the function relates to. For example, MANAGEMENT management performance reports. The function subject code uniquely identifies subjects. Function subjects, types, and titles are used to build menus.
  • Function Title Title or name of function is the name of the function as it appears at the top of the window or in the menu.
  • Function Maintenance is a function title.
  • Function Type Code User assigned identification code.
  • Function types, subject, and titles can be used to build menus.
  • Last Changed Date Last Changed By Timestamp Function Function Number User assigned identification Column number.
  • the function number is the unique identification of a function of the system. Function numbers are assigned by programmers. For example, ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • Table Name SQL table name The table name is the SQL table or view name that will be used as part of a WHERE phrase to limit report retrieval.
  • Column Name SQL column name The column name is the SQL table or view column name that will be used as part of a WHERE phrase to limit report retrieval.
  • DPT_NBR is the department number column name.
  • Column Type SQL datatype (DATE, INT, CHAR, FLOAT, YESNO).
  • the relationship code is BOTH, then the user can choose either an equality or string search relationship.
  • Sequence Number Sort sequence number The sequence number is a character column used to sort the column titles for display on the screen. The sequence number allows the system to display a list of column names in some other sort order besides alphabetically by column title.
  • Last Changed Date Last Changed By Timestamp Function Function Number User assigned identification Column Last number. The function number is Used the unique identification of a function of the system.
  • ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • Column Name SQL column name The column name is the SQL table or view column name that will be used as part of a WHERE phrase to limit report retrieval.
  • DPT_NBR is the department number column name.
  • User Identification logon user identification The user identification is the SQL database name for the user.
  • Table Name SQL table name is the SQL table or view name that will be used as part of a WHERE phrase to limit report retrieval.
  • Operator Code Code to indicate exact value or list of values. Determines whether the user can enter a value or select from a list of values. Last Changed Date Last Changed By Timestamp Function Table Name SQL table name.
  • the table name Data Window is the SQL table or view name that will be used as part of a WHERE phrase to limit report retrieval.
  • Column Name SQL column name The column name is the SQL table or view column name that will be used as part of a WHERE phrase to limit report retrieval.
  • DPT_NBR is the department number column name.
  • Function Number User assigned identification number.
  • the function number is the unique identification of a function of the system. Function numbers are assigned by programmers. For example, ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • Order By SQL ORDER BY and/or GROUP BY The order by column contains the SQL GROUP BY and/or ORDER BY phrase for the report request.
  • Data Window Name PowerBuilder Data Window name The Data Window name is the name of the PowerBuilder Data Window name that should be displayed when a particular sort is requested by the user.
  • Order By Title Title or long name of the sort The order by title is what the user sees when selecting from a list of sort sequences to apply to a report.
  • the order by column value may be ORDER BY CO_NBR, DPT_NBR, CST_CTR_NBR.
  • the order by title would be ‘By Company, Department, and Cost Center Numbers’. Sequence Number Sort sequence number.
  • the sequence number column is used to sort the order by titles in some other sequence other than alphabetically by order by title.
  • Last Changed Date Last Changed By Requires Stored Required stored procedure name Procedure The purpose of this column is to record the name of any stored procedure required to generate a report output. Some reports, because of their complexity, can not be created without the use of an SQL stored procedure. If a stored procedure is needed, its name would be found in this column. Timestamp Function Sort Function Number User assigned identification Last Used number. The function number is the unique identification of a function of the system. Function numbers are assigned by programmers. For example, ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • Order By SQL ORDER BY and/or GROUP BY The order by column contains the SQL GROUP BY and/or ORDER BY phrase for the report request.
  • the function subject code uniquely identifies subjects. Function subjects, types, and titles are used to build menus.
  • the function subject description is the long name for the subject.
  • management performance reports, operational reports, utility, user functions are all subject descriptions.
  • Last Changed Date Last Changed By Timestamp Function Type Function Type Code User assigned identification code.
  • Function Type Long name, description, or title for Description code.
  • the function type description is the meaning of the function type code.
  • report, update, menu, utility, and interface are all function type descriptions.
  • the usage start date is the date and time the update or report was activated.
  • Function Number User assigned identification number.
  • the function number is the unique identification of a function of the system. Function numbers are assigned by programmers. For example, ERS110 could be a function number assigned to a performance report.
  • Function numbers 000 to 099 are utility functions, 100 to 199 are performance or management reports, 200 to 299 are operational reports, 300 to 399 are audit reports, 400 to 499 are static table listings, 500 to 599 are user functions, 600 to 699 are interface functions, 700 to 799 are dynamic table update functions, 800 to 899 are static table update functions, and 900 to 999 are administration functions.
  • User Identification Logon user identification The user identification is the SQL database name for the user. Normally, it is the user's first name initial and full last name.
  • Rows Processed Quantity of rows retrieved or updated The quantity of rows retrieved for a reporting function or the quantity of rows inserted, updated, or deleted for an update function. Usage End Date Date/time function stopped being used.
  • the usage end date is the date and time the function completed processing the rows.
  • the difference between the usage start and end dates is the seconds required to retrieve the report rows or post the changes to the database for an update function.
  • Last Changed Date Last Changed By Timestamp Inventory Inventory System assigned identification Identification number.
  • the inventory identification is the unique identifier for a document. It is a system assigned integer, not user assigned.
  • Organization System assigned identification Identification number The organization identification is the unique identification for a company, department, or cost center.
  • the integer value is system assigned, not user assigned. Organizations own users and classifications.
  • Class Identification System assigned identification number The class identification is the unique identifier for the classification. This integer is a system assigned value, not user assigned.
  • the user identification is the SQL database name for the user. Normally, it is the user's first name initial and full last name.
  • Inventory Label First line of label The inventory Line 1 label consists of three columns that appear on the label for the document, file folder, or box. The first label line typically contains a name. For example, vendor name, customer name, person name, etc. for the document.
  • Inventory Label Second line of label The Line 2 inventory label consists of three columns that appear on the label for the document, file folder, or box. The second label line typically contains a geography.
  • Inventory Label Third line of label typically contains a geography.
  • the inventory Line 3 label consists of three columns that appear on the label for the document, file folder, or box.
  • the third label line typically contains numbers or dates. For example, part numbers, purchase order numbers, contract numbers, employee numbers, etc.
  • Location System assigned identification Identification number The location identification is the unique identifier for a shelf or drawer within an aisle or file cabinet in a storage area. It is a system assigned integer, not user assigned.
  • Record Type Code User assigned identification code The record type code defines importance to a classification.
  • the center retention months is the quantity of months an inventory item is held in a records center or off site storage facility.
  • the office retention plus the center retention months equals the total retention period for a classification.
  • Office Retention Quantity of months stored on site. Months The office retention months is the quantity of months an inventory item is held in an office storage area before it is moved to a long term, off site storage facility.
  • the office retention plus the center retention months equals the total retention period for a classification.
  • the inventory identification is the unique identifier for a document. It is a system assigned integer, not user assigned.
  • the user identification is the SQL database name for the user. Normally, it is the user's first name initial and full last name.
  • Request Type Code User assigned identification code is a user created code to define what needs to be done to an inventory item.
  • Location System assigned identification Identification number The location identification is the unique identifier for a shelf or drawer within an aisle or file cabinet in a storage area. It is a system assigned integer, not user assigned.
  • the request date is the date and time a user has requested and inventory item be moved from one media to another.
  • Last Changed Date Last Changed By Timestamp Inventory Class Identification System assigned identification Statistics number.
  • the class identification is the unique identifier for the classification. This integer is a system assigned value, not user assigned.
  • Location System assigned identification Identification number The location identification is the unique identifier for a shelf or drawer within an aisle or file cabinet in a storage area. It is a system assigned integer, not user assigned.
  • the quantity of inventory items by class and record type will be collected once a month or once a quarter.
  • Inventory Quantity Quantity of inventory items found The inventory quantity contains the number of inventory items found for a class and record type at a given point in time.
  • Last Changed Date Last Changed By Timestamp Location
  • Identification Number The location identification is the unique identifier for a shelf or drawer within an aisle or file cabinet in a storage area. It is a system assigned integer, not user assigned. Location Long name, description, or title. Description The location description is the meaning of a location number. For example, ‘Third drawer down’ or ‘Fourth shelf up’ are location descriptions.
  • Location Number User assigned identification number The location number is the user assigned identifier for a file cabinet drawer or shelf.
  • Location Type Code User assigned identification code for location type.
  • the Identification parent location identification is the unique identifier for building or file area that owns the location. Last Changed Date Last Changed By Timestamp Location Type Location Type Code User assigned identification code for location type.
  • the archive facility flag is a yes/no column used to define if the location is found in an archive facility.
  • An archive facility would be an offsite warehouse, for example.
  • Level Number Location hierarchy level number The level number defines what level of the location hierarchy this location can be found. Level one is the top level of the hierarchy and level number five is the bottom.
  • the media type description adds meaning to the media type code. For example, ‘Hardcopy’ and ‘Magnetic Tape’ are media type descriptions.
  • the Flag purpose of this column is to record whether a document being entered for a given media type should have a file name entered also. For example, if a document is entered into the system that has a media type of ‘hard disk’ , and the file name required flag is set to ‘yes’, then the system will prompt the user to input a file name for the document. If the file name required flag is set to ‘no’ then the system will not prompt the user for a file name when they input information about a document.
  • the object name is the SQL database name for a table or view.
  • the identification column contains the last or highest integer value assigned to the identification column in the table. For example, if the table name was tbl_dpt and the identification column contains 145, then the highest identification number assigned thus far to departments is 145.
  • Last Changed Date Last Changed By Timestamp Filler 1 This is a character field of 255 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Filler 2 This is a character field of 255 bytes used to pad one row in the identification table out to one page long.
  • This technique is use because SQLServer only has page locking, not row locking.
  • Filler 3 This is a character field of 255 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Filler 4 This is a character field of 255 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Filler 5 This is a character field of 255 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Filler 6 This is a character field of 255 bytes used to pad one row in the identification table out to one page long.
  • This technique is use because SQLServer only has page locking, not row locking.
  • Filler 7 This is a character field of 255 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Filler 8 This is a character field of 151 bytes used to pad one row in the identification table out to one page long. This technique is use because SQLServer only has page locking, not row locking.
  • Organization Organization System assigned identification Identification number The organization identification is the unique identification for a company, department, or cost center. The integer value is system assigned, not user assigned. Organizations own users and classifications.
  • Organization Code User assigned identification code The organization code is a user assigned identification for a company, department, or cost center. Organization Name Long name, description, or title.
  • the organization name is the meaning for the organization code.
  • ‘Account Payable’, ‘Payroll’ , ‘Inside Sales’ are all organization names for cost centers.
  • Organization Type User assigned organization type Code code The organization type code defines if an organization is a company, department, or cost center. Parent Organization Parent owner for organization. Identification The parent organization identification is the unique identification for a company, or department that owns the organization. Last Changed Date Last Changed By Timestamp Organization
  • Organization Type User assigned organization type Type Code code The organization type code defines if an organization is a company, department, or cost center.
  • the level number defines at what level of the organization hierarchy this organization (company, department, or cost center) can be found. Level number one is the top of the hierarchy and level number five is the bottom.
  • Last Changed Date Last Changed By Timestamp Record Type Record Type Code
  • the Procedure record type procedure states the office policy associated with the record type. For example, ‘Inventory items assigned a classification having an official record type can only be deleted by a Department Coordinator’.
  • Last Changed Date Last Changed By Timestamp Request Type Request Type Code User assigned identification code.
  • the request type code is a user created code to define what needs to be done to an inventory item.
  • Last Changed Date Last Changed By Timestamp Retention Retention Reference User assigned identification Reference number.
  • the retention reference column is used to store the identification number for the reference document or law governing a set of classes and their retention periods. For example, ‘26 CFR 1.6001.1’ is a document defining how checks ought to stored.
  • Last Changed Date Last Changed By Timestamp Retention Retention Start User assigned identification code.
  • Start Code The retention start code defines when the retention period of the document starts. The quantity of months an inventory item is held may start when the document first created, or it may start when the document is moved to an off site storage facility.
  • Retention Start Long name, description, or title Description The retention start description adds meaning to the retention start code. It is the office policy stating when the retention period begins for a document.
  • Last Changed Date Last Changed By Timestamp Sensitivity Sensitivity Code User assigned identification code.
  • Last Changed Date Last Changed By Timestamp Synonym Synonym System assigned identification Identification number.
  • the synonym identification is the unique identifier for the synonym. This integer is a system assigned value, not user assigned.
  • the synonym name is the name of the synonym. Synonyms are alternate means to refer to a classification. Synonyms can be class codes, class names, or any value the user wishes.
  • the class identification is the unique identifier for the classification. This integer is a system assigned value, not user assigned.
  • the user identification is the SQL database name for the user. Normally, it is the user's first name initial and full last name.
  • Default Location System assigned identification Identification number The location identification is the unique identifier for a shelf or drawer within an aisle or file cabinet in a storage area. It is a system assigned integer, not user assigned.
  • Organization System assigned identification Identification number The organization identification is the unique identification for a company, department, or cost center. The integer value is system assigned, not user assigned. Organizations own users and classifications. Mail Stop User's mail stop.
  • Output Directory Directory path for extract files.
  • the output directory is the disk drive and directory name where the user would like extract files placed. If the user elects to have a report exported into a spread sheet, then the spread sheet will be placed in the output directory.
  • Last Changed Date Last Changed By Timestamp User Class Class Identification System assigned identification number.
  • the class identification is the unique identifier for the classification. This integer is a system assigned value, not user assigned.
  • the user identification is the SQL database name for the user. Normally, it is the user's first name initial and full last name.
  • Access Code User assigned identification code The access code defines what a user can do to a database object.
  • Last Assigned Date Date last used. The date and time the class was last assigned by the user to a document. This column can help determine if a user has ever assigned this class to a document. Last Changed Date Last Changed By Timestamp
  • FIG. 13 is a logical view of the database. It shows all the entities or tables and their attributes or columns. The purpose of this diagram is to provide a more detailed picture of the database and its contents.
  • Triggers are business rules embedded in the database. These rules are activated every time a row is added, changed, or delete for a table. They can be used insure referential integrity, enforce security, and/or calculate values for columns. The triggers defined for this system are described below by table. Note, that referential integrity triggers are not listed. They are too numerous to display, but will be part of the application.
  • Update Trigger See if the class code is being changed. If it is, then update the synonym name in the synonym table and the synonym name in the class synonym table.
  • Delete Trigger Delete the corresponding rows in the synonym table and the class synonym table where the following is true:
  • Synonym name equals class code and user identification equals ‘SA’ or
  • Synonym name equals classification title and user identification equal ‘SA’
  • Delete Trigger Create a cascading delete that will remove the function form all other tables.
  • Update Trigger If the function type is changed for ‘REPORT’ to something else, a search for the function column and function sort tables should be performed. If there are any rows in these tables, then they ought to be deleted.
  • Insert Trigger The function type column in the function table must be set to ‘REPORT’. If the function is not a report, then it should not have rows in the function column or sort table.
  • the relationship code can only have values of ‘EQUAL’, ‘LIKE’ or ‘BOTH’. Also the column type values can only be ‘CHAR’, ‘INT’, ‘DATE’, and ‘FLOAT’.
  • Update Trigger The relationship code can only have values of ‘EQUAL’, ‘LIKE’or ‘BOTH’. Also the column type values can only be ‘CHAR’, ‘INT’, ‘DATE’, and ‘FLOAT’.
  • Insert Trigger There can only be one row having a default sort flag value of ‘Y’ for yes for each function.
  • Update Trigger There can only be one row having a default sort flag value of ‘Y’ for yes for each function.
  • Insert Trigger The usage start date must be less than the usage end date.
  • Update Trigger The usage start date must be less than the usage end date.
  • Insert Trigger If the level number for the location type is one, then the parent location identification equals the location identification. If the level number of the location type is not equal to one, then the parent location identification can not be equal to the location identification.
  • level number is not equal to one, then the level number must be equal to one minus the level number for the parent location.
  • Insert Trigger The object purpose can not be null if the object type code is ‘V’ for view.
  • Insert Trigger The object purpose can not be null if the object type code is ‘V’ for view.
  • Insert Trigger Insure that the object type column value in the object table is set to ‘U’ for user table.
  • Update Trigger Insure that the object type column value in the object table is set to ‘U’ for user table.
  • Insert Trigger If the level number for the organization type is one, then the parent organization identification equals the organization identification. If the level number of the organization type is not equal to one, then the parent organization identification can not be equal to the organization identification. If the level number is not equal to one, then the level number must be equal to one minus the level number for the parent organization.
  • Update Trigger If the level number for the organization type is one, then the parent organization identification equals the organization identification. If the level number of the organization type is not equal to one, then the parent organization identification can not be equal to the organization identification.
  • level number is not equal to one, then the level number must be equal to one minus the level number for the parent organization.
  • Insert Trigger When inserting a new user, create rows for the user class table. Copy the user class rows for the person doing the inserting and place them into the user class table for the new user. The processing steps are:
  • Delete Trigger Create a cascading delete that will remove the user for all other tables.
  • Insert Table There can only be one row having a default class flag value of ‘Y’ for yes for each user.
  • Update Table There can only be one row having a default class flag value of ‘Y’ for yes for each user.
  • Insert Trigger There can only be one row having a default database flag value of ‘Y’ for yes for each user.
  • Update Trigger There can only be one row having a default database flag value of ‘Y’ for yes for each user.
  • the physical database model displays all the SQL attributes about each column in the application. It is the combination of the logical view, abbreviations, triggers, and user defined datatypes.
  • the physical database model is presented in FIG. 14.
  • the following table displays the SQL attributes (column name, datatype, null option, etc.) for each column being stored.
  • Entity Column Alternate Foreign Prime Column Name Attribute Name Name Key Key Key Datatype Null Option Access Access Code acc_cd (PK) char(1) NOT NULL Access Description dsc (AK1) varchar(40) NOT NULL Last Changed Date 1st_chg_dte datetime NULL Last Changed By 1st_chg_by char(20) NULL Timestamp timestamp timestamp NULL Class Class cls_idn (PK) int NOT NULL Identification Abstract abs varchar(255) NOT NULL Class Code cls_cd (AK1) char(10) NOT NULL Classification Title tle varchar(40) NOT NULL Classification Title tle_ext varchar(40) NOT NULL Extended Center Retention ctr_rtnt_mth int NOT NULL Months Organization org_idn (FK
  • the client workstation is the personal computer run by the average user. Its purpose is to create word processing documents, spreadsheets, presentations, and to run the ERS application.
  • Network Software such as Novell or Windows for Workgroups.
  • the developer workstation is used to construct and maintain the application. It contains all the tools needed to modify the source code for the system.
  • Network Software such as Novell or Windows for Workgroups.
  • the server supports the user community and developers. It acts as the centralized storage point for the system's database and archived documents.
  • the server should support two modems for remote access trouble shooting, demonstrations, and training sessions. The amount of disk space requested should be enough to support two versions of the database.

Abstract

An interlingual mechanism to achieve uniformity when classifying anything by subject. Using generic terminology in an especially oriented hierarchical structure, it directs the user to a single classification. The system captures acronyms, vernacular and industry-specific, as well as foreign terms, into a thesaurus that can be modified and appended as classification needs change. The system “learns” as synonyms are added to “family groups”, capturing differences in individual perception. Searching for an entity is quickly successful by reversing the process. To ask the system for the location of any item, a descriptive term is entered that the individual believes best describes the object in question. If this entry results in a “hit”, all information pertaining to the item is then available to query. If the entry term does not find a match in the generic structure, the system will search the synonym data base for a match. By arranging “generic terms” in a classified format, the system provides a single location for each record series and enables linking all relevant administrative document management functions and legal retention requirements. Selective and timely purging of documents is thus made possible, greatly facilitating the management of information for both current and prospective use.

Description

    BACKGROUND OF THE INVENTION
  • The exponential growth of information within an enterprise which is stored in individual document form has created a need for a reliable mechanism to purge individual documents when no longer legally or otherwise required, as well as locate them in an efficient manner. [0001]
  • In an age when the growth of information contained within documents has been exponential, a missing element is the ability to determine the proper life cycle for a document, and thus, make it possible for the document to be purged on a scheduled basis. However, to safely accomplish this purging process, a document management system typically requires that a significant amount of detail be stored with the document. [0002]
  • Since all retention scheduling is based on the subject matter of a document, it is essential that the system identify the subject matter of all documents in a consistent manner. Additionally, the terms used to identify the subject matter must conform to the terms used in legislation to identify documents as well as the terminology in current use within the enterprise. [0003]
  • The present invention provides a reliable mechanism to accomplish this task. [0004]
  • In systems having this capability, the “type” of document must also be determined. Different types of documents within the same subject matter area may have different retention requirements. The system must be able to determine the type of document at the outset. This “type” information specifies whether a particular document is “official” or “informational” and whether it is also “vital” or “sensitive.” The type of document determines the level of protection afforded and has a direct impact on determining the life-cycle of the document. Additionally, document type impacts the decision as to the media selected to store it, whether electronic, paper or film. [0005]
  • Official documents are those documents identified in a retention schedule as having either administrative or legislative retention requirements. Properly, only official documents are subject to archiving. [0006]
  • Informational documents (largely copies) have their own destruction schedule based on need. They are not archived and their life cycle must not exceed official documents of the same subject. They are destroyed at the office level when their usefulness is over. Normally, informational documents have a substantially shorter life-cycle than official documents pertaining to the same subject. [0007]
  • Vital documents are those that are absolutely essential to the conduct of the enterprise and whose loss would be hugely expensive or would irrefutably damage continued operations. [0008]
  • Sensitive documents contain, for example: [0009]
  • 1. Personnel information which provides confidential data. [0010]
  • 2. Information that in the hands of a competitor could be used to embarrass or cast a bad image on the enterprise with its customers or the public. [0011]
  • 3. Marketing, product development or corporate changes that could sabotage effectiveness. [0012]
    • SUMMARY OF THE INVENTION
  • A system is disclosed for providing a true interlingual mechanism to achieve uniformity when classifying documents by subject to assist in the management, complying with retention requirements and long term storage of documents of an organization. In this connection, as used herein, the term document includes, without limitation, the hard copy and digitally stored version of the output of a computer program such as a wordprocessor, microfilm or microfiche, correspondence of all types and office folders which themselves may contain documents. Although not a document by this definition, objects such as furniture and the like may also be classified by creating a label (in this case, the document) which contains all of the relevant classification information for the object. Using generic terminology in a hierarchical structure, use of the system directs a user of the system to a single classification for any document. The system captures acronyms, vernacular and industry specific terms as well, as foreign terms, into a thesaurus that can be modified and appended as classification needs change. The system learns as synonyms are added to the hierarchical structure capturing differences in individual perception. [0013]
  • Legislative terminology describes document retention requirements by subject. In this connection, two major issues exist: [0014]
  • 1. Documents whose retention is covered by legislative requirements must be retained a prescribed period of time, after a certain event takes place, e.g., after an audit is completed, when the document is superseded, when its purpose has been completed (such as a contract) and for certain corporate documents). [0015]
  • 2. Legal penalties exist, including fines, where purging of documents occurs before their legal requirements have been met. On the other hand, retaining documents longer than their legal requirement can have both a “sword and a shield” effect where litigation is concerned. [0016]
  • With billions of documents being filed every day, the volume of documents subject to legislative retention offer additional justification for a system that makes retrieval inexpensive and predictable. Current practices involving the classification of documents make it difficult to identify documents by subject. However, retention legislation identifies documents by subject. [0017]
  • Accordingly, all documents must be identified by subject and ultimately destroyed consistently with the enterprise's official retention schedule. [0018]
  • In most cases legislation is silent as to the specific media to be used to “house” a document, This means that legislative retention requirements apply to all media. For example, if the paper document is destroyed and it continues to exist on magnetic media, the retention schedule is not effective and is not being enforced. This invention provides a reliable structure to accomplish compliance with all legislative retention requirements. [0019]
  • In addition to classifying documents to ensure compliance with legislatively or other required retention schedules, as a bi-product, the invention includes the capability of searching for the location of a particular document. To use the system for the location of any particular document, a descriptive term is entered at a query prompt that the user believes best describes the subject matter of the document in question. If this entry results in a hit, all information pertaining to the document is then available to query. An example of a screen display in which such a query may be made is shown in FIG. 3. For example, entry of a descriptive term produces a particular subject classification (i.e., a class code as described below). [0020]
  • For a typical user, there is just a small set of documents within his or her responsibility. Thus, once within this relatively small set of documents, if only those assigned a particular class code are deemed to be “hits,” the user is able to easily select the correct document from the set of hits. For users whose responsibility includes a large set of documents such that it would not be feasible to select a desired document from a list of documents assigned a particular class code hit list, a full range of attribute filters would be available to narrow the hits. Examples of such attribute filters include location (physical location such as file cabinet or work station), acronym (class codes, alpha and/or numeric references, i.e., form numbers, department IDs), organizational unit (cost center number, department number), subject description (i.e., class code), label description (e.g., three line description for a particular tangible asset as shown in FIG. 1. If the entry term does not find a match in the hierarchical structure, the system will search a synonym database for a match. If the search of the synonym database also does not yield the desired document, it must be concluded that the desired document has not been classified. [0021]
  • By arranging terms from the general to the specific in a consistent classification format, the system is able to specify a physical location for a hard copy of a document by office, box, in draw and folder, or of a document on magnetic or similar media by diskette location, hard disk drive location (i.e., computer) or network drive location (i.e., server) and file name. In this manner, for each document within a set of records, linking all relevant administrative document management functions and legal retention requirements for each document classified in the system is possible. [0022]
  • Selective and timely purging of documents is thus made possible, greatly facilitating the management of information for both current and prospective use.[0023]
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a screen display showing a query screen for performing a search. [0024]
  • FIG. 2 is a screen display showing a list of synonyms. [0025]
  • FIG. 3 is a screen display showing a query screen for performing a search. [0026]
  • FIG. 4 is a screen display showing the results of a query of the type shown in FIG. 3. [0027]
  • FIG. 5 is a screen display showing a query screen for performing a search. [0028]
  • FIG. 6 is a screen display showing the results of a query of the type shown in FIG. 5. [0029]
  • FIG. 7 is a screen display showing the results of a query of the type shown in FIG. 5. [0030]
  • FIG. 8 is a block diagram showing a high level view of the functions performed by the invented system. [0031]
  • FIG. 9 is a block diagram showing the store documents function. [0032]
  • FIG. 10 is a block diagram showing the maintain inventory function. [0033]
  • FIG. 11 is a block diagram showing the maintain system function. [0034]
  • FIG. 12 shows the layout for the entity relationship diagram shown in FIGS. [0035] 12A-12F.
  • FIGS. [0036] 12A-12C show the first row of Figures forming the entity relationship diagram.
  • FIGS. [0037] 12D-12F show the second row of Figures forming the entity relationship diagram.
  • FIG. 13 shows the layout for the logical database model shown in FIGS. [0038] 13A-13L.
  • FIGS. [0039] 13A-13D show the first row of Figures forming the logical database model.
  • FIGS. [0040] 13E-13H show the second row of Figures forming the logical database model.
  • FIGS. [0041] 13I-13L show the third row of Figures forming the logical database model.
  • FIG. 14 shows the layout for the physical database model shown in FIGS. [0042] 14A-14L.
  • FIGS. [0043] 14A-14D show the first row of Figures forming the physical database model.
  • FIGS. [0044] 14E-14H show the second row of Figures forming the physical database model.
  • FIGS. [0045] 14I-14L show the third row of Figures forming the physical database model.
    • DETAILED DESCRIPTION OF THE INVENTION
  • This invention is a computer based system which provides a reliable structure to properly identify and track documents used by an enterprise throughout their life cycle to provide an efficient and easy to use mechanism to ensure that document retention requirements are complied with while enabling the orderly destruction of documents once their retention requirements have been satisfied. [0046]
  • In order to meet all the requirements of a document management system, it is necessary to develop a technique for classifying documents by subject. For this reason, the requirements of a document management system are more disciplined than any other component of an information resource management environment. One particular component is a detail tracking mechanism that must be in place to know where each document is and how many copies exist so that they all may be destroyed according to schedule. [0047]
  • Schedules must be rigorously followed. If the documents in question have to do with a litigation, the court in which the litigation is pending will test to determine if a true schedule exists and if records are destroyed in accordance with the schedule. If a true retention schedule does not exist, the company can be sanctioned for destroying records related to the case. The source of protection, and limiting exposure, lies within a disciplined document management program and enforcement of document retention policies covering all media. [0048]
  • Classification is performed when the document is created. There are a number of reasons for developing software that makes retrieval easier and control and tracking a bi-product of the processing which of necessity is already being performed. One factor which leads to performing document classification at document creation is placing the responsibility for classifying the document on the individual creating the document. The individual creating the document is in the best position to provide its proper classification. The time it takes to learn proper classifications for the subject areas involved for the normal user is relatively short, typically a matter of hours. This small investment in time substantially reduces the time required for searches to locate documents for retention schedule compliance and for retrieval. Learning to classify at the time a document is “saved” enables the use of the same procedure when a search needs to be performed. [0049]
  • Almost all search engines in use today rely on various mechanical techniques and sophisticated algorithms to find documents that have been saved by an author using “on-the-fly” techniques for classifying. This invention provides a mechanism for the author/creator of the document to classify the document properly, and, in such a form that anyone searching for the document would, following the same sequence, find the document with ease. This makes investing a small amount of time on the “save” side important because it makes the search time much more productive and far quicker than prior art approaches. [0050]
  • The selection of terms and what are referred to as classes used in a hierarchical structure to classify documents must be of the most generic form possible. Terms used in each class, i.e., Major, Primary, Secondary, Tertiary and Quaternary, requires that each word has a relative relationship and the same value level as any other word in that grouping. In order to simplify the subject description, where possible, the first two letters of the word used in each level of hierarchy is selected as its acronym. [0051]
  • In a very short period of time, the acronyms become easily translatable as the individual users have an opportunity to work with the system. This ease of learning is more easily understood since the range of subjects in use by a predominance of users is limited to a very small number, usually between 10 and 15 classes. Rarely does anyone using a typical work station require global searches, i.e., searches extending through multiple organizational units. Such searches would require special security clearance and a substantial knowledge of system navigation. [0052]
  • The invention also employs the intelligent use of synonyms, i.e., a synonym database, as pointers. Synonyms are used to direct the user to the “official” term for the appropriate classification. To populate the synonym database, a document inventory is taken to collect the local terms being used to describe documents. It should be noted that a detailed inventory of document descriptions currently existing (i.e., prior to implementation of the invention) is not needed. However, when a system implementing the invention is initially used, it is preferable that there be some inventory of terms (synonyms) in use be available to the new users of the system to improve acceptance of the system and productivity. This inventory or synonym database can be created manually, i.e., by manual entry as part of the Browse Synonym function shown in FIG. 9. The synonym database contains all or a subset of terms in use by the organization to refer to a particular document instead of the “official” term used to classify that document. A screen display used for this purpose is shown in FIG. 2. [0053]
  • Synonyms are assigned to each level of the hierarchy. This enables anyone to use a term that they perceive is related to the subject matter and be directed to a unique official classification. [0054]
  • There should be only one location in the hierarchy for any document. If it appears that there is more than one location, it generally means that the selected classification is not as precise as it should be, and it is likely that an additional classification should be added. [0055]
  • One of the most important strengths of using a synonym database to link the elements of the hierarchy is that it makes possible the use of local vernacular. Changes to the hierarchy are rare, leaving its structure stable. Almost all changes can be easily accomplished through changes in synonyms. [0056]
  • Because of the global scope of this invention, such as its use on the Internet, the use of foreign language terms in the synonym database makes it possible for the system to uniformly classify documents (as well as any other item) using any language throughout the world. With this range of flexibility, a unique classification tool exists for any multi-national information system. [0057]
  • One of the important aspects of this invention relates to its record retention components which create a records retention linkage. This includes tracking and providing a direct linkage to the terminology used in the U.S. Code of Federal Regulations and to similar legislative retention requirements of any other country. In addition to identifying the media, it also catalogs the type of record. [0058]
  • The document type determines the essential security requirements for these documents. [0059]
  • Use of the invention provides a system that ensures uniformity by all users when classifying documents by subject, i.e., a uniform subject classification system. This invention provides a hierarchically structured, subject oriented database, populated with terms in current use by the enterprise (i.e., chart of accounts and organizational chart) and by legislative references which pertain to the retention of documents. A typical set of class codes names with class code acronyms in a uniform subject classification is shown in Appendix I. [0060]
  • When a document is “saved,” as on a magnetic media, or simply classified manually as in hardcopy documents, the system provides classification tools that enable the process to “find” the single proper classification in the hierarchy. [0061]
  • The “search” process is the reverse, where the search word (subject description) is entered into the system and the classification tools lead the user to the proper classification and then to the document being sought. [0062]
  • Supplemental databases containing synonyms are available for each line of the classification scheme. These databases can be added to by the user and in this way translate acronyms, local vernacular, abbreviations and foreign terms that reveal the user's perception of the subject being sought. [0063]
  • Associated with all documents belonging to the same subject (referred to as a “File Series”) are a body of particular attributes set forth by legislative or informational requirements. [0064]
  • The invention provides a tracking mechanism to enable protecting, finding and retrieving a document, or group of documents (file series) when needed and to ultimately locate and destroy them when their life-cycle has been completed, as specified by an official retention schedule. [0065]
  • Using The Uniform Subject Classification System [0066]
  • I. Build A Classification Structure [0067]
  • Select terms from legislative, business, government and other industry sources. Adapt terms used in the Code of Federal Regulations, state statutes and terms that are industry specific. Organize selected terms into hierarchical order, i.e., primary class and sub-classes (i.e., secondary, tertiary, etc.). [0068]
  • II. Apply Synonyms To The Classification Structure [0069]
  • Assemble synonyms into a thesaurus and connect the synonyms with a particular file series (i.e., a line in the class hierarchy). [0070]
  • Build a database of local vernacular, acronyms, technical terms, etc. [0071]
  • Organize the database into the classification structure built in step I, appending to the synonym database, as appropriate. [0072]
  • Modify major classes, primary classes, secondary classes, etc. as required to fit the working environment. [0073]
  • III. Classify Documents [0074]
  • Determine major classes, e.g.,: Accounting, Administration, Finance, Marketing, Corporate, Legal, Engineering, etc. Major classes should be by functional class, not organizational names. [0075]
  • Using the first two characters in the class description, assign functional descriptions from the general to the specific, under the selected major class, then do the same thing for the selected primary class, secondary class, etc., until no further delineation is needed to classify all documents of interest. In most cases, no more than tertiary or quaternary classes are needed. For example, a document containing “Employee Expense Accounts” would be classified as follows: [0076]
  • AC Accounting (MAJOR) [0077]
  • PA Payables (PRIMARY) [0078]
  • EM Employee (SECONDARY) [0079]
  • which results in the Uniform Subject Classification Code: [0080]
  • ACPAEM ACCOUNTING, PAYABLES, EMPLOYEE [0081]
  • Depending on need, class levels can be adjusted to fit local conditions. [0082]
  • [0083] AD Administration Level 1
  • [0084] FA Facilities Level 2
    AD Administration Level 1
    FA Facilities Level 2
    BU Buildings Level 3
      OF Offices Level 4
       FU Furnishings Level 5
        AR Art Level 6
        DE Desk Level 6
  • With the above class levels, the following are examples of acronyms which could be employed: [0085]
  • ADFAOF Administration, Facilities, Offices [0086]
  • ADFAOFFU Administration, Facilities, Offices, Furnishings [0087]
  • ADFUDE Administration, Furnishings, Desk [0088]
  • ADFUAR Administration, Furnishings, Art [0089]
  • The particular acronym which would be employed in any given situation would depend on how many levels are needed to identify particular items of interest so that they can be efficiently retrieved. For example, in some situations just two or three levels are sufficient because the number of items which are classified at that level of detail is sufficiently small such that a user can see on a single screen display all potential hits from which the desired item may be selected. In other situations, more levels may be needed where there are numerous items that satisfy a particular class code. [0090]
  • In these examples, the document would be a label affixed to the artwork or the desk. Such labels may also be affixed to a document or folder or box containing documents and/or folders. Additional data appearing on the label, referred to as “label lines,” providing specific descriptions beyond the class itself. Label line descriptions are extensions of the class code and are searchable using well known automated search techniques. Labels are a part of the record when attached with the same retention value as the record which normally is then case when the label is associated with a particular folder. It should be noted that labels do not have a retention value when attached to an asset such as a desk. [0091]
  • IV: Finding Documents using the Uniform Subject Classification System [0092]
  • To illustrate this step, assume that it is desired to find job descriptions for an employee's new assignment as Budget Analyst, a newly created position. [0093]
  • To determine what may be available to aid in the creation of a new job description, enter lid the term “job description” in an inventory label search field to determine the location for all Job Descriptions. In this connection, the label search field is part of a query screen display, an example of which is shown in FIG. 1. [0094]
  • A typical response to the query provides the acronym of “HRJD”, or “[0095] Human Resources, Job Descriptions” as shown in the screen display of FIG. 3.
  • Next, assuming that any job description for an Analyst would help in creating the new job description, a search on the word “Analyst” within the “HRJD” segment of the hierarchy displays “HRJDSA” for job descriptions related to a range of Systems Analysts positions as shown in the screen display of FIG. 4 and “HRJDMA” for job description of a Marketing Analyst also shown in the screen display of FIG. 4. [0096]
  • Next, search for job descriptions that are involved with the budgeting process to identify the terms used in describing the tasks and skills required: [0097]
  • Enter the word “budget” as shown in the screen display of FIG. 5. [0098]
  • With full security clearance, the system would return: [0099]
  • “FIBU” or Finance, Budgets. [0100]
  • as shown in the screen display of FIG. 6. [0101]
  • From the synonym table, the display would show the contents of the class table for the item located by the search as containing: [0102]
  • “HRJD” or “Human Resources, Job Description”[0103]
  • as shown in the screen display of FIG. 4. [0104]
  • From the synonym table, a display would show the “folder” contents as containing a job description for “Manager, Budget Planning ” as shown in the screen display of FIG. 7. [0105]
  • By inspection, the searcher would select the analyst job descriptions as well as the one for “Manager” that might help in preparing the new description. [0106]
  • V. Associate The Class Acronym With Retention Data [0107]
  • Once steps I-III have been performed, it is possible to generate a report for each classification with the information shown in Table I. The information in the Med Typ, Rec Typ, Start After, Off Ret and RC Ret columns is initialized for each new document added to the system based on the class code. That is, for each class code, this information is stored in a class table and is predetermined based on business and government regulations. The information in the RCopy CC# column is obtained from a location table and is preset with a location code based on the workstation from which the data for the record was entered. By changed the data in the class table or location table, all documents associated with that class code or location would be changed as well. However, all of this information can be changed for individual documents, and once changed for a particular document, changes at the class table or location table level are not reflected in the records for such documents. [0108]
    TABLE I
    Class Med Rec Start Off RC RCopy
    No. Acronym Class Code Name Typ Typ After Ret Ret CC#
    124 AD Administration 0 O AR 12  0
    125 ADFU Furnishings 0 O CT 12 24 993452
    126 ADFUDE Desks 0 O SU 12 24 993452
    127 ADFUDEEX Executive 0 O SU 12 36 993452
  • In Table I, each row corresponds to a file series. [0109]
  • The column labeled “No.” contains a unique computer generated numbers used to represent each file series. [0110]
  • The column labeled “Class Acronym” contains the classification acronyms. [0111]
  • The column labeled “Class Code Name” contains the official terms to describe documents. [0112]
  • The column labeled “Med Typ” represents media type, i.e., paper, magnetic, microfiche, etc. Each media type in the example is represented by a number, for example, 0 for paper, 1 for magnetic, 2 for microfilm, 3 for microfiche, 4 for CD-ROM. [0113]
  • The column labeled “Rec Typ” represents record type, i.e., Vital (V), Informational (I), Official (O), Sensitive (S). [0114]
  • The column labeled Start After contains the date starting the retention, e.g., annual review (AR), completed (CT), superseded (SU), current year (CY) and final audit (FA). The retention start date marks the beginning of the “clock” as related to “upon the completion of the audit” when the record is superseded, or beginning when the contract has been completed, or when a license has expired. As a result, the creation date has little relevance to the legislative requirement for retention. [0115]
  • The column labeled “Off Ret” represents office retention in months. [0116]
  • The column labeled “RC Ret” represents records center retention in months. [0117]
  • The column labeled “RCopy CC#” represents record responsibility copy cost center number. This is the cost center number as identified in the Chart-of-Accounts for the organization. This cost center is the only cost center which can send documents in this file series to a long term storage facility (for archival). All other holders of copies of such documents (i.e., informational copies) would have been instructed to destroy such copies at the office level according to a predefined schedule for destruction of such documents, which as previously noted, would predate scheduled destruction of the official copy of the document. An expanded example of a retention schedule appears in Table II. [0118]
    TABLE II
    REPRESENTATIVE CLASSIFIED RETENTION SCHEDULE
    WITH CITATIONS AND REFERENCES
    CLASS MED REC START OFF RC TOT R COPY
    ACRONYM CLASS CODE NAME TYP TYP AFTER RET RET RET CC# REFERENCE
    AC ACCOUNTING 1 O FA 12 0 12 55000 26 CFR 1.6001.1
    ACAJ ADJUSTMENTS 1 O CY 12 24 36 55260 26 CFR 1.6001.1
    ACAJIT INVENTORY 1 O CY 12 36 48 55260 ADMIN. DECISION
    ACAJITCN CONSOLIDATIONS 1 O CY 12 12 24 55260 26 CFR 1.6001.1
    ACAJITMN MAINTENANCE 1 O CY 36 0 36 55260 ADMIN. DECISION
    ACAJITWH WAREHOUSE 1 O CT 84 0 84 55260 26 CFR 1.6001.1
    ACAJRB REIMBURSEMENTS 1 O CY 12 24 36 55800 26 CFR 1.6001.1
    ACAS ASSETS 1 V CY 24 36 60 55300 26 CFR 1.6001.1
    ACASAM AMORTIZATIONS 1 O FA 24 36 60 55330 26 CFR 1.6001.1
    ACASAP APPROPRIATIONS 1 O CT 12 12 24 55330 26 CFR 1.6001.1
    ACASCA CAPITALASSETS 1 V FA 24 216 240 55330 26 CFR 1.6001.1
    ACASCACC COMPANY VEHICLES 1 O CT 120 0 120 55330 26 CFR 1.6001.1
    ACASDE DEPRECIATING 1 O FA 12 24 36 55340 26 CFR 1.312-15
    ACASIT INVENTORY 3 V FA 24 36 60 55440 26 CFR 1.6001.1
    ACASITSP SPECIAL ACCOUNTS 1 O FA 12 24 36 55440 26 CFR 1.6001.1
    ACASITSU SURPLUS 1 O CT 12 24 36 55440 26 CFR 1.6001.1
    ACASITWH WAREHOUSE 1 O FA 12 72 84 55440 26 CFR 1.6001.1
    ACASITWHDI DISBURSEMENTS 1 O FA 12 60 72 55440 26 CFR 1.6001.1
    ACASPR APPRAISALS 1 O SU 24 216 240 55200 26 CFR 1.6001.1
    ACASVE VEHICLES 2 O CT 24 36 60 55440 26 CFR 1.6001.1
    ACAU AUDIT 1 O FA 24 36 60 56000 26 CFR 1.6001.1
    ACAUEX EXTERNAL 1 O FA 24 36 60 56000 26 CER 1.6001.1
    ACAUIN INTERNAL 1 O FA 24 36 60 56100 26 CFR 1.6001.1
    ACAZ AUTHORIZATIONS 1 O CT 24 48 72 55260 ADMIN. DECISION
    ACAZAV TRAVEL 2 O CT 24 0 24 55290 ADMIN. DECISION
    ACAZAVDO DOMESTIC 2 O CT 12 24 36 55290 ADMIN. DECISION
    ACAZAVIN INTERNATIONAL 2 O CT 12 24 36 55290 ADMIN. DECISION
    ACBA BANKING 2 O CY 24 12 36 55500 ADMIN. DECISION
    ACBACH CHECKS 1 O FA 12 48 60 55500 26 CFR 1.6001.1
    ACBACHCO CHECK COPIES 1 O CT 36 48 84 55500 26 CFR 1.6001.1
    ACBACHPC PETTY CASH 1 O CT 36 48 84 55500 26 CFR 1.6001.1
    ACBACHPY PAYROLL 3 O CY 12 48 60 55550 29 CFR 516.2,.5,.6
    ACBACHRE REQUEST 1 O CT 2 0 2 55500 ADMIN. DECISION
    ACBACO CASH OPERATIONS 3 O CT 12 60 72 55570 26 CFR 1.6001.1
    ACBADP DEPOSIT SLIPS 1 O CY 12 60 72 55570 26 CFR 1.6001.1
    ACBADR DRAFTS 1 O CY 12 60 12 55570 26 CFR 1.6001.1
    ACBALC LETTERS OF CREDIT 1 V CT 12 60 72 55570 26 CFR 1.6001.1
    ACBARE RECONCILIATIONS 3 O FA 18 24 42 55570 26 CFR 1.6001.1
    ACBARM BANK REMITTANCE 1 O CT 36 0 36 55570 26 CFR 1.6001.1
    ACBARS RESOLUTIONS 1 O CT 12 24 36 55500 26 CFR 1.6001.1
    ACBAST STATEMENTS 1 O FA 12 84 96 55570 26 CFR 1.6001.1
    ACBASTDO DOMESTIC 1 O FA 12 24 36 55570 26 CFR 1.6001.1
    ACBASTFO FOREIGN 1 O FA 12 48 60 55570 31 CFR 103.32
    ACBI BALANCE SHEETS/INCOME 2 O FA 24 456 480 77000 26 CFR 1.6001.1
    STATEMNT
    ACBIAN ANALYSIS 1 O FA 24 456 480 77000 26 CFR 1.6001.1
    ACBIPL PROFIT & LOSS 1 O FA 24 456 480 77000 26 CFR 1.6001.1
    ACCA CAPITAL EXPENDITURES 1 V FA 12 24 36 55440 26 CFR 1.6001.1
    ACCARE REQUESTS 1 O CT 24 446 470 55440 ADMIN. DECISION
    ACCAWP WORKING PAPERS 1 O CT 24 446 470 55440 ADMIN. DECISION
    ACCH CHART OF ACCOUNTS 1 V CY 12 987 999 55000 ADMIN. DECISION
    ACCO COST ACCOUNTING 1 O CY 12 24 36 55700 26 CFR 1.6001.1
    ACCR CREDIT 1 O FA 48 60 108 55800 26 CFR 1.6001.1
    ACCRAD ADJUSTMENTS 1 O FA 12 48 60 55800 31 CFR 103.33
    ACCRAL APPROVAL 1 O CY 12 48 60 55800 ADMIN. DECISION
    ACCRAP APPLICATIONS 1 O FA 24 36 60 55800 31 CFR 103.33
    ACCRCO COLLECTIONS 1 O CT 24 24 48 55800 29 CFR 516.2
    ACCRCODO DOUBTFUL ACCOUNTS 1 O CT 12 108 120 55800 26 CFR 1.6001.1
    ACCRDO DEPOSITS 1 O CY 24 0 24 55800 ADMIN. DECISION
    ACCRMM MEMOS 1 O CY 12 36 48 55800 26 CFR 1.6001.1
    ACCRRT REMITTANCES 1 O CY 24 48 72 55800 26 CFR 1.6001.1
    ACIN INVOICES 1 O CY 24 48 72 55100 ADMIN. DECISION
    ACINEX EXPORT 1 V CY 24 48 72 55100 ADMIN. DECISION
    ACIV INVESTMENT CREDITS 1 V CY 12 24 36 77000 26 CFR 1.46.1&
    1.6001.1
    ACJV JOURNAL VOUCHERS 1 V FA 24 216 240 55440 26 CFR 1.6001.1
    ACLE LEDGERS 1 V FA 12 987 999 55440 26 CFR 1.6001.1
    ACLEAS CAPITAL ASSETS 3 V FA 12 48 60 55440 26 CFR 1.6001.1;
    1.312-15
    ACLEBA BANK 3 V FA 24 96 120 55440 26 CFR 1.6001.1
    ACLEBO BOND 3 V FA 24 96 120 55440 26 CFR 16001.1
    ACLECA CASH 3 O FA 12 48 60 55440 26 CFR 1.6001.1
    ACLECC COST & CONTROL 3 O CY 12 36 48 55440 26 CFR 1.6001.1
    ACLECH CHECK REGISTER 3 O FA 12 60 72 55440 26 CFR 1.6001.1
    ACLECM CREDIT MEMOS 3 O FA 12 24 36 55440 26 CFR 1.6001.1
    ACLECU CREDIT UNION 3 V FA 12 60 72 55440 26 CFR 1.6001.1
    ACLEDI DIVIDEND 3 V CT 24 96 120 55440 26 CFR 1.56-2
    ACLEDR DRAFTS 3 O FA 12 48 60 55440 26 CFR 1.6001.1
    ACLEEX EXPENSE 3 O CT 12 36 48 55440 26 CFR 1.6001.1
    ACLEGL GENERAL LEDGER 3 V CY 12 987 999 55440 26 CFR 1.6001.1
    CCCP 3001
    ACLEIN INVOICES 3 V FA 12 48 60 55440 26 CFR 1.6001.1
    ACLEIS INSURANCE 3 V CT 12 72 84 55440 ADMIN. DECISION
    ACLEIV INVENTORY 3 V FA 24 216 240 55440 26 CFR 1.6001.1
    ACLENO NOTE REGISTER 3 V CT 24 12 36 55440 ADMIN. DECISION
    ACLEPA PAYABLE 3 O CY 12 987 999 55440 26 CFR 1.6001.1
    ACLEPB PAYROLL 3 V CT 12 24 36 55550 29 CFR 516.2,.5,.6
    ACLEPE PERSONNEL 3 O CT 24 96 120 55440 29 CFR 1627.3
    ACLEPR PROPERTY ACCOUNTS 3 V FA 24 216 240 55440 26 CFR 1.6001.1
    ACLEPU PURCHASING 3 O FA 12 24 36 55440 26 CFR 1.6001.1
    ACLERE RECEIVABLE 3 V CT 84 0 84 55440 ADMIN. DECISION
    ACLESA SALES 3 V CT 12 24 36 55440 ADMIN. DECISION
    ACLESE SECURITIES 3 V FA 24 96 120 77000 26 CFR 1.6001.1
    ACLEST CAPITAL STOCK 3 V FA 24 96 120 10000 26 CFR 1.56-5
    ACLESU SUBSIDIARY 3 V CT 12 24 36 55440 26 CFR 1.6001.1
    ACPA PAYABLES 3 O CY 12 24 36 55100 26 CFR 1.6001.1
    ACPAEM EMPLOYEE EXPENSES 3 O FA 12 24 36 55100 26 CFR 1.274-5
    ACPAEMCC CREDIT CARDS 3 O CY 12 48 60 55100 26 CFR 1.274-5
    ACPAFR FREIGHT 3 O FA 12 24 36 55150 26 CFR 1.6001.1
    ACPAIN INVOICES 3 O FA 24 48 72 55150 26 CFR 1.6001.1
    ACPALE LEASING 1 O FA 12 24 36 55100 26 CFR 1.6001.1
    ACPALEVE VEHICLES 1 O FA 24 36 60 55100 26 CFR 1.6001.1
    ACPALEVEQ QUESTIONNAIRES 1 O FA 24 36 60 55100 26 CFR 1.6001.1
    ACPANO NOTES, PAYABLE 1 O CT 24 12 36 55100 26 CFR 1.6001.1
    ACPAPP PREPAID EXPENSES 1 O CT 12 0 12 55100 ADMIN. DECISION
    ACPATC TELEPHONE BILLS 1 O CY 12 24 36 55100 26 CFR 1.6001.1
    ACPAVE VENDORS 1 O CY 12 24 36 55100 26 CFR 1.6001.1
    ACPAVO VOUCHERS 1 O CY 12 60 72 55100 26 CFR 1.6001.1
    ACPB PAYROLL 3 O FA 18 18 36 55300 29 CFR 516.2
    ACPBDE DEDUCTIONS 3 O CT 12 36 48 55300 26 CFR 31.6001.1
    ACPBTI TIME SHEETS 1 O CT 12 60 72 55300 29 CFR 516.2,.5,.6
    ACPBWX W-2'S & ALL GOVNMT PAYROLL RP 1 O FA 12 24 36 55300 29 CFR 516.2
    ACRC RECONCILIATIONS 3 O FA 12 24 36 55800 26 CFR 1.6001.1
    ACRE RECEIVABLES 3 V CT 12 24 36 55900 26 CFR 1.6001.1
    ACREAJ ADJUSTMENTS 3 O CT 12 108 120 55900 ADMIN. DECISION
    ACREBI BILLING 3 B CT 12 108 120 55900 29 CFR 516.2
    ACRT REMITTANCES 3 O CY 24 48 72 55910 ADMIN. DECISION
    ACTA TAX 1 O FA 12 48 60 55920 26 CFR 1.6001.1
    ACTACO CORPORATE 1 V CY 12 24 36 55920 26 CFR 1.6001.1
    ACTAFE FEDERAL 1 V FA 12 24 36 55920 26 CFR 1.6001.1
    ACTAFO FOREIGN 1 V FA 24 96 120 55930 29 CFR 516.2
    ACTALO LOCAL 1 V FA 12 24 36 55920 26 CFR 1.6001.1
    ACTAPB PAYROLL 1 V FA 12 24 36 55950 26 CFR 1.6001.1
    ACTAPR PROPERTY 1 V FA 12 24 36 55940 26 CFR 1.6001.1
    ACTASA SALES 1 V FA 12 24 36 55960 26 CFR 1.6001.1
    ACTAST STATE 1 V FA 12 24 36 55920 26 CFR 1.6001.1
    ACTAUN UNEMPLOYMENT 1 O FA 12 60 72 55945 26 CFR 31.6001.1
    AD ADMINISTRATION 1 O AR 12 0 12 20000 ADMIN. DECISION
    ADAG AGENDAS/SCHEDULES 1 O CT 12 36 48 21000 ADMIN. DECISION
    ADAS ASSOCIATIONS/ORGANIZATIONS 1 O CT 12 0 12 21000 ADMIN. DECISION
    ADBU BULLETINS/PUBLICATIONS 1 O CT 12 24 36 21100 ADMIN. DECISION
    ADBUDM DEVELOPMENT MATERIAL 1 O CY 12 6 18 21100 ADMIN. DECISION
    ADBUFR FREIGHT BROCHURES 1 O SU 12 24 36 21100 ADMIN. DECISION
    ADBUPD PRODUCTION 3 O CT 12 48 60 21000 ADMIN. DECISION
    ADCH CHRONOLOGICAL FILES 1 O CT 36 0 36 22000 ADMIN. DECISION
    ADCO COMMITTEES/MEETINGS 1 O CT 12 48 50 21000 ADMIN. DECISION
    ADCQ COMMUNICATIONS 1 O CY 12 0 12 25000 ADMIN. DECISION
    ADCR CONSULTANT INFORMATION 3 O CT 12 0 12 21000 ADMIN. DECISION
    ADCU CORRESPONDENCE 1 O CY 12 24 36 22000 ADMIN. DECISION
    ADCUID INTERDEPARTMENT 1 O CT 24 0 24 22000 ADMIN. DECISION
    ADCUIN INSURANCE 1 O CT 120 0 120 22000 ADMIN. DECISION
    ADCUMK MARKETING 1 O CT 24 0 24 22000 ADMIN. DECISION
    ADDP EDP-INFORMATION SYSTEMS 3 O CT 12 24 36 24000 ADMIN. DECISION
    ADDPLY TAPE LIBRARY 3 O CY 12 24 36 24100 ADMIN. DECISION
    ADES EMPLOYEE SUGGESTIONS 1 O CT 24 48 72 20000 ADMIN. DECISION
    ADIN INSURANCE 3 V CT 12 24 36 26000 ADMIN. DECISION
    ADINCL 3 O CY 12 72 84 26000 ADMIN. DECISION
    ADINCV COMPANY VEHICLES 3 O CT 12 24 36 26100 ADMIN. DECISION
    ADISPO PRINTOUT 1 O CT 12 0 12 26100 ADMIN. DECISION
    ADLS LEASING 3 V CT 12 24 36 26400 ADMIN. DECISION
    ADLSOF OFFICE EQUIPMENT 3 O CT 24 36 60 26400 ADMIN. DECISION
    ADLY LIBRARY 1 O CT 12 12 24 22000 ADMIN. DECISION
    ADOA OFFICE AUTOMATION 3 O CT 12 24 36 24000 ADMIN. DECISION
    ADOF OFFICE EQUIPMENT 3 O CT 12 24 36 22100 ADMIN. DECISION
    ADOR ORGANIZATION CHARTS 1 V SU 12 228 240 22000 ADMIN. DECISION
    ADPC PROCEDURES 3 V SU 24 216 240 22700 ADMIN. DECISION
    ADPL PLANNING 1 O SU 12 24 36 22700 ADMIN. DECISION
    ADPO POLICIES 1 O SU 12 228 240 22700 ADMIN. DECISION
    ADPR PROJECTS 3 O CT 24 36 60 22000 ADMIN. DECISION
    ADPS PRESENTATION MATERIAL 1 O CT 24 36 60 22000 ADMIN. DECISION
    ADPU PURCHASING 3 O CT 24 60 84 22800 ADMIN. DECISION
    ADPUDS DISTRIBUTION 3 O CY 12 24 36 22800 ADMIN. DECISION
    ADRE RECORDS MANAGEMENT 1 O CT 12 24 36 22900 ADMIN. DECISION
    ADRERQ REQUESTS 1 O CY 12 12 24 22900 ADMIN. DECISION
    ADRERS RETENTION SCHEDULE 1 O CT 36 963 999 22900 ADMIN. DECISION
    ADRERV VITAL RECORDS 1 O CT 0 999 999 22900 ADMIN. DECISION
    ADRG REPROGRAPHICS 1 O CT 12 24 36 22800 ADMIN. DECISION
    ADSH SHIPPING 3 O FA 12 24 36 23000 26 CFR 1.6001.1
    ADSHBL BILLS OF LADING 1 O CT 84 0 84 23000 26 CFR 1.6001.1
    ADSU SUPPLIES 3 O CY 12 0 12 22800 ADMIN. DECISION
    ADTR TRAVEL INFORMATION 3 O CY 12 24 36 20200 ADMIN. DECISION
    CO CORPORATE 1 V CY 12 987 999 10000 ADMIN. DECISION
    COAC ACQUISITIONS 1 V CT 24 216 240 12000 26 CFR 1.6001.1
    COAU AUDITS 1 V FA 12 24 36 15000 26 CFR 1.6001.1
    COBD BONDS 1 V CT 24 96 120 12000 ADMIN. DECISION
    COBO BOARD OF DIRECTORS 3 V CY 24 975 999 10100 CCCP 1500
    COBOCM COMMITTEES 3 O CT 24 975 999 10100 CCCPCH 15
    SEC1500+
    COBOCO COMPENSATION 3 O AR 24 48 72 10100 CCCPCH 15 SEC
    1500+
    COBOME MEETINGS/MINUTES 1 O CT 24 975 999 10100 CCCPCH 15 SEC
    1500+
    COBY BY-LAWS 1 V SU 24 0 24 10100 CCCPCH 15 SEC
    1500+
    COCH CHARTER 1 V SU 24 0 24 10100 CCCPCH 15 SEC
    1500+
    COCT CONTRIBUTIONS 3 O CT 12 24 36 13000 26 CFR 1.70A-13
    COCTMCH MEETINGS/MINUTES 1 O CT 24 975 999 13000 CCCPCH 15 SEC
    1500+
    CODB DOING BUSINESS AS 1 O CT 999 999 1998 10000 ADMIN. DECISION
    COER ELECTION RECORDS 3 O FA 24 216 240 10100 CCCPCH 15 SEC
    500+
    COHI HISTORY 1 O CY 12 24 36 10000 ADMIN.DECISION
    COIN ARTICLES OF INCORPORATION 1 V CT 120 0 120 10000 CCCPCH 15 SEC
    1500+
    COME MERGERS 3 V CT 24 216 240 12000 CCCP 1109
    COSE SEALS 1 V CT 120 0 120 10000 ADMIN. DECISION
    COSH SHAREHOLDERS 3 V SU 24 975 999 16000 CCCPCH 15 SEC
    1500+
    COSHME MEETINGS 1 V CT 24 975 999 16000 CCCP. Sec 15:1500+
    COSHNO NOTES 1 V CT 24 96 120 16000 ADMIN. DECISION
    COSHPR PROXIES 1 O CT 24 96 120 16000 CCCP Sec3
    COST STOCK 1 O CT 24 975 999 16100 26 CFR 1.57-5
    COSTDI DIVIDENDS 3 O CT 24 96 120 16100 26 CFR 1.6001.1
    COSTSB SUBSCRIBERS 3 O AR 24 12 36 16100 ADMIN. DECISION
    COSTSU SUBSCRIPTIONS 1 O AR 24 96 120 16100 ADMIN. DECISION
    EN ENGINEERING 1 O CT 12 24 36 90000 ADMIN. DECISION
    ENBP BLUEPRINTS 1 O CT 24 96 120 91000 ADMIN. DECISION
    ENDA DATA BOOKS 1 O CT 24 96 120 91000 ADMIN. DECISION
    ENDE DESIGNS 1 O CY 12 987 999 91000 ADMIN. DECISION
    ENDR DRAWINGS 3 O CT 12 987 999 91000 ADMIN. DECISION
    ENFO FORMULAS, TECHNICAL 3 V CT 24 96 120 91100 ADMIN. DECISION
    ENIE INDUSTRIAL ENGINEERING 1 O AR 24 0 24 91300 ADMIN. DECISION
    ENIEME METHODS IMPROVEMENTS 1 O CT 24 0 24 91300 ADMIN. DECISION
    ENMA MAPS 1 O CT 24 216 240 91000 ADMIN. DECISION
    ENPR PROJECTS 3 O CT 24 216 240 95000 ADMIN. DECISION
    ENSC SPECIFICATIONS 3 O CT 12 987 999 91100 ADMIN. DECISION
    ENST STANDARDS 1 V CT 12 987 999 91300 ADMIN. DECISION
    ENTS TESTING 3 O CT 12 0 12 96000 ADMIN. DECISION
    FI FINANCE 1 O FA 12 24 36 70000 26 CFR 1.6001.1
    FIAN ANALYSIS/STUDIES 1 O CY 24 12 36 71000 ADMIN. DECISION
    FIBU BUDGETS 1 O CT 12 24 36 72000 ADMIN. DECISION
    FIBUAZ AUTHORIZATIONS 1 O CT 24 12 36 72000 ADMIN. DECISION
    FIBUES ESTIMATES 1 O CT 12 72 84 72000 ADMIN. DECISION
    FIBUPE PERFORMANCE ANALYSIS 1 O CT 12 24 36 72000 ADMIN. DECISION
    FIBUPL PLANNING 1 O SU 12 24 36 72000 ADMIN. DECISION
    FIBURD RESEARCH & DEVELOPMENT 1 O CT 24 12 36 72000 ADMIN. DECISION
    FICA CAPITAL PLAN 1 V FA 12 24 36 72500 26 CFR 1.6001.1
    FICAEX EXPENDITURES 3 O FA 24 12 36 72500 26 CFR 1.6001.1
    FIEC ECONOMIC ANALYSIS 1 O SU 24 96 120 72200 ADMIN. DECISION
    FIFI FINANCIAL REPORTS 1 V CT 12 24 36 72200 ADMIN. DECISION
    HR HUMAN RESOURCES 1 O AR 12 0 12 30000 ADMIN. DECISION
    HRAF AFFIRMATIVE ACTION 1 O CY 12 24 36 31000 41 CFR 60-741.5,52.
    HRBE BENEFITS 3 V CT 12 48 60 32000 26 CFR 1.414(F)-1
    HRBEBP BONUS PLAN 3 O CT 12 96 108 32000 ADMIN. DECISION
    HRBEIN INSURANCE 1 O CT 12 24 36 32100 ADMIN. DECISION
    HRBEINAU AUTHORIZATIONS 1 O CT 12 72 84 32100 26 CFR 1.6001.1
    HRBEINCC COMPANY VEHICLES 1 O CT 0 0 0 32200 26 CFR 1.6001.1
    HRBEINCL 1 O CT 12 146 158 32100 26 CFR 1.6001.1
    HRBEINDE DENTAL 1 O CT 12 60 72 32100 26 CFR 1.6001.1
    HRBEINDI DISABILITY 1 O CT 12 60 72 32100 26 CFR 1.6001.1
    HRBEINLI LIFE 1 O CT 12 48 60 32110 29 USC 626
    HRBEINME MEDICAL 1 O CT 12 72 84 32110 26 CFR 1.6001.1
    HRBEINPL PLAN 1 O SU 12 48 60 32110 29 USC 626
    HRBEINUN UNEMPLOYMENT 1 O CT 12 24 36 33000 CA C.P.S.1132; 26
    CFR 31.6001.1
    HRBEINWC CA WORKERS' COMPENSATION A 1 O CT 12 108 120 33000 WORKERS'
    COMPENSATION
    HRBEIV INVESTMENTS/SAVINGS 1 O CT 12 24 36 32000 26 CFR 1.6001.1
    HRBELO EMPLOYEE LOANS 1 O CT 24 48 72 32000 26 CFR 1.6001.1
    HRBEMI MANAGEMENT INCENTIVE PLAN 1 O CT 12 96 108 34000 ADMIN. DECISION
    HRBEPE PENSION PLAN 1 V CY 12 48 60 34000 29 USC 626; 26 CFR
    1.6001.1
    HRBEPU EMPLOYEE PURCHASE 3 O CY 12 48 60 34000 ADMIN. DECISION
    HRBERE RETIREMENT PLAN 1 V CY 12 84 96 34000 29 CFR 2610.11; 26
    CFR 1.6001.1
    HRBESB SAVINGS BOND 3 O CT 24 48 72 34000 ADMIN. DECISION
    HRBEST STOCK OPTION PLAN 1 V SU 24 48 72 34000 26 CFR 1.6001-1
    HRBEVA VACATIONS 3 O CY 12 24 36 34000 ADMIN. DECISION
    HRED EDUCATION/TRAINING 3 O CY 12 24 36 35000 ADMIN. DECISION
    HREE EEO 1 O CY 12 987 999 31000 29 CFR 1607.4; 29
    CFR 516.5
    HREM EMPLOYEES 3 O CT 12 24 36 35000 29 CFR 1627.3
    HREMAC ACTIVE 3 O CT 12 987 999 35000 29 CFR 1627.3
    HREMAP APPLICATIONS 1 O CY 12 24 36 35000 29 CFR 1627.3
    HREMAPRE RESUMES 1 O CT 60 0 60 35000 ADMIN. DECISION
    HREMET EMPLOYMENT 3 O CT 12 24 36 35000 29 CFR 1627.3 &
    516.2
    HREMHI HISTORY 3 O CT 12 36 48 35000 29 CFR 1627.3
    HREMMS MILITARY SERVICE 3 O CT 24 12 36 35000 26 CFR 1.6001.1
    HREMPA PERFORMANCE APPRAISAL 1 O CY 12 12 24 35000 ADMIN. DECISION
    HREMRE RETIRED 3 O CT 12 987 999 35100 29 CFR 516.2
    HREMRL RELOCATIONS 3 O CT 12 146 158 35200 29 CFR 1627.3
    HREMSF STAFF TRANSFERS 3 O CY 12 24 36 35200 26 CFR 1.6001.1
    HREMTE TERMINATED 3 O CT 12 24 36 35000 29 CFR 516.2
    HREMWS WAGE/SALARY 3 O CY 12 12 24 35000 ADMIN. DECISION
    HREP EMPLOYEE RELATIONS 1 O CY 0 36 36 36000 ADMIN. DECISION
    HREPCS CAREER SERVICING 1 O CT 12 36 48 36000 ADMIN. DECISION
    HREPJE JOB EVALUATION 1 O CY 12 96 108 36000 26 CFR 1.6001.1
    HREPSU SURVEYS 1 O CY 12 12 24 36000 ADMIN. DECISION
    HRJD JOB DESCRIPTION 1 O CY 12 24 36 35300 ADMIN. DECISION
    LE LEGAL 1 O CY 12 0 12 10500 ADMIN. DECISION
    LEAF AFFIDAVITS 1 O CT 24 116 140 10500 ADMIN. DECISION
    LECA CASE RECORDS 3 O CT 24 96 120 10500 ADMIN. DECISION
    LECAAB ARBITRATION, STATE 3 O CY 12 24 36 10500 ADMIN. DECISION
    LECM COMPLIANCE 1 O CT 36 o 36 10510 ADMIN. DECISION
    LECMIG INVESTIGATIONS 1 O CT 36 0 36 10510 ADMIN. DECISION
    LECMRE REGULATIONS 1 O CT 60 0 60 10510 ADMIN. DECISION
    LECMRK RIGHT-TO-KNOW 1 O CT 12 0 12 10510 ADMIN. DECISION
    LECO CONTRACTS/AGREEMENTS 1 V CT 12 48 60 10600 ADMIN. DECISION
    LECOBS BILLS OF SALE 1 O CT 12 24 36 10600 26 CFR 1.6001.1
    LECOLA LABOR 1 O CT 12 987 999 10600 26 CFR 1.6001.1
    LECOPA PROMOTIONAL AGREEMENTS 1 O CY 12 12 24 10600 26 CFR 1.6001.1
    LECOSA SALE OF PRODUCTS 1 O CT 12 36 48 10600 26 CFR 1.6001.1
    LECU U.S. CUSTOMS 1 O CY 12 24 36 10600 ADMIN. DECISION
    LEDE DEEDS/ABSTRACTS/TITLES 1 V CT 240 0 240 10600 ADMIN. DECISION
    LEEA EASEMENTS/RIGHTS OF WAY 1 V CT 240 0 240 10600 ADMIN. DECISION
    LEEX EXPORT REGULATIONS 1 O SU 12 12 24 10600 ADMIN. DECISION
    LEFD FOOD AND DRUG ADMINISTRATION 1 O CY 240 0 240 10510 ADMIN. DECISION
    LELE LEASES 1 V CT 24 216 240 10600 26 CFR 1.6001.1
    LELI LITIGATION 1 O CT 12 12 24 10700 ADMIN. DECISION
    LELIAP OPSAAC 1 O CT 24 12 36 10700 ADMIN. DECISION
    LEMO MORTGAGES 1 V CT 12 24 36 10600 ADMIN. DECISION
    LENO NOTARIES 1 O CT 12 0 12 10500 ADMIN. DECISION
    LEOC OUTSIDE COUNSEL 1 O CY 12 24 36 10500 ADMIN. DECISION
    LEPA PATENTS/TRADEMARKS 1 O CT 12 987 999 10510 ADMIN. DECISION
    LEPE PERMITS 1 O CT 24 219 243 10600 ADMIN. DECISION
    LEPL PRODUCT LIABILITY CLAIMS 1 O CT 12 60 72 10700 ADMIN. DECISION
    LETS TRADE SECRETS 1 V CT 240 0 240 10510 ADMIN. DECISION
    LEWA WARRANTIES 1 O CY 12 48 60 10510 ADMIN. DECISION
    MF MANUFACTURING 1 O AR 24 0 24 40000 ADMIN. DECISION
    MFAR DRAWINGS 1 O CT 12 60 72 41000 ADMIN. DECISION
    MFJR JOB RECORDS 1 O CT 24 36 60 41000 ADMIN. DECISION
    MFPC PRODUCTION CONTROL 3 O CT 12 24 36 41000 ADMIN. DECISION
    MFPCPS PLANNING/SCHEDULING 3 O CT 24 0 24 41000 ADMIN. DECISION
    MFPCWO WORK ORDERS 3 O CT 24 24 48 41000 ADMIN. DECISION
    MFRM RAW MATERIALS 3 O CY 12 36 48 42000 ADMIN. DECISION
    MFSH SHIPPING 3 O AR 24 12 36 43000 26 CFR 1.6001.1
    MFSHCL 1 O CT 12 48 60 43000 ADMIN. DECISION
    MFSHTA TARIFFS 3 O SU 12 36 48 10600 ADMIN. DECISION
    MK MARKETING 1 O CY 12 24 36 80000 ADMIN. DECISION
    MKAD ADVERTISING 1 O CY 12 24 36 81000 ADMIN. DECISION
    MKBD BUSINESS DEVELOPMENT 1 O CY 12 24 36 81100 ADMIN. DECISION
    MKBDPT PRODUCT TESTING 1 O CT 24 0 24 81100 ADMIN. DECISION
    MKCO COMPETITION 3 O CY 24 0 24 81100 ADMIN. DECISION
    MKCR CONSUMER RELATIONS 1 O CY 12 24 36 81200 ADMIN. DECISION
    MKGR GRAPHICS 3 O AR 12 24 36 82000 ADMIN. DECISION
    MKMR MARKET RESEARCH 3 O CY 12 24 36 83000 ADMIN. DECISION
    MKMRDV DEVELOPMENT 3 O CY 12 6 18 83000 ADMIN. DECISION
    MKMRSU SURVEYS 3 O CY 12 6 18 83000 ADMIN. DECISION
    MKPD PRODUCT DEVELOPMENT 1 O CY 12 24 36 84000 ADMIN. DECISION
    MKPR PUBLIC RELATIONS 1 O CY 12 24 36 85000 ADMIN. DECISION
    MKSA SALES 1 O CY 12 24 36 81100 ADMIN. DECISION
    MKSAEX EXPORT 1 O CT 12 24 36 81200 15 CFR 30.11
    MKSAPR PRICING 1 O SU 12 36 48 80000 ADMIN. DECISION
    OP OPERATIONS 1 O AR 12 0 12 45000 ADMIN. DECISION
    PDC DISTRIBUTION CONTROL 3 O CY 12 24 36 45000 ADMIN. DECISION
    OPDCFG FINISHED GOODS 3 O CY 12 24 36 45100 ADMIN. DECISION
    OPDR DISASTER RECOVERY PLANNING 1 V SU 24 975 999 22900 ADMIN. DECISION
    OPFA FACILITIES 3 O CT 24 48 72 45200 ADMIN. DECISION
    OPFAPL PLANS 3 O CY 12 24 36 45300 ADMIN. DECISION
    OPMA MAINTENANCE 3 O CY 12 987 999 45300 ADMIN. DECISION
    OPOR ORDERS 3 O AR 24 0 24 45100 ADMIN. DECISION
    OPQA QUALITY ASSURANCE 3 O CT 60 0 60 46000 ADMIN. DECISION
    OPQARP REPORTS 1 O CT 18 6 24 46000 ADMIN. DECISION
    OPSA SAFETY/ENVIRONMENTAL HEALTH 3 O CY 12 48 60 47000 29 CFR 1910.20
    OPSAAC ACCIDENTS 1 O CY 12 348 360 47100 29 CFR 1904.4
    OPSADS SAFETY RECORDS 1 O CT 999 0 999 47100 ADMIN. DECISION
    OPSAHM HAZARDOUS MATERIAL PLAN 3 O SU 120 0 120 47100 29 CFR 1910.120
    OPSAHW HAZARDOUS WASTE 3 O CY 12 24 26 47100 29 CFR 1910.120
    OPSAIG INVESTIGATIONS 3 O CY 12 24 36 47110 ADMIN. DECISION
    OPSATE TESTS 3 O CY 12 12 24 47200 ADMIN. DECISION
    OPSE SECURITY 3 O CY 12 24 36 48000 ADMIN. DECISION
    OPSEC COUNTER MEASURES 3 O CT 24 0 24 48000 ADMIN. DECISION
    RE RESEARCH/DEVELOPMENT 1 O CY 12 24 36 93000 ADMIN. DECISION
    REIN INGREDIENTS/FORMULAS 3 O SU 24 975 999 93100 ADMIN. DECISION
    REPR PRODUCTS 3 O CT 24 96 120 93200 ADMIN. DECISION
    REPT PROJECTS 3 O CT 24 96 120 93400 ADMIN. DECISION
    RESP ENGINEERING/TECH SPECIFICATION 3 O CT 24 96 120 93500 ADMIN. DECISION
    RETR TECHNICAL REFERENCES 3 O CT 24 96 120 93600 ADMIN. DECISION
  • VI. Purge Documents Selectively And Within Legal And Administratively Defined Requirements [0119]
  • Using predetermined life-cycles (retention schedules) for each file series, the system identifies documents subject to purging. [0120]
  • The system automatically identifies the “owner” of the document and the location of all copies, both Official and Informational. Such ownership is determined by virtue of the ownership of the file series of the document which in turn is determined by the functional responsibility of the cost center in the Chart-of-Accounts (organizationally). As noted above, the system captures the location and the cost center when the user “saves” a created (or modified) document based on information in the class table and location table. [0121]
  • By use of the system a report may be produced identifying the selected document's key attributes allowing the “owner” to review the document and authorize the purge process, or any other access to or modification of a file series and records in the file series. [0122]
  • The above described system may be implemented entirely in software as described below. [0123]
  • Design Details [0124]
  • The following is a description of an implementation of an Electronic Records System (ERS) according to the present invention as a computer program designed to assist in the management and long term storage of an organization's documents. [0125]
  • Overview [0126]
  • ERS is a client/server application to assist in the management of valuable corporate information. [0127]
  • ERS maintains a record retention schedule detailing how information ought to be stored, where, and for how long. [0128]
  • The application helps the user classify documents into groups of similar information. [0129]
  • ERS provides document security. It can prevent unauthorized reading of. or writing to official corporate information. [0130]
  • ERS provides a means to search for documents pertaining to a specific subject, date range, author, etc. [0131]
  • The system acts as a pointer to direct users to where information is stored. [0132]
  • Definition of User Community [0133]
  • The ERS application has four categories of user. Each group of users and their responsibilities are described below. [0134]
  • Records Manager [0135]
  • The Records Manager is responsible for the overall performance of the system. The manager has the greatest amount of authority and access. The responsibilities of the Records Manager are the following: [0136]
  • Sets policy for record storage. This policy includes what media to use for long term storage. [0137]
  • Creates new classes and maintains the retention schedule. [0138]
  • Monitors the performance of the entire application. [0139]
  • Re-classifies documents that have been mis-classified. [0140]
  • Information Services [0141]
  • The Data Processing, Management Information Systems, or the Information Services organization plays a role in the management of documents. Their responsibilities are defined below: [0142]
  • Under the direction of the Records Manager, move documents from one media to another. For example, Information Services will be responsible for moving documents from disk to tape or microfiche. [0143]
  • Also Information Services will be responsible for moving documents from one location to another. Movement of records will apply to only those media they deal with (Tapes, microfiche, etc.). [0144]
  • Information Services will be responsible for maintaining the technical environment. This includes setting up databases, insuring that all users and servers are configured properly, etc. [0145]
  • Department Coordinator [0146]
  • The Department Coordinator is sometimes referred to as a ‘Super User’. They have more authority and system access than a normal user, but less than the Records Manager. The responsibilities of the Department Coordinator are the following: [0147]
  • Provide training and technical support to users within the department. [0148]
  • Monitors the performance of the system regarding departmental records. [0149]
  • Creates and sets up new users. [0150]
  • Enforces record retention policy for official records created by the department. [0151]
  • Manages the logistics of moving records to and from a storage facility. [0152]
  • User [0153]
  • The majority of individuals accessing the system will be categorized as users. Their responsibilities are listed below: [0154]
  • Properly classifies records they create. [0155]
  • Enforces record retention policy for informational records created by them. [0156]
  • Policies [0157]
  • There are a number of office policies and procedure that need to be followed in order for ERS to be a successful application. Some of these policies are documented below. [0158]
  • Users and Class Assignments [0159]
  • Any user can assign any class to a document. They will not be prevented by the ERS application from assigning classes outside their area of the organization. However, audit reports will be made available to the Departmental Coordinators and Records Manager to help insure that classes are being used properly. [0160]
  • No Class Attribute Overrides [0161]
  • Each class has attributes. There attributes are retention period, record type (official, informational), sensitivity, and vital flag, etc. Users can not override these values with their own when storing a document. If they need different attribute values than what is associated with a given class, then they should contact the Record Manager. The Record Manager may then create a sub class having the attribute values desired by the user. [0162]
  • Classification Owner [0163]
  • There will be one cost center that owns each classification. A classification will no be the responsibility of two or more cost centers. The cost center the owns a classification is responsible for all the documents that have been assigned to that classification. The cost center must insure that the inventory of documents is correct and properly maintained. [0164]
  • Location and Class Assignment [0165]
  • If a document is assigned a classification at the major level, then it can not be located in any archive facility. For example, if a document is classified as ‘AC’ for accounting, then it can not be stored at a off site storage facility. If the same document was classified as ‘ACAP’ for accounting, accounts payable, then it could be stored at a warehouse. [0166]
  • One Production Database Per User [0167]
  • A user can have access to several ERS databases. One for production work and one database for training, for example. However, no user will have write access to two production databases. There will be no support for across production database searches. [0168]
  • System Functions [0169]
  • All the capabilities of the system can be described as functions. Functions fall into five types. They are reports, updates, inquires, interfaces, utilities. These functions are described below by the group of user who will access them. [0170]
  • User Functions [0171]
  • All individuals who have access to the system will be able to operate the functions defined as follows: [0172]
  • Application Package File Open Function [0173]
  • From a word processing, spreadsheet, or presentation software package, a user will be able to pull down the package's File menu and activate the Open menu item. This will access ERS, automatically. The features of this function are described below. [0174]
  • Search and Retrieve Feature [0175]
  • The user will have the ability to retrieve and open a document by searching for its classification, synonym, or other attributes such as author, title, and/or date. If multiple documents are found that satisfy the users search criteria, a list of these documents will be displayed for the user to pick from. The documents being searched may be found on the users hard drive, shared network drive, or archive facility (Mezzanine). [0176]
  • Application Package File Save Function [0177]
  • From a word processing, spreadsheet, or presentation software package, a user will be able to pull down the package's File menu and activate the Save or Save As menu items. This will access ERS, automatically. The features of this function are described below. [0178]
  • Document Storage Feature [0179]
  • The users will have the ability to store at document on their hard drives, shared network drives, or archive facility (Mezzanine). Regardless of where the user stores the document, they will have the ability to manage their documents with ERS classifications and synonyms. [0180]
  • Classification Assignment Feature [0181]
  • Users will be able to assign any classification directly to the document. Or, users can select a corporate synonym (official term or keyword) to be applied to the document. Behind the scenes, ERS will assign the classification associated with the corporate synonym to the document. Also, the user may wish to assign one of their own synonyms to the document. ERS will automatically translate from the user's synonym to the appropriate corporate synonym and assign the classification to the document. [0182]
  • Synonym Maintenance Feature [0183]
  • Users will have the ability to add, change, or delete their own synonyms. They may create synonyms different than the corporate synonyms. However, user created synonyms must be related to corporate synonyms. User synonyms will be children of a corporate synonym. [0184]
  • Attribute Maintenance Feature [0185]
  • When saving a document, a user will have the ability to store other attributes about the document. These attributes are title, subject, author, date created, etc. [0186]
  • Stand Alone ERS User Functions [0187]
  • Not all the functions the user needs can be accessed via an application package such as Microsoft Word. There will need to be a stand alone ERS application (.EXE) the user can run. The functions contained within this facility are described below. [0188]
  • Update Functions [0189]
  • Inventory Maintenance [0190]
  • The ability to correct mis-assigned classifications given to items in inventory. This function assists the user in properly assigning classifications to documents. [0191]
  • Inventory Entry [0192]
  • The ability to add an item to inventory and to assign it a classification. This function is needed to store items that are not word processing documents, spread sheets, or presentations. Such items might be Write, text, or bit mapped files. [0193]
  • Inventory Request [0194]
  • The ability to request via the system that an inventory item be (1) moved to an off site storage facility, (2) retrieved from an off site storage facility, (3) changed from one media type to another. [0195]
  • Synonym Maintenance [0196]
  • The ability to add, change, or delete user synonyms. [0197]
  • User Profile Maintenance [0198]
  • This update function would allow a users to change information the system stored about them. Such information as phone number, mail stop, spread sheet directory name, and location would be fields a user could change. The function would not allow them to change their user group or create a new user. [0199]
  • Inquiry Functions [0200]
  • Inventory Retrieval [0201]
  • The ability to search and view a document in inventory. This function is needed to retrieve items that are not word processing documents, spread sheets, or presentations. Such items might be Write, text, or bit mapped files. [0202]
  • Reporting Functions [0203]
  • Inventory Detail Reports [0204]
  • The ability to display what items are in inventory by retirement date, or by class, or by age. The purpose of these reports is to help the user (1) re-assign classification codes (if needed), (2) retire inventory items. [0205]
  • Synonym Reports [0206]
  • Listings of the user's synonyms by classification or corporate synonym. The purpose of these reports is to help the users determine which of their synonyms they no longer need. [0207]
  • Department Coordinator Functions [0208]
  • The Department Coordinator would have access to the same functions as the normal user. However, in their stand alone ERS application they would access to these additional functions. [0209]
  • Update Functions [0210]
  • User Maintenance [0211]
  • The ability to add, change, or delete information about a user, the group they belong to, and the classes they can assign to a document. [0212]
  • Inventory Maintenance [0213]
  • The ability to change an inventory item's classification, location, or media. This update function helps the Department Coordinator correct mis-assigned classifications and move inventory items from one location to another. [0214]
  • When changing an inventory items media, this will create a media request. A media request is a note to Information Services that items found on hard disk need to be moved to CD. [0215]
  • Reporting Functions [0216]
  • Inventory Detail Reports [0217]
  • The ability to display what items are in inventory by department and cost center, or by retirement date, or by class, or by media type and age. The purpose of these reports is to help the Department Coordinator (1) retire inventory items, (2) move inventory items from one location to another. [0218]
  • Inventory Count Reports [0219]
  • The ability to count the quantity of inventory items by age, or by department and cost center, or by retirement date, or by classification. The purpose these reports is to help the Department Coordinator (1) understand how many items are inventory and their age, (2) determine if classifications are being properly used, and (3) manage the retirement process. [0220]
  • Center Retention Required [0221]
  • The purpose this report is to display those items in inventory that are approaching the end of their office retention period and starting their center retention period. These inventory items may require a media change and/ or location change. [0222]
  • This report would be used to issue inventory requests for media change. This report would help the Department Coordinator manage the logistics of moving records to and from a storage facility. [0223]
  • Classification Audit Reports [0224]
  • The purpose of these reports are to display where classifications may be mis used. The reports should list (1) the documents assigned classifications that are not approved by the Departmental Coordinator for application by the user, and (2) the documents only assigned a major classification. [0225]
  • Inventory Requests Report [0226]
  • The purpose of this report is to display the documents that need to be (1) placed in a off site storage facility, (2) retrieved from an off site storage facility, and/or (3) under go a media change. [0227]
  • This report would help the Departmental Coordinator manage the logistics of moving records to and from a storage facility. [0228]
  • Static Table Listings [0229]
  • The ability to list the contents of various static tables such as record type, sensitivity codes, retention start codes, synonyms, classes, users, user groups, organization structure, media types, and locations. [0230]
  • Information Services Functions [0231]
  • The Information Services organization needs some of the same functions of the Department Coordinator, but not all. Information Services needs to be able to maintain inventory locations and media. They will also need the same inventory reports and media life reports available to the Department Coordinator. In addition, the following functions would be available to only Information Services users. [0232]
  • Update Functions [0233]
  • There are several update functions that only Information Services personnel would use. These functions are described below. [0234]
  • Database Definition [0235]
  • The purpose of this function is to describe the various ERS databases that may be at an organizations and their addresses. [0236]
  • Function Maintenance [0237]
  • The purpose of this update is to record what functions are in the system, which tables or database objects they access, which user groups can run them. This update would also maintain how a report is sorted and what columns can be used in its selection criteria. [0238]
  • Batch Functions [0239]
  • The following functions are intended to run once a day in the evening hours. The overall purpose of these functions is to keep the various ERS servers in sync with one another and healthy. [0240]
  • Function Usage Maintenance [0241]
  • ERS will record who is running what, when, and for how long. This usage activity can create a large volume of data in a short period of time. For this reason, there will be a batch job available to remove usage activity prior to a certain date. In this fashion, the Records Manager can select to keep usage information for only one quarter, for example. [0242]
  • Security Grants [0243]
  • The purpose of this batch job would be to re-do all the security grants on all the database objects (tables, view, etc.) to match what is defined in the function and user group tables. This batch job would be run during implementation of a new release of ERS. [0244]
  • Records Manager Functions [0245]
  • The Records Manager would have access to all the functions available to the normal user and the Department Coordinator. However, the Records Manager would have access to the following additional functions in their stand alone ERS application. [0246]
  • Update Functions [0247]
  • Class Maintenance [0248]
  • Add, change, or delete information about classifications, abstracts, and retention schedules. [0249]
  • Synonym Maintenance [0250]
  • Add, change, and delete synonyms used corporate wide. These synonyms are also referred to as keywords and official terms. [0251]
  • Static Table Maintenance [0252]
  • Add, change or delete rows from any of the application's static tables. Static tables would include record type, sensitivity codes, retention start codes, synonyms, classes, users, user groups, companies, departments, and cost centers, media types, buildings, aisles, and locations, etc. [0253]
  • Reporting Functions [0254]
  • Class Availability Report [0255]
  • Display a list of classifications available and applied by company, departments, cost centers, and user. The purpose of this report is to determine if departments are potentially mis-using classifications. [0256]
  • Function Usage Reports [0257]
  • List the system function number, title, and the quantity of times it was accessed by department, cost center, and user. The purpose of this report is to support a activity analysis or charge back. [0258]
  • Data Dictionary Reports [0259]
  • Database columns definitions by column name and table name. The purpose of these reports is to educate the record manager and developers as to what is stored in the database and where. [0260]
  • Catalog of Functions [0261]
  • The purpose of the catalog of functions is to display a summarized list of all the update and reporting capabilities of the system by type, subject, name, and description. [0262]
    Type Subject Name Description
    Reports Class ERS110 Class Authority Report.
    ERS120 Class Usage Report.
    ERS130 Classification Audit Report.
    Dictionary ERS150 Data Dictionary Report.
    Function ERS210 Function Usage Report.
    ERS220 Function/Object Relationship.
    ERS230 Function/Column Relationship.
    ERS240 Function/Sort Relationship.
    Inventory ERS250 Center Retention Required.
    ERS255 Inventory Detail Report.
    ERS260 Inventory Count Report.
    ERS265 Inventory Request Report.
    ERS270 Inventory Retirement Required.
    ERS275 Inventory Retrieval.
    Synonym ERS310 Synonym Report.
    User ERS340 Group Function Access Report.
    ERS350 User Class Access Report.
    Tables ERS410 Location Report.
    ERS415 Location Type Report.
    ERS420 Media Type Report.
    ERS425 Organization Report.
    ERS430 Organization Type Report.
    ERS435 Record Type Report.
    ERS440 Retention Reference Report.
    ERS445 Retention Start Report.
    ERS450 Sensitivity Report.
    Batch Function ERS510 Function Usage Maintenance.
    Inventory ERS520 Inventory Statistics Maintenance.
    Security ERS510 Grant Creation.
    UpdateClass ERS610 Class Maintenance.
    Function ERS650 Function Maintenance.
    UpdateInventory ERS710 Inventory Entry.
    ERS720 Inventory Maintenance.
    ERS730 Inventory Re-Classification.
    ERS730 Inventory Request.
    Synonym ERS750 Keyword Maintenance.
    ERS760 Synonym Maintenance.
    User ERS810 User Maintenance.
    ERS820 User Profile Maintenance.
    Tables ERS905 Database Definition.
    ERS910 Location Maintenance.
    ERS915 Location Type Maintenance.
    ERS920 Media Type Maintenance.
    ERS925 Organization Maintenance.
    ERS930 Organization Type Maintenance.
    ERS935 Record Type Maintenance.
    ERS940 Retention Reference Maintenance.
    ERS945 Retention Start Maintenance.
    ERS950 Sensitivity Maintenance.
    Utilities Inventory ERS010 Application Package, File Open.
    ERS020 Application Package, File Close.
    ERS030 Application Package, File Save.
  • Generic Description of All Function and Features [0263]
  • The purpose of this section of the document is to describe, in a generic fashion, what the system will be able to do. This section defines the functions and features of the application. [0264]
  • Any system is made up of functions. Functions are software that produce menus, reports, updates, interfaces, and utility activities. Features are the capabilities of each function. For example, reporting functions have the capability to output their information to the screen, the printer, or to an extract file for easy entry into a spread sheet. These output routing capabilities are all features of a reporting function. [0265]
  • Menu Functions [0266]
  • The purpose of menus is to provide access to all other functions of the system. Pull down menus are placed at the top of each window. The features of all menus are described below: [0267]
  • Function Access [0268]
  • All menus will provide access to the various functions of the system. An example of the pull down menus and their options would be the following: [0269]
  • File [0270]
  • New [0271]
  • Open [0272]
  • Delete [0273]
  • Close [0274]
  • Print [0275]
  • Printer Setup [0276]
  • Exit [0277]
  • Edit [0278]
  • Undo [0279]
  • Cut [0280]
  • Copy [0281]
  • Paste [0282]
  • Clear [0283]
  • Find [0284]
  • Go To [0285]
  • Search [0286]
  • Sort [0287]
  • Filter [0288]
  • View [0289]
  • First Page [0290]
  • Prior Page [0291]
  • Next Page [0292]
  • Last Page [0293]
  • Toolbars [0294]
  • Date and Time [0295]
  • Maintenance [0296]
  • [0297] Update 1
  • [0298] Update 2
  • Etc. [0299]
  • Reports [0300]
  • [0301] Report 1
  • [0302] Report 2
  • Etc. [0303]
  • Window [0304]
  • Tile [0305]
  • Layered [0306]
  • Cascade [0307]
  • Arrange Icons [0308]
  • [0309] Window 1
  • [0310] Window 2
  • Etc. [0311]
  • Help [0312]
  • Contents [0313]
  • Search for Help on [0314]
  • How to Use Help [0315]
  • About ERS [0316]
  • Micro Help [0317]
  • As a user points to a menu option and holds the left mouse button down, they will see a one line description of that menu option at the bottom of the window. [0318]
  • Button Bar [0319]
  • A bar of push buttons will be located just below the menu at the top of the window. The push buttons will contain icons symbolizing frequently used functions or menu options. Thereby a user can access a function one of two ways. The first method is by pulling down the appropriate menu and clicking on the option desired. The second means of accessing a function would be to click on the icon for the function found on the button bar. [0320]
  • Disabled Functions [0321]
  • The pull down menus will show all functions planned for the application at all times. However, some of the functions will appear in gray letters. These will be the functions that are not completed and are not available for use. As the system development effort continues, more and more of these functions will be enabled and will appear in black letters. In this fashion, a user can see all the functions of the system, and what is available for use today. [0322]
  • User Access [0323]
  • The functions an individual user can access will depend upon the level of security. Certain users will have all of their menu options enabled, others will not. The functions each user can access will be assigned by the Records Manager. [0324]
  • Reporting Functions [0325]
  • Reports are functions used to output information. Reporting functions can produce output in tabular listings, graphs, or spread sheets formats. This output can be sent to the screen, a printer, or a file directory. The features of reporting functions are the following: [0326]
  • Custom Sub Heading [0327]
  • The user will have the option to create their own report sub heading that will appear at the top of each page. The sub heading can be used to document the items selected or their purpose for running the report. [0328]
  • Selection Criteria [0329]
  • The user will have the ability to limit the size of the report. They will be able to select one or more columns on the report and state what values they would like to have retrieved for those columns. For example, if department number is a column on a report, then a user will be able to state which departments should appear on the report. For inventory related reports, users will have the ability to do string search on the title and description of items. [0330]
  • Variable Sorting [0331]
  • Each report can have more than one method of sorting. The user will have the ability to select, from a pre-set list, how the information should be sorted. [0332]
  • Routing of Output [0333]
  • Each report can be routed to one of three different places. The report can be viewed on the screen, sent to a printer, or placed in comma delimited file. The comma delimited file can be read by Lotus or Excel spread sheet software. [0334]
  • Report Footing [0335]
  • On the last page of each report will be displayed the sort sequence and selection criteria used to create the report. In this fashion, the reader of the report will know that the report may not contain all the information in the system. [0336]
  • Print After View [0337]
  • Every report routed to the screen will have the ability to be printed. This feature will allow the users to view the first several pages of a report, and then print it, if they desire. [0338]
  • Micro Help [0339]
  • Every object of the window used to specify report sub-headings, selection criteria, sorting, and routing will have a help message associated with it. The help message will offer a one line description of the object. [0340]
  • Usage Tracking [0341]
  • Just prior to exiting a reporting function, the system will post to the database the name of the reporting function run, rows retrieved, the user's ID, date, and time. In this fashion, tracking of reporting function usage and charge back activities can be supported. [0342]
  • Update Functions [0343]
  • Update functions provide the ability to add, change, or delete records in the database. The features of update functions are the following: [0344]
  • Add, Change, Delete [0345]
  • A single update function will allow the user to add new records, change existing ones, or delete records from a table. The user will not have to select three different update functions from a menu to maintain one table. [0346]
  • Point and Shoot [0347]
  • The user will not have to know key field values such as department numbers, building numbers, or document numbers. In each update function, they will be shown a list of records that can be updated. Then, they can point to an existing record to change it, or delete it. By displaying a list of existing records in a table first, the user can scroll through them and decide which one they would like to update. [0348]
  • Drop Down Lists [0349]
  • The user will not have to memorize codes to operate update functions. If a code field value is asked for on a data entry window, it will be displayed in a drop down list box along with its description. For example, if a user must input an cost center number, then they will be given a drop down list box containing cost center number and names to choose from. [0350]
  • Drag and Drop [0351]
  • Where ever possible, ERS will allow the user to drag an object on to a command button to signal that they wish to perform the command. [0352]
  • Jumping [0353]
  • If several windows are used to collect all the data being entered into a table or group of tables, then the user will have the ability to jump from one window to another. For example, an update function could consist of three windows. The first could be a list of documents to update. The second window could be all the descriptive information about the document. The third window could be used to input key words or phases about the document. The user would not be forced into going from the first, to the second, and then to the third window. They would be given push buttons to jump from the first window to the third, and from the third to the second window. In this fashion, the user would not be forced into traversing through several windows in a pre-set pattern to enter the data. [0354]
  • Validation [0355]
  • Each field will be validated at the time the user moves the cursor from one field to another on a data entry window. This will prevent the user from entering several fields of erroneous information before realizing that any of it is wrong. [0356]
  • Referential Integrity [0357]
  • All update functions will use referential integrity rules. These rules will prevent deletion of code values being used else where in the system. For example, a user will not be able to delete a department number from the department table if it is being used to describe a document in the inventory table. [0358]
  • Confirmation [0359]
  • At the bottom of each data entry window, in an update function, would be several push buttons. These buttons would be used to signal the computer to write the transaction out to the database, or cancel the transaction. Each time one of these buttons is pressed, the user will see a message a the bottom of the window confirming the computer's actions. [0360]
  • Micro Help [0361]
  • Each object and field in a data entry window will have a help text associated with it. This one line of help message will appear at the bottom of the screen when the object or field is clicked on. [0362]
  • Usage Tracking [0363]
  • Just prior to exiting an update function, the system will post to the database the name of the update function run, the quantity of records processed, the user's ID, date, and time. In this fashion, tracking of update function usage and charge back activities can be supported. [0364]
  • Process Model [0365]
  • The purpose of a business process model is to show the relationship between people, systems, data, office policy and procedures, and documents. [0366]
  • Node Tree Diagrams [0367]
  • A component of a business process model is a node tree diagram. FIG. 8 shows the major activities associated with an application. FIGS. 9 through 11 show the node tree diagrams for ERS. [0368]
  • Database Design [0369]
  • The application will store its information in a set of relational tables. The total size of the database is expected to be approximately 500 Megs of disk space for a 300,000 inventory items. There will be roughly 1,200 total users, about 300 will be activity at any point in time. [0370]
  • Entity Definitions [0371]
  • The nature of each table in the database is described in the following entity definitions. [0372]
    Entity Name Entity Definition
    Access The purpose of this entity is to store the
    access codes and descriptions. Access
    codes are select, update, insert, and deleted.
    Class The purpose of this entity is to store the all
    the information about a classification. This
    information contains classification code,
    title, retention periods, record type,
    sensitivity, etc.
    Data Dictionary The purpose of this entity is to store entity,
    attribute, and physical column information.
    This entity is used to support data
    dictionary reporting.
    Function The purpose of this entity is to store a valid
    list of system functions. System functions
    are window objects such as reports,
    updates, inquiries, interfaces, etc.
    Function Column The purpose of this entity is to store a valid
    list of columns than can be used to limit
    retrieval of a reporting function.
    Function Column Last Used The purpose of the last used function
    column entity is to record the selection
    criteria chosen by a specific user when a
    report was run. This entity supports storing
    the last query parameters applied by a user
    for a given report.
    Function Data Window
    Function Sort The purpose of this entity is to store a valid
    list of storing options that can be applied to
    a reporting function.
    Function Sort Last Used The purpose of the last used function sort
    entity is to record what sort sequence a user
    requested the last time they ran a specific
    report. This entity support recalling the
    last query for a report and user.
    Function Subject The purpose of this entity is to define what
    area of interest, for the user, the function
    relates to.
    Function Type The purpose of this entity is to store a valid
    list of function types. Function types are
    used to group functions together. Function
    types are reports, updates, interfaces, etc.
    Function Usage The purpose of this entity is to track who
    has accessed a function of the system and
    when. This entity could be used as a basis
    for activity analysis and usage charge back
    costing.
    Inventory The purpose of this entity is to store
    information about an item in inventory.
    The information includes title, date stored,
    media, classification, etc.
    Inventory Abstract
    Inventory Request The purpose of this entity is to store
    requests to move inventory from one form
    of media to another. For example, request
    to move documents from disk to tape.
    Once the media has been moved, the
    request is deleted. No past history of
    media requests are stored.
    Inventory Statistics The purpose of this entity is to store the
    quantity of items in inventory for each
    class, record type, level one location, and
    month. These statistics can be used to
    determine if classifications are being
    properly applied.
    Location The purpose of this entity is to store a valid
    list of locations. Locations can be storage
    areas, buildings, property, shelves, drawers,
    etc.
    Location Type The purpose of this entity is to store valid
    location types. Location types are
    building, floor, aisle, storage area, shelf,
    property number, drawer, etc. The location
    type also denotes what level of the
    hierarchy the location can be found.
    Media Type The purpose of this entity is to store a valid
    list of media types and descriptions. Media
    are hardcopy, disk, tape, CD, microfiche,
    etc.
    Object Identification The purpose of this entity is to store the last
    identification number assigned to a table.
    For example, the last class identification
    assigned to the class table.
    Organization The purpose of this entity is store a valid
    list of companies, departments, and cost
    centers.
    Organization Type The purpose of this entity is to store a valid
    list of organization types. For example,
    company, department, cost center are all
    organization type. This entity also defines
    what level of the organization hierarchy the
    organization will be found on.
    Record Type The purpose of this entity is to store the
    valid record types and their descriptions.
    Valid record types would be official and
    informational.
    Request Type the purpose of this entity is to store a valid
    list of inventory request type codes and
    descriptions. Inventory request types are to
    change media or to move to or from offsite
    storage.
    Retention Reference The purpose of the retention reference
    entity is to store the text of the law or
    regulation that governs a set of classes and
    their retention periods.
    Retention Start The purpose of this entity is to store a valid
    list of retention type codes and
    descriptions. Retention types define when
    a record's retention period begins.
    Sensitivity The purpose of this entity is to store a valid
    list of sensitivity codes and descriptions.
    Sensitivities are confidential, secrete, etc.
    Synonym The purpose of this entity is to store
    alternative names for a classification. A
    synonym may be a classification code, a
    portion of the classification name, or a
    commonly used alternative to the
    classification name.
    User The purpose of this entity is to store a list
    of valid users for the system.
    User Class The purpose of this entity is to store every
    classification the user has access to and
    may assigned to documents. The classes
    are initially set up by the Departmental
    Coordinator.
  • Entity Relationship Diagram [0373]
  • FIG. 12 is the entity relationship diagram. Its purpose is to provide a high level view of the database and its structure. The diagram shows each table in the system and how it relates to other tables. The solid lines between entities denotes identifying relationships. The dotted lines denotes non-identifying relationships. [0374]
  • Attribute Definitions [0375]
  • Following are the attribute definitions. Attributes are the columns that can be found in each entity or table within the database. The definitions are sorted by entity name and attribute name. [0376]
    Entity Name Attribute Name Attribute Definition
    Access Access Code User assigned identification code.
    The access code defines what a
    user can do to a database object.
    Access codes are S = Select, U =
    Update, I = Insert, D = Delete. If a
    user has an access code of I or D
    then they can automatically do U
    or S. If a user has an access code
    of U then they can also do S.
    Access Description Long name, description, or title for
    code. The access description
    stores the meaning of the access
    code. For example, insert, update,
    delete, and select are all
    descriptions of access codes.
    Last Changed Date
    Last Changed By
    Timestamp
    Class Class Identification System assigned identification
    number. The class identification is
    the unique identifier for the
    classification. This integer is a
    system assigned value, not user
    assigned.
    Abstract Description of classification. The
    abstract is the legal definition of
    the classification.
    Class Code User assigned identification code.
    The class code is a 10 character
    user assigned classification code.
    The first two characters of the
    class code are the major class. The
    third and fourth characters are the
    primary class. The fifth and sixth
    characters are the secondary class.
    Characters 7-8 represent the next
    relationship level. Characters 9-10
    represent the last relationship
    level.
    Classification Title Long name or title for class. The
    classification title is the name of
    the class code.
    Classification Title Class title and all parent class
    Extended titles. The extended classification
    title contains the titles of all the
    parent classifications plus this
    classification's title. For example,
    if this classification code is ACAP,
    then the extended classification
    title is ‘Accounting, Payables’.
    Center Retention Quantity of months in offsite
    Months storage. The center retention
    months is the quantity of months
    an inventory item is held in a
    records center or off site storage
    facility. The office retention plus
    the center retention months equals
    the total retention period for a
    classification.
    Organization System assigned identification
    Identification number. The organization
    identification is the unique
    identification for a company,
    department, or cost center. The
    integer value is system assigned,
    not user assigned. Organizations
    own users and classifications.
    Created By User ID of person who created the
    class. The created by column
    contains the user identification of
    the Records Manager who created
    the classification.
    Media Type Code User assigned identification code
    for media type. The media type
    code defines what form the
    inventory item is stored in. For
    example, DISK=hard disk,
    FLOPPY=floppy disk, CD=CD
    ROM, TAPE =magnetic table,
    FICH=microfich,
    PAPER=hardcopy.
    Office Retention Quantity of months stored on site.
    Months The office retention months is the
    quantity of months an inventory
    item is held in an office storage
    area before it is moved to a long
    term, off site storage facility. The
    office retention plus the center
    retention months equals the total
    retention period for a
    classification.
    Parent Class Owning parent classification. The
    Identification parent class identification is the
    identification number to the class
    that owns this one.
    Record Type Code User assigned identification code.
    The record type code defines
    importance to a classification. For
    example, I=informational and
    O=official record types. Inventory
    items assigned a classification
    having an official record type can
    only be deleted by a Department
    Coordinator.
    Retention Reference User assigned identification
    number. The retention reference
    column is used to store the
    identification number for the
    reference document or law
    governing a set of classes and their
    retention periods. For example,
    ‘26 CFR 1.6001.1’ is a document
    defining how checks ought to
    stored.
    Retention Start User assigned identification code.
    Code The retention start code defines
    when the retention period of the
    document starts. The quantity of
    months an inventoiy item is held
    may start when the document first
    created, or it may start when the
    document is moved to an off site
    storage facility.
    Sensitivity Code User assigned identification code.
    The sensitivity code defines the
    security associated with a
    classification. For example,
    TS=top secrete and
    CO=confidential are sensitivity
    codes.
    Vital Flag Vital record (Y=yes, N=no). The
    vital flag is a yes/no column
    denoting if the classification
    involves vital documents. Vital
    documents are those records
    whose loss would have a financial
    impact on the organization.
    Last Changed Date
    Last Changed By
    Timestamp
    Data Entity Name Entity or long table name. The
    Dictionary name of the entity in the logical
    data model. In most cases, the
    entity name is similar to the long
    name for the table in the database.
    Attribute Name Attribute or long column name.
    The attribute name from the
    logical data model. In most cases,
    this is the long name for the
    column.
    Attribute Definition Attribute description or meaning.
    The attribute definition contains
    the description, meaning, or
    purpose of the attribute.
    Column Name SQL column name. The column
    name is the physical name for the
    attribute in the SQL database.
    Datatype SQL column datatype. The
    datatype is the physical format of
    the column in the SQL database.
    Entity Definition Entity description or meaning.
    The entity definition contains the
    description, meaning, or purpose
    of the entity.
    Null Option SQL null option. The null option
    is a flag denoting if a column must
    always contain data or not. If the
    null option equals ‘Yes’ then the
    column does not have to contain
    data all the time. If the null option
    is set to ‘No’ then the column must
    always have data in it.
    User Defined Data-
    type Name
    Last Changed Date
    Last Changed By
    Timestamp
    Function Function Number User assigned identification
    number. The function number is
    the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    Function Purpose Description or purpose of function.
    The function purpose is a text
    column defining how the report or
    update screen ought to be applied
    by the user.
    Function Subject User assigned identification code.
    Code The function subject code defines
    what area of interest, for the user,
    the function relates to. For
    example, MANAGEMENT =
    management performance reports.
    The function subject code uniquely
    identifies subjects. Function
    subjects, types, and titles are used
    to build menus.
    Function Title Title or name of function. The
    function title is the name of the
    function as it appears at the top of
    the window or in the menu. For
    example ‘User Maintenance’ is a
    function title.
    Function Type Code User assigned identification code.
    The function type code is a way of
    grouping like functions together.
    For example R=report, U=update,
    M=menu, T=utility, I=interface are
    all function type codes. Function
    types, subject, and titles can be
    used to build menus.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Function Number User assigned identification
    Column number. The function number is
    the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    Table Name SQL table name. The table name
    is the SQL table or view name that
    will be used as part of a WHERE
    phrase to limit report retrieval.
    Column Name SQL column name. The column
    name is the SQL table or view
    column name that will be used as
    part of a WHERE phrase to limit
    report retrieval. For example,
    DPT_NBR is the department
    number column name.
    Column Null Flag Column contains NULL's, Y=yes,
    N=no. The column null flag is
    used to state if the WHERE phrase
    should be constructed to search for
    null values for the column. For
    example, if the column name is
    DPT_NBR and the column null
    flag is set to Y=yes, then the
    WHERE phrase should be
    WHERE DPT_NBR = NULL.
    Column Title Long name or title of column. The
    column title is what the users sees
    when selecting from a list of
    columns to use to limit report
    retrieval. For example, when the
    user wishes to pick the DPT_NBR
    column, they would see
    ‘Department Number’.
    Column Type SQL datatype (DATE, INT,
    CHAR, FLOAT, YESNO). The
    column type is a code defining the
    columns datatype. For example,
    DATE, INT, CHAR, FLOAT are
    all column types. The column type
    dictates which dialogue box
    appears displaying values for the
    column.
    Relationship Code Column/value relation (EQUAL,
    LIKE, BOTH). The relationship
    code defines if the relationship in
    the WHERE phase could be an
    equality, a string search, or both.
    For example, if the relationship
    code is EQUAL then the
    relationship between the column
    name and its values in the
    WHERE phrase is IN for character
    type columns, BETWEEN for nun-
    null numeric columns, and = for
    null numeric columns. If the
    relationship code is LIKE then the
    relationship between the column
    name and its values is LIKE. If
    the relationship code is BOTH,
    then the user can choose either an
    equality or string search
    relationship.
    Required Flag Column value required (Y=yes,
    N=no). The required flag denotes
    if the user must use this column to
    limit retrieval. This column helps
    prevent the user from constructing
    a report request that extracts every
    row from the database by forcing
    them to have a WHERE phrase on
    at least one column name.
    Sequence Number Sort sequence number. The
    sequence number is a character
    column used to sort the column
    titles for display on the screen.
    The sequence number allows the
    system to display a list of column
    names in some other sort order
    besides alphabetically by column
    title.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Function Number User assigned identification
    Column Last number. The function number is
    Used the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    Column Name SQL column name. The column
    name is the SQL table or view
    column name that will be used as
    part of a WHERE phrase to limit
    report retrieval. For example,
    DPT_NBR is the department
    number column name.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Table Name SQL table name. The table name
    is the SQL table or view name that
    will be used as part ofa WHERE
    phrase to limit report retrieval.
    Column Value Column values last used. This text
    column stores the ‘right hand side’
    of a SQL WHERE phrase. It
    contains the list of values desired
    for column when a specific report
    was last run by a given user. For
    example, if a user had requested a
    set of departments to appear on a
    report the last time it was run, then
    this column would contain that list
    of departments.
    Operator Code Code to indicate exact value or list
    of values. Determines whether the
    user can enter a value or select
    from a list of values.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Table Name SQL table name. The table name
    Data Window is the SQL table or view name that
    will be used as part of a WHERE
    phrase to limit report retrieval.
    Column Name SQL column name. The column
    name is the SQL table or view
    column name that will be used as
    part of a WHERE phrase to limit
    report retrieval. For example,
    DPT_NBR is the department
    number column name.
    Data Window Name Data Window Used for selection of
    column for SQL table.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Sort Function Number User assigned identification
    number. The function number is
    the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    Order By SQL ORDER BY and/or GROUP
    BY. The order by column contains
    the SQL GROUP BY and/or
    ORDER BY phrase for the report
    request.
    Data Window Name PowerBuilder Data Window name.
    The Data Window name is the
    name of the PowerBuilder
    Data Window name that should be
    displayed when a particular sort is
    requested by the user. Different
    Data Windows are used for
    different sorts because there may
    be different subtotaling on the
    same report depending upon how it
    is sorted.
    Default Sort Flag Default sort (Y=yes, N=no). The
    default sort flag is a yes/no column
    denoting what sort will be applied
    to the report if the user does not
    select one.
    Order By Title Title or long name of the sort. The
    order by title is what the user sees
    when selecting from a list of sort
    sequences to apply to a report. For
    example, the order by column
    value may be ORDER BY
    CO_NBR, DPT_NBR,
    CST_CTR_NBR. The order by
    title would be ‘By Company,
    Department, and Cost Center
    Numbers’.
    Sequence Number Sort sequence number. The
    sequence number column is used
    to sort the order by titles in some
    other sequence other than
    alphabetically by order by title.
    Last Changed Date
    Last Changed By
    Requires Stored Required stored procedure name.
    Procedure The purpose of this column is to
    record the name of any stored
    procedure required to generate a
    report output. Some reports,
    because of their complexity, can
    not be created without the use of
    an SQL stored procedure. If a
    stored procedure is needed, its
    name would be found in this
    column.
    Timestamp
    Function Sort Function Number User assigned identification
    Last Used number. The function number is
    the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    Order By SQL ORDER BY and/or GROUP
    BY. The order by column contains
    the SQL GROUP BY and/or
    ORDER BY phrase for the report
    request.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Function Subject User assigned identification code.
    Subject Code The function subject code defines
    what area of interest, for the user,
    the function relates to. For
    example, MANAGEMENT =
    management performance reports.
    The function subject code uniquely
    identifies subjects. Function
    subjects, types, and titles are used
    to build menus.
    Function Subject Long name, description or title for
    Description code. The function subject
    description is the long name for
    the subject. For example
    management performance reports,
    operational reports, utility, user
    functions are all subject
    descriptions.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Type Function Type Code User assigned identification code.
    The function type code is a way of
    grouping like functions together.
    For example R=report, U=update,
    M=menu, T=utility, I=interface are
    all function type codes. Function
    types, subject, and titles can be
    used to build menus.
    Function Type Long name, description, or title for
    Description code. The function type
    description is the meaning of the
    function type code. For example,
    report, update, menu, utility, and
    interface are all function type
    descriptions.
    Last Changed Date
    Last Changed By
    Timestamp
    Function Usage Start Date Date/time function started being
    Usage used. The usage start date is the
    date and time the update or report
    was activated.
    Function Number User assigned identification
    number. The function number is
    the unique identification of a
    function of the system. Function
    numbers are assigned by
    programmers. For example,
    ERS110 could be a function
    number assigned to a performance
    report. Function numbers 000 to
    099 are utility functions, 100 to
    199 are performance or
    management reports, 200 to 299
    are operational reports, 300 to 399
    are audit reports, 400 to 499 are
    static table listings, 500 to 599 are
    user functions, 600 to 699 are
    interface functions, 700 to 799 are
    dynamic table update functions,
    800 to 899 are static table update
    functions, and 900 to 999 are
    administration functions.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Rows Processed Quantity of rows retrieved or
    updated. The quantity of rows
    retrieved for a reporting function
    or the quantity of rows inserted,
    updated, or deleted for an update
    function.
    Usage End Date Date/time function stopped being
    used. The usage end date is the
    date and time the function
    completed processing the rows.
    The difference between the usage
    start and end dates is the seconds
    required to retrieve the report rows
    or post the changes to the database
    for an update function.
    Last Changed Date
    Last Changed By
    Timestamp
    Inventory Inventory System assigned identification
    Identification number. The inventory
    identification is the unique
    identifier for a document. It is a
    system assigned integer, not user
    assigned.
    Organization System assigned identification
    Identification number. The organization
    identification is the unique
    identification for a company,
    department, or cost center. The
    integer value is system assigned,
    not user assigned. Organizations
    own users and classifications.
    Author Document written-by user
    identification. Identification for
    writer of the document. It can be
    any value.
    Class Identification System assigned identification
    number. The class identification is
    the unique identifier for the
    classification. This integer is a
    system assigned value, not user
    assigned.
    Created By Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Original File Name PC file name and extension. The
    name of the computer file from
    which the inventory item
    originated.
    Inventory Label First line of label. The inventory
    Line
    1 label consists of three columns that
    appear on the label for the
    document, file folder, or box. The
    first label line typically contains a
    name. For example, vendor name,
    customer name, person name, etc.
    for the document.
    Inventory Label Second line of label. The
    Line 2 inventory label consists of three
    columns that appear on the label
    for the document, file folder, or
    box. The second label line
    typically contains a geography.
    Inventory Label Third line of label. The inventory
    Line 3 label consists of three columns that
    appear on the label for the
    document, file folder, or box. The
    third label line typically contains
    numbers or dates. For example,
    part numbers, purchase order
    numbers, contract numbers,
    employee numbers, etc.
    Location System assigned identification
    Identification number. The location
    identification is the unique
    identifier for a shelf or drawer
    within an aisle or file cabinet in a
    storage area. It is a system
    assigned integer, not user assigned.
    Media Type Code User assigned identification code
    for media type. The media type
    code defines what form the
    inventory item is stored in. For
    example, DISK=hard disk,
    FLOPPY=floppy disk, CD=CD
    ROM, TAPE=magnetic table,
    FICH=microfich,
    PAPER=hardcopy.
    Record Type Code User assigned identification code.
    The record type code defines
    importance to a classification. For
    example, I=informational and
    O=official record types. Inventory
    items assigned a classification
    having an official record type can
    only be deleted by a Department
    Coordinator.
    Storage Date Date entered into the Electronic
    Records System. The storage date
    is the date and time the inventory
    item was placed into the system.
    Series Code Code to flag special documents. A
    10 character code applied by the
    user to help flag documents that
    are special to them.
    System Entry Date Date Inventory was entered into
    the system. It can never be
    changed.
    Last Changed Date
    Last Changed By
    Timestamp
    Inventory Inventory System assigned identification
    Abstract Identification number. The inventory
    identification is the unique
    identifier for a document. It is a
    system assigned integer, not user
    assigned.
    Abstract Long description of inventory
    item. The abstract column
    contains a long textual description
    of the inventory item.
    Center Retention Quantity of months in offsite
    Months storage. The center retention
    months is the quantity of months
    an inventory item is held in a
    records center or off site storage
    facility. The office retention plus
    the center retention months equals
    the total retention period for a
    classification.
    Office Retention Quantity of months stored on site.
    Months The office retention months is the
    quantity of months an inventory
    item is held in an office storage
    area before it is moved to a long
    term, off site storage facility. The
    office retention plus the center
    retention months equals the total
    retention period for a
    classification.
    Last Changed Date
    Last Changed By
    Timestamp
    Inventory Inventory System assigned identification
    Request Identification number. The inventory
    identification is the unique
    identifier for a document. It is a
    system assigned integer, not user
    assigned.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Request Type Code User assigned identification code.
    The request type code is a user
    created code to define what needs
    to be done to an inventory item.
    Request type codes are M=Change
    Media R=Retrieve from storage
    facility, S=sent to storage facility,
    T=Retire inventory item.
    Location System assigned identification
    Identification number. The location
    identification is the unique
    identifier for a shelf or drawer
    within an aisle or file cabinet in a
    storage area. It is a system
    assigned integer, not user assigned.
    Media Type User assigned identification code
    Requested for media type. The media type
    code defines what form the
    inventory item is stored in. For
    example, DISK=hard disk,
    FLOPPY=floppy disk, CD=CD
    ROM, TAPE=magnetic table,
    FICH=microfich,
    PAPER=hardcopy.
    Request Date Date inventory request was
    created. The request date is the
    date and time a user has requested
    and inventory item be moved from
    one media to another.
    Last Changed Date
    Last Changed By
    Timestamp
    Inventory Class Identification System assigned identification
    Statistics number. The class identification is
    the unique identifier for the
    classification. This integer is a
    system assigned value, not user
    assigned.
    Location System assigned identification
    Identification number. The location
    identification is the unique
    identifier for a shelf or drawer
    within an aisle or file cabinet in a
    storage area. It is a system
    assigned integer, not user assigned.
    Record Type Code User assigned identification code.
    The record type code defines
    importance to a classification. For
    example, I=informational and
    O=official record types. Inventory
    items assigned a classification
    having an official record type can
    only be deleted by a Department
    Coordinator.
    Collection Date Date statistics were collected. The
    date the count of inventory items
    was collected. The quantity of
    inventory items by class and
    record type will be collected once
    a month or once a quarter.
    Inventory Quantity Quantity of inventory items found.
    The inventory quantity contains
    the number of inventory items
    found for a class and record type at
    a given point in time.
    Last Changed Date
    Last Changed By
    Timestamp
    Location Location System assigned identification
    Identification number. The location
    identification is the unique
    identifier for a shelf or drawer
    within an aisle or file cabinet in a
    storage area. It is a system
    assigned integer, not user assigned.
    Location Long name, description, or title.
    Description The location description is the
    meaning of a location number. For
    example, ‘Third drawer down’ or
    ‘Fourth shelf up’ are location
    descriptions.
    Location Number User assigned identification
    number. The location number is
    the user assigned identifier for a
    file cabinet drawer or shelf.
    Location Type Code User assigned identification code
    for location type. The location
    type code is a user assigned code
    for the type of document storage
    facility. For example,
    BL=Building, FA=File area,
    PR=Property, SH=Shelf,
    AI=Aisle.
    Parent Location Parent or owner of location. The
    Identification parent location identification is the
    unique identifier for building or
    file area that owns the location.
    Last Changed Date
    Last Changed By
    Timestamp
    Location Type Location Type Code User assigned identification code
    for location type. The location
    type code is a user assigned code
    for the type of document storage
    facility. For example,
    BL=Building, FA=File area,
    PR=Property, SH=Shelf,
    AI=Aisle.
    Archive Facility Archive facility (offsite storage)
    Flag Y/N flag. The archive facility flag
    is a yes/no column used to define
    if the location is found in an
    archive facility. An archive
    facility would be an offsite
    warehouse, for example.
    Location Type Long name or title of location
    Description type. The location description is
    the meaning of the location type
    code.
    Level Number Location hierarchy level number.
    The level number defines what
    level of the location hierarchy this
    location can be found. Level one
    is the top level of the hierarchy and
    level number five is the bottom.
    Last Changed Date
    Last Changed By
    Timestamp
    Media Type Media Type Code User assigned identification code
    for media type. The media type
    code defines what form the
    inventory item is stored in. For
    example, DISK=hard disk,
    FLOPPY=floppy disk, CD=CD
    ROM, TAPE=magnetic table,
    FICH=microfich,
    PAPER=hardcopy.
    Media Type Long name, description, or title.
    Description The media type description adds
    meaning to the media type code.
    For example, ‘Hardcopy’ and
    ‘Magnetic Tape’ are media type
    descriptions.
    ERSExpress Access File name required yes/no. The
    Flag purpose of this column is to record
    whether a document being entered
    for a given media type should have
    a file name entered also. For
    example, if a document is entered
    into the system that has a media
    type of ‘hard disk’ , and the file
    name required flag is set to ‘yes’,
    then the system will prompt the
    user to input a file name for the
    document. If the file name
    required flag is set to ‘no’ then the
    system will not prompt the user for
    a file name when they input
    information about a document.
    Last Changed Date
    Last Changed By
    Timestamp
    Object Object Name Name of database object (table or
    Identification view). The object name is the
    SQL database name for a table or
    view.
    Identification Last system assigned identification
    number. The identification
    column contains the last or highest
    integer value assigned to the
    identification column in the table.
    For example, if the table name was
    tbl_dpt and the identification
    column contains 145, then the
    highest identification number
    assigned thus far to departments is
    145.
    Last Changed Date
    Last Changed By
    Timestamp
    Filler
    1 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 2 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 3 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 4 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 5 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 6 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 7 This is a character field of 255
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Filler 8 This is a character field of 151
    bytes used to pad one row in the
    identification table out to one page
    long. This technique is use
    because SQLServer only has page
    locking, not row locking.
    Organization Organization System assigned identification
    Identification number. The organization
    identification is the unique
    identification for a company,
    department, or cost center. The
    integer value is system assigned,
    not user assigned. Organizations
    own users and classifications.
    Organization Code User assigned identification code.
    The organization code is a user
    assigned identification for a
    company, department, or cost
    center.
    Organization Name Long name, description, or title.
    The organization name is the
    meaning for the organization code.
    For example, ‘Account Payable’,
    ‘Payroll’ , ‘Inside Sales’ are all
    organization names for cost
    centers.
    Organization Type User assigned organization type
    Code code. The organization type code
    defines if an organization is a
    company, department, or cost
    center.
    Parent Organization Parent owner for organization.
    Identification The parent organization
    identification is the unique
    identification for a company, or
    department that owns the
    organization.
    Last Changed Date
    Last Changed By
    Timestamp
    Organization Organization Type User assigned organization type
    Type Code code. The organization type code
    defines if an organization is a
    company, department, or cost
    center.
    Organization Type Long name, description, or title.
    Description The organization type description
    is the meaning of the organization
    type code.
    Level Number Organization hierarchy level
    number. The level number defines
    at what level of the organization
    hierarchy this organization
    (company, department, or cost
    center) can be found. Level
    number one is the top of the
    hierarchy and level number five is
    the bottom.
    Last Changed Date
    Last Changed By
    Timestamp
    Record Type Record Type Code User assigned identification code.
    The record type code defines
    importance to a classification. For
    example, I=informational and
    O=official record types. Inventory
    items assigned a classification
    having an official record type can
    only be deleted by a Department
    Coordinator.
    Record Type Long name, description, or title.
    Description The record type description adds
    meaning to the record type code.
    Record Type Office policy for record type. The
    Procedure record type procedure states the
    office policy associated with the
    record type. For example,
    ‘Inventory items assigned a
    classification having an official
    record type can only be deleted by
    a Department Coordinator’.
    Last Changed Date
    Last Changed By
    Timestamp
    Request Type Request Type Code User assigned identification code.
    The request type code is a user
    created code to define what needs
    to be done to an inventory item.
    Request type codes are M=Change
    Media, R=Retrieve from storage
    facility, S=sent to storage facility,
    T=Retire inventory item.
    Request Type Long name, description, or title.
    Description The request type description
    defines the meaning for the request
    type code.
    Last Changed Date
    Last Changed By
    Timestamp
    Retention Retention Reference User assigned identification
    Reference number. The retention reference
    column is used to store the
    identification number for the
    reference document or law
    governing a set of classes and their
    retention periods. For example,
    ‘26 CFR 1.6001.1’ is a document
    defining how checks ought to
    stored.
    Abstract Long description of reference.
    The abstract column contains a
    paragraph about the reference.
    This paragraph states the policy for
    storing a type of document.
    Last Changed Date
    Last Changed By
    Timestamp
    Retention Retention Start User assigned identification code.
    Start Code The retention start code defines
    when the retention period of the
    document starts. The quantity of
    months an inventory item is held
    may start when the document first
    created, or it may start when the
    document is moved to an off site
    storage facility.
    Retention Start Long name, description, or title.
    Description The retention start description adds
    meaning to the retention start code.
    It is the office policy stating when
    the retention period begins for a
    document.
    Last Changed Date
    Last Changed By
    Timestamp
    Sensitivity Sensitivity Code User assigned identification code.
    The sensitivity code defines the
    security associated with a
    classification. For example,
    TS=top secrete and
    CO=confidential are sensitivity
    codes.
    Sensitivity Long name, description, or title.
    Description The sensitivity description adds
    meaning to the sensitivity code.
    Last Changed Date
    Last Changed By
    Timestamp
    Synonym Synonym System assigned identification
    Identification number. The synonym
    identification is the unique
    identifier for the synonym. This
    integer is a system assigned value,
    not user assigned.
    Synonym Name Name of synonym. The synonym
    name is the name of the synonym.
    Synonyms are alternate means to
    refer to a classification. Synonyms
    can be class codes, class names, or
    any value the user wishes.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Class Identification System assigned identification
    number. The class identification is
    the unique identifier for the
    classification. This integer is a
    system assigned value, not user
    assigned.
    Keyword Flag Corporate keyword (Y=yes,
    N=no). The keyword flag denotes
    if this synonym is a Corporate
    synonym. All synonyms have to
    be related to a Corporate keyword.
    Last Changed Date
    Last Changed By
    Timestamp
    User User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Default Location System assigned identification
    Identification number. The location
    identification is the unique
    identifier for a shelf or drawer
    within an aisle or file cabinet in a
    storage area. It is a system
    assigned integer, not user assigned.
    Organization System assigned identification
    Identification number. The organization
    identification is the unique
    identification for a company,
    department, or cost center. The
    integer value is system assigned,
    not user assigned. Organizations
    own users and classifications.
    Mail Stop User's mail stop. Physical mailing
    address of an ERSuser in the
    company.
    Output Directory Directory path for extract files.
    The output directory is the disk
    drive and directory name where
    the user would like extract files
    placed. If the user elects to have a
    report exported into a spread sheet,
    then the spread sheet will be
    placed in the output directory.
    Last Changed Date
    Last Changed By
    Timestamp
    User Class Class Identification System assigned identification
    number. The class identification is
    the unique identifier for the
    classification. This integer is a
    system assigned value, not user
    assigned.
    User Identification Logon user identification. The
    user identification is the SQL
    database name for the user.
    Normally, it is the user's first name
    initial and full last name.
    Access Code User assigned identification code.
    The access code defines what a
    user can do to a database object.
    Access codes are S = Select, U =
    Update, I = Insert, D = Delete. If a
    user has an access code of I or D
    then they can automatically do U
    or S. If a user has an access code
    of U then they can also do S.
    Default Class Flag Default class (Y=yes, N=no).
    Denotes default class if none is
    selected.
    Last Assigned Date Date last used. The date and time
    the class was last assigned by the
    user to a document. This column
    can help determine if a user has
    ever assigned this class to a
    document.
    Last Changed Date
    Last Changed By
    Timestamp
  • Logical View [0377]
  • FIG. 13 is a logical view of the database. It shows all the entities or tables and their attributes or columns. The purpose of this diagram is to provide a more detailed picture of the database and its contents. [0378]
  • Standard Abbreviations [0379]
  • The following lists the standard abbreviations for database object and column names. Several of these abbreviations will be merged together to derive a name. For example, the user tables will be named ‘tbl_usr’. The user's last name column will be called lst_nme’. [0380]
  • abs abstract [0381]
  • acc access [0382]
  • adr address [0383]
  • ctr center [0384]
  • chg change [0385]
  • cd code [0386]
  • cst cost [0387]
  • cls class [0388]
  • col column [0389]
  • cre created [0390]
  • d DataWindow object [0391]
  • db database [0392]
  • dw DataWindow control [0393]
  • def default [0394]
  • dsc description [0395]
  • dir directory [0396]
  • dte date [0397]
  • dur duration [0398]
  • end end [0399]
  • flg flag [0400]
  • fst first [0401]
  • fcn function [0402]
  • grp group [0403]
  • hst history [0404]
  • idn identification [0405]
  • inv inventory [0406]
  • key key [0407]
  • lst last [0408]
  • loc location [0409]
  • log logon [0410]
  • mail mail [0411]
  • med media [0412]
  • mth month [0413]
  • nbr number [0414]
  • nme name [0415]
  • off office [0416]
  • obj object [0417]
  • ord order [0418]
  • org organization [0419]
  • out output [0420]
  • par parent [0421]
  • phn phone [0422]
  • psw password [0423]
  • pro procedure [0424]
  • pcs processed [0425]
  • pps purpose [0426]
  • rec record [0427]
  • rel relationship [0428]
  • rqs request [0429]
  • rqr require [0430]
  • ret retention [0431]
  • row rows [0432]
  • snt sensitivity [0433]
  • seq sequence [0434]
  • srt sort [0435]
  • str start [0436]
  • sts status [0437]
  • sto storage [0438]
  • stp stop [0439]
  • sub subject [0440]
  • syn synonym [0441]
  • tbl table [0442]
  • tm time [0443]
  • tle title [0444]
  • trg trigger [0445]
  • typ type [0446]
  • udt user defined datatype [0447]
  • usg usage [0448]
  • usp user stored procedure [0449]
  • usr user [0450]
  • vtl vital [0451]
  • vw view [0452]
  • vwb base view [0453]
  • w window [0454]
  • wrd word [0455]
  • Triggers [0456]
  • Triggers are business rules embedded in the database. These rules are activated every time a row is added, changed, or delete for a table. They can be used insure referential integrity, enforce security, and/or calculate values for columns. The triggers defined for this system are described below by table. Note, that referential integrity triggers are not listed. They are too numerous to display, but will be part of the application. [0457]
  • Class Table [0458]
  • Insert Trigger—Two rows should be added to the synonym table. The values for the synonym table are as follows: [0459]
  • [0460] Row 1
    Synonym Name The class code
    User Identification ‘SA’
    Parent Synonym Name The class code of the parent
    classification
    Keyword Flag ‘Y’
  • [0461] Row 2
    Synonym Name The classification title
    User Identification ‘SA’
    Parent Synonym Name The class code
    Keyword Flag ‘N’
  • When inserting a row into the class table, add two rows to the class synonym table. The values for the class synonym table should be the following: [0462]
  • [0463] Row 1
    Synonym Name The class code
    User Identification ‘SA’
    Class Identification The class identification
  • [0464] Row 2
    Synonym Name The class title
    User Identification ‘SA’
    Class Identification The class identification
  • Update Trigger—See if the class code is being changed. If it is, then update the synonym name in the synonym table and the synonym name in the class synonym table. [0465]
  • When updating a row in the class table, see if the class title is being changed. If it is, then update the synonym name in the synonym table and the synonym name in the class synonym table. [0466]
  • When updating a row in the class table, see if the parent classification identification is being changed. If it is, then update the parent synonym name in the synonym table. [0467]
  • Delete Trigger—Delete the corresponding rows in the synonym table and the class synonym table where the following is true: [0468]
  • Synonym name equals class code and user identification equals ‘SA’ or [0469]
  • Synonym name equals classification title and user identification equal ‘SA’[0470]
  • Function Table [0471]
  • Delete Trigger—Create a cascading delete that will remove the function form all other tables. [0472]
  • Update Trigger—If the function type is changed for ‘REPORT’ to something else, a search for the function column and function sort tables should be performed. If there are any rows in these tables, then they ought to be deleted. [0473]
  • Function Column Table [0474]
  • Insert Trigger—The function type column in the function table must be set to ‘REPORT’. If the function is not a report, then it should not have rows in the function column or sort table. [0475]
  • The relationship code can only have values of ‘EQUAL’, ‘LIKE’ or ‘BOTH’. Also the column type values can only be ‘CHAR’, ‘INT’, ‘DATE’, and ‘FLOAT’. [0476]
  • Update Trigger—The relationship code can only have values of ‘EQUAL’, ‘LIKE’or ‘BOTH’. Also the column type values can only be ‘CHAR’, ‘INT’, ‘DATE’, and ‘FLOAT’. [0477]
  • Function Sort Table [0478]
  • Insert Trigger—There can only be one row having a default sort flag value of ‘Y’ for yes for each function. [0479]
  • Update Trigger—There can only be one row having a default sort flag value of ‘Y’ for yes for each function. [0480]
  • Function Usage Table [0481]
  • Insert Trigger—The usage start date must be less than the usage end date. [0482]
  • Update Trigger—The usage start date must be less than the usage end date. [0483]
  • Location Table [0484]
  • Insert Trigger—If the level number for the location type is one, then the parent location identification equals the location identification. If the level number of the location type is not equal to one, then the parent location identification can not be equal to the location identification. [0485]
  • If the level number is not equal to one, then the level number must be equal to one minus the level number for the parent location. [0486]
  • Object Table [0487]
  • Insert Trigger—The object purpose can not be null if the object type code is ‘V’ for view. [0488]
  • Insert Trigger—The object purpose can not be null if the object type code is ‘V’ for view. [0489]
  • Object Identification Table [0490]
  • Insert Trigger—Insure that the object type column value in the object table is set to ‘U’ for user table. [0491]
  • Update Trigger—Insure that the object type column value in the object table is set to ‘U’ for user table. [0492]
  • Organization Table [0493]
  • Insert Trigger—If the level number for the organization type is one, then the parent organization identification equals the organization identification. If the level number of the organization type is not equal to one, then the parent organization identification can not be equal to the organization identification. If the level number is not equal to one, then the level number must be equal to one minus the level number for the parent organization. [0494]
  • Update Trigger—If the level number for the organization type is one, then the parent organization identification equals the organization identification. If the level number of the organization type is not equal to one, then the parent organization identification can not be equal to the organization identification. [0495]
  • If the level number is not equal to one, then the level number must be equal to one minus the level number for the parent organization. [0496]
  • User Table [0497]
  • Insert Trigger—When inserting a new user, create rows for the user class table. Copy the user class rows for the person doing the inserting and place them into the user class table for the new user. The processing steps are: [0498]
  • Retrieve the user ID of the individual inserting a new row into the user table. [0499]
  • Take the user ID found in the previous step and read the user class table for the person doing the inserting. Retrieve their set of classifications and access codes. [0500]
  • Insert the classifications and access codes found in the previous step under the ID of the new user. [0501]
  • Ignore the processing describe above if the user doing the inserting is SA. [0502]
  • Delete Trigger—Create a cascading delete that will remove the user for all other tables. [0503]
  • User Class Table [0504]
  • Insert Table—There can only be one row having a default class flag value of ‘Y’ for yes for each user. [0505]
  • If an individual is inserting a new row into the user class table, then that individual must have read or write access to that same class. The new row can not have write access to the class if the individual doing the inserting only has read access. Ignore this logic if the person doing the inserting is SA. [0506]
  • Update Table—There can only be one row having a default class flag value of ‘Y’ for yes for each user. [0507]
  • If the access code is being changed from R=read to W=write then the individual making the change must have write access to that same class. Ignore this logic if the person doing the changing is SA. [0508]
  • User Database Table [0509]
  • Insert Trigger—There can only be one row having a default database flag value of ‘Y’ for yes for each user. [0510]
  • Update Trigger—There can only be one row having a default database flag value of ‘Y’ for yes for each user. [0511]
  • User Defined Datatypes [0512]
  • User defined datatypes are common formats that will be applied to columns. The attributes for each datatype in this system are listed below. [0513]
  • udt_integer [0514]
  • integer System generated identification numbers. [0515]
  • udt_ndt [0516]
  • varchar(40) Names, descriptions and [0517] titles 40 chars or less.
  • udt_name [0518]
  • char(20) First, Last Names, [0519] other names 20 chars or less.
  • udt_label [0520]
  • char(25) Labels. [0521]
  • udt_text [0522]
  • varchar(255) Long descriptions, text, explanations, summaries etc. [0523]
  • udt_identifier [0524]
  • char(20) Any type of database object identifier. [0525]
  • udt_yesno [0526]
  • char(1)Any yes/no column. [0527]
  • udt_phone [0528]
  • char(13) Full length phone number—Do not store dashes. [0529]
  • udt_code_a [0530]
  • char(1) Codes and other data of various lengths. [0531]
  • udt_code_b [0532]
  • char(2) [0533]
  • udt_code_c [0534]
  • char(6) [0535]
  • udt_code_d [0536]
  • char(8) [0537]
  • udt_code_e [0538]
  • char(10) [0539]
  • udt_code_f [0540]
  • char(12) [0541]
  • udt_code_g [0542]
  • char(15) [0543]
  • Physical Database Model [0544]
  • The physical database model displays all the SQL attributes about each column in the application. It is the combination of the logical view, abbreviations, triggers, and user defined datatypes. The physical database model is presented in FIG. 14. [0545]
  • Physical Attributes [0546]
  • The following table displays the SQL attributes (column name, datatype, null option, etc.) for each column being stored. [0547]
    Entity Column Alternate Foreign Prime Column
    Name Attribute Name Name Key Key Key Datatype Null Option
    Access Access Code acc_cd (PK) char(1) NOT NULL
    Access Description dsc (AK1) varchar(40) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Class Class cls_idn (PK) int NOT NULL
    Identification
    Abstract abs varchar(255) NOT NULL
    Class Code cls_cd (AK1) char(10) NOT NULL
    Classification Title tle varchar(40) NOT NULL
    Classification Title tle_ext varchar(40) NOT NULL
    Extended
    Center Retention ctr_rtnt_mth int NOT NULL
    Months
    Organization org_idn (FK) int NOT NULL
    Identification
    Created By cre_by char(20) NOT NULL
    Media Type Code med_typ_cd (FK) char(6) NOT NULL
    Office Retention ofc_rtnt_mth int NOT NULL
    Months
    Parent Class prnt_cls_idn (FK) int NOT NULL
    Identification
    Record Type Code rec_typ_cd (FK) char(1) NOT NULL
    Retention rtnt_rfr (FK) varchar(40) NOT NULL
    Reference
    Retention Start rtnt_str_cd (FK) char(2) NOT NULL
    Code
    Sensitivity Code sntv_cd (FK) char(2) NOT NULL
    Vital Flag vtl_fk char(1) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Data Entity Name ent_nine (PK) varchar(40) NOT NULL
    Dictionary
    Attribute Name att_nme (PK) varchar(40) NOT NULL
    Attribute att_def varchar(255) NOT NULL
    Definition
    Column Name col_nme varchar(40) NOT NULL
    Datatype dtyp char(20) NOT NULL
    Entity Definition ent_def varchar(255) NOT NULL
    Null Option null opt char(20) NOT NULL
    User Defined udt_nme char(20) NOT NULL
    Datatype Name
    Last Changed Date 1st_chg_dte datetime NOT NULL
    Last Changed By 1st_chg_by char(20) NOT NULL
    Timestamp timestamp timestamp NULL
    Function Function Number fxn_nbr (PK) char(8) NOT NULL
    Function Purpose prps varchar(255) NOT NULL
    Function Subject fxn_subj_cd (FK) char(10) NOT NULL
    Code
    Function Title tle (AK1) varchar(40) NOT NULL
    Function Type fxn_typ_cd (FK) char(1) NOT NULL
    Code
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Function Number fxn_nbr (FK) (PK) char(8) NOT NULL
    Column
    Table Name tbl_nme (FK) (PK) char(20) NOT NULL
    Column Name col_nme (FK) (PK) char(20) NOT NULL
    Column Null Flag null_flg char(1) NOT NULL
    Column Title tle varchar(40) NOT NULL
    Column Type typ char(20) NOT NULL
    Relationship Code rel_cd char(6) NOT NULL
    Required Flag rqr_flg char(1) NOT NULL
    Sequence Number seq_nbr int NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Function Number fxn_nbr (FK) (PK) char(8) NOT NULL
    Column
    Last Used
    Column Name col_nme (FK) (PK) char(20) NOT NULL
    User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Table Name tbl_nme (FK) (PK) char(20) NOT NULL
    Column Value col_val varchar(255) NOT NULL
    Operator Code oprcd char(2) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Table Name tbl_nme (PK) char(20) NOT NULL
    Data Window
    Column Name col_nme (PK) char(20) NOT NULL
    Data Window dw_nme varchar(40) NOT NULL
    Name
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(18) NULL
    Timestamp timestamp timestamp NULL
    Function Function Number fxn_nbr (FK) (PK) char(8) NOT NULL
    Sort
    Order By ord_by (PK) varchar(200) NOT NULL
    DataWindow dw_nme varchar(40) NOT NULL
    Name
    Default Sort Flag dft_srt_flg char(1) NOT NULL
    Order By Title tle varchar(255) NOT NULL
    Sequence Number seq_nbr int NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Requires Stored rqr_usp char(20) NULL
    Procedure
    Timestamp timestamp timestamp NULL
    Function Function Number frn_nbr (FK) (PK) char(8) NOT NULL
    Sort Last
    Used
    Order By ord_by (FK) (PK) varchar(200) NOT NULL
    User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Function Subject fxn_subj_cd (PK) char(10) NOT NULL
    Subject Code
    Function Subject dsc (AK1) varchar(40) NOT NULL
    Description
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Function Type fxn_typ_cd (PK) char(1) NOT NULL
    Type Code
    Function Type dsc varchar(40) NOT NULL
    Description
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Function Usage Start Date usg_str_dte (PK) datetime NOT NULL
    Usage
    Function Number fxn_nbr (FK) (PK) char(8) NOT NULL
    User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Rows Processed row_prcs int NOT NULL
    Usage End Date usg_end_dte datetime NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Inventory Inventory inv_idn (PK) int NOT NULL
    Identification
    Organization org_idn (AK1) (FK) int NOT NULL
    Identification
    Author athr (IE1) varchar(40) NOT NULL
    Class cls_idn (FK) int NOT NULL
    Identification
    Created By cre_by (FK) char(30) NULL
    Original File orgn_file_nme varchar(40) NULL
    Name
    Inventory Label inv_lbl_ln_1 (AK1) char(25) NOT NULL
    Line 1
    Inventory Label inv_lbl_ln_2 (AK1) char(25) NOT NULL
    Line 2
    Inventory Label inv_lbl_ln_3 (AK1) char(25) NOT NULL
    Line 3
    Location loc_idn (FK) int NOT NULL
    Identification
    Media Type Code med_typ_cd (AK1) (FK) char(6) NOT NULL
    Record Type Code rec_typ_cd (AK1) (FK) char(1) NOT NULL
    Storage Date strg_dte (IE3) datetime NOT NULL
    Series Code ser_cde (IE2) char(10) NOT NULL
    System Entry Date sys_ntry_dte datetime NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NOT NULL
    Timestamp timestamp timestamp NULL
    Inventory Inventory inv_idn (FK) (PK) int NOT NULL
    Abstract Identification
    Abstract abs text NULL
    Center Retention ctr_rtnt_mth int NOT NULL
    Months
    Office Retention ofc_rtnt_mth int NOT NULL
    Months
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Inventory Inventory inv_idn (FK) (PK) int NOT NULL
    Request Identification
    User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Request Type rqst_typ_cd (FK) (PK) char( I) NOT NULL
    Code
    Location loc_idn (FK) int NULL
    Identification
    Media Type med_typ_cd (FK) char(6) NULL
    Requested
    Request Date rqst_dte datetime NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Inventory Class cls_idn (FK) (PK) int NOT NULL
    Statistics Identification
    Location loc_idn (FK) (PK) int NOT NULL
    Identification
    Record Type Code rec_typ_cd (FK) (PK) char(1) NOT NULL
    Collection Date colc_dte (PK) datetime NOT NULL
    Inventory Quantity inv_qty int NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Location Location loc_idn (PK) int NOT NULL
    Identification
    Location dsc varchar(50) NOT NULL
    Description
    Location Number nbr (AK1) char(10) NOT NULL
    Location Type loc_typ_cd (FK) char(2) NOT NULL
    Code
    Parent Location prnt_loc_idn (FK) int NOT NULL
    Identification
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Location Location Type loc_typ_cd (PK) char(2) NOT NULL
    Type Code
    Archive Facility arch_fac_flg char(1) NOT NULL
    Flag
    Location Type dsc (AK1) varchar(40) NOT NULL
    Description
    Level Number lvl_nbr int NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Media Type Media Type Code med_typ_cd (PK) char(6) NOT NULL
    Media Type dsc (AK1) varchar(40) NOT NULL
    Description
    ERS Express ers_expr_acc char(1) NOT NULL
    Access Flag _flg
    Last Changed Date 1st_chgdte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Object Object Name obj_nme (PK) char(20) NOT NULL
    Identification
    Identification idn int NOT NULL
    Last Changed Date 1st_chg_dte datetime NOT NULL
    Last Changed By 1st_chg_by char(20) NOT NULL
    Timestamp timestamp timestamp NOT NULL
    Filler 1 filler_1 char(255) NOT NULL
    Filler 2 filler_2 char(255) NOT NULL
    Filler 3 filler_3 char(255) NOT NULL
    Filler 4 filler_4 char(255) NOT NULL
    Filler 5 filler_5 char(255) NOT NULL
    Filler 6 filler_6 char(255) NOT NULL
    Filler 7 filler_7 char(255) NOT NULL
    Filler 8 filler_8 char(103) NOT NULL
    Organization Organization org_idn (PK) int NOT NULL
    Identification
    Organization Code org_cd (AK1) char(10) NOT NULL
    Organization org_nme varchar(40) NOT NULL
    Name
    Organization Type org_typ_cd (FK) char(2) NOT NULL
    Code
    Parent prnt_org_idn (FK) int NOT NULL
    Organization
    Identification
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Organization Organization Type org_typ_cd (PK) char(2) NOT NULL
    Type Code
    Organization Type dsc (AK1) varchar(40) NOT NULL
    Description
    Level Number lvl_nbr int NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Record Record Type Code rec_typ_cd (PK) char(1) NOT NULL
    Type
    Record Type dsc varchar(40) NOT NULL
    Description
    Record Type pcdr varchar(255) NOT NULL
    Procedure
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Request Request Type rqst_typ_cd (PK) char(1) NOT NULL
    Type Code
    Request Type dsc (AK1) varchar(40) NOT NULL
    Description
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Retention Retention rtnt_rfr (PK) varchar(40) NOT NULL
    Reference Reference
    Abstract abs varchar(255) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Retention Retention Start rtnt_str_cd (PK) char(2) NOT NULL
    Start Code
    Retention Start dsc (AK1) varchar(255) NOT NULL
    Description
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Sensitivity Sensitivity Code sntv_cd (PK) char(2) NOT NULL
    Sensitivity dsc (AK1) varchar(40) NOT NULL
    Description
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    Synonym Synonym syn_idn (PK) int NOT NULL
    Identification
    Synonym Name syn_nme (AK) varchar(40) NOT NULL
    User Identification usr_idn (AK) (FK) char(30) NOT NULL
    Class cls_idn (AK) (FK) int NOT NULL
    Identification
    Keyword Flag key_wrd_flg char(1) NOT NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    User User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Default Location loc_idn (FK) int NOT NULL
    Identification
    Organization org_idn (FK) int NOT NULL
    Identification
    Mail Stop mail_stop char(10) NULL
    Output Directory out_dir varchar(255) NULL
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
    User Class Class cls_idn (FK) (PK) int NOT NULL
    Identification
    User Identification usr_idn (FK) (PK) char(30) NOT NULL
    Access Code acc_cd (FK) char(1) NULL
    Default Class Flag dft_cls_flg char(1) NOT NULL
    Last Assigned 1st_asgn_dte datetime NULL
    Date
    Last Changed Date 1st_chg_dte datetime NULL
    Last Changed By 1st_chg_by char(20) NULL
    Timestamp timestamp timestamp NULL
  • System Requirements [0548]
  • The purpose of this section of the document is to define the minimum hardware and software needed to run and maintain the application. This section is divided into three parts; Client Workstation, Developers Workstation, and Server. The requirements defined below assume that there are no other applications running on this equipment at the same time. [0549]
  • Client Workstation [0550]
  • The client workstation is the personal computer run by the average user. Its purpose is to create word processing documents, spreadsheets, presentations, and to run the ERS application. [0551]
  • Hardware [0552]
  • Processor [0553]
  • 486/66 MHz processor, or faster. [0554]
  • Memory [0555]
  • 16 Meg. of memory or more. [0556]
  • Hard Disk [0557]
  • 500 Meg. of available disk space or more. [0558]
  • Access to a common network drive containing the application software. [0559]
  • Monitor [0560]
  • VGA color monitor. [0561]
  • Printer [0562]
  • Access to a LASER printer, 300 dpi resolution or higher. [0563]
  • Network Card [0564]
  • Must be compatible with available cabling, network software, and PC hardware. [0565]
  • Keyboard [0566]
  • Mouse [0567]
  • Software [0568]
  • Operating System [0569]
  • Microsoft DOS, release 6.22. [0570]
  • Microsoft Windows for Workgroups, release 3.11. [0571]
  • Network Software such as Novell or Windows for Workgroups. [0572]
  • Application Packages Microsoft Office containing Word, Excel, and PowerPoint. [0573]
  • Developer Workstation [0574]
  • The developer workstation is used to construct and maintain the application. It contains all the tools needed to modify the source code for the system. [0575]
  • Hardware [0576]
  • Processor [0577]
  • Pentium 100 MHz processor, or faster. [0578]
  • Memory [0579]
  • 24 Meg. of memory or more. [0580]
  • Hard Disk [0581]
  • 1 Gig. of available disk space or more. [0582]
  • Access to a common network drive containing the application software. [0583]
  • CD ROM [0584]
  • 4x speed, or faster. [0585]
  • Tape Drive [0586]
  • 250 Meg tape backup, or larger. [0587]
  • Monitor [0588]
  • 17″ VGA color monitor. [0589]
  • Printer [0590]
  • Access to a laser printer, 300 dpi resolution or higher. [0591]
  • Network Card [0592]
  • Must be compatible with available cabling, network [0593]
  • software, and PC hardware. [0594]
  • Modem [0595]
  • 28.8 FAX/Modem, or faster. [0596]
  • Keyboard [0597]
  • Mouse [0598]
  • Software [0599]
  • Operating System [0600]
  • Microsoft DOS, release 6.22. [0601]
  • Microsoft Windows for Workgroups, release 3.11. [0602]
  • Network Software such as Novell or Windows for Workgroups. [0603]
  • Application Packages [0604]
  • Microsoft Office containing Word, Excel, and PowerPoint. [0605]
  • Microsoft Project, release 4.0. [0606]
  • Development Tools PowerSoft PowerBuilder, release [0607] 4.0.4.
  • MetaSolv PowerFrame, release 4.0. [0608]
  • Norton Desktop for Windows, release 3.0. [0609]
  • Logic Works ERWin for PowerBuilder, release 2.5. [0610]
  • Embarcadero Technologies DBArtisan, release 2.02. [0611]
  • Embarcadero Technologies Rapid SQL, release 1.02. [0612]
  • Blue Sky Software RoboHelp, release 3.0. [0613]
  • PC Install for Windows 3.X. [0614]
  • Saros Mezzanine Developers Tool Kit. [0615]
  • Saros Document Manager. [0616]
  • Server [0617]
  • The server supports the user community and developers. It acts as the centralized storage point for the system's database and archived documents. The server should support two modems for remote access trouble shooting, demonstrations, and training sessions. The amount of disk space requested should be enough to support two versions of the database. [0618]
  • Hardware [0619]
  • Processor [0620]
  • Two Pentium 100 MHz processors, or faster. [0621]
  • Memory [0622]
  • 64 Meg. of memory or more. [0623]
  • Hard Disk [0624]
  • 1 Gig. of available disk space or more. [0625]
  • Access to a common network drive containing the application software. [0626]
  • CD ROM [0627]
  • 4x speed, or faster. [0628]
  • Tape Drive [0629]
  • 250 Meg tape backup, or larger. [0630]

Claims (11)

I claim:
1. A computer implemented method for uniformly classifying documents comprising the steps of:
a) assigning to a document to be classified a set of predetermined class codes from a class database, said class codes arranged in a hierarchy from general to specific;
b) assigning a retention period to said document;
c) storing the class code and retention period assigned to said document as part of a record in a document database.
2. The method defined by claim 1 wherein each of said class codes is selected from terms used in business and government.
3. The method defined by claim 1 further comprising the steps of:
a) assigning to said document a document type;
b) storing the document type assigned to said document as part of said record in said document database.
4. The method defined by claim 3 wherein said assigned retention period is based upon the class code and document type assigned to the document.
5. The method defined by claim 3 wherein said document type is one of official, informational, vital and sensitive.
6. The method defined by claim 1 further comprising the steps of:
a) assigning to said document a media type and location;
b) storing the media type and location assigned to said document as part of said record in a document database.
7. The method defined by claim 1 wherein at least one of said class codes has at least one associated synonym stored in a synonym database.
8. The method defined by claim 1 further comprising the steps of:
a) searching said document database by class code and
b) generating a display showing matching records.
9. The method defined by claim 7 further comprising the steps of:
a) receiving a term as search parameter; and
b) searching said document database using said search parameter by class code and generating a display showing records in said document database where said search parameter matches the class code, and if no matching records are found, searching said synonym database and generating a display showing records in said document database having a class code associated with a synonym which matches said search parameter.
10. The method defined by claim 7 wherein said synonym database is customizable at a user workstation for use by a user at said user workstation.
11. The method defined by claim 9 further comprising the step of:
a) assigning to said document a document access code specifying permitted user access based on at least one of a chart of accounts and an organization chart;
b) stored the access code in said document database;
c) assigning to a user a user access code based on said user's position within at least one of said chart of accounts and said organization chart;
d) preventing said user from accessing records in said document database which do not have a document access code which matches said user's user access code.
US09/778,029 1996-09-23 2001-02-05 Defining a uniform subject classification system incorporating document management/records retention functions Abandoned US20020010708A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/778,029 US20020010708A1 (en) 1996-09-23 2001-02-05 Defining a uniform subject classification system incorporating document management/records retention functions

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US71789796A 1996-09-23 1996-09-23
US09/176,394 US6185576B1 (en) 1996-09-23 1998-10-21 Defining a uniform subject classification system incorporating document management/records retention functions
US09/778,029 US20020010708A1 (en) 1996-09-23 2001-02-05 Defining a uniform subject classification system incorporating document management/records retention functions

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/176,394 Continuation US6185576B1 (en) 1996-09-23 1998-10-21 Defining a uniform subject classification system incorporating document management/records retention functions

Publications (1)

Publication Number Publication Date
US20020010708A1 true US20020010708A1 (en) 2002-01-24

Family

ID=24883934

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/176,394 Expired - Lifetime US6185576B1 (en) 1996-09-23 1998-10-21 Defining a uniform subject classification system incorporating document management/records retention functions
US09/778,029 Abandoned US20020010708A1 (en) 1996-09-23 2001-02-05 Defining a uniform subject classification system incorporating document management/records retention functions

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/176,394 Expired - Lifetime US6185576B1 (en) 1996-09-23 1998-10-21 Defining a uniform subject classification system incorporating document management/records retention functions

Country Status (3)

Country Link
US (2) US6185576B1 (en)
AU (1) AU4495597A (en)
WO (1) WO1998012616A2 (en)

Cited By (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020161804A1 (en) * 2001-04-26 2002-10-31 Patrick Chiu Internet-based system for multimedia meeting minutes
US6547136B1 (en) * 2000-11-27 2003-04-15 Pitney Bowes, Inc. Verifiable carrier payment method for returning merchandise
US6714922B1 (en) 2000-11-27 2004-03-30 Pitney Bowes Inc. Method for returning merchandise
US20050027566A1 (en) * 2003-07-09 2005-02-03 Haskell Robert Emmons Terminology management system
US20050055519A1 (en) * 2003-09-08 2005-03-10 Stuart Alan L. Method, system, and program for implementing retention policies to archive records
US20050055518A1 (en) * 2003-09-08 2005-03-10 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US20050065947A1 (en) * 2003-09-19 2005-03-24 Yang He Thesaurus maintaining system and method
US20050076042A1 (en) * 2003-10-07 2005-04-07 Stakutis Christopher John Method, system, and program for archiving files
US20060156381A1 (en) * 2005-01-12 2006-07-13 Tetsuro Motoyama Approach for deleting electronic documents on network devices using document retention policies
US20060200508A1 (en) * 2003-08-08 2006-09-07 Jp Morgan Chase Bank System for archive integrity management and related methods
US7139977B1 (en) * 2001-01-24 2006-11-21 Oracle International Corporation System and method for producing a virtual online book
US20070162412A1 (en) * 2003-03-03 2007-07-12 Richard Percy System and method using alphanumeric codes for the identification, description, classification and encoding of information
US20070219987A1 (en) * 2005-10-14 2007-09-20 Leviathan Entertainment, Llc Self Teaching Thesaurus
US20070226267A1 (en) * 2006-03-23 2007-09-27 Haagenson Marsh K Automated records inventory and retention schedule generation system
US20080088873A1 (en) * 2006-10-13 2008-04-17 Fuji Xerox Co., Ltd. Document administration system and document destruction apparatus
US20080098038A1 (en) * 1998-10-06 2008-04-24 Tetsuro Motoyama Method And System To Erase Data By Overwriting After Expiration Or Other Condition
US20080201322A1 (en) * 2007-02-21 2008-08-21 Fujifilm Corporation Apparatus and method for retrieval of contents
US7430513B2 (en) 2002-12-17 2008-09-30 Baydel North America, Inc. Data storage management driven by business objectives
CN100429634C (en) * 2004-11-24 2008-10-29 夏普株式会社 Copy device, copy system, copy administration system, and copy controlling method
US20080288479A1 (en) * 2006-08-16 2008-11-20 Pss Systems, Inc. System and method for leveraging historical data to determine affected entities
US20080294492A1 (en) * 2007-05-24 2008-11-27 Irina Simpson Proactively determining potential evidence issues for custodial systems in active litigation
US20090132262A1 (en) * 2007-09-14 2009-05-21 Pss Systems Proactively determining evidence issues on legal matters involving employee status changes
US20090165026A1 (en) * 2007-12-21 2009-06-25 Deidre Paknad Method and apparatus for electronic data discovery
US20090164790A1 (en) * 2007-12-20 2009-06-25 Andrey Pogodin Method and system for storage of unstructured data for electronic discovery in external data stores
US20090187797A1 (en) * 2008-01-21 2009-07-23 Pierre Raynaud-Richard Providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery
US20090228525A1 (en) * 2008-03-10 2009-09-10 Ubs Ag Methods and systems for group data management and classification
US20090313196A1 (en) * 2008-06-12 2009-12-17 Nazrul Islam External scoping sources to determine affected people, systems, and classes of information in legal matters
US20090327048A1 (en) * 2008-06-30 2009-12-31 Kisin Roman Forecasting Discovery Costs Based on Complex and Incomplete Facts
US20090327021A1 (en) * 2008-06-27 2009-12-31 Pss Systems, Inc. System and method for managing legal obligations for data
US20090327375A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Method and Apparatus for Handling Edge-Cases of Event-Driven Disposition
US20090328070A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Event Driven Disposition
US20090326969A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Method and Apparatus for Managing the Disposition of Data in Systems When Data is on Legal Hold
US20100017239A1 (en) * 2008-06-30 2010-01-21 Eric Saltzman Forecasting Discovery Costs Using Historic Data
US20100082382A1 (en) * 2008-09-30 2010-04-01 Kisin Roman Forecasting discovery costs based on interpolation of historic event patterns
US20100082676A1 (en) * 2008-09-30 2010-04-01 Deidre Paknad Method and apparatus to define and justify policy requirements using a legal reference library
US20100095349A1 (en) * 2008-10-15 2010-04-15 Tetsuro Motoyama Approach for Managing Access to Electronic Documents on Network Devices Using Document Retention Policies and Document Security Policies
US7895229B1 (en) 2007-05-24 2011-02-22 Pss Systems, Inc. Conducting cross-checks on legal matters across an enterprise system
US20110060670A1 (en) * 2009-09-04 2011-03-10 Hartford Fire Insurance Company System and method for managing data relating to investments from a variety of sources
US20110153578A1 (en) * 2009-12-22 2011-06-23 Andrey Pogodin Method And Apparatus For Propagation Of File Plans From Enterprise Retention Management Applications To Records Management Systems
US20110153579A1 (en) * 2009-12-22 2011-06-23 Deidre Paknad Method and Apparatus for Policy Distribution
US20110173033A1 (en) * 2006-08-16 2011-07-14 Pss Systems, Inc. Systems and methods for utilizing an enterprise map to determine affected entities
US20110173202A1 (en) * 2006-08-16 2011-07-14 Pss Systems, Inc. Systems and methods for utilizing organization-specific classification codes
US20110173218A1 (en) * 2006-08-29 2011-07-14 Pss Systems, Inc. Systems and methods for providing a map of an enterprise system
US20110179077A1 (en) * 2007-12-19 2011-07-21 Dr. Valentina Pulnikova Retrieval system and method of searching of information in the Internet
US20120089640A1 (en) * 2005-01-28 2012-04-12 Thomson Reuters Global Resources Systems, Methods, Software For Integration of Case Law, Legal Briefs, and Litigation Documents into Law Firm Workflow
US20130046754A1 (en) * 2001-03-21 2013-02-21 Eugene M. Lee Method and system to formulate intellectual property search and to organize results of intellectual property search
US8402359B1 (en) 2010-06-30 2013-03-19 International Business Machines Corporation Method and apparatus for managing recent activity navigation in web applications
US8484069B2 (en) 2008-06-30 2013-07-09 International Business Machines Corporation Forecasting discovery costs based on complex and incomplete facts
JP2013196175A (en) * 2012-03-16 2013-09-30 Nec Corp Information processing device including electronic document database, illegally stored document detection method, and program
US20130268538A1 (en) * 2005-05-06 2013-10-10 Nelson Information Systems Database and Index Organization for Enhanced Document Retrieval
US8566903B2 (en) 2010-06-29 2013-10-22 International Business Machines Corporation Enterprise evidence repository providing access control to collected artifacts
US8832148B2 (en) 2010-06-29 2014-09-09 International Business Machines Corporation Enterprise evidence repository
US20150142801A1 (en) * 2013-11-15 2015-05-21 International Business Machines Corporation System and Method for Intelligently Categorizing Data to Delete Specified Amounts of Data Based on Selected Data Characteristics
US9053484B1 (en) 2013-11-18 2015-06-09 Access Sciences Corporation Computer implemented system for forming an accelerated compliance plan with a graphic visualization
US9058606B1 (en) 2013-11-18 2015-06-16 Access Sciences Corporation Computer implemented method for forming an accelerated compliance plan with a graphic visualization
WO2016028594A1 (en) * 2014-08-18 2016-02-25 Lexisnexis, A Division Of Reed Elsevier Inc. Systems and methods for providing for display hierarchical views of content organization nodes associated with captured content and for determining organizational identifiers for captured content
US20160140207A1 (en) * 2014-11-14 2016-05-19 Symantec Corporation Systems and methods for aggregating information-asset classifications
US10025804B2 (en) 2014-05-04 2018-07-17 Veritas Technologies Llc Systems and methods for aggregating information-asset metadata from multiple disparate data-management systems
US10635645B1 (en) 2014-05-04 2020-04-28 Veritas Technologies Llc Systems and methods for maintaining aggregate tables in databases
US10783495B1 (en) 2014-04-30 2020-09-22 Information Exchange Holdings Inc. Document management for ingredient suppliers

Families Citing this family (180)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5822720A (en) 1994-02-16 1998-10-13 Sentius Corporation System amd method for linking streams of multimedia data for reference material for display
AUPO489297A0 (en) * 1997-01-31 1997-02-27 Aunty Abha's Electronic Publishing Pty Ltd A system for electronic publishing
US7293228B1 (en) * 1997-01-31 2007-11-06 Timebase Pty Limited Maltweb multi-axis viewing interface and higher level scoping
GB9821787D0 (en) * 1998-10-06 1998-12-02 Data Limited Apparatus for classifying or processing data
JP4025443B2 (en) * 1998-12-04 2007-12-19 富士通株式会社 Document data providing apparatus and document data providing method
EP1049030A1 (en) * 1999-04-28 2000-11-02 SER Systeme AG Produkte und Anwendungen der Datenverarbeitung Classification method and apparatus
US7979382B2 (en) 1999-05-04 2011-07-12 Accenture Global Services Limited Component based information linking during claim processing
US6839879B1 (en) * 1999-05-07 2005-01-04 Xilinx, Inc. Method and system for time-stamping and managing electronic documents
US6175830B1 (en) * 1999-05-20 2001-01-16 Evresearch, Ltd. Information management, retrieval and display system and associated method
US7277931B1 (en) 1999-06-08 2007-10-02 International Business Machines Corporation Representing, configuring, administering, monitoring, and/or modeling connections using catalogs and matrixes
US6647394B1 (en) * 1999-06-08 2003-11-11 International Business Machines Corporation Doing business employing linked trees having retrievable embedded information
US6772156B1 (en) 1999-11-29 2004-08-03 Actuate Corporation Method and apparatus for creating and displaying a table of content for a computer-generated report having page-level security
US6650344B1 (en) * 1999-11-29 2003-11-18 International Business Machines Corporation Method and system for displaying computer documents
US6859805B1 (en) * 1999-11-29 2005-02-22 Actuate Corporation Method and apparatus for generating page-level security in a computer generated report
US7251666B2 (en) * 2000-02-01 2007-07-31 Internet Business Information Group Signature loop authorizing method and apparatus
EP1128278B1 (en) * 2000-02-23 2003-09-17 SER Solutions, Inc Method and apparatus for processing electronic documents
US20010044735A1 (en) * 2000-04-27 2001-11-22 Colburn Harry S. Auditing and monitoring system for workers' compensation claims
US20070181736A1 (en) * 2000-05-01 2007-08-09 Shaikh Mohammed N S Method and apparatus for remote filing and recordation of documents
US20060271554A1 (en) * 2000-05-01 2006-11-30 Shaikh Mohammed Nisar S Method and apparatus for remote filing and recordation of documents
CA2307404A1 (en) * 2000-05-02 2001-11-02 Provenance Systems Inc. Computer readable electronic records automated classification system
US7421645B2 (en) * 2000-06-06 2008-09-02 Microsoft Corporation Method and system for providing electronic commerce actions based on semantically labeled strings
US7712024B2 (en) * 2000-06-06 2010-05-04 Microsoft Corporation Application program interfaces for semantically labeling strings and providing actions based on semantically labeled strings
US7716163B2 (en) * 2000-06-06 2010-05-11 Microsoft Corporation Method and system for defining semantic categories and actions
US7770102B1 (en) 2000-06-06 2010-08-03 Microsoft Corporation Method and system for semantically labeling strings and providing actions based on semantically labeled strings
US7788602B2 (en) * 2000-06-06 2010-08-31 Microsoft Corporation Method and system for providing restricted actions for recognized semantic categories
US6757692B1 (en) * 2000-06-09 2004-06-29 Northrop Grumman Corporation Systems and methods for structured vocabulary search and classification
US6678692B1 (en) * 2000-07-10 2004-01-13 Northrop Grumman Corporation Hierarchy statistical analysis system and method
US9177828B2 (en) 2011-02-10 2015-11-03 Micron Technology, Inc. External gettering method and device
EP1182577A1 (en) * 2000-08-18 2002-02-27 SER Systeme AG Produkte und Anwendungen der Datenverarbeitung Associative memory
US7707153B1 (en) * 2000-10-06 2010-04-27 Esys Technologies, Llc Automated work-flow management and document generation system and method
US7054833B1 (en) 2000-10-27 2006-05-30 Mcdonald Patrick D Method and system for processing unclaimed property information
JP3943824B2 (en) * 2000-10-31 2007-07-11 株式会社東芝 Information management method and information management apparatus
US7353228B2 (en) 2000-12-07 2008-04-01 General Electric Capital Corporation Method and product for calculating a net operating income audit and for enabling substantially identical audit practices among a plurality of audit firms
JP2002175331A (en) * 2000-12-07 2002-06-21 Patent Mall:Kk Display method of patent classification, device, recording medium and program thereof
JP3701197B2 (en) * 2000-12-28 2005-09-28 松下電器産業株式会社 Method and apparatus for creating criteria for calculating degree of attribution to classification
US9715691B2 (en) * 2001-01-16 2017-07-25 Gtj Ventures, Llc Apparatus and method for providing transaction history information, account history information, and/or charge-back information
US9117206B2 (en) * 2001-01-16 2015-08-25 Gtj Ventures, Llc Apparatus and method for providing transaction history information, account history information, and/or charge-back information
US7032174B2 (en) * 2001-03-27 2006-04-18 Microsoft Corporation Automatically adding proper names to a database
US7778816B2 (en) * 2001-04-24 2010-08-17 Microsoft Corporation Method and system for applying input mode bias
US20030009497A1 (en) * 2001-07-05 2003-01-09 Allen Yu Community based personalization system and method
TW566041B (en) * 2001-07-06 2003-12-11 Hitachi Ltd Digital data recording device and output device
US20030041305A1 (en) * 2001-07-18 2003-02-27 Christoph Schnelle Resilient data links
US7130861B2 (en) * 2001-08-16 2006-10-31 Sentius International Corporation Automated creation and delivery of database content
ATE537507T1 (en) 2001-08-27 2011-12-15 Bdgb Entpr Software Sarl METHOD FOR AUTOMATICALLY INDEXING DOCUMENTS
US7363310B2 (en) 2001-09-04 2008-04-22 Timebase Pty Limited Mapping of data from XML to SQL
US20030061132A1 (en) * 2001-09-26 2003-03-27 Yu, Mason K. System and method for categorizing, aggregating and analyzing payment transactions data
AUPR796701A0 (en) * 2001-09-27 2001-10-25 Plugged In Communications Pty Ltd Database query system and method
AUPR796801A0 (en) * 2001-09-27 2001-10-25 Plugged In Communications Pty Ltd Computer user interface tool for navigation of data stored in directed graphs
US7051012B2 (en) * 2001-10-22 2006-05-23 Siemens Medical Solutions Health Services Corporation User interface system for maintaining organization related information for use in supporting organization operation
US7305392B1 (en) 2001-11-02 2007-12-04 Apex Innovations, Inc. Multi-organizational project management system
US7281206B2 (en) 2001-11-16 2007-10-09 Timebase Pty Limited Maintenance of a markup language document in a database
US20030217062A1 (en) * 2001-12-18 2003-11-20 Shawn Thomas Method and system for asset transition project management
US6947924B2 (en) 2002-01-07 2005-09-20 International Business Machines Corporation Group based search engine generating search results ranking based on at least one nomination previously made by member of the user group where nomination system is independent from visitation system
US7233959B2 (en) * 2002-06-03 2007-06-19 International Business Machines Corporation Life-cycle management engine
US20040205660A1 (en) * 2002-04-23 2004-10-14 Joe Acton System and method for generating and displaying attribute-enhanced documents
US7325194B2 (en) * 2002-05-07 2008-01-29 Microsoft Corporation Method, system, and apparatus for converting numbers between measurement systems based upon semantically labeled strings
US7707496B1 (en) 2002-05-09 2010-04-27 Microsoft Corporation Method, system, and apparatus for converting dates between calendars and languages based upon semantically labeled strings
US7742048B1 (en) 2002-05-23 2010-06-22 Microsoft Corporation Method, system, and apparatus for converting numbers based upon semantically labeled strings
US7707024B2 (en) * 2002-05-23 2010-04-27 Microsoft Corporation Method, system, and apparatus for converting currency values based upon semantically labeled strings
US7827546B1 (en) 2002-06-05 2010-11-02 Microsoft Corporation Mechanism for downloading software components from a remote source for use by a local software application
US7281245B2 (en) * 2002-06-05 2007-10-09 Microsoft Corporation Mechanism for downloading software components from a remote source for use by a local software application
US7356537B2 (en) * 2002-06-06 2008-04-08 Microsoft Corporation Providing contextually sensitive tools and help content in computer-generated documents
US7003522B1 (en) 2002-06-24 2006-02-21 Microsoft Corporation System and method for incorporating smart tags in online content
US7716676B2 (en) 2002-06-25 2010-05-11 Microsoft Corporation System and method for issuing a message to a program
US20040001099A1 (en) * 2002-06-27 2004-01-01 Microsoft Corporation Method and system for associating actions with semantic labels in electronic documents
US7392479B2 (en) 2002-06-27 2008-06-24 Microsoft Corporation System and method for providing namespace related information
US7209915B1 (en) 2002-06-28 2007-04-24 Microsoft Corporation Method, system and apparatus for routing a query to one or more providers
US9811805B2 (en) * 2002-09-18 2017-11-07 eSys Technologies, Inc. Automated work-flow management system with dynamic interface
US7370271B2 (en) * 2002-10-30 2008-05-06 Actuate Corporation Methods and apparatus for generating a spreadsheet report template
US20040088157A1 (en) * 2002-10-30 2004-05-06 Motorola, Inc. Method for characterizing/classifying a document
US7016889B2 (en) * 2003-01-30 2006-03-21 Hewlett-Packard Development Company, Lp. System and method for identifying useful content in a knowledge repository
US7783614B2 (en) 2003-02-13 2010-08-24 Microsoft Corporation Linking elements of a document to corresponding fields, queries and/or procedures in a database
US20040172584A1 (en) * 2003-02-28 2004-09-02 Microsoft Corporation Method and system for enhancing paste functionality of a computer software application
US7711550B1 (en) 2003-04-29 2010-05-04 Microsoft Corporation Methods and system for recognizing names in a computer-generated document and for providing helpful actions associated with recognized names
US8126742B2 (en) 2003-05-09 2012-02-28 Accenture Global Services Limited Automated assignment of insurable events
US7734627B1 (en) * 2003-06-17 2010-06-08 Google Inc. Document similarity detection
US7739588B2 (en) * 2003-06-27 2010-06-15 Microsoft Corporation Leveraging markup language data for semantically labeling text strings and data and for providing actions based on semantically labeled text strings and data
TW200512602A (en) * 2003-09-19 2005-04-01 Hon Hai Prec Ind Co Ltd Method and system of fuzzy searching
US8515923B2 (en) * 2003-11-17 2013-08-20 Xerox Corporation Organizational usage document management system
US7434157B2 (en) 2003-12-09 2008-10-07 Microsoft Corporation Programmable object model for namespace or schema library support in a software application
US7178102B1 (en) 2003-12-09 2007-02-13 Microsoft Corporation Representing latent data in an extensible markup language document
US7404195B1 (en) 2003-12-09 2008-07-22 Microsoft Corporation Programmable object model for extensible markup language markup in an application
US7487515B1 (en) 2003-12-09 2009-02-03 Microsoft Corporation Programmable object model for extensible markup language schema validation
US7801920B2 (en) * 2004-01-21 2010-09-21 Emc Corporation Methods and apparatus for indirectly identifying a retention period for data in a storage system
US7509573B1 (en) 2004-02-17 2009-03-24 Microsoft Corporation Anti-virus security information in an extensible markup language document
US20050182617A1 (en) * 2004-02-17 2005-08-18 Microsoft Corporation Methods and systems for providing automated actions on recognized text strings in a computer-generated document
US8260764B1 (en) * 2004-03-05 2012-09-04 Open Text S.A. System and method to search and generate reports from semi-structured data
KR100470440B1 (en) * 2004-06-14 2005-02-05 (주)젠솔소프트 Rule-based method of automatically making reports required for law modification examination process
US7925658B2 (en) * 2004-09-17 2011-04-12 Actuate Corporation Methods and apparatus for mapping a hierarchical data structure to a flat data structure for use in generating a report
US20060080316A1 (en) * 2004-10-08 2006-04-13 Meridio Ltd Multiple indexing of an electronic document to selectively permit access to the content and metadata thereof
US7801863B2 (en) * 2005-03-04 2010-09-21 Microsoft Corporation Method and computer-readable medium for formula-based document retention
US7870480B1 (en) 2005-03-14 2011-01-11 Actuate Corporation Methods and apparatus for storing and retrieving annotations accessible by a plurality of reports
US20060259468A1 (en) * 2005-05-10 2006-11-16 Michael Brooks Methods for electronic records management
US20070011020A1 (en) * 2005-07-05 2007-01-11 Martin Anthony G Categorization of locations and documents in a computer network
US7788590B2 (en) * 2005-09-26 2010-08-31 Microsoft Corporation Lightweight reference user interface
US7992085B2 (en) 2005-09-26 2011-08-02 Microsoft Corporation Lightweight reference user interface
US20070083554A1 (en) * 2005-10-12 2007-04-12 International Business Machines Corporation Visual role definition for identity management
US7747495B2 (en) * 2005-10-24 2010-06-29 Capsilon Corporation Business method using the automated processing of paper and unstructured electronic documents
US8176004B2 (en) * 2005-10-24 2012-05-08 Capsilon Corporation Systems and methods for intelligent paperless document management
US7933786B2 (en) 2005-11-01 2011-04-26 Accenture Global Services Limited Collaborative intelligent task processor for insurance claims
JP4315161B2 (en) * 2006-02-16 2009-08-19 村田機械株式会社 Image reader with time authentication request function
US20070300295A1 (en) 2006-06-22 2007-12-27 Thomas Yu-Kiu Kwok Systems and methods to extract data automatically from a composite electronic document
US20080005667A1 (en) 2006-06-28 2008-01-03 Dias Daniel M Method and apparatus for creating and editing electronic documents
US7610315B2 (en) * 2006-09-06 2009-10-27 Adobe Systems Incorporated System and method of determining and recommending a document control policy for a document
US7657513B2 (en) * 2006-12-01 2010-02-02 Microsoft Corporation Adaptive help system and user interface
JP2008186176A (en) * 2007-01-29 2008-08-14 Canon Inc Image processing apparatus, document merging method and control program
US20090020604A1 (en) * 2007-07-17 2009-01-22 Moody Ernest W Method for information archival and retrieval
US8650221B2 (en) 2007-09-10 2014-02-11 International Business Machines Corporation Systems and methods to associate invoice data with a corresponding original invoice copy in a stack of invoices
EP2045959B1 (en) * 2007-10-03 2011-07-20 Accenture Global Services Limited Technology agnostic universally appliable data model for a telecommunication service provider archtitecture
US10304095B2 (en) * 2008-02-04 2019-05-28 Thomson Reuters Global Resources Unlimited Company System and method for accounting gateway
US8515786B2 (en) 2008-02-22 2013-08-20 Accenture Global Services Gmbh Rule generation system adapted for an insurance claim processing system
US8478769B2 (en) 2008-02-22 2013-07-02 Accenture Global Services Limited Conversational question generation system adapted for an insurance claim processing system
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US8340634B2 (en) 2009-01-28 2012-12-25 Headwater Partners I, Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8406748B2 (en) 2009-01-28 2013-03-26 Headwater Partners I Llc Adaptive ambient services
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8402111B2 (en) 2009-01-28 2013-03-19 Headwater Partners I, Llc Device assisted services install
US8346225B2 (en) 2009-01-28 2013-01-01 Headwater Partners I, Llc Quality of service for device assisted services
US8250207B2 (en) 2009-01-28 2012-08-21 Headwater Partners I, Llc Network based ambient services
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8275830B2 (en) 2009-01-28 2012-09-25 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US8391834B2 (en) 2009-01-28 2013-03-05 Headwater Partners I Llc Security techniques for device assisted services
US8365241B1 (en) * 2008-06-09 2013-01-29 Symantec Corporation Method and apparatus for archiving web content based on a policy
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10484858B2 (en) 2009-01-28 2019-11-19 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US11080790B2 (en) 2009-09-24 2021-08-03 Guidewire Software, Inc. Method and apparatus for managing revisions and tracking of insurance policy elements
US9152883B2 (en) * 2009-11-02 2015-10-06 Harry Urbschat System and method for increasing the accuracy of optical character recognition (OCR)
US9158833B2 (en) * 2009-11-02 2015-10-13 Harry Urbschat System and method for obtaining document information
US8321357B2 (en) * 2009-09-30 2012-11-27 Lapir Gennady Method and system for extraction
US9213756B2 (en) * 2009-11-02 2015-12-15 Harry Urbschat System and method of using dynamic variance networks
GB0920339D0 (en) * 2009-11-20 2010-01-06 Vodafone Plc Archiving method and apparatus
US8490056B2 (en) * 2010-04-28 2013-07-16 International Business Machines Corporation Automatic identification of subroutines from test scripts
US8161073B2 (en) 2010-05-05 2012-04-17 Holovisions, LLC Context-driven search
US9020946B2 (en) 2010-07-12 2015-04-28 Qvinci Software, Llc System and method for compilation of quickbooks accounts data
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9858624B2 (en) * 2012-10-04 2018-01-02 Qvinci Software, Llc Methods and apparatus for providing data normalization, scalability and maintainability
WO2014159862A1 (en) 2013-03-14 2014-10-02 Headwater Partners I Llc Automated credential porting for mobile devices
US20150178372A1 (en) * 2013-12-19 2015-06-25 OpenGov, Inc. Creating an ontology across multiple semantically-related data sets
US20170132590A1 (en) * 2015-09-22 2017-05-11 Joom3D.Com Technologies Incorporated Systems and methods for providing online access to resources
US11057191B2 (en) * 2016-09-01 2021-07-06 Sap Se Data retention management in databases
US11625662B2 (en) 2016-09-22 2023-04-11 Qvinci Software, Llc Methods and apparatus for the manipulating and providing of anonymized data collected from a plurality of sources
EP3489870A1 (en) * 2017-11-22 2019-05-29 Hybris AG System and method for collecting and/or retrieving information relating to objects
US11734586B2 (en) 2019-10-14 2023-08-22 International Business Machines Corporation Detecting and improving content relevancy in large content management systems

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4276597A (en) 1974-01-17 1981-06-30 Volt Delta Resources, Inc. Method and apparatus for information storage and retrieval
JPS589982B2 (en) 1980-05-30 1983-02-23 工業技術院長 information retrieval device
US4674066A (en) 1983-02-18 1987-06-16 Houghton Mifflin Company Textual database system using skeletonization and phonetic replacement to retrieve words matching or similar to query words
US5206949A (en) 1986-09-19 1993-04-27 Nancy P. Cochran Database search and record retrieval system which continuously displays category names during scrolling and selection of individually displayed search terms
US4879648A (en) 1986-09-19 1989-11-07 Nancy P. Cochran Search system which continuously displays search terms during scrolling and selections of individually displayed data sets
US4862408A (en) 1987-03-20 1989-08-29 International Business Machines Corporation Paradigm-based morphological text analysis for natural languages
US4899299A (en) * 1987-12-23 1990-02-06 International Business Machines Corporation Method for managing the retention of electronic documents in an interactive information handling system
US5051891A (en) 1987-12-23 1991-09-24 International Business Machines Corporation Method to manage transfer of ownership of electronic documents stored in an interactive information handling system
US5107419A (en) * 1987-12-23 1992-04-21 International Business Machines Corporation Method of assigning retention and deletion criteria to electronic documents stored in an interactive information handling system
JPH021057A (en) 1988-01-20 1990-01-05 Ricoh Co Ltd Document retrieving device
US5261103A (en) 1988-09-12 1993-11-09 Hitachi, Ltd. Method of and system for compiling source program
US5201048A (en) 1988-12-01 1993-04-06 Axxess Technologies, Inc. High speed computer system for search and retrieval of data within text and record oriented files
US5018060A (en) 1989-01-26 1991-05-21 Ibm Corporation Allocating data storage space of peripheral data storage devices using implied allocation based on user parameters
US5369763A (en) * 1989-02-01 1994-11-29 Kansas State University Research Foundation Data storage and retrieval system with improved data base structure
US5197005A (en) 1989-05-01 1993-03-23 Intelligent Business Systems Database retrieval system having a natural language interface
US5056021A (en) 1989-06-08 1991-10-08 Carolyn Ausborn Method and apparatus for abstracting concepts from natural language
US5218696A (en) 1989-07-24 1993-06-08 International Business Machines Corporation Method for dynamically expanding and rapidly accessing file directories
US5204812A (en) * 1989-11-02 1993-04-20 International Business Machines Corp. User access of multiple documents based on document relationship classification
EP0434588A3 (en) 1989-12-20 1993-01-20 International Business Machines Corporation Method of expanding user access to a library of shared electronic documents
US5201047A (en) 1989-12-21 1993-04-06 International Business Machines Corporation Attribute-based classification and retrieval system
US5404514A (en) 1989-12-26 1995-04-04 Kageneck; Karl-Erbo G. Method of indexing and retrieval of electronically-stored documents
US5274806A (en) 1990-05-02 1993-12-28 Electronic Data Systems Corporation Hierarchical data encyclopedia
JP2895184B2 (en) 1990-08-22 1999-05-24 株式会社日立製作所 Document processing system and document processing method
US5229936A (en) 1991-01-04 1993-07-20 Franklin Electronic Publishers, Incorporated Device and method for the storage and retrieval of inflection information for electronic reference products
JP2943447B2 (en) 1991-01-30 1999-08-30 三菱電機株式会社 Text information extraction device, text similarity matching device, text search system, text information extraction method, text similarity matching method, and question analysis device
JP3303926B2 (en) 1991-09-27 2002-07-22 富士ゼロックス株式会社 Structured document classification apparatus and method
US5265065A (en) 1991-10-08 1993-11-23 West Publishing Company Method and apparatus for information retrieval from a database by replacing domain specific stemmed phases in a natural language to create a search query
US5428778A (en) 1992-02-13 1995-06-27 Office Express Pty. Ltd. Selective dissemination of information
JPH05324726A (en) 1992-05-25 1993-12-07 Fujitsu Ltd Document data classifying device and document classifying function constituting device
US5423034A (en) * 1992-06-10 1995-06-06 Cohen-Levy; Leon Network file management with user determined hierarchical file structures and means for intercepting application program open and save commands for inputting and displaying user inputted descriptions of the location and content of files
GB9220404D0 (en) 1992-08-20 1992-11-11 Nat Security Agency Method of identifying,retrieving and sorting documents
US5454101A (en) 1992-09-15 1995-09-26 Universal Firmware Industries, Ltd. Data storage system with set lists which contain elements associated with parents for defining a logical hierarchy and general record pointers identifying specific data sets
US5530848A (en) 1992-10-15 1996-06-25 The Dow Chemical Company System and method for implementing an interface between an external process and transaction processing system
JP3025724B2 (en) 1992-11-24 2000-03-27 富士通株式会社 Synonym generation processing method
US5689699A (en) * 1992-12-23 1997-11-18 International Business Machines Corporation Dynamic verification of authorization in retention management schemes for data processing systems
CA2166420C (en) 1993-07-01 2006-03-28 James R. Woodhill System and method for distributed storage management on networked computer systems
JPH07105023A (en) * 1993-09-20 1995-04-21 Internatl Business Mach Corp <Ibm> Method and apparatus for detection of spurious interrupt at inside of data processing system
CA2175187A1 (en) 1993-10-28 1995-05-04 William K. Thomson Database search summary with user determined characteristics
US5630125A (en) * 1994-05-23 1997-05-13 Zellweger; Paul Method and apparatus for information management using an open hierarchical data structure
US5655130A (en) * 1994-10-14 1997-08-05 Unisys Corporation Method and apparatus for document production using a common document database

Cited By (116)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080098038A1 (en) * 1998-10-06 2008-04-24 Tetsuro Motoyama Method And System To Erase Data By Overwriting After Expiration Or Other Condition
US8005936B2 (en) 1998-10-06 2011-08-23 Ricoh Company, Ltd. Method and system to erase data by overwriting after expiration or other condition
US6547136B1 (en) * 2000-11-27 2003-04-15 Pitney Bowes, Inc. Verifiable carrier payment method for returning merchandise
US6714922B1 (en) 2000-11-27 2004-03-30 Pitney Bowes Inc. Method for returning merchandise
US7139977B1 (en) * 2001-01-24 2006-11-21 Oracle International Corporation System and method for producing a virtual online book
US20130046754A1 (en) * 2001-03-21 2013-02-21 Eugene M. Lee Method and system to formulate intellectual property search and to organize results of intellectual property search
US20020161804A1 (en) * 2001-04-26 2002-10-31 Patrick Chiu Internet-based system for multimedia meeting minutes
US7260771B2 (en) * 2001-04-26 2007-08-21 Fuji Xerox Co., Ltd. Internet-based system for multimedia meeting minutes
US7672854B2 (en) 2002-12-17 2010-03-02 Dataframeworks, Inc. Data storage management driven by business objectives
US7430513B2 (en) 2002-12-17 2008-09-30 Baydel North America, Inc. Data storage management driven by business objectives
US20070162412A1 (en) * 2003-03-03 2007-07-12 Richard Percy System and method using alphanumeric codes for the identification, description, classification and encoding of information
US20050027566A1 (en) * 2003-07-09 2005-02-03 Haskell Robert Emmons Terminology management system
US20060200508A1 (en) * 2003-08-08 2006-09-07 Jp Morgan Chase Bank System for archive integrity management and related methods
US7617261B2 (en) * 2003-08-08 2009-11-10 Jp Morgan Chase Bank System for archive integrity management and related methods
US7107416B2 (en) 2003-09-08 2006-09-12 International Business Machines Corporation Method, system, and program for implementing retention policies to archive records
US8281087B2 (en) 2003-09-08 2012-10-02 Google Inc. Method, system, and program implementing retention policies to archive records
US8583881B1 (en) 2003-09-08 2013-11-12 Google Inc. Method, system, and program for implementing retention policies to archive records
US7117322B2 (en) 2003-09-08 2006-10-03 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US20090119354A1 (en) * 2003-09-08 2009-05-07 International Business Machines Corporation Method, system, and program implementing retention policies to archive records
US20050055519A1 (en) * 2003-09-08 2005-03-10 Stuart Alan L. Method, system, and program for implementing retention policies to archive records
US20050055518A1 (en) * 2003-09-08 2005-03-10 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US20060282630A1 (en) * 2003-09-08 2006-12-14 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US7600086B2 (en) 2003-09-08 2009-10-06 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US20050065947A1 (en) * 2003-09-19 2005-03-24 Yang He Thesaurus maintaining system and method
US7765177B2 (en) 2003-10-07 2010-07-27 International Business Machines Corporation Method, system and program for archiving files
US8041698B2 (en) 2003-10-07 2011-10-18 International Business Machines Corporation Method, system and program for archiving files
US8700576B2 (en) 2003-10-07 2014-04-15 Google Inc. Method, system, and program for archiving files
US20050076042A1 (en) * 2003-10-07 2005-04-07 Stakutis Christopher John Method, system, and program for archiving files
US7146388B2 (en) 2003-10-07 2006-12-05 International Business Machines Corporation Method, system, and program for archiving files
US20060282484A1 (en) * 2003-10-07 2006-12-14 International Business Machines Corporation Method, system and program for archiving files
CN100429634C (en) * 2004-11-24 2008-10-29 夏普株式会社 Copy device, copy system, copy administration system, and copy controlling method
US7703125B2 (en) 2005-01-12 2010-04-20 Ricoh Company, Ltd. Approach for deleting electronic documents on network devices using document retention policies
US20060156381A1 (en) * 2005-01-12 2006-07-13 Tetsuro Motoyama Approach for deleting electronic documents on network devices using document retention policies
US20060156382A1 (en) * 2005-01-12 2006-07-13 Tetsuro Motoyama Approach for deleting electronic documents on network devices using document retention policies
US20120089640A1 (en) * 2005-01-28 2012-04-12 Thomson Reuters Global Resources Systems, Methods, Software For Integration of Case Law, Legal Briefs, and Litigation Documents into Law Firm Workflow
US8938458B2 (en) * 2005-05-06 2015-01-20 Nelson Information Systems Database and index organization for enhanced document retrieval
US20130268538A1 (en) * 2005-05-06 2013-10-10 Nelson Information Systems Database and Index Organization for Enhanced Document Retrieval
US20070219987A1 (en) * 2005-10-14 2007-09-20 Leviathan Entertainment, Llc Self Teaching Thesaurus
US8577852B2 (en) * 2006-03-23 2013-11-05 Infaxiom Group, Llc Automated records inventory and retention schedule generation system
US20070226267A1 (en) * 2006-03-23 2007-09-27 Haagenson Marsh K Automated records inventory and retention schedule generation system
US8131719B2 (en) * 2006-08-16 2012-03-06 International Business Machines Corporation Systems and methods for utilizing organization-specific classification codes
US20110173202A1 (en) * 2006-08-16 2011-07-14 Pss Systems, Inc. Systems and methods for utilizing organization-specific classification codes
US20110173033A1 (en) * 2006-08-16 2011-07-14 Pss Systems, Inc. Systems and methods for utilizing an enterprise map to determine affected entities
US8200690B2 (en) 2006-08-16 2012-06-12 International Business Machines Corporation System and method for leveraging historical data to determine affected entities
US20080288479A1 (en) * 2006-08-16 2008-11-20 Pss Systems, Inc. System and method for leveraging historical data to determine affected entities
US8626727B2 (en) 2006-08-29 2014-01-07 International Business Machines Corporation Systems and methods for providing a map of an enterprise system
US8700581B2 (en) 2006-08-29 2014-04-15 International Business Machines Corporation Systems and methods for providing a map of an enterprise system
US20110173218A1 (en) * 2006-08-29 2011-07-14 Pss Systems, Inc. Systems and methods for providing a map of an enterprise system
US20080088873A1 (en) * 2006-10-13 2008-04-17 Fuji Xerox Co., Ltd. Document administration system and document destruction apparatus
US7973959B2 (en) * 2006-10-13 2011-07-05 Fuji Xerox Co., Ltd. Document administration system and document destruction apparatus
US20080201322A1 (en) * 2007-02-21 2008-08-21 Fujifilm Corporation Apparatus and method for retrieval of contents
US7895229B1 (en) 2007-05-24 2011-02-22 Pss Systems, Inc. Conducting cross-checks on legal matters across an enterprise system
US20080294492A1 (en) * 2007-05-24 2008-11-27 Irina Simpson Proactively determining potential evidence issues for custodial systems in active litigation
US20090132262A1 (en) * 2007-09-14 2009-05-21 Pss Systems Proactively determining evidence issues on legal matters involving employee status changes
US20110179077A1 (en) * 2007-12-19 2011-07-21 Dr. Valentina Pulnikova Retrieval system and method of searching of information in the Internet
US9524341B2 (en) * 2007-12-19 2016-12-20 Valentina Pulnikova Retrieval system and method of searching of information in the internet
US20090164790A1 (en) * 2007-12-20 2009-06-25 Andrey Pogodin Method and system for storage of unstructured data for electronic discovery in external data stores
US8572043B2 (en) 2007-12-20 2013-10-29 International Business Machines Corporation Method and system for storage of unstructured data for electronic discovery in external data stores
US20090165026A1 (en) * 2007-12-21 2009-06-25 Deidre Paknad Method and apparatus for electronic data discovery
US8112406B2 (en) 2007-12-21 2012-02-07 International Business Machines Corporation Method and apparatus for electronic data discovery
US20090187797A1 (en) * 2008-01-21 2009-07-23 Pierre Raynaud-Richard Providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery
US8140494B2 (en) 2008-01-21 2012-03-20 International Business Machines Corporation Providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery
US8131683B2 (en) * 2008-03-10 2012-03-06 Ubs Ag Methods and systems for group data management and classification
US20090228525A1 (en) * 2008-03-10 2009-09-10 Ubs Ag Methods and systems for group data management and classification
US8275720B2 (en) 2008-06-12 2012-09-25 International Business Machines Corporation External scoping sources to determine affected people, systems, and classes of information in legal matters
US20090313196A1 (en) * 2008-06-12 2009-12-17 Nazrul Islam External scoping sources to determine affected people, systems, and classes of information in legal matters
US9830563B2 (en) 2008-06-27 2017-11-28 International Business Machines Corporation System and method for managing legal obligations for data
US20090327021A1 (en) * 2008-06-27 2009-12-31 Pss Systems, Inc. System and method for managing legal obligations for data
US8515924B2 (en) 2008-06-30 2013-08-20 International Business Machines Corporation Method and apparatus for handling edge-cases of event-driven disposition
US8484069B2 (en) 2008-06-30 2013-07-09 International Business Machines Corporation Forecasting discovery costs based on complex and incomplete facts
US20090326969A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Method and Apparatus for Managing the Disposition of Data in Systems When Data is on Legal Hold
US20090327375A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Method and Apparatus for Handling Edge-Cases of Event-Driven Disposition
US20090328070A1 (en) * 2008-06-30 2009-12-31 Deidre Paknad Event Driven Disposition
US20090327048A1 (en) * 2008-06-30 2009-12-31 Kisin Roman Forecasting Discovery Costs Based on Complex and Incomplete Facts
US8327384B2 (en) 2008-06-30 2012-12-04 International Business Machines Corporation Event driven disposition
US20100017239A1 (en) * 2008-06-30 2010-01-21 Eric Saltzman Forecasting Discovery Costs Using Historic Data
US8489439B2 (en) 2008-06-30 2013-07-16 International Business Machines Corporation Forecasting discovery costs based on complex and incomplete facts
US7792945B2 (en) 2008-06-30 2010-09-07 Pss Systems, Inc. Method and apparatus for managing the disposition of data in systems when data is on legal hold
US8204869B2 (en) 2008-09-30 2012-06-19 International Business Machines Corporation Method and apparatus to define and justify policy requirements using a legal reference library
US8073729B2 (en) 2008-09-30 2011-12-06 International Business Machines Corporation Forecasting discovery costs based on interpolation of historic event patterns
US20100082382A1 (en) * 2008-09-30 2010-04-01 Kisin Roman Forecasting discovery costs based on interpolation of historic event patterns
US20100082676A1 (en) * 2008-09-30 2010-04-01 Deidre Paknad Method and apparatus to define and justify policy requirements using a legal reference library
US20100095349A1 (en) * 2008-10-15 2010-04-15 Tetsuro Motoyama Approach for Managing Access to Electronic Documents on Network Devices Using Document Retention Policies and Document Security Policies
US8272028B2 (en) 2008-10-15 2012-09-18 Ricoh Company, Ltd. Approach for managing access to electronic documents on network devices using document retention policies and document security policies
US20110060670A1 (en) * 2009-09-04 2011-03-10 Hartford Fire Insurance Company System and method for managing data relating to investments from a variety of sources
US8266029B2 (en) * 2009-09-04 2012-09-11 Hartford Fire Insurance Company System and method for managing data relating to investments from a variety of sources
US8682767B2 (en) * 2009-09-04 2014-03-25 Hartford Fire Insurance Company System and method for accessing and displaying data relating to financial securities
US20130006891A1 (en) * 2009-09-04 2013-01-03 Hartford Fire Insurance Company System and method for accessing and displaying data relating to financial securities
US20110153579A1 (en) * 2009-12-22 2011-06-23 Deidre Paknad Method and Apparatus for Policy Distribution
US8655856B2 (en) 2009-12-22 2014-02-18 International Business Machines Corporation Method and apparatus for policy distribution
US20110153578A1 (en) * 2009-12-22 2011-06-23 Andrey Pogodin Method And Apparatus For Propagation Of File Plans From Enterprise Retention Management Applications To Records Management Systems
US8250041B2 (en) 2009-12-22 2012-08-21 International Business Machines Corporation Method and apparatus for propagation of file plans from enterprise retention management applications to records management systems
US8566903B2 (en) 2010-06-29 2013-10-22 International Business Machines Corporation Enterprise evidence repository providing access control to collected artifacts
US8832148B2 (en) 2010-06-29 2014-09-09 International Business Machines Corporation Enterprise evidence repository
US8402359B1 (en) 2010-06-30 2013-03-19 International Business Machines Corporation Method and apparatus for managing recent activity navigation in web applications
US9292704B2 (en) 2012-03-16 2016-03-22 Nec Corporation Information processing device for detecting an illegal stored document, illegal stored document detection method and recording medium
JP2013196175A (en) * 2012-03-16 2013-09-30 Nec Corp Information processing device including electronic document database, illegally stored document detection method, and program
US9870363B2 (en) 2013-11-15 2018-01-16 International Business Machines Corporation Intelligently categorizing data to delete specified amounts of data based on selected data characteristics
US20150142758A1 (en) * 2013-11-15 2015-05-21 International Business Machines Corporation Method for Intelligently Categorizing Data to Delete Specified Amounts of Data Based on Selected Data Characteristics
US9870364B2 (en) 2013-11-15 2018-01-16 International Business Machines Corporation Intelligently categorizing data to delete specified amounts of data based on selected data characteristics
US9355118B2 (en) * 2013-11-15 2016-05-31 International Business Machines Corporation System and method for intelligently categorizing data to delete specified amounts of data based on selected data characteristics
US9372869B2 (en) * 2013-11-15 2016-06-21 International Business Machines Corporation Method for intelligently categorizing data to delete specified amounts of data based on selected data characteristics
US20150142801A1 (en) * 2013-11-15 2015-05-21 International Business Machines Corporation System and Method for Intelligently Categorizing Data to Delete Specified Amounts of Data Based on Selected Data Characteristics
US9053484B1 (en) 2013-11-18 2015-06-09 Access Sciences Corporation Computer implemented system for forming an accelerated compliance plan with a graphic visualization
US9058606B1 (en) 2013-11-18 2015-06-16 Access Sciences Corporation Computer implemented method for forming an accelerated compliance plan with a graphic visualization
US11100468B2 (en) 2014-04-30 2021-08-24 Information Exchange Holdings Inc. Document management for ingredient suppliers
US10783495B1 (en) 2014-04-30 2020-09-22 Information Exchange Holdings Inc. Document management for ingredient suppliers
US10025804B2 (en) 2014-05-04 2018-07-17 Veritas Technologies Llc Systems and methods for aggregating information-asset metadata from multiple disparate data-management systems
US10073864B1 (en) 2014-05-04 2018-09-11 Veritas Technologies Llc Systems and methods for automated aggregation of information-source metadata
US10078668B1 (en) 2014-05-04 2018-09-18 Veritas Technologies Llc Systems and methods for utilizing information-asset metadata aggregated from multiple disparate data-management systems
US10635645B1 (en) 2014-05-04 2020-04-28 Veritas Technologies Llc Systems and methods for maintaining aggregate tables in databases
US10817510B1 (en) 2014-05-04 2020-10-27 Veritas Technologies Llc Systems and methods for navigating through a hierarchy of nodes stored in a database
WO2016028594A1 (en) * 2014-08-18 2016-02-25 Lexisnexis, A Division Of Reed Elsevier Inc. Systems and methods for providing for display hierarchical views of content organization nodes associated with captured content and for determining organizational identifiers for captured content
US9953062B2 (en) 2014-08-18 2018-04-24 Lexisnexis, A Division Of Reed Elsevier Inc. Systems and methods for providing for display hierarchical views of content organization nodes associated with captured content and for determining organizational identifiers for captured content
US10095768B2 (en) * 2014-11-14 2018-10-09 Veritas Technologies Llc Systems and methods for aggregating information-asset classifications
US20160140207A1 (en) * 2014-11-14 2016-05-19 Symantec Corporation Systems and methods for aggregating information-asset classifications

Also Published As

Publication number Publication date
WO1998012616A3 (en) 1998-07-16
US6185576B1 (en) 2001-02-06
WO1998012616A2 (en) 1998-03-26
AU4495597A (en) 1998-04-14

Similar Documents

Publication Publication Date Title
US6185576B1 (en) Defining a uniform subject classification system incorporating document management/records retention functions
Olson Data quality: the accuracy dimension
Montgomery et al. Comparing library and user related costs of print and electronic journal collections
US7873557B2 (en) Information, document, and compliance management for financial professionals, clients, and supervisors
US20010039532A1 (en) Chargeback calculator
Marco et al. Universal meta data models
US20030061225A1 (en) Hierarchical hybrid OLAP scenario management system
Groh et al. Access 2007 Bible
Hogan A practical guide to database design
US7539634B2 (en) Account reconciliation system and method
US20090171884A1 (en) System and method for web-based case management
EP2325764B1 (en) Archiving system
Skupsky Applying records retention to electronic records
Gehling et al. Using imaging to reengineer business
Ross The procurement of an automated library system with a model RFP
Roe From archival gothic to MARC modern: building common data structures
Bloss The value-added acquisitions librarian: Defining our role in a time of change
Boss A model RFP for an automated library system
Clapper Standards for serials
Eaton DATA MANAGEMENT AND ANALYSIS IN THE LITIGATION ENVIRONMENT: LITIGATION ANALYSIS DATABASES
Boudewijns et al. Design of an event handling
Blocher Analytical procedures and the microcomputer
Sealy Maintaining data integrity by documenting the system: putting database policy in writing
Sankar et al. Technical Issues in Implementing ERP Systems
Curtis et al. Developing a Data Warehouse: Some Guidelines and Suggestions

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION