US20010054042A1 - Computing system for information management - Google Patents

Computing system for information management Download PDF

Info

Publication number
US20010054042A1
US20010054042A1 US08857576 US85757697A US2001054042A1 US 20010054042 A1 US20010054042 A1 US 20010054042A1 US 08857576 US08857576 US 08857576 US 85757697 A US85757697 A US 85757697A US 2001054042 A1 US2001054042 A1 US 2001054042A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
database
file
step
files
object
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US08857576
Other versions
US6457017B2 (en )
Inventor
Richard M. Watkins
Henry C. Watkins
David V. Watkins
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SOFTSCAPE SOFTWARE LLC
Original Assignee
Softscape Inc
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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30067File systems; File servers
    • G06F17/30115File and folder operations
    • G06F17/30126Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • 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/912Applications of a database
    • Y10S707/917Text
    • 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/953Organization of data
    • Y10S707/955Object-oriented
    • 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/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • 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/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure

Abstract

An information management system includes an indexing subsystem and a document management subsystem. The system layers an object-oriented architecture over a relational database to manage folders and files from a variety of file systems. Managed files are incrementally indexed by the indexing subsystem and can be retrieved by a user by knowing content of a managed file. Folders and documents are also logically organized for presentation to the user.

Description

    RELATED APPLICATIONS
  • This application claims priority to U.S. Provisional Application No. 60/017,450 filed May 17, 1996, the contents of which are incorporated herein by reference in their entirety.[0001]
  • BACKGROUND OF THE INVENTION
  • In a typical computer, a file system manages data stored on a disk. The data is logically stored in files, which are linked lists of physical data records on the disk. Files, in turn, are logically stored in a hierarchical directory or folder structure. A file allocation table is used by the computer to manage the relationship between these logical constructs and the physical records stored on the disk. [0002]
  • Typically, for a user to access a file, the user must know the name of the file and which folder the file is stored in. File names, however, are often cryptic or otherwise not easily remembered. For that reason, search engines exist to facilitate locating a file containing a specified search string. These search engines typically perform a file-by-file search of the file system. Such a brute force method of locating a file can take a considerable amount of time if the file system is large. [0003]
  • Once a file is found, the correct application must be launched to view the file contents. The viewing application is typically dependent on the file extension being associated with a compatible application at the time of file creation. This association is typically a one-to-one relationship where all files of a particular file extension are associated with one specific application. [0004]
  • SUMMARY OF THE INVENTION
  • In accordance with a preferred embodiment of the invention, a personal desktop information management tool is combined with advanced information search and retrieval with object-based file management. A preferred embodiment of the invention also provides universal viewing of any file without the application that created that file. In addition, a preferred embodiment of the invention provides indexed searching. A relational database stores additional information about the files. [0005]
  • In accordance with the preferred embodiment of the invention, a computing system manages a plurality of files from a file system. The computing system includes a database for storing attributes of the managed files and an object-oriented manager coupled to the database. The manager preferably affects changes to a managed file by modifying the stored attributes in the database. The database is preferably a relational database. [0006]
  • The manager preferably includes a plurality of instantiated base objects. The relationships between the base objects are defined by information stored in the database. Preferably, the base objects represent a subsection of a plurality of files. [0007]
  • In the computing system, a manager preferably supports recursive processing. The stored attributes can include an ordered sequence between a plurality of sibling files. The computing system can further comprise an indexer for maintaining an index of all managed files and a general purpose file viewer for displaying content of a file created by an external complication. [0008]
  • The above and other features of the invention, including various novel details of construction and combination of parts will now be more particularly described with the reference to the accompanying drawings and pointed out in the claims. It will be understood that the particular computing system for information management embodying the invention is shown by way of illustration only and not as a limitation of the invention. The principles and features of this invention may be embodied in varied and numerous embodiments without departing from the scope of the invention.[0009]
  • BRIEF DESCRIPTION OF THE DRAWING
  • FIG. 1 is a schematic block diagram of a preferred computing system for information management embodying the invention. [0010]
  • FIG. 2 is a schematic block diagram of a preferred indexing subsystem of FIG. 1. [0011]
  • FIG. 3 is a flowchart of the watchdog object of FIG. 2. [0012]
  • FIG. 4 is a flowchart of a preferred work queue object of FIG. 2. [0013]
  • FIG. 5 is a flowchart of a preferred bulk file creator object of FIG. 2. [0014]
  • FIG. 6 is a flowchart of a preferred document collection object of FIG. 2. [0015]
  • FIG. 7 is a schematic block diagram of a preferred document management subsystem of FIG. 1. [0016]
  • FIG. 8 is a schematic diagram of a preferred container of FIG. 7. [0017]
  • FIG. 9 is a schematic block diagram of an ODBC database objects and their interaction with containers. [0018]
  • FIG. 10 is a schematic diagram of a preferred parent-child database table in accordance with the invention. [0019]
  • FIG. 11 is a schematic diagram of a preferred parent-child database table for old versions of objects in the system. [0020]
  • FIG. 12 is a schematic diagram of a preferred check out database table in accordance with the invention. [0021]
  • FIG. 13 is a schematic diagram of a preferred current metadata database table in accordance with the invention. [0022]
  • FIG. 14 is a schematic diagram of a preferred database table for old metadata in accordance with the invention. [0023]
  • FIG. 15 is a schematic diagram of a preferred database table for mapping metadata to column names. [0024]
  • FIG. 16 is a schematic diagram of a preferred object type database table in accordance with the invention. [0025]
  • FIG. 17 is a flowchart illustrating the creation of a document in accordance with the preferred embodiment of the invention. [0026]
  • FIGS. [0027] 18A-18B is a flowchart illustrating the steps for accessing a container object in accordance with the preferred embodiment of the invention.
  • DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION
  • FIG. 1 is a schematic block diagram of a preferred computing system for information management embodying the invention. An information management system [0028] 2 interfaces with a file system 4 and a main user interface 5. The file system 4 can be a local file system on a user's local disk, or a remote file system on a local area network (LAN), intranet or internet source. The information management system 2 includes an indexing subsystem 1 and a document management subsystem 6.
  • In a preferred embodiment of the invention, the information management system [0029] 2 is a software program executing on a desktop or laptop personal computer, server computer, or other suitable computing platforms. The information management system 2 is preferably embedded in a computer-readable medium, such as a CD-ROM, diskette, hard disk, or another distribution medium. A particular preferred embodiment of the invention is commercially available as Softscape Explorer Plus, Version 1.02, from Softscape Incorporation of Acton, Mass.
  • Indexing Subsystem
  • For the information management system [0030] 2 to work efficiently, the indexing subsystem 1 maintains an index list of all managed files, directories and sites. The indexing subsystem 1 preferably performs incremental updates to the index list to increase the system response time to new or modified data.
  • FIG. 2 is a schematic block diagram of a preferred indexing subsystem [0031] 1 of FIG. 1. As illustrated, the indexing subsystem 1 includes an indexing interface 15 for receiving commands from the main user interface 5 and from external application programs 8. The indexing subsystem 1 includes a programmable timer 12, a directory list controller 10, a watchdog 20, a work queue 30, a bulk file creator 40 having an associated file compare engine 47, a document collector 50 and an index database 58. These various functions communicate with each other and the, file system 4 as illustrated. Each architectural component is preferably implemented as a global object that persistently exist while the subsystem is running.
  • The directory list controller [0032] 10 is an object that manages a list of folders, drives, sites, and files that require indexing. The watchdog 20 is responsible for determining when files have been renamed, moved, modified, deleted, or created. For each of the items managed by the directory list controller 10, the watchdog 20 is notified of changes immediately as they occur, or after a user-defined scheduled time period provided by the timer 12.
  • The directory list controller [0033] 10 ensures that no two threads access the directory list at the same time, and that the index list does not have two directories that overlap. The directory list controller 10 uses a binary data file to store the information it needs to build an in-memory linked list of places that are indexed. The information managed and maintained by the directory list controller 10 is used by the watchdog 20 to know which directories or sites need to be watched.
  • Specifically, the watchdog object [0034] 20 sets up a plurality of watcher threads 25 a, . . . , 25 m based on the information in the directory list. For example, one of the nodes of the list represents a file system on the network n: drive that is being monitored continuously, and that was last indexed yesterday at 2:00. Another node may represent a File Transfer Protocol (FTP) site that is checked every 45 minutes for changes and updates. For each location (e.g., directory or site), a respective thread is established with location-specific execution requirements.
  • FIG. 3 is a flowchart of a preferred watchdog object [0035] 20 of FIG. 2. At step 205, the watchdog loads a list of directories to be watched from the directory list controller 14. At step 210, the watchdog 20 creates a watcher thread 25 for each watched directory.
  • At step [0036] 250, a watcher thread 25 is activated by a trigger, such as a change in the watched directory or a periodic timer. When the thread 25 is triggered, it will wake up to process the watched directory. At step 255, a delay timer is initialized. At step 260, the type of change to the directory is determined. At step 265, if there has been a change then the delay timer is reset at step 270 and a thread-local task list entry 29 (FIG. 2) is created at step 275. If there has been no change at step 265, processing jumps to step 280.
  • At step [0037] 280, the watcher thread 25 determines whether a preselected delay period of preferably two seconds has been completed. If not, then processing is suspended until a wake up is received at step 285. After the wake-up, processing continues to step 260 to complete a processing loop. This processing loop allows the watcher thread 25 to recognize when the file system has not changed for a specific period of time. Once it is determined that the file system is unchanged, processing continues to step 290 where the object creates a work task to be placed on the work queue.
  • In summary, when the watcher thread [0038] 25 recognizes that something has changed, a task is entered into the work queue 30 at step 290. When the bulk file creator 40 writes bulk files, it pulls tasks from the work queue 30. During this time, the watcher thread 25 stops waiting and restarts.
  • The watchdog class [0039] 20 thus manages scheduled directory checks using a windows timer 12 and watcher threads 25 to perform processing at specific time periods. When indexing is required, a work task is added to the work queue 30 and the bulk file creator 40 is notified to check the work queue.
  • Returning to FIG. 2, the work queue [0040] 30 is a persistent queue for managing work task 39. This component class is capable of managing an infinite number of types of work tasks. When the watchdog 20 determines that a subset of files in the file system 4 needs to be reindexed, it places a work task on the work queue 30 for the bulk file creator 40 to process. Other objects in the system can also query the queue 30 for work. If the queue 30 includes a work request that the calling class can process it will pass the task to the calling class so the task can be removed from the queue. The work queue 30 is fault tolerant, such that if the system fails tasks in the queue are not lost and can be processed when the system returns on-line.
  • FIG. 4 is a flowchart of a preferred work queue object [0041] 30 of FIG. 2. The work queue object 30 maintains records of work to be processed, and the type of task work. This global object is called by the watchdog 20, bulk file creator 40, and the document collector 50 to add work tasks and remove work tasks. It maintains any number of types of work tasks—tasks for the bulk file creator 40 and task for the document collector 50. The work tasks maintained are extensible, such that future components leverage the work queue to manage tasks that need to be processed. The work queue object 30 uses file system files 34 for each of the tasks so that after a system shut down, this task list 34 is maintained and persistent. Other classes in the system query the work queue to see if there is any work available in it, or to take a process task off the queue.
  • At step [0042] 305, a persistent task list 34 is loaded into a thread-safe linked list (task queue) 39 in memory. At step 310, the work queue waits for an event to trigger a response, which can be an add 312, a request for work 314, or a remove event 316.
  • In the case of an add event [0043] 312, processing jumps to step 320 where the work queue is locked. At step 325, an identifier is assigned to the task to be added. At step 330, the task is added to the persistent list 34. At step 335, the task is added to the in-memory linked list 39. At step 340, the queue is unlocked. Processing then returns to step 310 to wait for the next event.
  • In the case of a request for work [0044] 314, processing jumps to step 350 where the work queue object 30 receives from a requestor a requested task type and any tasks to be skipped. At step 355, the linked list 39 is searched for a task which meets the requested criteria. At step 360, the next task matching the requested criteria from the linked list 39 is returned to the requestor. Processing then returns to step 310 to wait for the next event.
  • In the case of a remove event [0045] 316, processing jumps to step 370 where the work queue is locked. At step 375, a task identifier is received from the requestor. At step 380, the task having the requested task identifier is removed from the persistent list 34. At step 385, the task is also removed from the in-memory linked list 39. At step 390, the queue is unlocked. Processing then returns to step 310 to wait for the next event.
  • Returning to FIG. 2, the bulk file creator [0046] 40 processes tasks by creating a bulk file 44. A bulk file 44 is a tagged text file used by the document collector 50 to determine which files to delete, add or update in the indexes 58. The bulk files 44 are also used to provide for fault tolerant processing—if the system fails, the bulk files are still available from disk 4 to resume indexing at the point during the file processing where the crash occurred.
  • The file compare engine [0047] 47 is used by the bulk file creator 40 to determine what files have been added, removed, or changed. This engine determines the difference between two ASCII files (a left-side file 49L, and a right-side file 49R) by comparing them line-by-line. Using a callback function, the bulk file creator 40 is notified regarding the lines that are the same in both files, and the lines that only exist in only one of the files. The input files used are preferably encrypted directory lists of all the files in a particular file system directory or site.
  • FIG. 5 is a flowchart of a preferred bulk file creator object [0048] 40 of FIG. 2. The bulk file creator 40 is a class which comprises a part of the infrastructure that allows incremental indexing by indexing only files that have been added or removed. This provides for an efficient method of file indexing, as opposed to indexing an entire directory. For example, if there were 10,000 files in an index, and one is deleted or added, only the incremental changes are applied to that one file—rather than having to rebuild the entire index.
  • The bulk file creator [0049] 40 receives notification of work tasks from the work queue 30 at step 405. This notification indicates that a directory requires indexing and the type of directory (e.g., FTP, e-mail, network, file system). At step 410, the bulk file creator 40 receives a work task. At step 415, the work task is checked for a directory path. At step 420, the task type is checked. The task type can either be to add a directory 422, remove a directory 424, or update a directory 426.
  • Briefly, a control file is created as an encrypted list of all the files and their last modification dates in the directory and subdirectories. This new control file is compared with an old control file using the file compare engine [0050] 47. The result of the comparison is used to create a bulk file 44.
  • In the case of an add directory task [0051] 422, processing continues to step 430 where a new control file is created. At step 435, the new control file is copied to the right-side file 49R. At step 437, the left-side file 49L is blanked. Processing then continues to step 470.
  • In the case of a remove directory task [0052] 424, processing continues to step 440. At step 440, the last created control file is copied to the left-side file 49L. At step 442, the right-side file 49R is blanked. Processing then continues to step 470.
  • In the case of an update directory task [0053] 426, processing continues to step 450. At step 450, the current control file is copied to the left-side file 49L. At step 455, a new control file is created. At step 460, the new control file is copied to the right-side file 49R. Processing then continues to step 470.
  • At step [0054] 470, the file compare engine 47 is called to compare the left-side file 49L and the right-side file 49R line-by-line. The file compare engine 47 is preferably a call back function of the bulk file creator 40. When the bulk file creator 40 processes a file comparison, it calls a function in the file compare engine 47 and passes a pointer to this call back. The call back is called once for every file that the file compare engine 47 determines has been deleted, modified or added.
  • The file compare engine [0055] 47 is preferably implemented as a dynamic link library (DLL) with an export method. This class is passed the names of the two files to compare and a call back function to call for each line of the files analyzed.
  • There are three possible outcomes from the comparison for each line. One possibility [0056] 472 is that there has been a deletion so the line exists only in the left-side file 49L. Another possibility 474 is that there has been an addition so the line exists only in the right-side file 49R. The final possibility 476 is that there has been no change so the line exists in both files. Note that a modified file will have different modification dates in the two files. Consequently, a modify is viewed as a file deletion and a file addition.
  • If the line exists only in the left-side file [0057] 49L (condition 472), then a file which previously existed has been deleted from or modified in the watched directory. The file name is written to a “delete” bulk file at step 475 and processing continues to step 490. If the line exists only in the right-side file 49R (condition 474), then a file now exists which did not previously exist in the directory. The file name is written to an “add” bulk file at step 480 and processing also continues to step 490. If a line exists in both files (condition 476), then there has been no change to the file and processing returns to step 405.
  • At step [0058] 490, the linked list of bulk files 44 is updated for the document collector object 50. Processing then returns to step 405.
  • Thus, for each file to be added or deleted from the index, a record in a bulk file [0059] 44 is created. The bulk files are text files that preferably have 1 to 250 records listing files that need to be deleted or added. The bulk files 44 are stored on the file system 4 (e.g., hard drive) and used by the document collector object 50 to process the files that require indexing.
  • The bulk file creator [0060] 40 can also manage the creation of the bulk files for e-mail directories. Preferably, the bulk file creator 40 parses the e-mail text files and deciphers what file offsets include text that can be indexed. A single e-mail file can contain hundreds or thousands of messages and attachments appended to one another. This parsing function determines the beginning and end of a list of concatenated messages.
  • The bulk file creator [0061] 40 also preferably has to separate the bulk files for e-mail, PDF, and regular collections. This implies that there be six types of bulk files created: two for each collection (“add” file and “delete” file). The PDF task is accomplished based on the file extension. The e-mail task is accomplished based on a work order to process the directory. For e-mail, the system determines the type of e-mail in order to determine the proprietary file extensions and how to parse the files.
  • Returning to FIG. 2, the document collector [0062] 50 is responsible for managing the indexes 58 of the system. This includes any system generated indexes as well as indexes that are connected to the system (i.e., remote indexes). All file indexing, e-mail indexing, index maintenance, and filtering is performed by this class. The document collector 50 uses the bulk files 44 created by the bulk file creator 40 to determine which files need to be indexed, reindexed, deleted, etc.
  • FIG. 6 is a flowchart of a preferred document collector object [0063] 50 of FIG. 2. The document collector 50 is a class that manages the text indexes and file filtering. It maintains a list of these indexes and an index list serialized into a file.
  • At step [0064] 505, a request to the work queue 30 is made for a work task by specifying a task type. At step 510, a response is received from the work queue 30. If there are no work tasks to be processed, processing return to step 505, after a possible delay. If there is a work task to process, processing continues to step 515 where the work task is checked for bulk file names and the type of processing to perform. At step 520, the bulk file 44 is opened and file names are parsed at step 525.
  • A processing loop is entered at step [0065] 530, where the document collector 50 processes the file action. At step 535, if there are more files to process, the bulk file 44 is indexed to the next file name at step 540 and processing returns to step 530. Once the bulk file 44 has been processed, processing continues to step 545 where a request is sent to the work queue 30 to remove the task associated with the process bulk file. Processing then returns to step 505. On start up, the document collector 50 checks the work queue for work and connects to the enabled indexes, remote or managed. When the document collector 50 is idle, it may disconnect from the index to save system memory. Therefore, the document collector 50 has to keep track if it has a session to work with. It will then check for more work for itself. This object also maintains a list of remote indexes that it is connected to.
  • Document Management Subsystem
  • FIG. 7 is a schematic block diagram of a preferred document management subsystem [0066] 60 of FIG. 1. At the core of the subsystem is an object oriented file system 66 layered over an Open Database Connectivity (ODBC) database 62 which utilizes a full-text information retrieval engine. This file system provides text searching, attribute searching, custom object creation, configuration management and version control.
  • Managed files from the file system [0067] 4 are represented as relational database information in the ODBC database 62. Layered over the file system 4 in the ODBC database 62 are database classes 64. An object oriented architecture 66 is in turn layered over the database classes 64. A user interface 68 permits communication with the object oriented architecture 66 and includes a general-purpose viewer 63 for displaying textual content, which can be stored in various native formats, to the user. The object oriented architecture 66 defines a central object 70 which has a plurality of object definitions 72 1, . . . , 72 N. In addition, the object oriented architecture provides a linked list of containers 74 1, . . . , 74 n. The containers 74 are defined by the object definitions 72.
  • In accordance with one aspect of the invention, the containers [0068] 74 are Object Linking and Embedding (OLE) objects. A container 74 is the base class for all objects of the system. A system object can be a folder, a document or an external information type (i.e., Universal Resource Locator (URL), link, or external document manager object). The document management functions are preferably implemented using the container objects 74 and derived classes.
  • FIG. 8 is a schematic diagram of a preferred container of FIG. 7. The base container class [0069] 74 x preferably has three derived classes from it: a container document 75 x, a folder 77 x, and a workbin 79 x.
  • A preferred object model of the system allows the document management objects (i.e., their container derivatives) to remain persistent. All relationships that the containers [0070] 74 have with one another in the system, as well as all the attribute and metadata information, are stored in the ODBC database 62. The database 62 is manipulated by the additional class architecture 64. Therefore, the container objects 74 themselves are separated from the database 62 by this layer of database class objects 64. Textual information is maintained in a full-text index database that works in parallel and in conjunction with the ODBC database 62.
  • Much of the document management functionality requires recursive processing. For example, when a new version is made for a parent folder, all of its child folders need to have their version attributes incremented (if they are changed). When the parent folder is checked out (described in detail below), all of its children and descendants are also required to be checked out. This functionality is provided by the container object containing a controlling function for checking-out children. This function relies on the virtual members of the container to traverse through the tree of objects and process each, as well as its children, accordingly. It is the responsibility of the derived classes to implement the functionality required by a check out, delete, versioning, etc. [0071]
  • The recursive methods of a container [0072] 74 allow entire hierarchies to be versioned, checked out, deleted, etc. This recursion is preferably implemented by making the object aware of not only its metadata, but of its parent-child relationship with other objects in the system. For example, when checking in a container, the container alters its metadata to make its state persistent, and then uses its relationship information to check in children.
  • During a program session, container objects [0073] 74 are instantiated only when needed, and discarded when not needed. Therefore, container objects 74 can be used to view repositories of any size, they are only instantiated when needed to view a particular piece of the repository. The user interface 6 for the system preferably includes five container objects 74, each used to provide a view of a subset of the repository. The on-demand instantiation of each container and its children allows viewing and navigating through large hierarchies of information. When needed, the database is accessed to get a block of child containers. Memory caching is also preferably used to ensure that too many containers do not request memory at the same time, and to maintain quick system response time.
  • Database Objects
  • FIG. 9 is a schematic block diagram of ODBC database objects and their interaction with containers. Container objects [0074] 74 are created as an instantiation of attributes (names, data created, type) and relationships (parent, child). This instantiation is done by ODBC objects 65 1, . . . , 65 3 which are queried for objects with certain metadata or relationships. The ODBC objects 65 1, . . . , 65 3, then in return, pass back container objects 74 matching the criteria. The layer of ODBC objects 65 with containers 74 on top of the relational database 62 turn the database 62 into an object repository. Each object in the system gets its attribute values (metadata) from a single row in a database table. The relationships for the object come from many rows from another database table.
  • The objects in the repository all share several common attributes including user ID, object ID, name, date created, date modified, and checked out user ID. In addition, each object can have custom attributes of type, for example, data, Boolean, decimal, or integer. These custom attributes are stored as raw data in the database and converted to the specified type at run-time by the system. This allows data definition altering and data modification without altering database structure. When the container object [0075] 74 needs to view an attribute, it converts the attribute to a human-readable form. When the data is saved back, the container 74 converts the data from the human-readable form back to the database data form. The database data form is also created such that a SQL query can be done on the data as if it were being stored in its native format.
  • When a container [0076] 74 makes itself persistent, it needs to store its relationship data and its metadata in a permanent storage, such as a database file. The container 74 also needs to keep track of its relationship and metadata information in memory as long as it is instantiated. Changes which occur to a container 74 in memory must be immediately reflected in the database to ensure data integrity. This is done by using the ODBC database objects 65 to write to a database and then by having the container objects synchronized their memory information.
  • Database Tables
  • Each object in the system has its own metadata or attributes and belongs to a user-defined and database-driven class. For example, there may be a class called a customer folder that has attributes which include: customer name, customer phone number, and last contact date. The metadata for all classes is stored as strings in two database tables—one for current objects and one for old versions. At run-time, the string values are mapped or converted to their display type. Although the data is stored in the database as a string, to the outside world, the data can be in an integer, date, Boolean, string, or decimal. The container classes manage the data mapping from the external view of the data to the internal storage string. [0077]
  • To manage, modify, add, and delete these class definitions, (e.g., the attribute list for a customer folder), other tables are used to store the class definition information. These tables are accessed by database objects (which are accessed by the container) in order to know how to display the metadata for a particular instance of a container [0078] 74.
  • For speed efficiency, the object metadata for the latest versions of containers is stored in one database table (FIG. 13), whereas the metadata for old versions of these objects are stored in a mirror image of the table (FIG. 14). These tables will be discussed in further detail below. [0079]
  • The attribute definitions are managed in linked lists by the central object [0080] 70 which manages the document management session. The containers 74 are responsible for maintaining their attribute values. In addition, object definitions are not loaded into memory from the database until an object of that type is instantiated. This allows the system to dynamically update metadata definitions on the fly without rebuilding the database or restarting the system. Therefore, one can add another attribute to the definition of, for example, a customer folder, without restarting or reorganizing the database.
  • One object definition object exists for each type of object in the system. Linked objects exist in a linked list on the central object [0081] 70. As definitions are altered, added or deleted, the in-memory object definitions are modified. The object definition information comes from tables in the ODBC database 62 (FIGS. 15 and 16). These tables will be discussed in further detail below.
  • A preferred object model allows multiple versions of a single document or folder (each a container), as well as multiple versions of hierarchies (i.e., configuration management). In addition, each version of a container [0082] 74 can have different values for its metadata. This is because, to uniquely identifying an object in this system, an object ID as well as a version member is required. Physically, for each object in the system, there is one record in one of the metadata tables.
  • The relationship information not only maintains the relationships between current objects, but also the relationship that old version of the object may have maintained with other objects in the system. From one version to a newer version, the configuration may change and the relationships between objects in the system may change. These changes are processed by the recursive container object and made persistent by the database ODBC objects [0083] 65.
  • As described above, the containers [0084] 74 in the system have relationships with other containers 74. The types of relationships preferably supported include parent-child with sequence. Therefore, the system can have a parent folder with ten child documents (or folders), in a specific order for the children. This relationship management is maintained in two database tables, one for the latest version objects (FIG. 10) and one for old objects (FIG. 11). For a given container 74, the information in these tables can tell who its parent(s) are, who its children are, what order its children exist, and what order it is among its own siblings.
  • Check Out
  • A document or folder hierarchy can be checked out, meaning uncompressed and marked such that it will not be available to other users. The hierarchy is checked out to another container-derived type called a workbin [0085] 79. The workbin 79 is extended such that it can have children from the archive repository as well as the current repository. The workbin 79 is a view of information in the system; a child in a workbin 79 can also be the child of another container in the system, but when the relationship with the workbin object is severed, it only means the object is being viewed somewhere else—not that the object is now orphaned. Therefore, rather than present a sea of information (documents and folders) to the user, the user only sees what is currently being worked on (i.e., checked out), which in this case is a workbin.
  • When an item is checked out, moved or worked on, there are rules created to ensure data integrity. For example, allowing a situation for a parent object is suddenly made into a child of its child is legal from a relationship standpoint, but results in a recursive relationship between the objects in the system. To avoid this, and other potential data integrity violations, rules are instantiated. These rules are as follows: [0086]
  • Old versions and read-only versions of documents and folders cannot have their children moved or edited. In addition, they cannot be edited or moved from their parents either. [0087]
  • Objects are checked out only to workbins. The object can have children that subsequently get checked out as a result of the parent getting checked out. However, one object cannot be checked out from the repository as child of another object. [0088]
  • An object can be checked out without checking out its parents. If an object is checked out to a first user, and second user checks out the parent object, the second user will not be able to move or edit the child object which is checked out to the first user. [0089]
  • If an object is checked out without its parent, it becomes the direct descendent of a workbin. From here, it can only be moved to other workbins. If the system were to allow the object to be moved to be a child of another object, the original relationship it had with its non-checked out parent would be violated. [0090]
  • Objects, folders and documents can be moved, copied and linked to each other. If an object is linked or shadowed, it can exist as a child of many other objects, but only maintained in one place. If an object is a shadow (exists as a child of two or more objects), it cannot be shadowed with a workbin because the workbins are only views of information. [0091]
  • If a child is checked out without its parent, and then the parent is checked out by the same user, the system makes sure the child object ends up as a child, and not on the same level as the parent in the workbin. Specifically, the system renames the relationship the child has with the workbin before allowing the check out to continue. [0092]
  • When an item is checked out, all of its children also must be checked out. [0093]
  • When an item is checked in, it must be the direct descendent of a workbin. This makes the situation where a parent is checked out but its children are not an impossible situation. When the parent is checked in, all of its children are check in as well. [0094]
  • Full-text Index
  • Returning to FIG. 9, a full text index feature is preferably implemented using a full-index object [0095] 67 analogous to the database objects 65. Again, the container 74 is a layer between the user interface and a full-text index database 69. When a query is passed to the full-text index object 67, it passes back a link list of matching containers 74, which, in turn, gather the metadata in full text search capabilities.
  • Data about a particular container, in the case of a document, resides in both the ODBC database [0096] 62 and in the full-text index 69. The container 74 and the architecture synchronizes the information in both of these places. This allows a container 74 to be instantiated from data residing anywhere in the system. The container object provides a view of compiled information in many different sources (attribute database, relationship database, and full-text index). Via its properties and methods, the container object ensures that data sources from which it is instantiated are synchronized. For example, if an item is donated from one information source, the full text index needs to be aware.
  • In a preferred embodiment of the invention, any searching technology can be employed to facilitate full-text searching. One suitable search engine is Topic, versions 1.52 and 2.0, commercially available from Verity Incorporated. Another suitable search engine is CPL, version 6.1, commercially available from Personal Library Services. Custom engines can also be used. [0097]
  • User Interface
  • The main feature of the user interface [0098] 68 is the visual representation of workbin objects. These objects maintain relationships and properties as described above. Items can be checked out from the local repository as well as external repositories. Items checked out from other repositories maintain their information from the other repositories and can be checked back in.
  • The containers are displayed visually and in the same relationships as defined by their metadata and relationship data attributes. Folders have methods pertaining to handling children and to publishing methods that can be used directly by the user interface. Container documents have similar methods, but in addition have document manipulation methods, such as file format conversion to HyperText Markup Language (HTML) and compression. [0099]
  • In accordance with one aspect of the invention, containers can have both parent-child relationships and sequencing between children. For example, a document may include a plurality of ordered sections, such as chapters, each residing in a respective container. By sorting these chapter containers by a sequence number, the document structure is displayed to the user ordered by chapter instead of alphabetically. [0100]
  • In accordance with another preferred aspect of the invention, a general purpose viewer [0101] 63 is used to display file contents to the user. The viewer 63 includes filters for a plurality of file formats, such as word processors, spread sheets, databases, graphics and compression from various manufacturers. Although custom filters for the most common formats can be used, a preferred embodiment of the invention incorporates KeyView filters and viewers, commercially available from FTP Software, Inc.
  • Database Tables
  • FIG. 10 is a schematic diagram of a preferred parent-child table in accordance with the invention. The CDI_PARENT_CHILD table [0102] 610 manages and maintains the relationships between the different objects in the system. Specifically, this table 610 manages the relationships for the most recent versions of objects. Information stored in this table 610 facilitates hierarchies of objects for the order that an object exists among its siblings is persistent.
  • As illustrated, the CDI_PARENT_CHILD table [0103] 610 include five attributes (i.e., columns) of data. A ParentObjID 615-1 identifies a unique identifier for a parent object. A ChildObjID 615-2 identifies a unique identifier for a child object. A ChildSeqNum 615-3 specifies the order that the child falls in among its siblings (1st, 2nd, 3rd, . . . , last). A ChildVerNum 615-4 specifies a version number of the child object. Finally, a ParentVerNum 615-5 specifies a version number of the parent object.
  • FIG. 11 is a schematic diagram of a preferred parent-child database table for old versions of objects in the system. As illustrated, an OLD_PARENT_CHILD table [0104] 620 is analogous to the CDI_PARENT_CHILD table 610.
  • FIG. 12 is a schematic diagram of a preferred check out database table in accordance with the invention. The CHECKOUT table [0105] 630 manages which documents are checked out and how these documents are checked out in a multi-user environment. For each checked-out file in the system, the CHECKOUT table 630 records associated extended check out information. At a minimum, check out status and basic information can be stored with the objects metadata.
  • However, the CHECKOUT table [0106] 630 allows for extended types, such as types checked out from foreign systems (i.e., other document managers). In such a case, this record will list the names of the DLLs that are used to interact with the source for the checked out object. Each of the DLLs will have predefined functions exported in them that the information management subsystem can expect to successfully call.
  • Therefore, knowing that an object was checked out from, for example, an FTP site or other document manager, a special DLL would be listed in the LibPath[0107] 1 column 635-13. This DLL would be loaded into memory and functions in it would be called to check the document back in.
  • FIG. 13 is a schematic diagram of a preferred current metadata table in accordance with the invention. A CURRENT_CDI_METADATA table [0108] 640 stores all metadata associated with a given object. It stores the basic attributes, such as name and date created (attributes that all objects have) as well as the custom attributes in their raw form. The data definition object is used to map this raw data into a form that is human-readable.
  • As illustrated, there are a plurality of attributes in the CURRENT_CDI_METADATA table [0109] 640. A CDIObjID 645-1 provides a unique identifier for the object. A CDIVerNum 645-2 provides a version number of the object. A CDIObjType 645-3 is a string which defines the type (i.e., filter, document or external). A CDIObjSubType 645-4 is a stream which defines a custom type (i.e., custom folder for website document). A CheckedOutFlg 645-5 indicates whether the object is checked out or not. A CheckedOutType 645-6 indicates the type of check out (i.e., read only or editable). A CheckedOutUsrID 645-7 indicates the user that has currently checked out the object. A CreationDT 645-8 indicates the date the object was created. A CreatedByUsrID 645-9 indicates the user that originally created the item. An author attribute 645-10 identifies the user that authored the item. A CDIObjName 645-11 provides a human-readable name for the object. A DeletedFlg 645-12 is used to tag the object for deletion. Columns m0, . . . , mZ 645-13, . . . , 645-z provide custom raw data for storing custom attributes.
  • FIG. 14 is a schematic diagram of a preferred database table for old metadata in accordance with the invention. As illustrated, an OLD_CDI_METADATA table [0110] 650 is analogous to the CURRENT_CDI_METADATA table 640, except that it stores the attribute information for old versions of objects in the system.
  • FIG. 15 is a schematic diagram of a preferred database table for mapping metadata to column names in accordance with the invention. The METADATA_TO_COLNAMES table [0111] 660 maps, for each object type, the type and human-readable title. It is used such that attribute information for all object types can be stored in a single database table. Because all actual metadata is stored as binary data (strings) in the CURRENT_CDI_METADATA table 640, the METADATA_TO_COLNAMES table 660 is used to derive useful meaning from the binary data sets. For example, one record in the CURRENT_CDI_METADATA table 640 may be for a customer folder (which is a user-defined custom type) whereas the next record may be for a website document (which is another user-defined custom type). Although the data for these attributes are physically stored the same way, the attributes for the two records are different. The METADATA_TO_COLNAMES table 660 defines structure and meaning for the different attributes.
  • As illustrated, there are nine attributes. A CDIObjType [0112] 665-1 indicates the object type (folder, document, external). A CDIObjSubType 665-2 indicates a custom object type name. A CDIMetaColName 665-3 provides a metadata column name (i.e., m0 645-13, . . . , mZ 645-z of FIG. 13). A UserChangeFlg 6654 indicates whether a user can change this attribute. A ColDesc 665-5 provides a long human-readable description of the attribute. A ColType 665-6 indicates the column type (Boolean, date, time, number, decimal, string). A MandatoryFlg 665-7 indicates whether the attribute must be filled in. A UserViewFlg 665-8 indicates whether a user can see the attribute. Finally, a SystemFlg 665-9 indicates whether the attribute is used solely by the system.
  • FIG. 16 is a schematic diagram of a preferred object type database table in accordance with the invention. An OBJ_TYPE table [0113] 670 defines custom object types. A complete definition for a user-defined custom object is made up of the data in this table along with the data in the METADATA_TO_COLNAMES table 660. For specific instance of an object, the data comes from the CURRENT_CDI_METADATA table 640 or the OLD_CDI_METADATA table 650.
  • As illustrated, there are seven attributes in the OBJ_TYPE table [0114] 670. An ObjType 675-1 indicates the basic type of the object (folder, document, external). An ObjSubType 675-2 provides a user-defined name for the sub-type (customer folder, web document, etc.). An ObjDescription 675-3 provides a long description of the object type. A TemplateFileFlg 675-4 specifies whether there is a template associated with the object. A TemplateFileName 675-5 specifies a path to the template, if any. An Icon attribute 675-6 identifies an icon to be used for the object. Finally, a SystemFlg 675-7 specifies whether the object is a system type, which is not to be created by the user.
  • EXAMPLES
  • FIG. 17 is a flowchart illustrating the creation of a document in accordance with the preferred embodiment of the invention. A document creation task [0115] 700 is performed by a user through the user interface 5. At step 705, the document management subsystem 6 displays a list of custom document types. Specifically, the object definition list is enumerated to get each available object type. This list preferably exists as a linked list connected to the central object 70.
  • The document types are associated with files in a template directory on the user's hard drive. At step [0116] 710, the user is prompted for an actual file or template to associate with this new document object. Optionally, this association can be done at a later time.
  • The object definition is queried for which attributes exist for the new object. These include custom and standard attributes. At step [0117] 720, the user is prompted to enter the standard attributes and any custom attributes for this document type.
  • Once the object is created, this associated file is launched for editing at step [0118] 725. The metadata is stored in the ODBC database. The relationship between this document object and parent objects are also stored in the ODBC database.
  • Information is also stored in a text index for textual-type data. At step [0119] 730, the indexer processes the text into the full-text index.
  • FIGS. [0120] 18A-18B is a flowchart illustrating the steps for accessing a container object in accordance with the preferred embodiment of the invention. As illustrated, the user first searches for and checks out a container. At step 805, a search interface is opened for entry of attribute and text search criteria. A global definition object is used to present fields which can be queried by the user.
  • At step [0121] 810, the search engine receives the user's search criteria. One of many database access objects can be used to search the database for objects matching the given criteria. At step 815, the database class accesses one or more tables to gather a first result list of matching containers.
  • At step [0122] 820, a text index class is used to search for all documents that contain any text entered by the user. The results of the fall-text search yields a second result list.
  • At step [0123] 825, the results of the database search and text index search are merged to produce one link list of containers. At step 830, a background thread is formed to gather further details for each container hit.
  • At step [0124] 835, a list of the matching containers is presented to the user for a selection. At step 840, the user selects one of the hits to be checked out for editing. At step 845, the container checks to see if it has already been checked out.
  • If the container has already been checked out to another user, processing returns to step [0125] 835 after the displaying a message to the user at step 847. If the container has not already been checked out, processing continues to step 850.
  • At step [0126] 850, the container checks to see what type of object it is so that it can determine the mechanics for processing the check out. The container can either be a folder, document, or external type object that uses an additional DLL to process the check out.
  • If the object is a folder [0127] 852, the folder recurses through its subfolders to request that each container (subfolder or document) check itself out. At step 855, the recursive indexes are initialized. At step 860, the container check out is processed for the current container in a recursion. At step 865, the container checks to see if it is already checked out.
  • If already checked out, processing continues to step [0128] 867 wherein the user receives a read-only check out of the container. If a document or subfolder is already checked out, the user may edit higher branches of the checked out folder, but not the viewed only branch. If the container has not already been checked out, processing continues to step 869 where the user receives a writable check out. In either case, processing then continues to step 870. At step 870, a check is done to see if the recursion is completed, if not, then processing returns to step 860 after implementing the recursion indexes at step 877.
  • If the object is a document [0129] 854, processing continues to step 880 where the document is uncompressed. At step 885, the uncompressed document is copied to local storage. At step 890, the container processes its check out code for right access to make sure that no one else can check out the document.
  • Equivalents [0130]
  • While the invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and detail can be made without departing from the spirit and scope of the invention as defined by the appended claims. For example, although the invention has been described with reference to particular hardware and software embodiments, it will be understood that there are aspects of the invention which can be embodied in either hardware, software, or firmware. [0131]
  • These and all other equivalents are intended to be encompassed by the following claims. [0132]

