WO1998012616A2 - 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
WO1998012616A2
WO1998012616A2 PCT/US1997/017004 US9717004W WO9812616A2 WO 1998012616 A2 WO1998012616 A2 WO 1998012616A2 US 9717004 W US9717004 W US 9717004W WO 9812616 A2 WO9812616 A2 WO 9812616A2
Authority
WO
WIPO (PCT)
Prior art keywords
document
user
database
class
documents
Prior art date
Application number
PCT/US1997/017004
Other languages
French (fr)
Other versions
WO1998012616A3 (en
Inventor
Lowrie Mcintosh
Original Assignee
Lowrie Mcintosh
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 Lowrie Mcintosh filed Critical Lowrie Mcintosh
Priority to AU44955/97A priority Critical patent/AU4495597A/en
Publication of WO1998012616A2 publication Critical patent/WO1998012616A2/en
Publication of WO1998012616A3 publication Critical patent/WO1998012616A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/93Document management systems
    • YGENERAL 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
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99953Recoverability

Definitions

  • 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.
  • a document management system typically requires that a significant amount of detail be stored with the document.
  • the present invention provides a reliable mechanism to accomplish this task.
  • the "type” of document 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.
  • 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.
  • 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.
  • 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 Figure 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 Figure 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, 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.
  • diskette location i.e., computer
  • network drive location i.e., server
  • Figure 1 is a screen display showing a query screen for performing a search.
  • Figure 2 is a screen display showing a list of synonyms.
  • Figure 3 is a screen display showing a query screen for performing a search.
  • Figure 4 is a screen display showing the results of a query of the type shown in Figure 3.
  • Figure 5 is a screen display showing a query screen for performing a search.
  • Figure 6 is a screen display showing the results of a query of the type shown in Figure 5.
  • Figure 7 is a screen display showing the results of a query of the type shown in Figure 5.
  • Figure 8 is a block diagram showing a high level view of the functions performed by the invented system.
  • Figure 9 is a block diagram showing the store documents function.
  • Figure 10 is a block diagram showing the maintain inventory function.
  • Figure 11 is a block diagram showing the maintain system function.
  • Figure 12 shows the layout for the entity relationship diagram shown in Figures 12A-12F.
  • Figures 12A-12C show the first row of Figures forming the entity relationship diagram.
  • Figures 12D-12F show the second row of Figures forming the entity relationship diagram.
  • Figure 13 shows the layout for the logical database model shown in Figures 13A-13L.
  • Figures 13A-13D show the first row of Figures forming the logical database model.
  • Figures 13E-13H show the second row of Figures forming the logical database model.
  • Figures 131- 13L show the third row of Figures forming the logical database model.
  • Figure 14 shows the layout for the physical database model shown in Figures 14A-14L.
  • Figures 14A-14D show the first row of Figures forming the physical database model.
  • Figures 14E-14H show the second row of Figures forming the physical database model.
  • Figures 141- 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.
  • 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 Figure 9.
  • the synonym database contains all or a subset of terms in use by the 1 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 Figure 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. s
  • the system 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.
  • 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 vemacular, 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.
  • Hierarchical order i.e., primary class and sub-classes (i.e., secondary, tertiary, etc.).
  • Classify Documents Determine major classes, e.g.,: Accounting, Administration, Finance, Marketing, Corporate, Legal, Engineering, etc. Major classes should be by functional class, not organizational names.
  • class levels can be adjusted to fit local conditions.
  • 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.
  • the label search field is part of a query screen display, an example of which is shown in Figure 1.
  • the display would show the contents of the class table for the item located by the search as containing: "HRJD” or "Human Resources, Job Description” as shown in the screen display of Figure 4.
  • 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.
  • each row corresponds to a file series.
  • the column labeled "No.” contains a unique computer generated numbers used to represent each file series.
  • Class Acronym contains the classification acronyms.
  • 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 11 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 Using predetermined life-cycles (retention schedules) for each file series, the system identifies documents subject to purging.
  • 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 Electronic Records System
  • ERS is a client/server application to assist in the management of valuable corporate information.
  • • ERS provides a means to search for documents pertaining to a specific subject, date range, author, etc.
  • 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:
  • This policy includes what media to use for long term storage.
  • the Data Processing, Management Information Systems, or the Information Services organization plays a role in the management of documents. Their responsibilities are defined below:
  • 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.).
  • 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. 21
  • 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.
  • a user 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.
  • Inventory Maintenance The ability to correct mis-assigned classifications given to items in inventory. This function assists the user in properly assigning classifications to documents.
  • Inventory Entry 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.
  • Inventory Request 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.
  • Synonym Maintenance The ability to add, change, or delete user synonyms.
  • 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.
  • Inventory Retrieval 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 I presentations. Such items might be Write, text, or bit mapped files.
  • Inventory Detail Reports 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.
  • 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.
  • User Maintenance 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.
  • Inventory Maintenance 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.
  • a media request is a note to Information Services that items found on hard disk need to be moved to CD.
  • Inventory Detail Reports 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.
  • Inventory Count Reports 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 IS inventory and their age, (2) determine if classifications are being properly used, and (3) manage the retirement process.
  • 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.
  • Classification Audit Reports 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.
  • Inventory Requests Report 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. This report would help the Departmental Coordinator manage the logistics of moving records to and from a storage facility.
  • Static Table Listings 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.
  • 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.
  • This function is to describe the various ERS databases that may be at an organizations and their addresses.
  • Function Maintenance 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.
  • 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.
  • Function Usage Maintenance 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 Table Maintenance 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.
  • Class Availability Report 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.
  • Function Usage Reports 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.
  • 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.
  • ERS935 Record Type Maintenance.
  • 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:
  • 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: 2. ⁇
  • Custom Sub Heading 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.
  • 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.
  • Report Footing 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.
  • Print After View 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.
  • 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:
  • Add, Change, Delete 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.
  • Point and Shoot The user will not have to know key field values such as department numbers, building numbers, or document numbers.
  • 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.
  • displaying a list of existing records in a table the user can scroll through them and decide which one they would like to update.
  • Drop Down Lists The user will not have to memo ⁇ ze 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.
  • 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 desc ⁇ ptive 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 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.
  • Figure 8 shows the major activities associated with an application.
  • Figures 9 through 1 1 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.
  • Figure 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.
  • Entity Name Attribute Name Attribute Definition column name that will be used as part of a WHERE phrase to limit report retrieval.
  • DPT_NBR is the department number column name.
  • 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 is the SQL table or view name that will be used as part of a WHERE phrase to limit report retrieval.
  • DataWindow Name PowerBuilder DataWindow name PowerBuilder DataWindow name.
  • the DataWindow name is the name of the PowerBuilder DataWindow name that should be displayed when a particular sort is requested by the user.
  • Different DataWindows are used for different sorts because there may be different subtotaling on the same report depending upon how it is sorted.
  • 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 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'.
  • DISK hard disk
  • FLOPPY floppy disk
  • CD CD ROM
  • TAPE magnetic table
  • FICH microfich
  • PAPER hardcopy.
  • Record Type Code User assigned identification code.
  • Figure 13 is a logical view of the database. It shows all the entities or tables and their attributes or columns. The pu ⁇ ose 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.
  • class synonym table 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 :
  • Synonym name equals class code and user identification equals 'SA' or Synonym name equals classification title and user identification equal 'SA'
  • 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 ⁇ ' for yes for each function.
  • 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.
  • Insert Trigger - The object pu ⁇ ose can not be null if the object type code is 'V for view.
  • Insert Trigger - The object pu ⁇ ose 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.
  • 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.
  • 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.
  • 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 :
  • 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 ⁇ ' 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.
  • udt_ndt varchar(40) Names, descriptions and titles 40 chars or less.
  • udt_name char(20) First, Last Names, other names 20 chars or less.
  • udt_label char(25) Labels.
  • udt_identifier char(20) Any type of database object identifier.
  • udt_yesno char(l) Any yes/no column.
  • udt_code_a char(l) Codes and other data of various lengths.
  • 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 Figure 14.
  • the following table displays the SQL attributes (column name, datatype, null option, etc.) for each column being stored.
  • the pu ⁇ ose 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.
  • the client workstation is the personal computer run by the average user. Its pu ⁇ ose is to create word processing documents, spreadsheets, presentations, and to run the ERS application.
  • Processor 486/66 MHz processor or faster.
  • Memory 16 Meg. of memory or more.
  • Hard Disk 500 Meg. of available disk space or more.
  • 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. I
  • Memory 24 Meg. of memory or more.
  • CD ROM 4x speed or faster.
  • Tape Drive 250 Meg tape backup, or larger.
  • Monitor 17" VGA color monitor.
  • Network Card Must be compatible with available cabling, network software, and PC hardware.
  • 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.
  • Processor Two Pentium 100 MHz processors, or faster. Memory 64 Meg. of memory or more. Hard Disk 1 Gig. of available disk space or more.
  • CD ROM 4x speed or faster.
  • ERS The production implementation of ERS will require one server. ERS will have 1 ,200 total users in one geographic location. 300 of the users will be active at any one point in time ERS is planned to be a 500 Meg database containing 300,000 inventory items.
  • Ad hoc reporting tools will not have access the ERS database.
  • User passwords will be encrypted to prevent ad hoc tools from gaining access to the database.
  • ERS acts as the pointer to archive facilities. Some these documents will be stored in archive facilities such as off site warehouses or in Mezzanine.
  • ERS will provide a means to easily input hard copy documents, Microsoft Word documents, and Excel spreadsheets into a inventory and to classify these documents.
  • Classification The process of assigning a class to a document.
  • a class determines the record type, retention period, and sensitivity for the document.
  • Informational Record Type The majority of all records can be categorized as informational records. These records are not covered by law. They can be originals or copies.
  • Keyword A co ⁇ orate created synonym. A synonym not created by a typical user. They are created by the Records Manger. Keywords can be referred to as official terms.
  • Media The form a document or record in inventory takes. Media are hard copy, disk, tape, microfiche, etc.
  • Sensitivity Records have four categories of sensitivity. They range from confidential to secret. Synonym A classification code, a portion of a classification name, and commonly used phrase that means the same as the classification name. Synonyms fall into two categories; co ⁇ orate and user. Co ⁇ orate synonyms are recognized throughout the organization and can be referred to as keywords or official terms. User synonyms are phrases made up by individual users. User synonyms always children to corporate synonyms.
  • Four user groups are planned; normal user, Departmental Coordinators, Information Services, and Record Manager.
  • Vital Attribute Records whose loss would have a financial impact on the organization, Vital record is an attribute of class. It is not a record type.

Abstract

Uniform classification of a subject is accomplished by using generic terminology organized into a hierarchical structure. The system captures acronyms, vernacular and industry-specific, as well as foreign terms, into a thesaurus that can be modified and appended to as classification needs change. The system 'learns' as synonyms are added to 'family groups', capturing differences in individual perception. Searching for the location of an object is accomplished by entering a descriptive term. If the entry term does not find a match in the 'generic structure', the system will look for a matching synonym. By arranging the 'generic terms' in a classified format, a single location is provided for each record series and enables linking all relevant administrative document management functions and legal retention requirements.

Description

DEFINING A UNIFORM SUBJECT CLASSIFICATION SYSTEM
INCORPORATING DOCUMENT MANAGEMENT/RECORDS RETENTION FUNCTIONS
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.
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.
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.
The present invention provides a reliable mechanism to accomplish this task.
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.
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.
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. I
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.
Sensitive documents contain, for example:
1. Personnel information which provides confidential data.
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.
3. Marketing, product development or corporate changes that could sabotage effectiveness.
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.
Legislative terminology describes document retention requirements by subject. In this connection, two major issues exist:
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).
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. 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.
Accordingly, all documents must be identified by subject and ultimately destroyed consistently with the enterprise's official retention schedule.
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.
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 Figure 3. For example, entry of a descriptive term produces a particular subject classification (i.e., a class code as described below).
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 Figure 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. 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, 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.
Selective and timely purging of documents is thus made possible, greatly facilitating the management of information for both current and prospective use.
Brief Description of the Drawings
Figure 1 is a screen display showing a query screen for performing a search.
Figure 2 is a screen display showing a list of synonyms.
Figure 3 is a screen display showing a query screen for performing a search.
Figure 4 is a screen display showing the results of a query of the type shown in Figure 3.
Figure 5 is a screen display showing a query screen for performing a search.
Figure 6 is a screen display showing the results of a query of the type shown in Figure 5.
Figure 7 is a screen display showing the results of a query of the type shown in Figure 5.
Figure 8 is a block diagram showing a high level view of the functions performed by the invented system.
Figure 9 is a block diagram showing the store documents function.
Figure 10 is a block diagram showing the maintain inventory function.
Figure 11 is a block diagram showing the maintain system function.
Figure 12 shows the layout for the entity relationship diagram shown in Figures 12A-12F.
Figures 12A-12C show the first row of Figures forming the entity relationship diagram.
Figures 12D-12F show the second row of Figures forming the entity relationship diagram.
Figure 13 shows the layout for the logical database model shown in Figures 13A-13L.
Figures 13A-13D show the first row of Figures forming the logical database model.
Figures 13E-13H show the second row of Figures forming the logical database model. Figures 131- 13L show the third row of Figures forming the logical database model.
Figure 14 shows the layout for the physical database model shown in Figures 14A-14L.
Figures 14A-14D show the first row of Figures forming the physical database model.
Figures 14E-14H show the second row of Figures forming the physical database model.
Figures 141- 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.
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.
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.
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.
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.
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.
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.
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 Figure 9. The synonym database contains all or a subset of terms in use by the 1 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 Figure 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.
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.
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 vemacular. Changes to the hierarchy are rare, leaving its structure stable. Almost all changes can be easily accomplished through changes in synonyms.
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.
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. s
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.
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.
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 vemacular, abbreviations and foreign terms that reveal the user's perception of the subject being sought.
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.
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.
Using The Uniform Subject Classification System
I. Build A Classification Structure:
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.).
II. Apply Synonyms To The Classification Structure
Assemble synonyms into a thesaurus and connect the synonyms with a particular file series (i.e., a line in the class hierarchy).
Build a database of local vernacular, acronyms, technical terms, etc.
Organize the database into the classification structure built in step 1, appending to the synonym database, as appropriate.
Modify major classes, primary classes, secondary classes, etc. as required to fit the working environment.
III. Classify Documents Determine major classes, e.g.,: Accounting, Administration, Finance, Marketing, Corporate, Legal, Engineering, etc. Major classes should be by functional class, not organizational names.
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:
AC Accounting (MAJOR)
PA Payables (PRIMARY)
EM Employee (SECONDARY)
which results in the Uniform Subject Classification Code:
ACPAEM ACCOUNTING, PAYABLES, EMPLOYEE
Depending on need, class levels can be adjusted to fit local conditions. 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:
ADFAOF Administration, Facilities, Offices
ADFAOFFU Administration, Facilities, Offices, Furnishings
ADFUDE Administration, Furnishings, Desk
ADFUAR Administration, Furnishings, Art
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. V. 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.
IY: Finding Documents using the Uniform Subject Classification System
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.
To determine what may be available to aid in the creation of a new job description, enter 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 Figure 1.
A typical response to the query provides the acronym of "HRJD", or "Human Resources, Job Descriptions" as shown in the screen display of Figure 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 Figure 4 and "HRJDMA" for job description of a Marketing Analyst also shown in the screen display of Figure 4.
Next, search for job descriptions that are involved with the budgeting process to identify the terms used in describing the tasks and skills required: Enter the word "budget" as shown in the screen display of Figure 5. With full security clearance, the system would return: "FIBU" or Finance, Budgets, as shown in the screen display of Figure 6.
From the synonym table, the display would show the contents of the class table for the item located by the search as containing: "HRJD" or "Human Resources, Job Description" as shown in the screen display of Figure 4.
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 Figure 7. 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.
V . Associate The Class Acronym With Retention Data
Once steps I-UI 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.
Figure imgf000013_0001
In Table I, each row corresponds to a file series.
The column labeled "No." contains a unique computer generated numbers used to represent each file series.
The column labeled " Class Acronym " contains the classification acronyms.
The column labeled "Class Code Name" contains the official terms to describe documents.
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 11 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.
The column labeled "Off Ret" represents office retention in months.
The column labeled "RC Ret" represents records center retention in months.
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.
M
Figure imgf000015_0001
Figure imgf000016_0001
vs
ADPS PRESENTATION MATERIAL
ADPU PURCHASING
ADPUDS DISTRIBUTION
ADRE RECORDS MANAGEMENT
ADRERQ REQUESTS
ADRERS RETENTION SCHEDULE
ADRERV VITAL RECORDS
ADRG REPROGRAPHICS
ADΞH SHIPPING
ADSHBL BILLS OF LADING
ADSU SUPPLIES
ADTR TRAVEL INFORMATION
CO CORPORATE
COAC ACQUISITIONS
COAU AUDITS
COBD BONDS
COBO BOARD OF DIRECTORS
COBOCM COMMITTEES
COBOCO COMPENSATION
COBOME MEETINGS/MINUTES
COBY BY-LAWS
COCH CHARTER
COCT CONTRIBUTIONS
COCTMCH MEETINGS/MINUTES
CODB DOING BUSINESS AS
COER ELECTION RECORDS
COHI HISTORY
COIN ARTICLES OF INCORPORATION
COME MERGERS
COSE SEALS
COSH SHAREHOLDERS
COSHME MEETINGS
COSHNO NOTES
COSHPR PROXIES
COST STOCK
COΞTDI DIVIDENDS
COSTSB SUBSCRIBERS
COSTSU SUBSCRIPTIONS
EN ENGINEERING
ENBP BLUEPRINTS
ENDA DATA BOOKS
ENDE DESIGNS
ENDR DRAWINGS
ENFO FORMULAS, TECHNICAL
ENIE INDUSTRIAL ENGINEERING
ENIEME METHODS IMPROVEMENTS
ENMA MAPS
ENPR PROJECTS
ENSC SPECIFICATIONS
ENST STANDARDS
ENTS TESTING
FI FINANCE
FIAN ANALYSIS/STUDIES
FIBU BUDGETS
FIBUAZ AUTHORIZATIONS
FIBUES ESTIMATES
FIBUPE PERFORMANCE ANALYSIS
FIBUPL PLANNING
FIBURD RESEARCH & DEVELOPMENT
FICA CAPITAL PLAN
FICAEX EXPENDITURES
FIEC ECONOMIC ANALYSIS
FIFI FINANCIAL REPORTS
HR HUMAN RESOURCES
HRAF AFFIRMATIVE ACTION .52,
HRBE BENEFITS
HRBEBP BONUS PLAN
HRBEIN INSURANCE
HRBEINAU AUTHORIZATIONS
HRBEINCC COMPANY VEHICLES
HRBEINCL CLAIMS
HRBEINDE DENTAL
HFBEINDI DISABILITY
HRBEINLI LIFE
HRBEINME MEDICAL
HRBEINPL PLAN
HRBEINUN UNEMPLOYMENT
HRBEINWC CA WORKERS' COMPENSATION
Figure imgf000017_0001
COMPENSATION
Figure imgf000018_0001
11
Figure imgf000019_0001
OPERATIONS
Figure imgf000019_0002
Figure imgf000019_0003
U
Figure imgf000020_0001
Table D
VI. Purge Documents Selectively And Within Legal And Administratively Defined Requirements
Using predetermined life-cycles (retention schedules) for each file series, the system identifies documents subject to purging.
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.
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.
The above described system may be implemented entirely in software as described below.
Design Details
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.
Overview
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. λo
Definition of User Community
The ERS application has four categories of user. Each group of users and their responsibilities are described below.
Records Manager
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:
Sets policy for record storage. This policy includes what media to use for long term storage.
Creates new classes and maintains the retention schedule.
Monitors the performance of the entire application.
Re-classifies documents that have been mis-classified.
Information Services
The Data Processing, Management Information Systems, or the Information Services organization plays a role in the management of documents. Their responsibilities are defined below:
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.
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.).
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.
Department Coordinator
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:
Provide training and technical support to users within the department.
Monitors the performance of the system regarding departmental records.
Creates and sets up new users.
Enforces record retention policy for official records created by the department.
Manages the logistics of moving records to and from a storage facility. Z\ User
The majority of individuals accessing the system will be categorized as users. Their responsibilities are listed below:
Properly classifies records they create.
Enforces record retention policy for informational records created by them.
Policies
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.
Users and Class Assignments
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.
No Class Attribute Overrides
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.
Classification Owner
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.
Location and Class Assignment
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.
One Production Database Per User
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. 21
System Functions
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.
User Functions
All individuals who have access to the system will be able to operate the functions defined as follows:
Application Package File Open Function
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.
Search and Retrieve Feature
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).
Application Package File Save Function
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.
Document Storage Feature
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.
Classification Assignment Feature
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.
Synonym Maintenance Feature 21
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.
Attribute Maintenance Feature
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.
Stand Alone ERS User Functions
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.
Update Functions
Inventory Maintenance The ability to correct mis-assigned classifications given to items in inventory. This function assists the user in properly assigning classifications to documents.
Inventory Entry 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.
Inventory Request 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.
Synonym Maintenance The ability to add, change, or delete user synonyms.
User Profile Maintenance 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.
Inquiry Functions
Inventory Retrieval 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 I presentations. Such items might be Write, text, or bit mapped files.
Reporting Functions
Inventory Detail Reports 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.
Synonym Reports 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.
Department Coordinator Functions
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.
Update Functions
User Maintenance 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.
Inventory Maintenance 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.
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.
Reporting Functions
Inventory Detail Reports 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.
Inventory Count Reports 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 IS inventory and their age, (2) determine if classifications are being properly used, and (3) manage the retirement process.
Center Retention Required 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. 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.
Classification Audit Reports 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.
Inventory Requests Report 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. This report would help the Departmental Coordinator manage the logistics of moving records to and from a storage facility.
Static Table Listings 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.
Information Services Functions
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.
Update Functions
There are several update functions that only Information Services personnel would use. These functions are described below.
Database Definition The purpose of this function is to describe the various ERS databases that may be at an organizations and their addresses. Function Maintenance 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.
Batch Functions
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.
Function Usage Maintenance 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.
Security Grants 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
Records Manager Functions
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.
Update Functions
Class Maintenance Add, change, or delete information about classifications, abstracts, and retention schedules. Synonym Maintenance Add, change, and delete synonyms used corporate wide. These synonyms are also referred to as keywords and official terms.
Static Table Maintenance 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. ZT
Reporting Functions
Class Availability Report 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.
Function Usage Reports 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.
Data Dictionary Reports 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.
Catalog of Functions
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.
2i
Figure imgf000030_0001
X°\
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
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.
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.
Menu Functions
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:
Function Access 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:
File
New
Open
Delete
Close
Print
Printer Setup
Exit
Edit
Undo
Cut
Copy
Paste
Clear
Find
Go To
Search
Sort
Filter
View
First Page Prior Page Next Page Last Page Toolbars Date and Time Maintenance
Update 1 Update 2 Etc. Λ1
Reports
Report 1
Report 2
Etc. Window
Tile
Layered
Cascade
Arrange Icons
Window 1
Window 2
Etc.
Help
Contents
Search for Help on How to Use Help About ERS
Micro Help 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.
Button Bar 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.
Disabled Functions 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.
User Access 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.
Reporting Functions
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: 2.Ϊ
Custom Sub Heading 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.
Selection Criteria 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.
Variable Sorting 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.
Routing of Output 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.
Report Footing 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.
Print After View 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.
Micro Help Every object of the window used to specify report subheadings, 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.
Usage Tracking 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
Update functions provide the ability to add, change, or delete records in the database. The features of update functions are the following:
Add, Change, Delete 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.
Point and Shoot 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.
Drop Down Lists The user will not have to memoπze 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.
Drag and Drop 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.
Jumping 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 descπptive 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
Validation 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.
Referential Integπty 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.
Confirmation 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.
Micro Help 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.
Usage Tracking 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.
Process Model
The purpose of a business process model is to show the relationship between people, systems, data, office policy and procedures, and documents.
Node Tree Diagrams
A component of a business process model is a node tree diagram. Figure 8 shows the major activities associated with an application. Figures 9 through 1 1 show the node tree diagrams for ERS.
Database Design
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 Definitions
The nature of each table in the database is described in the following entity definitions.
Figure imgf000036_0001
Figure imgf000037_0001
3<b
Figure imgf000038_0001
il
Figure imgf000039_0001
Entity Relationship Diagram
Figure 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.
Attribute Definitions
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.
Figure imgf000039_0002
2tø
Figure imgf000040_0001
^
Figure imgf000041_0001
Figure imgf000041_0002
o
Figure imgf000042_0001
\
Figure imgf000043_0001
ML
Figure imgf000044_0001
Figure imgf000044_0002
Figure imgf000045_0001
Figure imgf000046_0001
Entity Name Attribute Name Attribute Definition 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 of a 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. HS c
Figure imgf000047_0001
%
DataWindow Name PowerBuilder DataWindow name. The DataWindow name is the name of the PowerBuilder DataWindow name that should be displayed when a particular sort is requested by the user. Different DataWindows 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
Entity Name Attribute Name Attribute Definitions 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 Procedure Required stored procedure name. The puφose 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 H"?
Figure imgf000049_0001
-
Figure imgf000050_0001
^
Figure imgf000051_0001
Figure imgf000051_0002
so
Figure imgf000052_0001
Entiittyv Name Attribute Name Attribute Definition 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.
Figure imgf000053_0001
I
Figure imgf000054_0001
Figure imgf000054_0002
51
Figure imgf000055_0001
Figure imgf000055_0002
5H
Figure imgf000056_0001
s.~
Figure imgf000057_0001
£6
Figure imgf000058_0001
Figure imgf000058_0002
_r,
Figure imgf000059_0001
s
Figure imgf000060_0001
Figure imgf000061_0001
Figure imgf000062_0001
u
Figure imgf000063_0001
Logical View
Figure 13 is a logical view of the database. It shows all the entities or tables and their attributes or columns. The puφose of this diagram is to provide a more detailed picture of the database and its contents.
Standard Abbreviations
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 '1st nme'.
Figure imgf000063_0002
usg usage usp user stored procedure usr user vtl vital vw view vwb base view w window wrd word
Triggers
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.
Class Table
Insert Trigger - Two rows should be added to the synonym table. The values for the synonym table are as follows :
Row 1
Synonym Name The class code
User Identification 'SA'
Parent Synonym Name The class code of the parent classification
Keyword Flag 'Y' Row 2
Synonym Name The classification title
U ser Identification ' S A '
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 :
Row 1
Synonym Name The class code
User Identification ' S A '
Class Identification The class identification
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.
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. 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.
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'
Function Table
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.
Function Column Table
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'.
Function Sort Table
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 Υ' for yes for each function.
Function Usage Table
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. Location Table
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.
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.
Object Table
Insert Trigger - The object puφose can not be null if the object type code is 'V for view.
Insert Trigger - The object puφose can not be null if the object type code is 'V for view.
Object Identification Table
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.
Organization 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.
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.
User Table
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 :
Retrieve the user ID of the individual inserting a new row into the user table.
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.
Insert the classifications and access codes found in the previous step under the ID of the new user. Ignore the processing describe above if the user doing the inserting is SA.
Delete Trigger - Create a cascading delete that will remove the user for all other tables.
User Class Table
Insert Table - There can only be one row having a default class flag value of 'Y' for yes for each user.
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.
Update Table - There can only be one row having a default class flag value of Υ' for yes for each user.
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.
User Database Table
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.
User Defined Datatypes
User defined datatypes are common formats that will be applied to columns. The attributes for each datatype in this system are listed below. udt_integer integer System generated identification numbers.
udt_ndt varchar(40) Names, descriptions and titles 40 chars or less. udt_name char(20) First, Last Names, other names 20 chars or less. udt_label char(25) Labels. udt_text varchar(255) Long descriptions, text, explanations, summaries etc. udt_identifier char(20) Any type of database object identifier. udt_yesno char(l) Any yes/no column. udt_phone char(13) Full length phone number - Do not store dashes. udt_code_a char(l) Codes and other data of various lengths. udt_code_b char(2) udt_code_c char(6) udt_code_d char(8) udt_code_e char(lθ) udt_code_f char(12) udt_code_g char(15)
Physical Database Model
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 Figure 14.
Physical Attributes
The following table displays the SQL attributes (column name, datatype, null option, etc.) for each column being stored.
Figure imgf000069_0001
l*
Figure imgf000070_0001
^
Figure imgf000071_0001
Figure imgf000072_0001
1
Figure imgf000073_0001
71
Figure imgf000074_0001
Ii
Figure imgf000075_0001
1-i
Figure imgf000076_0001
System Requirements
The puφose 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.
Client Workstation
The client workstation is the personal computer run by the average user. Its puφose is to create word processing documents, spreadsheets, presentations, and to run the ERS application.
Hardware
Processor 486/66 MHz processor, or faster. Memory 16 Meg. of memory or more. Hard Disk 500 Meg. of available disk space or more.
Access to a common network drive containing the application software.
Monitor VGA color monitor. Printer Access to a LASER printer, 300 dpi resolution or higher. Network Card Must be compatible with available cabling, network software, and PC hardware.
Keyboard Mouse
Software
Operating System Microsoft DOS, release 6.22.
Microsoft Windows for Workgroups, release 3.11.
Network Software such as Novell or Windows for
Workgroups. Application Packages Microsoft Office containing Word, Excel, and
PowerPoint.
Developer Workstation
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. I
Hardware
Processor Pentium 100 MHz processor, or faster. Memory 24 Meg. of memory or more. Hard Disk 1 Gig. of available disk space or more.
Access to a common network drive containing the application software.
CD ROM 4x speed, or faster. Tape Drive 250 Meg tape backup, or larger. Monitor 17" VGA color monitor. Printer Access to a laser printer, 300 dpi resolution or higher. Network Card Must be compatible with available cabling, network software, and PC hardware.
Modem 28.8 FAX/Modem, or faster.
Keyboard
Mouse
Software
Operating System Microsoft DOS, release 6.22.
Microsoft Windows for Workgroups, release 3.11.
Network Software such as Novell or Windows for
Workgroups. Application Packages Microsoft Office containing Word, Excel, and
PowerPoint.
Microsoft Project, release 4.0. Development Tools PowerSoft PowerBuilder, release 4.0.4.
MetaSolv PowerFrame, release 4.0.
Norton Desktop for Windows, release 3.0.
Logic Works ERWin for PowerBuilder, release 2.5.
Embarcadero Technologies DBArtisan, release 2.02.
Embarcadero Technologies Rapid SQL, release 1.02.
Blue Sky Software RoboHelp, release 3.0.
PC Install for Windows 3.X.
Saros Mezzanine Developers Tool Kit.
Saros Document Manager.
Server
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.
Hardware
Processor Two Pentium 100 MHz processors, or faster. Memory 64 Meg. of memory or more. Hard Disk 1 Gig. of available disk space or more.
Access to a common network drive containing the application software.
CD ROM 4x speed, or faster.
Tape Drive 250 Meg tape backup, or larger.
Monitor VGA color monitor.
Printer Access to a LASER printer, 300 dpi resolution or higher. It- Network Card Must be compatible with available cabling, network software, and PC hardware. Modem Two 28.8 FAX Modems, or faster.
Keyboard Mouse
Software
Operating System Microsoft Windows NT, release 3.5. Database Server Microsoft SQLServer, release 4.2 or higher.
Document Server Saros Mezzanine Document Server.
The production implementation of ERS will require one server. ERS will have 1 ,200 total users in one geographic location. 300 of the users will be active at any one point in time ERS is planned to be a 500 Meg database containing 300,000 inventory items.
Clarifications
The puφose of this section of the design document is to clearly state limitations of the system. The items listed below are not planned to be implemented in ERS at the present time. However, there is nothing preventing these functions or capabilities from being added to the application at a later date.
Ad Hoc Reporting
• The menus within the ERS application will not provide access to any ad hoc reporting tools such as InfoMaker by PowerSoft or Microsoft Access.
• Ad hoc reporting tools will not have access the ERS database. User passwords will be encrypted to prevent ad hoc tools from gaining access to the database.
• ERS could be modified to bring up an ad hoc reporting tool from its menu some time in the future, if desired.
Multiple Databases
• ERS will use only one database.
• Only one database is needed. Based upon the size to the database (500 Megs.), the quantity of users(300 active users), and the location of the users (one building) can be supported on one server. For this reason, multiple databases will not be provided, nor will any across database functions be built.
• As the application grows in quantity of users or locations, additional databases can be considered at a later date.
Archive Facility Management
• ERS will track what documents are available and where.
• ERS acts as the pointer to archive facilities. Some these documents will be stored in archive facilities such as off site warehouses or in Mezzanine.
• ERS will not manage the operation of these archive facilities. It will not perform document check in and check out functions, or deliver the document to the user's workstation, for example. These functions will be the responsibility of the archive facility. 17
• In this fashion there will be a division of labor. ERS can do what it is designed to best and the archive facilities can continue to perform what they do best.
Total Control Over AH Corporate Information
• ERS will not provide a fully automated means to enroll all of a coφoration's information into a records management database. All information implies every eMail message, all application database transactions, telephone conversation, as well as electronic and hard copy documents.
• ERS will not provide an interface into off site storage facility's information system. If the volume of information flowing between an office and a off site storage facility warrants it, an interface could be added later.
• ERS will not provide an interface into eMail systems. The policies on the control and management of eMail messages needs to be established, first, before an interface can be considered.
• ERS will provide a means to easily input hard copy documents, Microsoft Word documents, and Excel spreadsheets into a inventory and to classify these documents.
Glossary Archive Facility Off site storage of an inventory item or the storage of an item online in Mezzanine.
Classification The process of assigning a class to a document. A class determines the record type, retention period, and sensitivity for the document.
ERS Electronic Records System.
Functions The capabilities of a system are functions. Functions fall into five types. They are reports, updates, inquires, interfaces, and utilities. System functions are composed of features.
Informational Record Type The majority of all records can be categorized as informational records. These records are not covered by law. They can be originals or copies.
Inventory A document or set of records stored for historical or legal purposes. Keyword A coφorate created synonym. A synonym not created by a typical user. They are created by the Records Manger. Keywords can be referred to as official terms.
Media The form a document or record in inventory takes. Media are hard copy, disk, tape, microfiche, etc.
Official Record Type A small quantity of the total records can be categorized as official records. These records are always originals and never copies. Official records are covered by law. 7S
Contracts would be an example of official records or documents.
Official Term A keyword or coφorate created synonym. Organization A company, department, or cost center. Record Type Records have two types; official and informational. Retention Period The quantity of months a document is stored for historical or legal puφoses. The retention period is determined by the class assigned to a document.
Retirement The process of destroying a document that has been stored in inventory past its retention period. Sensitivity Records have four categories of sensitivity. They range from confidential to secret. Synonym A classification code, a portion of a classification name, and commonly used phrase that means the same as the classification name. Synonyms fall into two categories; coφorate and user. Coφorate synonyms are recognized throughout the organization and can be referred to as keywords or official terms. User synonyms are phrases made up by individual users. User synonyms always children to corporate synonyms.
User Someone who can access the system. User Group A category or set of users all having the same security access to system functions and tables. Four user groups are planned; normal user, Departmental Coordinators, Information Services, and Record Manager.
Vital Attribute Records whose loss would have a financial impact on the organization, Vital record is an attribute of class. It is not a record type.