Claims (24)

    The invention claimed is:
  1. 1. A computing system for managing a plurality of files from a file system, comprising:
    a database for storing attributes of the managed files; and
    an object-oriented manager coupled to the database, the manager affecting changes to a managed file by modifying the stored attributes in the database.
  2. 2. The system of
    claim 1
    wherein the database is a relational database.
  3. 3. The system of
    claim 1
    wherein the manager includes a plurality of instantiated base objects, the relationships between the base objects being defined by information stored in the database.
  4. 4. The system of
    claim 3
    wherein the base objects represent a subsection of the plurality of files.
  5. 5. The system of
    claim 1
    wherein the manager includes recursive processing.
  6. 6. The system of
    claim 1
    wherein the stored attributes include an ordered sequence between a plurality of sibling files.
  7. 7. The system of
    claim 1
    further comprising an indexer for maintaining an index of all managed files.
  8. 8. The system of
    claim 1
    further comprising a general purpose file viewer for display contents of a file having a format from a plurality of supported formats.
  9. 9. A computing implemented method for managing a plurality of files from a file system, comprising:
    storing attributes of the managed files in a database;
    coupling an object-oriented manager to the database; and
    from the manager, affecting changes to a managed file by modifying the stored attributes in the database.
  10. 10. The method of
    claim 9
    wherein the database is a relational database.
  11. 11. The method of
    claim 9
    further comprising, from the manager, the step of instantiating a plurality of base objects, the relationships between the base objects being defined by information stored in the database.
  12. 12. The method of
    claim 11
    further comprising the step of representing a subsection of the plurality of files with the base objects.
  13. 13. The method of
    claim 9
    further comprising, from the manager, the step of recursively processing data.
  14. 14. The method of
    claim 9
    wherein the stored attributes include an ordered sequence between a plurality of sibling files.
  15. 15. The method of
    claim 9
    further comprising the step of maintaining an index of all managed files.
  16. 16. The method of
    claim 9
    further comprising the step of displaying contents of a file having a format from a plurality of supported formats.
  17. 17. An article of manufacture, comprising:
    a computer-readable medium;
    a computer program in the medium for managing a plurality of files from a file system, the computer program including the steps of:
    storing attributes of the managed files in a database;
    coupling an object-oriented manager to the database; and
    from the manager, affecting changes to a managed file by modifying the stored attributes in the database.
  18. 18. The article of
    claim 17
    wherein the database is a relational database.
  19. 19. The article of
    claim 17
    further comprising, from the manager, the step of instantiating a plurality of base objects, the relationships between the base objects being defined by information stored in the database.
  20. 20. The article of
    claim 17
    further comprising the step of representing a subsection of the plurality of files with the base objects.
  21. 21. The article of
    claim 17
    further comprising, from the manager, the step of recursively processing data.
  22. 22. The article of
    claim 17
    wherein the stored attributes include an ordered sequence between a plurality of sibling files.
  23. 23. The article of
    claim 17
    further comprising the step of maintaining an index of all managed files.
  24. 24. The article of
    claim 17
    further comprising the step of displaying contents of a file having a format from a plurality of supported formats.