Claims

Claims
I Claim:
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.
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.
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.
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.
PCT/US1997/017004 1996-09-23 1997-09-22 Defining a uniform subject classification system incorporating document management/records retention functions WO1998012616A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU44955/97A AU4495597A (en) 1996-09-23 1997-09-22 Defining a uniform subject classification system incorporating document management/records retention functions

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US71789796A 1996-09-23 1996-09-23
US08/717,897 1996-09-23

Publications (2)

Publication Number Publication Date
WO1998012616A2 true WO1998012616A2 (en) 1998-03-26
WO1998012616A3 WO1998012616A3 (en) 1998-07-16

Family

ID=24883934

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/017004 WO1998012616A2 (en) 1996-09-23 1997-09-22 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 (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1213665A2 (en) * 2000-12-07 2002-06-12 Patentmall Limited Patent classification displaying method and apparatus
US7933786B2 (en) 2005-11-01 2011-04-26 Accenture Global Services Limited Collaborative intelligent task processor for insurance claims
US7979382B2 (en) 1999-05-04 2011-07-12 Accenture Global Services Limited Component based information linking during claim processing
US8126742B2 (en) 2003-05-09 2012-02-28 Accenture Global Services Limited Automated assignment of insurable events
US8140468B2 (en) 2006-06-22 2012-03-20 International Business Machines Corporation Systems and methods to extract data automatically from a composite electronic document
US8453050B2 (en) 2006-06-28 2013-05-28 International Business Machines Corporation Method and apparatus for creating and editing electronic documents
US8478769B2 (en) 2008-02-22 2013-07-02 Accenture Global Services Limited Conversational question generation system adapted for an insurance claim processing system
US8515786B2 (en) 2008-02-22 2013-08-20 Accenture Global Services Gmbh Rule generation system adapted for an insurance claim processing system
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
US9984415B2 (en) 2009-09-24 2018-05-29 Guidewire Software, Inc. Method and apparatus for pricing insurance policies

Families Citing this family (230)

* 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
US7325052B1 (en) * 1998-10-06 2008-01-29 Ricoh Company, Ltd. Method and system to erase data after expiration or other condition
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
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
US6647394B1 (en) * 1999-06-08 2003-11-11 International Business Machines Corporation Doing business employing linked trees having retrievable embedded information
US7277931B1 (en) 1999-06-08 2007-10-02 International Business Machines Corporation Representing, configuring, administering, monitoring, and/or modeling connections using catalogs and matrixes
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
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
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
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
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
US7421645B2 (en) * 2000-06-06 2008-09-02 Microsoft Corporation Method and system for providing electronic commerce 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
EP1182577A1 (en) * 2000-08-18 2002-02-27 SER Systeme AG Produkte und Anwendungen der Datenverarbeitung Associative memory
US9177828B2 (en) 2011-02-10 2015-11-03 Micron Technology, Inc. External gettering method and device
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
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
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
JP3701197B2 (en) * 2000-12-28 2005-09-28 松下電器産業株式会社 Method and apparatus for creating criteria for calculating degree of attribution to classification
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
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
US7139977B1 (en) * 2001-01-24 2006-11-21 Oracle International Corporation System and method for producing a virtual online book
US8484177B2 (en) * 2001-03-21 2013-07-09 Eugene M. Lee Apparatus for and method of searching and organizing intellectual property information utilizing a field-of-search
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
US7260771B2 (en) * 2001-04-26 2007-08-21 Fuji Xerox Co., Ltd. Internet-based system for multimedia meeting minutes
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
ES2375403T3 (en) 2001-08-27 2012-02-29 BDGB Enterprise Software Sàrl A METHOD FOR THE AUTOMATIC INDEXATION OF 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
US6636857B2 (en) 2001-12-18 2003-10-21 Bluecurrent, Inc. Method and system for web-based asset 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
US7707024B2 (en) * 2002-05-23 2010-04-27 Microsoft Corporation Method, system, and apparatus for converting currency values 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
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
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
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
US7392479B2 (en) 2002-06-27 2008-06-24 Microsoft Corporation System and method for providing namespace related information
US20040001099A1 (en) * 2002-06-27 2004-01-01 Microsoft Corporation Method and system for associating actions with semantic labels in electronic documents
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
US7430513B2 (en) 2002-12-17 2008-09-30 Baydel North America, Inc. Data storage management driven by business objectives
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
GB0304782D0 (en) * 2003-03-03 2003-04-09 Percy Richard System and method using alphanumeric codes for the identification, description, classification and encoding of information
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
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
US20050027566A1 (en) * 2003-07-09 2005-02-03 Haskell Robert Emmons Terminology management system
US7069278B2 (en) * 2003-08-08 2006-06-27 Jpmorgan Chase Bank, N.A. 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
US7117322B2 (en) * 2003-09-08 2006-10-03 International Business Machines Corporation Method, system, and program for retention management and protection of stored objects
US7146388B2 (en) 2003-10-07 2006-12-05 International Business Machines Corporation Method, system, and program for archiving files
TW200512602A (en) * 2003-09-19 2005-04-01 Hon Hai Prec Ind Co Ltd Method and system of fuzzy searching
TWI290687B (en) * 2003-09-19 2007-12-01 Hon Hai Prec Ind Co Ltd System and method for search information based on classifications of synonymous words
US8515923B2 (en) * 2003-11-17 2013-08-20 Xerox Corporation Organizational usage document management system
US7404195B1 (en) 2003-12-09 2008-07-22 Microsoft Corporation Programmable object model for extensible markup language markup in an application
US7178102B1 (en) 2003-12-09 2007-02-13 Microsoft Corporation Representing latent data in an extensible markup language document
US7487515B1 (en) 2003-12-09 2009-02-03 Microsoft Corporation Programmable object model for extensible markup language schema validation
US7434157B2 (en) 2003-12-09 2008-10-07 Microsoft Corporation Programmable object model for namespace or schema library support in a software application
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
JP4372668B2 (en) * 2004-11-24 2009-11-25 シャープ株式会社 Copy apparatus, copy system, copy management system, copy control method, program, and recording medium recording the program
US20060156381A1 (en) * 2005-01-12 2006-07-13 Tetsuro Motoyama Approach for deleting electronic documents on network devices using document retention policies
WO2006081472A2 (en) * 2005-01-28 2006-08-03 Thomson Global Resources Systems, methods, and software for integration of case law, legal briefs, and/or litigation documents into law firm workflow
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
US7548917B2 (en) * 2005-05-06 2009-06-16 Nelson Information Systems, Inc. Database and index organization for enhanced document retrieval
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
US7992085B2 (en) 2005-09-26 2011-08-02 Microsoft Corporation Lightweight reference user interface
US7788590B2 (en) * 2005-09-26 2010-08-31 Microsoft Corporation Lightweight reference user interface
US20070083554A1 (en) * 2005-10-12 2007-04-12 International Business Machines Corporation Visual role definition for identity management
US20070219987A1 (en) * 2005-10-14 2007-09-20 Leviathan Entertainment, Llc Self Teaching Thesaurus
WO2007050646A2 (en) * 2005-10-24 2007-05-03 Capsilon Fsg, Inc. A 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
JP4315161B2 (en) * 2006-02-16 2009-08-19 村田機械株式会社 Image reader with time authentication request function
US8577852B2 (en) * 2006-03-23 2013-11-05 Infaxiom Group, Llc 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
US8200690B2 (en) * 2006-08-16 2012-06-12 International Business Machines Corporation System and method for leveraging historical data to determine affected entities
US20110173033A1 (en) * 2006-08-16 2011-07-14 Pss Systems, Inc. Systems and methods for utilizing an enterprise map 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
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
JP4089742B2 (en) * 2006-10-13 2008-05-28 富士ゼロックス株式会社 Document management system and document disposal apparatus
US7657513B2 (en) * 2006-12-01 2010-02-02 Microsoft Corporation Adaptive help system and user interface
JP5044236B2 (en) * 2007-01-12 2012-10-10 富士フイルム株式会社 Content search device and content search method
JP2008186176A (en) * 2007-01-29 2008-08-14 Canon Inc Image processing apparatus, document merging method and control program
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
US20090020604A1 (en) * 2007-07-17 2009-01-22 Moody Ernest W Method for information archival and retrieval
US20090132262A1 (en) * 2007-09-14 2009-05-21 Pss Systems Proactively determining evidence issues on legal matters involving employee status changes
EP2045959B1 (en) * 2007-10-03 2011-07-20 Accenture Global Services Limited Technology agnostic universally appliable data model for a telecommunication service provider archtitecture
US20090164418A1 (en) * 2007-12-19 2009-06-25 Valentina Pulnikova Retrieval system and method of searching information in the Internet
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
US8112406B2 (en) * 2007-12-21 2012-02-07 International Business Machines Corporation Method and apparatus for 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
US10304095B2 (en) * 2008-02-04 2019-05-28 Thomson Reuters Global Resources Unlimited Company System and method for accounting gateway
CA2718002C (en) * 2008-03-10 2016-07-19 Ubs Ag Methods and systems for group data management and classification
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
US8275830B2 (en) 2009-01-28 2012-09-25 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8346225B2 (en) 2009-01-28 2013-01-01 Headwater Partners I, Llc Quality of service for device assisted services
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
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
US8391834B2 (en) 2009-01-28 2013-03-05 Headwater Partners I Llc Security techniques for device assisted services
US8406748B2 (en) 2009-01-28 2013-03-26 Headwater Partners I Llc Adaptive ambient services
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US8331901B2 (en) 2009-01-28 2012-12-11 Headwater Partners I, Llc Device assisted ambient services
US8402111B2 (en) 2009-01-28 2013-03-19 Headwater Partners I, Llc Device assisted services install
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8365241B1 (en) * 2008-06-09 2013-01-29 Symantec Corporation Method and apparatus for archiving web content based on a policy
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
US9830563B2 (en) * 2008-06-27 2017-11-28 International Business Machines Corporation System and method for managing legal obligations for data
US8073729B2 (en) * 2008-09-30 2011-12-06 International Business Machines Corporation Forecasting discovery costs based on interpolation of historic event patterns
US8515924B2 (en) * 2008-06-30 2013-08-20 International Business Machines Corporation Method and apparatus for handling edge-cases of event-driven disposition
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
US8489439B2 (en) * 2008-06-30 2013-07-16 International Business Machines Corporation Forecasting discovery costs based on complex and incomplete facts
US20100017239A1 (en) * 2008-06-30 2010-01-21 Eric Saltzman Forecasting Discovery Costs Using Historic Data
US8327384B2 (en) * 2008-06-30 2012-12-04 International Business Machines Corporation Event driven disposition
US8484069B2 (en) 2008-06-30 2013-07-09 International Business Machines Corporation Forecasting discovery costs based on complex and incomplete facts
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
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
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
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
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
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
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
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
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
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
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
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
US10715342B2 (en) 2009-01-28 2020-07-14 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
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10841839B2 (en) 2009-01-28 2020-11-17 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
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
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
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
US9152883B2 (en) * 2009-11-02 2015-10-06 Harry Urbschat System and method for increasing the accuracy of optical character recognition (OCR)
GB0920339D0 (en) * 2009-11-20 2010-01-06 Vodafone Plc Archiving method and apparatus
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
US8655856B2 (en) * 2009-12-22 2014-02-18 International Business Machines Corporation Method and apparatus for policy distribution
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
US8832148B2 (en) 2010-06-29 2014-09-09 International Business Machines Corporation Enterprise evidence repository
US8566903B2 (en) 2010-06-29 2013-10-22 International Business Machines Corporation Enterprise evidence repository providing access control to collected artifacts
US8402359B1 (en) 2010-06-30 2013-03-19 International Business Machines Corporation Method and apparatus for managing recent activity navigation in web applications
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
JP5929369B2 (en) * 2012-03-16 2016-06-01 日本電気株式会社 Information processing apparatus including electronic document database, illegally stored document detection method, and program
US9858624B2 (en) * 2012-10-04 2018-01-02 Qvinci Software, Llc Methods and apparatus for providing data normalization, scalability and maintainability
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
US9058606B1 (en) 2013-11-18 2015-06-16 Access Sciences Corporation Computer implemented method for forming an accelerated compliance plan with a graphic visualization
US9053484B1 (en) 2013-11-18 2015-06-09 Access Sciences Corporation Computer implemented system for forming an accelerated compliance plan with a graphic visualization
US20150178372A1 (en) * 2013-12-19 2015-06-25 OpenGov, Inc. Creating an ontology across multiple semantically-related data sets
US10783495B1 (en) 2014-04-30 2020-09-22 Information Exchange Holdings Inc. Document management for ingredient suppliers
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
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
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

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
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
US5204812A (en) * 1989-11-02 1993-04-20 International Business Machines Corp. User access of multiple documents based on document relationship classification
US5369763A (en) * 1989-02-01 1994-11-29 Kansas State University Research Foundation Data storage and retrieval system with improved data base structure
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
US5630125A (en) * 1994-05-23 1997-05-13 Zellweger; Paul Method and apparatus for information management using an open hierarchical data structure
US5634130A (en) * 1993-09-20 1997-05-27 International Business Machines Corporation Method and apparatus for spurious interrupt detection in a data processing system
US5655130A (en) * 1994-10-14 1997-08-05 Unisys Corporation Method and apparatus for document production using a common document database
US5689699A (en) * 1992-12-23 1997-11-18 International Business Machines Corporation Dynamic verification of authorization in retention management schemes for data processing systems

Family Cites Families (31)

* 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
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
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
US4862408A (en) 1987-03-20 1989-08-29 International Business Machines Corporation Paradigm-based morphological text analysis for natural languages
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
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
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
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
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
CA2166420C (en) 1993-07-01 2006-03-28 James R. Woodhill System and method for distributed storage management on networked computer systems
WO1995012173A2 (en) 1993-10-28 1995-05-04 Teltech Resource Network Corporation Database search summary with user determined characteristics

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
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
US5369763A (en) * 1989-02-01 1994-11-29 Kansas State University Research Foundation Data storage and retrieval system with improved data base structure
US5204812A (en) * 1989-11-02 1993-04-20 International Business Machines Corp. User access of multiple documents based on document relationship classification
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
US5689699A (en) * 1992-12-23 1997-11-18 International Business Machines Corporation Dynamic verification of authorization in retention management schemes for data processing systems
US5634130A (en) * 1993-09-20 1997-05-27 International Business Machines Corporation Method and apparatus for spurious interrupt detection in a data processing system
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 (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8224859B2 (en) 1999-05-04 2012-07-17 Accenture Global Services Limited Component based information linking during claim processing
US7979382B2 (en) 1999-05-04 2011-07-12 Accenture Global Services Limited Component based information linking during claim processing
EP1213665A3 (en) * 2000-12-07 2003-12-10 Patentmall Limited Patent classification displaying method and apparatus
EP1213665A2 (en) * 2000-12-07 2002-06-12 Patentmall Limited Patent classification displaying method and apparatus
US8126742B2 (en) 2003-05-09 2012-02-28 Accenture Global Services Limited Automated assignment of insurable events
US8401896B2 (en) 2005-11-01 2013-03-19 Accenture Global Services Limited Automated task processor for insurance claims
US8180668B2 (en) 2005-11-01 2012-05-15 Accenture Global Services Limited Collaborative intelligent task processor for insurance claims
US7933786B2 (en) 2005-11-01 2011-04-26 Accenture Global Services Limited Collaborative intelligent task processor for insurance claims
US8140468B2 (en) 2006-06-22 2012-03-20 International Business Machines Corporation Systems and methods to extract data automatically from a composite electronic document
US8453050B2 (en) 2006-06-28 2013-05-28 International Business Machines Corporation Method and apparatus for creating and editing electronic documents
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
US8478769B2 (en) 2008-02-22 2013-07-02 Accenture Global Services Limited Conversational question generation system adapted for an insurance claim processing system
US8515786B2 (en) 2008-02-22 2013-08-20 Accenture Global Services Gmbh Rule generation system adapted for an insurance claim processing system
US9984415B2 (en) 2009-09-24 2018-05-29 Guidewire Software, Inc. Method and apparatus for pricing insurance policies
US11080790B2 (en) 2009-09-24 2021-08-03 Guidewire Software, Inc. Method and apparatus for managing revisions and tracking of insurance policy elements
US11900472B2 (en) 2009-09-24 2024-02-13 Guidewire Software, Inc. Method and apparatus for managing revisions and tracking of insurance policy elements

Also Published As

Publication number Publication date
US20020010708A1 (en) 2002-01-24
AU4495597A (en) 1998-04-14
WO1998012616A3 (en) 1998-07-16
US6185576B1 (en) 2001-02-06

Similar Documents

Publication Publication Date Title
WO1998012616A2 (en) Defining a uniform subject classification system incorporating document management/records retention functions
US9721016B2 (en) System and method to search and generate reports from semi-structured data including dynamic metadata
AU2004258514B2 (en) System and method for electronically managing discovery pleading information
US5164897A (en) Automated method for selecting personnel matched to job criteria
US8028231B2 (en) Document management system for searching scanned documents
US7853610B2 (en) Virtual foldering system for blending process and content in a collaborative environment
EP1693793A1 (en) Intellectual property management system
US20040199867A1 (en) Content management system for managing publishing content objects
US20060129538A1 (en) Text search quality by exploiting organizational information
US20060059162A1 (en) Method and system to convert paper documents to electronic documents and manage the electronic documents
US20110173202A1 (en) Systems and methods for utilizing organization-specific classification codes
US20050114302A1 (en) Method for fast searching and displaying a genealogical tree of patents from a patent database
US20100030605A1 (en) Automated Timesheet Generation with Auto Summarizer
US20050080820A1 (en) Method and system for generating, associating and employing user-defined fields in a relational database within an information technology system
US6636858B1 (en) Method for formatting, associating organizing, and retrieving data of and from a database stored in a computer system
EP1672544A2 (en) Improving text search quality by exploiting organizational information
Roe From archival gothic to MARC modern: building common data structures
Kappes et al. Document Management for the Knowledge Worker System
Pro System requirements
Ashford Document storage and retrieval in the electronic office
Chowdhury Text Retrieval Systems in Information Management
Moulton Building a special library's database—special considerations
Mallach A database project in a small company (or how the real world doesn't always follow the book)
Hu et al. Managing knowledge for an intelligent document processing system
Update Just-in-time Information AMERICAS

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CU CZ CZ DE DE DK DK EE EE ES FI FI GB GE GH HU ID IL IS JP KE KG KP KR KZ LC GH

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH KE LS MW SD SZ UG ZW AT BE CH DE DK ES FI FR

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1998515002

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: CA

122 Ep: pct application non-entry in european phase