US08857576 1996-05-17 1997-05-16 Computing system for information management Expired - Lifetime US6457017B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US1745096 true 1996-05-17 1996-05-17
US08857576 US6457017B2 (en) 1996-05-17 1997-05-16 Computing system for information management

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US08857576 US6457017B2 (en) 1996-05-17 1997-05-16 Computing system for information management

Publications (2)

Publication Number Publication Date
US20010054042A1 true true US20010054042A1 (en) 2001-12-20
US6457017B2 US6457017B2 (en) 2002-09-24

Family

ID=26689883

Family Applications (1)

Application Number Title Priority Date Filing Date
US08857576 Expired - Lifetime US6457017B2 (en) 1996-05-17 1997-05-16 Computing system for information management

Country Status (1)

Country Link
US (1) US6457017B2 (en)

Cited By (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030204522A1 (en) * 2002-04-23 2003-10-30 International Business Machines Corporation Autofoldering process in content management
US20040049767A1 (en) * 2002-09-05 2004-03-11 International Business Machines Corporation Method and apparatus for comparing computer code listings
US20040103102A1 (en) * 2002-11-27 2004-05-27 International Business Machines Corporation System and method for automatically linking items with multiple attributes to multiple levels of folders within a content management system
EP1467290A2 (en) * 2003-04-10 2004-10-13 Hitachi, Ltd. Method, system and program product for file access in a storage device
US20050027697A1 (en) * 2003-07-31 2005-02-03 Tom Cheng Generalized data handler
US20050033774A1 (en) * 2003-08-05 2005-02-10 James Brentano System and method for bulk transfer of digital goods
US20050091287A1 (en) * 1999-02-18 2005-04-28 Eric Sedlar Database-managed file system
US20050125800A1 (en) * 2003-12-08 2005-06-09 Himmer Richard P. Determination of dependent objects by a source control system and a method to automatically include those objects with the parent object when changes are enabled
US20050289106A1 (en) * 2004-06-25 2005-12-29 Jonah Petri Methods and systems for managing data
US20050289127A1 (en) * 2004-06-25 2005-12-29 Dominic Giampaolo Methods and systems for managing data
US20050289110A1 (en) * 2004-06-25 2005-12-29 Dominic Giampaolo Trusted index structure in a network environment
US20050289108A1 (en) * 2004-06-25 2005-12-29 Andrew Carol Methods and systems for managing data
US20050289107A1 (en) * 2004-06-25 2005-12-29 Yan Arrouye Methods and systems for managing data
US20050289109A1 (en) * 2004-06-25 2005-12-29 Yan Arrouye Methods and systems for managing data
US20060031263A1 (en) * 2004-06-25 2006-02-09 Yan Arrouye Methods and systems for managing data
US7035839B1 (en) * 1998-03-24 2006-04-25 David Gillespie Document management extension software
US20060129523A1 (en) * 2004-12-10 2006-06-15 Roman Kendyl A Detection of obscured copying using known translations files and other operational data
US20060190815A1 (en) * 2004-12-20 2006-08-24 Microsoft Corporation Structuring data for word processing documents
US20060235847A1 (en) * 2005-04-14 2006-10-19 Emc Corporation Traversing data in a repeatable manner
US20070112844A1 (en) * 2004-06-25 2007-05-17 Tribble Guy L Method and apparatus for processing metadata
US20070174310A1 (en) * 2004-06-25 2007-07-26 Yan Arrouye Methods and systems for managing data
EP1826692A2 (en) * 2006-02-22 2007-08-29 Copernic Technologies, Inc. Query correction using indexed content on a desktop indexer program.
US7280995B1 (en) 1999-08-05 2007-10-09 Oracle International Corporation On-the-fly format conversion
US20080065663A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Reestablishing process context
US20080065637A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Locating last processed data
US20080068648A1 (en) * 2001-12-18 2008-03-20 Oce Printing Systems Gmbh Method for saving and retrieving print data in a network
US7383502B2 (en) * 2004-04-30 2008-06-03 Microsoft Corporation Packages that contain pre-paginated documents
WO2008065679A2 (en) * 2006-11-27 2008-06-05 Gautam Dharamdas Goradia An interactive system
US7464330B2 (en) 2003-12-09 2008-12-09 Microsoft Corporation Context-free document portions with alternate formats
US7613689B2 (en) 2004-06-25 2009-11-03 Apple Inc. Methods and systems for managing data
US7673235B2 (en) 2004-09-30 2010-03-02 Microsoft Corporation Method and apparatus for utilizing an object model to manage document parts for use in an electronic document
US7752632B2 (en) 2004-12-21 2010-07-06 Microsoft Corporation Method and system for exposing nested data in a computer-generated document in a transparent manner
US7770180B2 (en) 2004-12-21 2010-08-03 Microsoft Corporation Exposing embedded data in a computer-generated document
US7774326B2 (en) 2004-06-25 2010-08-10 Apple Inc. Methods and systems for managing data
US7889676B1 (en) * 2006-04-13 2011-02-15 Infoblox Inc. Systems and methods for storing and retrieving data
US8131766B2 (en) 2004-12-15 2012-03-06 Oracle International Corporation Comprehensive framework to integrate business logic into a repository
US8180681B2 (en) 2003-08-05 2012-05-15 Intraware, Inc. Automated entitlement management method and apparatus for capturing maintenance renewals revenues
US20130166507A1 (en) * 2006-04-21 2013-06-27 Jason Staczek Declarative synchronization of shared data
US8538997B2 (en) 2004-06-25 2013-09-17 Apple Inc. Methods and systems for managing data
US9081872B2 (en) 2004-06-25 2015-07-14 Apple Inc. Methods and systems for managing permissions data and/or indexes

Families Citing this family (114)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030164856A1 (en) 1996-06-28 2003-09-04 Randy Prager Desktop, stream-based, information management system
US6006227A (en) * 1996-06-28 1999-12-21 Yale University Document stream operating system
US7003528B2 (en) * 1998-02-13 2006-02-21 3565 Acquisition, Llc Method and system for web management
US6745203B1 (en) * 1998-05-15 2004-06-01 E.Piphany, Inc. User interface for a distributed messaging framework
JP2000322303A (en) * 1999-05-10 2000-11-24 Fujitsu Ltd Integral document management system and document withdrawing device used for the system and computer readable recording medium for recording document withdraw program
CA2279119C (en) * 1999-07-29 2004-10-19 Ibm Canada Limited-Ibm Canada Limitee Heuristic-based conditional data indexing
JP2001169067A (en) 1999-12-10 2001-06-22 Ricoh Co Ltd Device and method for image processing and computer readable storage medium with program making computer perform the method stored therein
JP2001167087A (en) * 1999-12-14 2001-06-22 Fujitsu Ltd Device and method for retrieving structured document, program recording medium for structured document retrieval and index preparing method for structured document retrieval
US6584476B1 (en) * 2000-04-22 2003-06-24 Oracle Corp. System and method for enforcing referential constraints between versioned database tables
US7987217B2 (en) * 2000-05-12 2011-07-26 Oracle International Corporation Transaction-aware caching for document metadata
US7421541B2 (en) * 2000-05-12 2008-09-02 Oracle International Corporation Version management of cached permissions metadata
US7203709B2 (en) 2000-05-12 2007-04-10 Oracle International Corporation Transaction-aware caching for access control metadata
US7185005B1 (en) 2000-05-12 2007-02-27 Oracle International Corporation Nested transactions in a file system
US7389493B1 (en) 2000-05-12 2008-06-17 Oracle International Corporation Categories on a per instance basis
US6778972B2 (en) 2000-08-10 2004-08-17 Gustavo S. Leonardos′ System and method for providing integrated management of electronic information
US6961896B1 (en) * 2000-11-30 2005-11-01 Microsoft Corporation Method and system for setting document-linked timed reminders
US6910051B2 (en) * 2001-03-22 2005-06-21 International Business Machines Corporation Method and system for mechanism for dynamic extension of attributes in a content management system
US6772172B2 (en) * 2001-04-27 2004-08-03 Sun Microsystems, Inc. Method, system, program, and computer readable medium for indexing object oriented objects in an object oriented database
WO2003003248A1 (en) * 2001-06-26 2003-01-09 Sealedmedia Limited Search engine and digital rights management
US7003529B2 (en) * 2001-09-08 2006-02-21 Siemens Medical Solutions Health Services Corporation System for adaptively identifying data for storage
US6999972B2 (en) * 2001-09-08 2006-02-14 Siemens Medical Systems Health Services Inc. System for processing objects for storage in a document or other storage system
US20030050975A1 (en) * 2001-09-12 2003-03-13 Blaylock James G. System and method for managing electronic documents including multimedia files
US6678699B2 (en) * 2001-10-09 2004-01-13 International Business Machines Corporation Visual indexing of displayable digital documents
US7606819B2 (en) 2001-10-15 2009-10-20 Maya-Systems Inc. Multi-dimensional locating system and method
CA2601154C (en) 2007-07-07 2016-09-13 Mathieu Audet Method and system for distinguising elements of information along a plurality of axes on a basis of a commonality
US8010508B2 (en) 2001-10-15 2011-08-30 Maya-Systems Inc. Information elements locating system and method
US20080058106A1 (en) 2002-10-07 2008-03-06 Maya-Systems Inc. Multi-dimensional locating game system and method
US20030101155A1 (en) * 2001-11-23 2003-05-29 Parag Gokhale Method and system for scheduling media exports
US7058643B2 (en) * 2002-05-22 2006-06-06 Agilent Technologies, Inc. System, tools and methods to facilitate identification and organization of new information based on context of user's existing information
US20040054987A1 (en) * 2002-09-17 2004-03-18 Sonpar Nicki P. System and method of an incremental file audit in a computer system
WO2004090789A3 (en) 2003-04-03 2005-02-03 Commvault Systems Inc System and method for extended media retention
US20040199537A1 (en) * 2003-04-03 2004-10-07 Duff Robert Cory System for storing and retrieving database information
US7174433B2 (en) 2003-04-03 2007-02-06 Commvault Systems, Inc. System and method for dynamically sharing media in a computer network
US20040223648A1 (en) * 2003-05-05 2004-11-11 Keith Hoene Determining differences between documents
US20050079511A1 (en) * 2003-10-14 2005-04-14 Pharsight Corporation Drug model explorer
WO2005050382A3 (en) * 2003-11-13 2006-06-22 Commvault Systems Inc System and method for data storage and tracking
US7617447B1 (en) 2003-12-09 2009-11-10 Microsoft Corporation Context free document portions
US7984175B2 (en) 2003-12-10 2011-07-19 Mcafee, Inc. Method and apparatus for data capture and analysis system
US8548170B2 (en) 2003-12-10 2013-10-01 Mcafee, Inc. Document de-registration
US7774604B2 (en) 2003-12-10 2010-08-10 Mcafee, Inc. Verifying captured objects before presentation
US7814327B2 (en) 2003-12-10 2010-10-12 Mcafee, Inc. Document registration
US7899828B2 (en) * 2003-12-10 2011-03-01 Mcafee, Inc. Tag data structure for maintaining relational data over captured objects
US8656039B2 (en) 2003-12-10 2014-02-18 Mcafee, Inc. Rule parser
US7930540B2 (en) 2004-01-22 2011-04-19 Mcafee, Inc. Cryptographic policy enforcement
US7293039B1 (en) * 2004-03-12 2007-11-06 Network Appliance, Inc. Storage resource management across multiple paths
US7539702B2 (en) * 2004-03-12 2009-05-26 Netapp, Inc. Pre-summarization and analysis of results generated by an agent
US7844646B1 (en) * 2004-03-12 2010-11-30 Netapp, Inc. Method and apparatus for representing file system metadata within a database for efficient queries
US8661332B2 (en) 2004-04-30 2014-02-25 Microsoft Corporation Method and apparatus for document processing
US7359902B2 (en) * 2004-04-30 2008-04-15 Microsoft Corporation Method and apparatus for maintaining relationships between parts in a package
US7512878B2 (en) 2004-04-30 2009-03-31 Microsoft Corporation Modular document format
US7418652B2 (en) * 2004-04-30 2008-08-26 Microsoft Corporation Method and apparatus for interleaving parts of a document
US7487448B2 (en) 2004-04-30 2009-02-03 Microsoft Corporation Document mark up methods and systems
US7549118B2 (en) * 2004-04-30 2009-06-16 Microsoft Corporation Methods and systems for defining documents with selectable and/or sequenceable parts
US7519899B2 (en) 2004-05-03 2009-04-14 Microsoft Corporation Planar mapping of graphical elements
US7607141B2 (en) 2004-05-03 2009-10-20 Microsoft Corporation Systems and methods for support of various processing capabilities
US7634775B2 (en) 2004-05-03 2009-12-15 Microsoft Corporation Sharing of downloaded resources
US8243317B2 (en) 2004-05-03 2012-08-14 Microsoft Corporation Hierarchical arrangement for spooling job data
US7580948B2 (en) 2004-05-03 2009-08-25 Microsoft Corporation Spooling strategies using structured job information
US8363232B2 (en) 2004-05-03 2013-01-29 Microsoft Corporation Strategies for simultaneous peripheral operations on-line using hierarchically structured job information
US7755786B2 (en) 2004-05-03 2010-07-13 Microsoft Corporation Systems and methods for support of various processing capabilities
US7440132B2 (en) 2004-05-03 2008-10-21 Microsoft Corporation Systems and methods for handling a file with complex elements
US7962591B2 (en) 2004-06-23 2011-06-14 Mcafee, Inc. Object classification in a capture system
US8560534B2 (en) 2004-08-23 2013-10-15 Mcafee, Inc. Database for a capture system
US7949849B2 (en) 2004-08-24 2011-05-24 Mcafee, Inc. File system for a capture system
US7500053B1 (en) 2004-11-05 2009-03-03 Commvvault Systems, Inc. Method and system for grouping storage system components
US7584111B2 (en) * 2004-11-19 2009-09-01 Microsoft Corporation Time polynomial Arrow-Debreu market equilibrium
US7617229B2 (en) 2004-12-20 2009-11-10 Microsoft Corporation Management and use of data in a computer-generated document
US7617444B2 (en) 2004-12-20 2009-11-10 Microsoft Corporation File formats, methods, and computer program products for representing workbooks
US7614000B2 (en) 2004-12-20 2009-11-03 Microsoft Corporation File formats, methods, and computer program products for representing presentations
US7620889B2 (en) 2004-12-20 2009-11-17 Microsoft Corporation Method and system for linking data ranges of a computer-generated document with associated extensible markup language elements
US20070016870A1 (en) * 2005-07-15 2007-01-18 Microsoft Corporation Control panel framework
US7907608B2 (en) 2005-08-12 2011-03-15 Mcafee, Inc. High speed packet capture
US7818326B2 (en) 2005-08-31 2010-10-19 Mcafee, Inc. System and method for word indexing in a capture system and querying thereof
US20070055928A1 (en) * 2005-09-02 2007-03-08 Microsoft Corporation User workflow lists to organize multimedia files
US7730011B1 (en) 2005-10-19 2010-06-01 Mcafee, Inc. Attributes of captured objects in a capture system
US7657104B2 (en) 2005-11-21 2010-02-02 Mcafee, Inc. Identifying image type in a capture system
US7603518B2 (en) 2005-12-19 2009-10-13 Commvault Systems, Inc. System and method for improved media identification in a storage device
KR100804671B1 (en) * 2006-02-27 2008-02-20 엔에이치엔(주) System and Method for Searching Local Terminal for Removing Response Delay
US8504537B2 (en) 2006-03-24 2013-08-06 Mcafee, Inc. Signature distribution in a document registration system
WO2007109890A1 (en) 2006-03-29 2007-10-04 Mathieu Audet Multi-dimensional locating system and method
US7689614B2 (en) 2006-05-22 2010-03-30 Mcafee, Inc. Query generation for a capture system
US7958227B2 (en) 2006-05-22 2011-06-07 Mcafee, Inc. Attributes of captured objects in a capture system
US8010689B2 (en) 2006-05-22 2011-08-30 Mcafee, Inc. Locational tagging in a capture system
US7539783B2 (en) * 2006-09-22 2009-05-26 Commvault Systems, Inc. Systems and methods of media management, such as management of media to and from a media storage library, including removable media
US7831566B2 (en) 2006-12-22 2010-11-09 Commvault Systems, Inc. Systems and methods of hierarchical storage management, such as global management of storage operations
US8346733B2 (en) 2006-12-22 2013-01-01 Commvault Systems, Inc. Systems and methods of media management, such as management of media to and from a media storage library
CA2617688C (en) * 2007-02-22 2015-08-18 Alpex Pharma S.A. Solid dosage formulations containing weight-loss drugs
US8826123B2 (en) 2007-05-25 2014-09-02 9224-5489 Quebec Inc. Timescale for presenting information
US20090031239A1 (en) * 2007-07-17 2009-01-29 Gridiron Software Inc. Asset browser for computing environment
US8601392B2 (en) 2007-08-22 2013-12-03 9224-5489 Quebec Inc. Timeline for presenting information
US8706976B2 (en) 2007-08-30 2014-04-22 Commvault Systems, Inc. Parallel access virtual tape library and drives
JP5226283B2 (en) 2007-11-15 2013-07-03 キヤノン株式会社 The information processing apparatus and an information processing system, method, program
CA2657835C (en) 2008-03-07 2017-09-19 Mathieu Audet Documents discrimination system and method thereof
CA2666016C (en) 2008-05-15 2014-07-22 Mathieu Audet Method for building a search algorithm and method for linking documents with an object
US8205242B2 (en) 2008-07-10 2012-06-19 Mcafee, Inc. System and method for data mining and security policy management
US9253154B2 (en) 2008-08-12 2016-02-02 Mcafee, Inc. Configuration management for a capture/registration system
US8607155B2 (en) 2008-09-12 2013-12-10 9224-5489 Quebec Inc. Method of managing groups of arrays of documents
US8850591B2 (en) 2009-01-13 2014-09-30 Mcafee, Inc. System and method for concept building
US8706709B2 (en) 2009-01-15 2014-04-22 Mcafee, Inc. System and method for intelligent term grouping
US8473442B1 (en) 2009-02-25 2013-06-25 Mcafee, Inc. System and method for intelligent state management
US8447722B1 (en) 2009-03-25 2013-05-21 Mcafee, Inc. System and method for data mining and security policy management
US8667121B2 (en) 2009-03-25 2014-03-04 Mcafee, Inc. System and method for managing data and policies
US8676808B2 (en) * 2009-07-09 2014-03-18 Dillon Software Services, Llc Data store interface that facilitates distribution of application functionality across a multi-tier client-server architecture
US9244779B2 (en) 2010-09-30 2016-01-26 Commvault Systems, Inc. Data recovery operations, such as recovery from modified network data management protocol data
US8806615B2 (en) 2010-11-04 2014-08-12 Mcafee, Inc. System and method for protecting specified data combinations
US9058093B2 (en) 2011-02-01 2015-06-16 9224-5489 Quebec Inc. Active element
CA2790799A1 (en) 2011-09-25 2013-03-25 Mathieu Audet Method and apparatus of navigating information element axes
US20130246336A1 (en) 2011-12-27 2013-09-19 Mcafee, Inc. System and method for providing data protection workflows in a network environment
US9529871B2 (en) 2012-03-30 2016-12-27 Commvault Systems, Inc. Information management of mobile device data
US9519693B2 (en) 2012-06-11 2016-12-13 9224-5489 Quebec Inc. Method and apparatus for displaying data element axes
US9646080B2 (en) 2012-06-12 2017-05-09 9224-5489 Quebec Inc. Multi-functions axis-based interface
US9069799B2 (en) 2012-12-27 2015-06-30 Commvault Systems, Inc. Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system
US9928144B2 (en) 2015-03-30 2018-03-27 Commvault Systems, Inc. Storage management of data using an open-archive architecture, including streamlined access to primary data originally stored on network-attached storage and archived to secondary storage
US10101913B2 (en) 2015-09-02 2018-10-16 Commvault Systems, Inc. Migrating data to disk without interrupting running backup operations

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0592638B1 (en) * 1992-04-30 2001-02-07 Apple Computer, Inc. Method and apparatus for organizing information in a computer system
US5566333A (en) * 1992-11-05 1996-10-15 Trace Technologies, Inc. Relational database information management system for facilitating normalization of a relational database
WO1994012944A1 (en) * 1992-11-23 1994-06-09 Paragon Concepts, Inc. Computer filing system with user selected categories to provide file access
US5615367A (en) * 1993-05-25 1997-03-25 Borland International, Inc. System and methods including automatic linking of tables for improved relational database modeling with interface
JPH0744568A (en) * 1993-07-30 1995-02-14 Mitsubishi Electric Corp Retrieval interface device
US5682497A (en) * 1993-09-28 1997-10-28 Intel Corporation Managing file structures for a flash memory file system in a computer
US5568639A (en) * 1993-11-24 1996-10-22 Menai Corporation Method and apparatus for providing an object-oriented file structuring system on a computer
US5560005A (en) 1994-02-25 1996-09-24 Actamed Corp. Methods and systems for object-based relational distributed databases
US5657433A (en) * 1994-05-19 1997-08-12 Hitachi, Ltd. Method for generating, managing and displaying information retrieval data on information processing system
US5630125A (en) * 1994-05-23 1997-05-13 Zellweger; Paul Method and apparatus for information management using an open hierarchical data structure
FR2724471B1 (en) * 1994-09-13 1996-10-25 Bull Sa A object-oriented interfaces for generation of relational databases and method implemented by said device
US5742813A (en) * 1994-11-10 1998-04-21 Cadis, Inc. Method and apparatus for concurrency in an object oriented database using lock inheritance based on class objects
US5838965A (en) * 1994-11-10 1998-11-17 Cadis, Inc. Object oriented database management system
US5617568A (en) * 1994-12-14 1997-04-01 International Business Machines Corporation System and method for supporting file attributes on a distributed file system without native support therefor
US5893108A (en) * 1994-12-29 1999-04-06 International Business Machines Corporation System, method, and computer program product for efficiently translating relational tuples to object-oriented objects
US5680619A (en) * 1995-04-03 1997-10-21 Mfactory, Inc. Hierarchical encapsulation of instantiated objects in a multimedia authoring system
US5819275A (en) * 1995-06-07 1998-10-06 Trusted Information Systems, Inc. System and method for superimposing attributes on hierarchically organized file systems
US5717924A (en) * 1995-07-07 1998-02-10 Wall Data Incorporated Method and apparatus for modifying existing relational database schemas to reflect changes made in a corresponding object model
US5813009A (en) * 1995-07-28 1998-09-22 Univirtual Corp. Computer based records management system method
US5899998A (en) * 1995-08-31 1999-05-04 Medcard Systems, Inc. Method and system for maintaining and updating computerized medical records
US6092090A (en) * 1996-01-11 2000-07-18 Bhp Minerals International Inc. Management system for documents stored electronically
US5822580A (en) * 1996-01-19 1998-10-13 Object Technology Licensing Corp. Object oriented programming based global registry system, method, and article of manufacture
US5926816A (en) * 1996-10-09 1999-07-20 Oracle Corporation Database Synchronizer
US5926818A (en) * 1997-06-30 1999-07-20 International Business Machines Corporation Relational database implementation of a multi-dimensional database

Cited By (116)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060149795A1 (en) * 1998-03-24 2006-07-06 David Gillespie Document management extension software
US7493307B2 (en) 1998-03-24 2009-02-17 Search Resources Mgmt. L.L.C. Document management extension software
US7035839B1 (en) * 1998-03-24 2006-04-25 David Gillespie Document management extension software
US20050091287A1 (en) * 1999-02-18 2005-04-28 Eric Sedlar Database-managed file system
US7502782B2 (en) * 1999-02-18 2009-03-10 Oracle International Corporation Database-managed file system
US7280995B1 (en) 1999-08-05 2007-10-09 Oracle International Corporation On-the-fly format conversion
US20080068648A1 (en) * 2001-12-18 2008-03-20 Oce Printing Systems Gmbh Method for saving and retrieving print data in a network
US20090049078A1 (en) * 2002-04-23 2009-02-19 International Business Machines Corporation Autofoldering process in content management
US20030204522A1 (en) * 2002-04-23 2003-10-30 International Business Machines Corporation Autofoldering process in content management
US20040049767A1 (en) * 2002-09-05 2004-03-11 International Business Machines Corporation Method and apparatus for comparing computer code listings
US7158962B2 (en) 2002-11-27 2007-01-02 International Business Machines Corporation System and method for automatically linking items with multiple attributes to multiple levels of folders within a content management system
US20040103102A1 (en) * 2002-11-27 2004-05-27 International Business Machines Corporation System and method for automatically linking items with multiple attributes to multiple levels of folders within a content management system
EP1467290A2 (en) * 2003-04-10 2004-10-13 Hitachi, Ltd. Method, system and program product for file access in a storage device
US7797477B2 (en) 2003-04-10 2010-09-14 Hitachi, Ltd. File access method in a storage system, and programs for performing the file access
US7293131B2 (en) 2003-04-10 2007-11-06 Hitachi, Ltd. Access to disk storage using file attribute information
US20080016070A1 (en) * 2003-04-10 2008-01-17 Junji Ogawa File access method in a storage system, and programs for performing the file access
US20060206535A1 (en) * 2003-04-10 2006-09-14 Hitachi, Ltd. File access method in storage-device system, and programs for the file access
EP1467290A3 (en) * 2003-04-10 2007-01-31 Hitachi, Ltd. Method, system and program product for file access in a storage device
US20050027697A1 (en) * 2003-07-31 2005-02-03 Tom Cheng Generalized data handler
US8180681B2 (en) 2003-08-05 2012-05-15 Intraware, Inc. Automated entitlement management method and apparatus for capturing maintenance renewals revenues
US7958163B2 (en) 2003-08-05 2011-06-07 Intraware, Inc. System and method for bulk transfer of digital goods
US8499009B2 (en) 2003-08-05 2013-07-30 Flexera Software Llc Method and system for managing digital goods
US20050033774A1 (en) * 2003-08-05 2005-02-10 James Brentano System and method for bulk transfer of digital goods
US8135756B2 (en) 2003-08-05 2012-03-13 Intraware, Inc. Method and system for managing digital goods
US20070220051A1 (en) * 2003-08-05 2007-09-20 James Brentano Method and System for Managing Digital Goods
US20050125800A1 (en) * 2003-12-08 2005-06-09 Himmer Richard P. Determination of dependent objects by a source control system and a method to automatically include those objects with the parent object when changes are enabled
US7676793B2 (en) * 2003-12-08 2010-03-09 Honeywell International Inc. Determination of dependent objects by a source control system and a method to automatically include those objects with the parent object when changes are enabled
US7464330B2 (en) 2003-12-09 2008-12-09 Microsoft Corporation Context-free document portions with alternate formats
US7383502B2 (en) * 2004-04-30 2008-06-03 Microsoft Corporation Packages that contain pre-paginated documents
WO2006004670A2 (en) * 2004-06-25 2006-01-12 Apple Computer, Inc Methods and systems for managing data
US20070118651A1 (en) * 2004-06-25 2007-05-24 Dominic Giampaolo Trusted index structure in a network environment
US20070174310A1 (en) * 2004-06-25 2007-07-26 Yan Arrouye Methods and systems for managing data
US9317515B2 (en) 2004-06-25 2016-04-19 Apple Inc. Methods and systems for managing data
US9213708B2 (en) 2004-06-25 2015-12-15 Apple Inc. Methods and systems for managing data
US20070112844A1 (en) * 2004-06-25 2007-05-17 Tribble Guy L Method and apparatus for processing metadata
US20070112743A1 (en) * 2004-06-25 2007-05-17 Dominic Giampaolo Methods and systems for managing data
US20070112809A1 (en) * 2004-06-25 2007-05-17 Yan Arrouye Methods and systems for managing data
US20070112744A1 (en) * 2004-06-25 2007-05-17 Yan Arrouye Methods and systems for managing data
US9201491B2 (en) 2004-06-25 2015-12-01 Apple Inc. Methods and systems for managing data
US9081872B2 (en) 2004-06-25 2015-07-14 Apple Inc. Methods and systems for managing permissions data and/or indexes
US20070106655A1 (en) * 2004-06-25 2007-05-10 Jonah Petri Methods and systems for managing data
US9460096B2 (en) 2004-06-25 2016-10-04 Apple Inc. Methods and systems for managing data
US9063942B2 (en) 2004-06-25 2015-06-23 Apple Inc. Methods and systems for managing data
US7437358B2 (en) 2004-06-25 2008-10-14 Apple Inc. Methods and systems for managing data
US9626370B2 (en) 2004-06-25 2017-04-18 Apple Inc. Methods and systems for managing data
US9767161B2 (en) 2004-06-25 2017-09-19 Apple Inc. Methods and systems for managing data
WO2006004670A3 (en) * 2004-06-25 2006-03-16 Apple Computer Methods and systems for managing data
US9020989B2 (en) 2004-06-25 2015-04-28 Apple Inc. Methods and systems for managing data
US20060031263A1 (en) * 2004-06-25 2006-02-09 Yan Arrouye Methods and systems for managing data
US8983929B2 (en) 2004-06-25 2015-03-17 Apple Inc. Methods and systems for managing data
US20090216776A1 (en) * 2004-06-25 2009-08-27 Andrew Carol Methods and systems for managing data
US7613689B2 (en) 2004-06-25 2009-11-03 Apple Inc. Methods and systems for managing data
US7617225B2 (en) 2004-06-25 2009-11-10 Apple Inc. Methods and systems for managing data created by different applications
US7630971B2 (en) 2004-06-25 2009-12-08 Apple Inc. Methods and systems for managing data
US8868498B2 (en) 2004-06-25 2014-10-21 Apple Inc. Methods and systems for managing data
US8856074B2 (en) 2004-06-25 2014-10-07 Apple Inc. Methods and systems for managing data
US7672962B2 (en) 2004-06-25 2010-03-02 Apple Inc. Methods and systems for managing data
US20050289109A1 (en) * 2004-06-25 2005-12-29 Yan Arrouye Methods and systems for managing data
US8429208B2 (en) 2004-06-25 2013-04-23 Apple Inc. Methods and systems for managing data
US7693856B2 (en) 2004-06-25 2010-04-06 Apple Inc. Methods and systems for managing data
US7730012B2 (en) 2004-06-25 2010-06-01 Apple Inc. Methods and systems for managing data
US20100145949A1 (en) * 2004-06-25 2010-06-10 Yan Arrouye Methods and systems for managing data
US8793232B2 (en) 2004-06-25 2014-07-29 Apple Inc. Methods and systems for managing data
US8738670B2 (en) 2004-06-25 2014-05-27 Apple Inc. Methods and systems for managing data
US7774326B2 (en) 2004-06-25 2010-08-10 Apple Inc. Methods and systems for managing data
EP2169571A3 (en) * 2004-06-25 2010-08-25 Apple Inc. Methods and systems for managing data
US20050289107A1 (en) * 2004-06-25 2005-12-29 Yan Arrouye Methods and systems for managing data
EP2251803A3 (en) * 2004-06-25 2010-12-29 Apple Inc. Methods and systems for searching files
EP2273392A1 (en) * 2004-06-25 2011-01-12 Apple Inc. Methods and systems for seaching files
US7873630B2 (en) 2004-06-25 2011-01-18 Apple, Inc. Methods and systems for managing data
US8538997B2 (en) 2004-06-25 2013-09-17 Apple Inc. Methods and systems for managing data
US20050289108A1 (en) * 2004-06-25 2005-12-29 Andrew Carol Methods and systems for managing data
US8521720B2 (en) 2004-06-25 2013-08-27 Apple Inc. Methods and systems for managing data
US7970799B2 (en) 2004-06-25 2011-06-28 Apple Inc. Methods and systems for managing data
US8095506B2 (en) 2004-06-25 2012-01-10 Apple Inc. Methods and systems for managing data
US8131775B2 (en) 2004-06-25 2012-03-06 Apple Inc. Methods and systems for managing data
US20050289110A1 (en) * 2004-06-25 2005-12-29 Dominic Giampaolo Trusted index structure in a network environment
US8131674B2 (en) 2004-06-25 2012-03-06 Apple Inc. Methods and systems for managing data
US8135727B2 (en) 2004-06-25 2012-03-13 Apple Inc. Methods and systems for managing data
US20050289127A1 (en) * 2004-06-25 2005-12-29 Dominic Giampaolo Methods and systems for managing data
US8150826B2 (en) 2004-06-25 2012-04-03 Apple Inc. Methods and systems for managing data
US8150837B2 (en) 2004-06-25 2012-04-03 Apple Inc. Methods and systems for managing data
US8156106B2 (en) 2004-06-25 2012-04-10 Apple Inc. Methods and systems for managing data
US8156123B2 (en) 2004-06-25 2012-04-10 Apple Inc. Method and apparatus for processing metadata
US8156104B2 (en) 2004-06-25 2012-04-10 Apple Inc. Methods and systems for managing data
US8166065B2 (en) 2004-06-25 2012-04-24 Apple Inc. Searching metadata from files
US20050289106A1 (en) * 2004-06-25 2005-12-29 Jonah Petri Methods and systems for managing data
US8473511B2 (en) 2004-06-25 2013-06-25 Apple Inc. Methods and systems for managing data
US8190638B2 (en) 2004-06-25 2012-05-29 Apple Inc. Methods and systems for managing data
US8229889B2 (en) 2004-06-25 2012-07-24 Apple Inc. Methods and systems for managing data
US8229913B2 (en) 2004-06-25 2012-07-24 Apple Inc. Methods and systems for managing data
US8234245B2 (en) 2004-06-25 2012-07-31 Apple Inc. Methods and systems for managing data
US8352513B2 (en) 2004-06-25 2013-01-08 Apple Inc. Methods and systems for managing data
US8359331B2 (en) 2004-06-25 2013-01-22 Apple Inc. Methods and systems for managing data
US7962449B2 (en) 2004-06-25 2011-06-14 Apple Inc. Trusted index structure in a network environment
US8452751B2 (en) 2004-06-25 2013-05-28 Apple Inc. Methods and systems for managing data
US8190566B2 (en) 2004-06-25 2012-05-29 Apple Inc. Trusted index structure in a network environment
US7673235B2 (en) 2004-09-30 2010-03-02 Microsoft Corporation Method and apparatus for utilizing an object model to manage document parts for use in an electronic document
US20060129523A1 (en) * 2004-12-10 2006-06-15 Roman Kendyl A Detection of obscured copying using known translations files and other operational data
US8131766B2 (en) 2004-12-15 2012-03-06 Oracle International Corporation Comprehensive framework to integrate business logic into a repository
US20060190815A1 (en) * 2004-12-20 2006-08-24 Microsoft Corporation Structuring data for word processing documents
US7770180B2 (en) 2004-12-21 2010-08-03 Microsoft Corporation Exposing embedded data in a computer-generated document
US7752632B2 (en) 2004-12-21 2010-07-06 Microsoft Corporation Method and system for exposing nested data in a computer-generated document in a transparent manner
US20080065663A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Reestablishing process context
US7657579B2 (en) * 2005-04-14 2010-02-02 Emc Corporation Traversing data in a repeatable manner
US20080065637A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Locating last processed data
US20060235847A1 (en) * 2005-04-14 2006-10-19 Emc Corporation Traversing data in a repeatable manner
EP1826692A2 (en) * 2006-02-22 2007-08-29 Copernic Technologies, Inc. Query correction using indexed content on a desktop indexer program.
EP1826692A3 (en) * 2006-02-22 2009-03-25 Copernic Technologies, Inc. Query correction using indexed content on a desktop indexer program.
US20070208733A1 (en) * 2006-02-22 2007-09-06 Copernic Technologies, Inc. Query Correction Using Indexed Content on a Desktop Indexer Program
US7889676B1 (en) * 2006-04-13 2011-02-15 Infoblox Inc. Systems and methods for storing and retrieving data
US9898517B2 (en) * 2006-04-21 2018-02-20 Adobe Systems Incorporated Declarative synchronization of shared data
US20130166507A1 (en) * 2006-04-21 2013-06-27 Jason Staczek Declarative synchronization of shared data
WO2008065679A2 (en) * 2006-11-27 2008-06-05 Gautam Dharamdas Goradia An interactive system
US20100063962A1 (en) * 2006-11-27 2010-03-11 Gautam Dharamdas Goradia Interactive System that, Inter Alia, Does Away with the Need for a User, to Create, Store, Organize and/or Share Files and/or Uniform Resource Locators in Folders and Sub Folders, on a Computer System, Mobile Device, or on a Networks, Blogs, Forums, Intranets, Wireless Application Protocol Portals and the Like
WO2008065679A3 (en) * 2006-11-27 2009-02-19 Gautam Dharamdas Goradia An interactive system

Also Published As

Publication number Publication date Type
US6457017B2 (en) 2002-09-24 grant

Similar Documents

Publication Publication Date Title
US6279008B1 (en) Integrated graphical user interface method and apparatus for mapping between objects and databases
US6134552A (en) Knowledge provider with logical hyperlinks
US5568640A (en) Document retrieving method in a document managing system
US6691140B1 (en) Method and system for multidimensional storage model with interdimensional links
US6611838B1 (en) Metadata exchange
US5870734A (en) Three-dimensional file system using a virtual node architecture
US6453321B1 (en) Structured cache for persistent objects
Bernstein et al. An overview of repository technology
US6842758B1 (en) Modular method and system for performing database queries
US6449620B1 (en) Method and apparatus for generating information pages using semi-structured data stored in a structured manner
US7620665B1 (en) Method and system for a generic metadata-based mechanism to migrate relational data between databases
US5907837A (en) Information retrieval system in an on-line network including separate content and layout of published titles
Abiteboul Querying semi-structured data
US7383285B1 (en) Method for exposing hierarchical table structures and relationships to OLE DB applications
US7421458B1 (en) Querying, versioning, and dynamic deployment of database objects
US6031537A (en) Method and apparatus for displaying a thought network from a thought's perspective
US7076736B2 (en) Method and apparatus for sharing many thought databases among many clients
US6035303A (en) Object management system for digital libraries
US20060059204A1 (en) System and method for selectively indexing file system content
US20060015482A1 (en) System and method for creating dynamic folder hierarchies
US6088694A (en) Continuous availability and efficient backup for externally referenced objects
US20030135520A1 (en) Dynamic legal database providing historical and current versions of bodies of law
US20070033191A1 (en) Methods and systems for managing permissions data and/or indexes
US5842212A (en) Data modeling and computer access record memory
US6356901B1 (en) Method and apparatus for import, transform and export of data

Legal Events

Date Code Title Description
AS Assignment

Owner name: SOFTSCAPE, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WATKINS, RICHARD M.;WATKINS, HENRY C.;WATKINS, DAVID V.;REEL/FRAME:008837/0996

Effective date: 19971126

AS Assignment

Owner name: COMMERCE BANK & TRUST COMPANY, MASSACHUSETTS

Free format text: SECURITY AGREEMENT;ASSIGNORS:SOFTSCAPE, INC.;WATKINS, RICHARD M.;WATKINS, HENRY C.;AND OTHERS;REEL/FRAME:012730/0318

Effective date: 20011003

AS Assignment

Owner name: SOFTSCAPE (MASSACHUSETTS) INC., MASSACHUSETTS

Free format text: RELEASE OF SEC. INTEREST;ASSIGNOR:COMMERCE BANK & TRUST COMPANY;REEL/FRAME:015908/0723

Effective date: 20041001

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: SILICON VALLEY BANK, CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:SOFTSCAPE, INC.;REEL/FRAME:017823/0066

Effective date: 20060607

REMI Maintenance fee reminder mailed
SULP Surcharge for late payment

Year of fee payment: 7

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: SOFTSCAPE, INC., MASSACHUSETTS

Free format text: RELEASE;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:025051/0996

Effective date: 20100922

AS Assignment

Owner name: SOFTSCAPE SOFTWARE LLC, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SOFTSCAPE, INC.;REEL/FRAME:025084/0142

Effective date: 20100917

AS Assignment

Owner name: BANK OF MONTREAL, AS ADMINISTRATIVE AGENT, ILLINOI

Free format text: SECURITY AGREEMENT;ASSIGNORS:SUMTOTAL SYSTEMS, INC.;GEOLEARNING, INC.;SOFTSCAPE SOFTWARE LLC;REEL/FRAME:025579/0135

Effective date: 20101230

AS Assignment

Owner name: BANK OF AMERICA, N.A., NORTH CAROLINA

Free format text: SECOND LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:SOFTSCAPE SOFTWARE LLC;REEL/FRAME:029317/0689

Effective date: 20121116

Owner name: BANK OF AMERICA, N.A., NORTH CAROLINA

Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:SOFTSCAPE SOFTWARE LLC;REEL/FRAME:029317/0698

Effective date: 20121116

REMI Maintenance fee reminder mailed
AS Assignment

Owner name: GEOLEARNING, INC., IOWA

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:BANK OF MONTREAL, AS ADMINISTRATIVE AGENT;REEL/FRAME:033546/0219

Effective date: 20121116

Owner name: SUMTOTAL SYSTEMS LLC, FORMERLY KNOWN AS SUMTOTAL S

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:BANK OF MONTREAL, AS ADMINISTRATIVE AGENT;REEL/FRAME:033546/0219

Effective date: 20121116

Owner name: SOFTSCAPE SOFTWARE LLC, CALIFORNIA

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:BANK OF MONTREAL, AS ADMINISTRATIVE AGENT;REEL/FRAME:033546/0219

Effective date: 20121116

REIN Reinstatement after maintenance fee payment confirmed
LAPS Lapse for failure to pay maintenance fees
AS Assignment

Owner name: SOFTSCAPE SOFTWARE LLC, FLORIDA

Free format text: RELEASE OF SECOND LIEN SECURITY INTEREST;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:033872/0108

Effective date: 20140924

Owner name: SOFTSCAPE SOFTWARE LLC, FLORIDA

Free format text: RELEASE OF FIRST LIEN SECURITY INTEREST;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:033872/0133

Effective date: 20140924

AS Assignment

Owner name: BARCLAYS BANK PLC, AS ADMINISTRATIVE AND COLLATERA

Free format text: FIRST LIEN SECURITY INTEREST;ASSIGNORS:SOFTSCAPE SOFTWARE LLC;SUMTOTAL SYSTEMS LLC;CYBERSHIFT HOLDINGS, INC.;REEL/FRAME:033886/0767

Effective date: 20140930

AS Assignment

Owner name: BARCLAYS BANK PLC, AS ADMINISTRATIVE AND COLLATERA

Free format text: SECOND LIEN SECURITY INTEREST;ASSIGNORS:SOFTSCAPE SOFTWARE LLC;SUMTOTAL SYSTEMS LLC;CYBERSHIFT HOLDINGS, INC.;REEL/FRAME:033888/0452

Effective date: 20140930

FP Expired due to failure to pay maintenance fee

Effective date: 20140924

FPAY Fee payment

Year of fee payment: 12

PRDP Patent reinstated due to the acceptance of a late maintenance fee

Effective date: 20151019