WO2000051021A2 - Systeme et procede de recuperation et de stockage de documents electroniques - Google Patents

Systeme et procede de recuperation et de stockage de documents electroniques Download PDF

Info

Publication number
WO2000051021A2
WO2000051021A2 PCT/IB2000/000314 IB0000314W WO0051021A2 WO 2000051021 A2 WO2000051021 A2 WO 2000051021A2 IB 0000314 W IB0000314 W IB 0000314W WO 0051021 A2 WO0051021 A2 WO 0051021A2
Authority
WO
WIPO (PCT)
Prior art keywords
icons
attribute
icon
link
attributes
Prior art date
Application number
PCT/IB2000/000314
Other languages
English (en)
Other versions
WO2000051021A3 (fr
Inventor
Pascal Maas
Jan Jaap Van Der Hart
Ernest Hugues Boucher
Willem Lodewijk Boucher
Original Assignee
Signifile B.V.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Signifile B.V. filed Critical Signifile B.V.
Priority to AU29358/00A priority Critical patent/AU2935800A/en
Publication of WO2000051021A2 publication Critical patent/WO2000051021A2/fr
Publication of WO2000051021A3 publication Critical patent/WO2000051021A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers

Definitions

  • This invention relates to a software application and computer interface for indexing and retrieving data files.
  • document management can be divided into three essential categories: the hierarchy problem, the publication problem, and the needle in a haystack problem.
  • a hierarchical system enables users to associate files with a hierarchical set of drawers. For example, a user can create a drawer titled 'license agreements,' two sub-drawers titled 'local clients' and 'International clients,' and several additional sub-drawers, beneath each of the aforementioned sub-drawers, titled according to the appropriate client number.
  • a document stored in a sub-drawer can now be associated with the name of that drawer and also with the name of any and all parent drawers. In this case, a document may be associated as a licensing agreement for an international client, having a particular client number. Without the hierarchical system this flexibility would not be possible.
  • each document may have multiple associations or aspects and cannot be stored in only one location.
  • a law firm may desire to store documents by client number, by date, and by area of law. Even hierarchical storage cannot accomplish such a task.
  • An alternative method to create multiple associations would be to store more than one copy of a document, one per selected drawer or folder. Creating multiple copies of a document, however, causes many problems. If multiple documents exist it would be difficult to keep data accurate and uniform when one or more copies are modified. Further storage resources are extensively used and the process of creating multiple documents is time consuming and inefficient.
  • a second deficiency with current document management systems is the publication problem.
  • publication On a network system files are often shared by many users.
  • the process of sharing documents interchangeably is referred to as publication.
  • the problem here is that each individual on a network may have their own method of storing documents, and other users stay uninformed about the existence and content of other's documents. Since documents can only be stored in one manner it is difficult to establish the relevance of a document without opening and examining it. Furthermore, since each user has his own storage preferences, there is no common structure of reference that enables various users to efficiently share documents.
  • the needle in a haystack needs to be circumvented as well.
  • a system that has many files and many drawers becomes a handicap since unless a user remembers the content and position of each individual file it may be difficult or impossible to subsequently find it.
  • Finding one file in one sub-drawer among hundreds is comparable to finding a needle in a haystack.
  • Several applications have been developed to overcome these problems, but none offer a satisfactory solution. For example, Microsoft® incorporates a Find utility into Windows®. This utility searches all files or documents on a computer storage device for a particular file name or selected text within the searched file. This process is both very slow and inaccurate. Scanning an entire storage device takes time and the Find utility has no method for finding associations. Further, analyzing text within documents is only possible for text documents and the actual text is often not related to any association or aspect of the document.
  • index server Another utility, used frequently on the Internet, is an index server or search engine.
  • Products like AltaVista® or Microsoft Index Server keep a database of all documents and their locations. Simply, these programs perform similarly to Microsoft Find, but they are much faster and more customizable. Nevertheless, these utilities as well are limited to retrieving via the name of a document or text within a document.
  • a more specific object of the present invention is to provide a software system and computer interface that enables users to associate objects with multiple attributes and subsequently retrieve them efficiently and without significant trouble, so that the limitations of prior art document management systems, such as the traditional hierarchical file structure, can be avoided.
  • the system of this invention gives users greater visibility of files in a network or other environment, a means to communicate through files with others, and a way to control documents in a multi-user business environment. Essentially, users are able to index their documents with a principally unlimited number of attributes, describing the content, context, environment or any other aspect or interesting feature of that document. Thus, rather than using only one identifying feature when referencing an object, as with the prior art, this system uses multiple attributes so that any object can be retrieved via many ways.
  • the software system comprises an interface, which primarily includes an object view and an attribute view.
  • the object view is a file view, which displays multiple files or directories located on a workstation or network, referred to herein as object icons.
  • the attribute view displays link icons, attribute icons and folder icons, among other items or tools, for organizing and sorting the files or data (represented as object icons) from the object view.
  • the process of organizing these files is achieved by associating them with one or more customized attributes, as will be explained in more detail below.
  • the display of files or documents is based on the selection of one of three tabs: a browse tab, an unindexed tab, and a retrieved tab.
  • the browse tab allows a user to manipulate objects and files similar to the manner objects are manipulated in the environment their invention operates under.
  • the browse tab operates similar to a Microsoft Windows Explorer interface, whereby all files on a workstation or server are visible and the Windows directory structure can be traversed.
  • the unindexed tab is customizable, and typically displays recently created files from certain directories that have not been indexed by the user. This tab operates similar to an in-box, where the user can see which objects have not been integrated into the association system of this invention.
  • the retrieved tab operates in conjunction with the attribute view, which will be explained below, by displaying all documents associated with a selected attribute icon.
  • an object such as a file or other data
  • the user would typically select either the browse or unindexed tab and highlight one or more object icons that he or she wishes to index. Thereafter, the user creates an association between these selected object icons and one or more attribute icons by selecting a link icon, corresponding to each of the attribute icons.
  • a link icon corresponding to each of the attribute icons.
  • the user may click on the attribute icon at any time and all object icons associated with that attribute icon will be displayed in the retrieved tab.
  • the user may select multiple attribute icons simultaneously and any object icon that is associated with all selected attribute icons will be displayed.
  • the wording on the attribute icon changes color to show that is has been selected.
  • the attribute view also contains folder icons, in addition to attribute icons so that the user may sort their attributes according to a customized hierarchical structure as well. These folder icons may be selected and deselected to respectively display or hide all attribute icons or sub-folder icons associated with that folder icon. Folder icons with a down-facing arrow are selected folder icons, whereby their attribute icons are visible, while the folders with side-facing arrows are not-selected and hence do not display any sub-folder icons or attribute icons. Other features include, sorting attributes and folders alphabetically and displaying only selected attribute icons. Furthermore, the user is also able to adjust the display criteria of the retrieved tab via tighten and loosen icons on a button bar on the attribute view.
  • the user may simultaneously select attribute icons 'XYZ Consulting,' 'BDO CampsObers,' and 'ABC Bank.' Initially, the retrieved tab will only display object icons associated with all three of those attributes (i.e. files that have been assigned to all three selected attribute icons). The user can, however, adjust the criteria so that all object icons matching at least 2 out of 3 of these attributes or 1 out of 3 of these attributes will be shown, and so on.
  • FIGS, la-lc illustrate sample views of the computer interface in accordance to exemplary embodiments of this invention
  • FIG. 2 is a sample view of the computer interface of one embodiment of this invention, displaying the browse tab;
  • FIG. 3 is a sample view of the computer interface of one embodiment of this invention, displaying the unindexed tab;
  • FIG. 4 is a flow diagram which illustrates the sequence of operation, according to one embodiment of this invention, for creating an index and subsequently retrieving documents under that index;
  • FIG. 5 illustrates a selected document according to one embodiment of this invention
  • FIG. 6 illustrates a selected link icon according to one embodiment of this invention
  • FIG. 7 illustrates a link icon, which is turned on, according to one embodiment of this invention.
  • FIG. 8 illustrates a selected and non-selected attribute icon according to one embodiment of this invention
  • FIGS. 9 and 10 show how more than one attribute can be associated to each document or data file
  • FIG. 11 illustrates the inactive phase or cue of the link icon according to one embodiment of this invention
  • FIG. 12 illustrates the process of making an association between an object and an attribute, according to one embodiment of the invention
  • FIG. 13 illustrates how a user can retrieve objects via attribute icons, according to one embodiment of the invention
  • FIG. 14 shows how a user can inspect the attribute associations of an object, according to one embodiment of the invention
  • FIG. 15 shows how a user can remove an association between an attribute and an object, according to one embodiment of the invention.
  • FIG. 16 shows how a user can inspect the attribute associations of an object, where the object is associated with a plurality of attributes, according to one embodiment of the invention
  • FIG. 17 illustrates the selection of a plurality of objects, according to one embodiment of the invention.
  • FIG. 18 illustrates the use of a filter icon, according to one embodiment of the invention, to facilitate negation searches or other appropriate manipulation
  • FIG. 19 illustrates an example of a prior art file system
  • FIG. 20 illustrates the structure of the polymorphous object allocation table
  • FIG. 21 illustrates one embodiment of the invention where the POAT system is structured to control the access of individual users, such as in network environments;
  • FIG. 22 illustrates several graphic examples of alternative embodiments of this invention.
  • FIG. la illustrates a user interface 10 in accordance with one embodiment of the present invention.
  • Interface 10 may be displayed on a computer terminal monitor or any other commercially available display device.
  • Object icons 12 provide a visual representation of objects referenced by the system. It is noted that in case of objects stored in a memory system, the memory system includes memory devices that are disposed locally or remotely from a user, as for example in a computer network system, and as such, the invention is not limited in scope in that respect.
  • object icons 12 comprise a variety of objects in a variety of media.
  • object icons 12 in accordance with some embodiments of the invention represent: (1) electronic documents; (2) database records; (3) data corresponding to images; (4) references to documents, for example Internet URL addresses; (5) E-mail documents; (6) physical objects, e.g. books; and (7) any other type of object that is stored for later retrieval by users of the system.
  • user interface 10 is configured as a tool to index and retrieve the objects represented by object icons 12.
  • attribute icons 14, as illustrated in FIG. la provide a visual representation of certain attributes that a user desires to associate with the stored objects as represented by object icons 12.
  • a user may desire to associate a particular attribute to a plurality of objects.
  • Nice versa a user may desire to associate a particular object to a plurality of attributes.
  • the attributes provide indications that are meaningful to the user for purposes of associating to objects.
  • these attributes comprise descriptive indices that describe documents stored in a computer system based upon agreed upon terminology as explained in more detail below.
  • Other types of attributes include images or sounds that a user desires to associate with objects.
  • an indicative image may be associated with an object relating to an animation.
  • attributes comprise execution commands that a user desires to associate with one or more objects.
  • an attribute icon 14 advantageously represents an execution command that when selected by a user executes predefined codes on executable objects that have been previously associated with that attribute.
  • link icons 16 are provided that are visually disposed next to or adjacent to attribute icons 14, although the invention is not limited in scope in that respect.
  • link icons 16, in accordance with another embodiment of the invention are merged with attribute icons 14 as will be explained in more detail in reference with FIG. lb.
  • Link icons 16 provide a visual indication to a user who desires to set a link between an object represented by object icon 12 and an attribute represented by attribute icon 14.
  • a link may be set, for example, by a cursor pointer in conjunction with a computer mouse. The user may move the mouse so that the cursor pointer moves over a desired object icon, such as 12c. The user may then click on the mouse once to highlight the desired object icon. Thereafter the user may drag the mouse so that the cursor pointer moves over a desired link icon, for example 16a. By clicking the mouse, the system sets a link between a desired object represented by object icon 12c and an attribute represented by attribute icon 14a corresponding to its adjacent selected link icon 16a.
  • the user may repeat the tasks described above, consecutively, to set another link between object icon 12c and, for example, attribute icon 14c. Every time a link icon is selected by the user in accordance with the tasks described above, the system provides a visual indication of the corresponding association that is set between the object icon and attribute icon.
  • This visual indication may include a change of color of selected link icons as illustrated in FIG. la. Clicking on a link icon that already indicates an association removes the association between the selected object(s) and the attribute.
  • the task of making an association between an object represented by object icon 12a and an attribute represented by attribute icon 14c is shown in fig. 12. To do this, both object icon 12a and attribute icon 14c must be visible, as can be seen in step 11 of figure 12. Then, desired object icon 12a is selected as shown in step 13. Thereafter, as is shown in step 15, desired link icon 16c can be selected to set the association between the object, represented by object icon 12a, and the attribute, represented by attribute icon 14a.
  • the user can then accomplish desired tasks on objects identified by object icons 12 during a control and/or retrieval mode.
  • a desired attribute for example, by moving a cursor pointer over one or more desired attribute icons and highlights the selected attribute icon, for example by clicking the mouse.
  • the system shows all object icons that have been previously associated with the selected attribute icon(s).
  • a selected attribute icon represents a code- execution command
  • the system executes the executable codes represented by the attribute icon on objects represented by object icons associated with the selected attribute icon(s).
  • Fig 13 illustrates further how a user can retrieve objects by attributes, as specified above.
  • the user selects a desired attribute 14c.
  • the system subsequently searches for all objects associated with the selected attribute and displays them as objects, as shown in Step 21, where in this example object icon 12a is displayed.
  • the user can inspect the attribute associations of an object. Inspecting the attribute associations of an object enables users to determine which attributes are associated with that object. To do this, both the object icon representing an object and the attribute icon representing an attribute must be visible, as can be seen in step 23 of figure 14, wherein object icon 12a and attribute icon 14c are illustrated. The user then selects objects he wishes to inspect, such as object icon 12a at step 25. Thereafter the system shows the associated attribute icons by automatically displaying or highlighting the appropriate link icons, such as link icon 16c, as shown in step 27.
  • Figure 16 shows the same operation, this time when an object is associated to a plurality of attributes.
  • the user begins to inspect the attributes that have already been associated with a desired object, such as an object represented by object icon 12a.
  • object icon 12a the user selects object icon 12a, in response to which the system highlights it to the user.
  • the system at step 41, indicates all the associated attribute icons by automatically displaying and highlighting the appropriate link icons, such as link icons 16c, 16e and 16f.
  • the user can begin to remove an association between an attribute and an object in the following manner.
  • the user selects an object represented by an object icon, such as object icon 12a.
  • the system shows the associated attribute icons by displaying the appropriate link icons, such as link icon 16c.
  • the user deselects link icon 16c, causing the association to be removed, by clicking over icon 16c.
  • Figure 17 shows what happens when a user selects more than one object to simultaneously associate multiple selected objects with one or more common attributes.
  • the user selects one object, shown here as object icon 12a, and the system responds by displaying and highlighting the appropriate link icons, such as link icons 16c, 16e and 16f.
  • the user selects another object, shown here as object icon 12b, and the system responds by displaying and highlighting the appropriate link icons, such as link icons 16d and 16g.
  • the user selects both object icons 12a and 12b, whereby the system responds by displaying and highlighting in shaded form the appropriate link icons, such as link icons 16a-16g.
  • the system highlights a link icon in shaded form when its attribute icon is associated with one or more of the selected objects but not with all of them. Neither a highlighted or non- highlighted link icon would be appropriate in this situation since neither of these formats correspond to the status of all selected object icons. Since different objects do not need to carry the same associations, it is not always possible to display the associations of a plurality of objects at the same time. Thus, by any multiple selection of objects, associations between objects and attributes can be made, but not necessarily inspected.
  • step 49 the user selects link icon 16d, causing an association to be created with attribute icon 16d and all selected object icons, namely object icons 12a and 12b.
  • attribute icon 16d the corresponding link icon is shown highlighted and not in shaded form.
  • the user may deselect link icon 16d and remove the association between attribute icon 16d and object icons 12a and 12b. This is shown at step 51, whereby link icon 16d is displayed in a non-highlighted format, corresponding to selected object icons 12a and 12b both not having an association with object icon 16d.
  • the user can manipulate the way in which objects can be retrieved.
  • the user can also choose for certain associations not to be shown.
  • Figure 18 shows an attribute view 1800 and object view 1802.
  • attribute view further comprises supplemental icons for performing boolean and other related searches, such as filter icons 1804a and 1804b. Filter icons are used here to manipulate the filtering of objects when doing a retrieve action.
  • the associations for selected object 12a are shown.
  • the association for selected object 12b is shown.
  • attribute icon 14a is selected, which causes the system to show associated objects 12a and 12b in the object view.
  • the user selects a filter icon, such as filter icon 1804b, which, at step 61, immediately causes its corresponding attribute icon to become selected as well.
  • filter icon 1804b object icon 12b is shown on the object view. This result occurs because the filter icon acts as a negation toggle.
  • the object view displays all object icons associated with selected attribute icon 14a and NOT associated with 'filter selected' attribute icon 14b.
  • filter toggle such as filter icons 1804a and 1804b
  • objects associated with the corresponding attribute are excluded from display in the object view. If the toggle is not selected, objects associated with the corresponding attributes are selected for display.
  • FIG. lb illustrates a user interface 20 in accordance with another embodiment of the invention.
  • link icons 26 are disposed within the area defined by attribute icons 14.
  • link icons 26 may be embedded as a visual characteristic within various characters or letters associated with attribute icons 14. This visual characteristic may be the shading or coloring of the characters or letters. The visual characteristics may also be a change in the visual representation of images or letters displayed within the area defined by attribute icon 14.
  • the user associates an object icon with an attribute icon by first highlighting a desired object icon as described above in reference with FIG. la and then, moving, for example, the cursor pointer over an attribute icon and right click on the mouse.
  • the system changes the visual characteristic of letters or images within the attribute icon so as to provide an indication that the attribute represented by attribute icon 14 is associated with an object represented by selected object icon 12.
  • the color of letters within an attribute icon change from one color to the other to indicate that an association with a selected object icon has been made.
  • the letters or images within, or associated with an attribute icon function both as a description of the attributes that are being associated with an object icon and also as a link icon that can be highlighted or modified to indicate an association with an object icon.
  • the system of this invention can be implemented as a complete file system for more efficient storage and retrieval of data on a storage device or other similar structure.
  • objects e.g. files in a file-system
  • Each object has a unique identifier (e.g. a filename) and a location reference to that object (e.g. a track and sector number), indicating where the object is stored.
  • attributes may be added like the creation date, object size or a security descriptor.
  • Figure 19 illustrates an exemplary prior art system with regard to object control.
  • Column 1901 depicts the actual objects
  • column 1903 contains the object identifiers
  • column 1905 contains the object location references
  • column 1906 contains additional object attributes.
  • a unique object identifier (from 1903) is linked with a unique object location reference (from 1905) and optionally with an object attribute (from 1906). Any additional object attribute would require an additional column.
  • the table with columns 1903, 1905 and 1906 is further referred to as the Object Allocation Table (OAT).
  • OAT Object Allocation Table
  • Addressing objects stored in a logical memory is done in either of two ways; in case of fixed length ordered data objects the location or the start address or 'offset,' represented by small black squares 1904, is calculated based on the position of the object identifier in the Object allocation table (OAT). Hence, the location reference column 1905 is sometimes referred to as a virtual (calculated) column. In case of objects of differing length the position of the object's offset cannot be determined by calculation and, therefore, is saved as an attribute in a dedicated attribute column in the Object allocation table (OAT). Handling large numbers of objects creates a need for faster access and more detailed description and user identification of objects.
  • OAT Object allocation table
  • OAT can be used to address another Object allocation table (OAT) that addresses objects in its turn.
  • This is referred to as a hierarchical Object allocation table (HO AT).
  • HO AT Hierarchical Object allocation table
  • the amount of HOAT's underlying a principal Object allocation table (OAT) is theoretically unlimited.
  • OAT refers to both OAT and HOAT.
  • Practical examples of Object allocation table (OAT)'s at the file system level are FAT (File Allocation Table), NTFS (New Technology File System), and FAT32 (32-bit File Allocation Table), which are used, for example, with DOS and Windows.
  • GUI graphical user interface
  • GUI graphical user interface
  • Object allocation tables (OAT)'s are essential tools for the addressing of objects because, in order to address a data-object, a unique location reference and a unique identifier is needed; i.e. a one-to-one relationship between identifier and object.
  • OAT Object allocation table
  • GUI graphical user interface
  • a system in accordance with one embodiment of the present invention contains a system that enables many-to-many connections between attributes and objects. In this way the full identity of an object can be described in terms of attributes and objects can consequently be addressed and controlled via any attribute, or combination of attributes, that has been connected to it.
  • One application of the above-mentioned system is to couple filenames (objects) from a file system to descriptive indexes (attributes). This enables the user to 'store' a filename under a number of indexes (attributes) describing, for instance, the file's content. The user may attach, for example, the descriptive indexes 'offer', 'John' and 'XYZ, Inc.' to a filename.
  • the user can now retrieve this file via each index or via a combination of these.
  • This embodiment of the invention is hereinafter referred to as the polymorphous object allocation table (POAT) system.
  • POAT polymorphous object allocation table
  • Fig. 20 illustrates exemplary arrays employed for cross-referencing various attributes and objects in accordance with one embodiment of the invention.
  • the polymorphous object allocation table (POAT) system 2008 consists of two object allocation tables 2014 and 2010 also referred to as OAT 1 and OAT 2 respectively and a two column table 2012 referred to as polymorphous attribute connection table (PACT) as described below.
  • PACT polymorphous attribute connection table
  • Object allocation tables 2014 and 2010 are coupled by polymorphous attribute connection table (PACT) 2012.
  • Object allocation table 2014 contains attribute identifiers A, B, C, D and E.
  • Object allocation table 2010 contains object identifiers 1, 2, 3, 4 and 5.
  • the polymorphous attribute connection table (PACT) contains two columns X and Y.
  • a chosen object identifier in table 2010 is duplicated in polymorphous attribute connection table (PACT) under column 'x' in table 2012.
  • Column 'y' from table 2012 holds a duplicate of a chosen attribute identifier, represented in table 2014.
  • a filename represented by object identifier ' 1 ' in table 2010 can be connected to attribute 'B' in table 2014.
  • Integers in the same row of the polymorphous attribute connection table (PACT) form a unique connection between object and attribute and are referred to as object- attribute pairs.
  • the same object can be connected to many attributes. Connecting the same object identifier in object allocation table 2010 (OAT 2) to different attribute identifiers in object allocation table 2014 (OAT1), each time forms a new and unique object- attribute pair.
  • the invention allows the user to connect an unlimited number of attribute identifiers to a single object identifier (many- to-one), something that is not possible when using a prior art object allocation table (OAT) table, as described before.
  • OAT object allocation table
  • the polymorphous object allocation table POAT may be structured to control the access of individual users, such as in network environments.
  • identifiers User access to identifiers is granted via a structure of object allocation tables object allocation table (OAT)'s and polymorphous connection tables (PCT's), as described hereinafter.
  • OAT object allocation tables object allocation table
  • PCT's polymorphous connection tables
  • Fig. 21 each individual user is given a unique identifying integer in a user- OAT table 2102.
  • groups of users are also given a unique identifying integer in a user group-OAT table 2104.
  • Membership of an individual user to a user-group is granted by coupling a user-integer with a user group-integer in a 'membership'-PCT table 2106.
  • the coupled integers generate a unique identifier integer known as the 'security-ID' 2112.
  • Security-ID 2112 is coupled in a 'rights'-PCT table 2108 to object identifier-integers from object allocation table (OAT 1), which contains attribute identifiers as previously discussed in connection with Fig. 20.
  • OAT 1 object allocation table
  • the coupled identifiers in the 'rights'- PCT can be supplemented with a large number of 'rights' attributes contained in columns 2114, 2116, etc.
  • Such 'rights' attributes can, for instance, determine what actions individual users may perform on the objects, like reading, writing, renaming or deleting.
  • a computer interface 100 for a document indexing system is shown, according to such an embodiment of the invention
  • Computer interface 100 comprises a right pane 102, a left pane 104, a menu bar 106, and a status bar 108.
  • Right pane 102 displays a button bar 110, a plurality of rounded folder icons 112, a plurality of link icons 126, and a plurality of attribute icons.
  • left pane 104 referred to as a file view, displays three tabs, a browse tab 116, an unindexed tab 118, and a retrieved tab 120, each having a different display when selected, as will be explained below.
  • attribute icons 114 comprise light icons 126 that operate as link icons to associate and disassociate attributes with one or more objects.
  • the links and attributes each have visual cues to facilitate the indexing process.
  • the objects, links, and attributes may be graphically or non-graphically represented in many forms other than as described herein.
  • the computer interface is divided into two windows or panes.
  • the right pane is referred to as an attribute view since it is the location where attributes are created, removed, or otherwise manipulated.
  • the left pane is referred to as an object view since it is the location where all indexed and unindexed documents or files can be viewed, selected, copied, moved, etc. The structure and function of these two panes are hereinafter described.
  • Object view 104 is configured to display object icons, such as document files 122, in response to user input or selection, among other things. These object icons represent, for example, actual documents or other data stored on a computer system and are displayed in such a manner in order to facilitate the indexing, retrieving, and browsing functions of the system in accordance with one embodiment of this invention.
  • the retrieved tab is shown selected, whereas object view 104 displays document files 122, corresponding to a particular search result.
  • the retrieved tab displays files that have been found by the system in accordance with one embodiment of the invention during a user- initiated search action. Typically, these displayed files have been previously indexed, linked, or associated to one or more attribute icons. In response to a user selecting the corresponding attribute icon these files are displayed within the area defined by the retrieved tab. Notably, all linked files are displayed together regardless of the directory they are physically stored in. In addition to retrieving indexed files, users can use this tab-view to modify or create associations as well.
  • Selecting the browse tab would provide users with a directory structure for a familiar way to browse directories, allowing them, at the same time, to index files.
  • indexing a file corresponds to the tasks relating to setting an association between an attribute represented by an attribute icon and a file represented by an object icon in the object view.
  • This view is advantageously designed to give users an integrated standard way to navigate towards files.
  • the browse tab may provide a directory structure similar to the Explorer interface of a Microsoft Windows operating system.
  • An example of such a display, as provided by the browse tab is shown with reference to Fig. 2 in object view 104.
  • this enables the program to dynamically update associations so that documents can be copied and moved within the program and their associations will be maintained.
  • Fig. 3 illustrates the view of the unindexed tab on object view 104.
  • This tab displays certain files that have not yet been indexed, or have not been indexed sufficiently, and is useful for enabling users to efficiently associate attributes without complicated searching.
  • the user may customize the unindexed tab to only display files having a specific criteria.
  • criteria include, for instance, at what locations to search for documents, the age and type of searched documents and the number of attributes already associated with searched documents. For example if the user only wants to index Microsoft Word documents created in the past seven days, he or she may instruct the program to only list the unindexed files having those criteria.
  • attribute view 102 is the area where link icons 126 and attribute icons 114, collectively referred to as attribute buttons, are created and managed, in accordance with one embodiment of the invention.
  • each attribute button represents one attribute, as described above, which comprises zero or more links with documents or other objects. These links allow efficient storage and retrieval of such documents since only one click is needed to subsequently retrieve them, regardless of their physical location, as will be described in more detail. Understandably, attribute icons 114 can display text so that a name or other description can be associated with each one.
  • Each attribute button has two portions, corresponding to two functions.
  • link icon 126 on the smaller left portion of the attribute button, shown here as a light icon, is used to create and to remove associations between attributes and selected objects. As explained above, these link icons also provide a visual indication to the user of such creation and removal of an association.
  • the right larger portion of the attribute button generally referred to as an attribute icon 114, is used to retrieve previously indexed documents. Basically, the creation of a link is facilitated by a two step process. First, the desired objects from the object view are found and selected. Second, one or more attribute buttons are activated via link icons 126, located on the left portion of each attribute button. Such activation causes all selected files to be linked with the corresponding attribute button or buttons.
  • a visual cue such as change of color
  • an illuminated cue is provided to signal that the corresponding attribute button has been activated.
  • Subsequent retrieval of any linked documents is as simple as clicking the corresponding attribute icon 114, whereby the object view displays the retrieved tab with all files having that link.
  • the link icons, located on each of the attribute buttons preferably comprise additional functions to further facilitate the indexing process.
  • the link icons have, according to one embodiment of the invention, additional phases or visual cues. For example, with reference to Fig.
  • the link icon portion 1100 does not display a light. This inactive cue occurs when there are no selected objects, and hence nothing to index via the link icon. Another phase or visual cue occurs when more than one object icon is selected each having different links, referred to as a partially illuminated cue. In this situation, it becomes difficult to indicate the associations between attributes and objects since no one indication accurately reflects the links or associations of all selected object icons. Therefore, a different icon, for example a partially lit or shaded link icon, is displayed to signify such a status, as is depicted in figure 17.
  • the attribute view further comprises folder icons 112 for potentially organizing the attribute buttons according to a multi-leveled structure. Similar to a hierarchical file system, attribute buttons can be associated with a folder or sub-folder and efficiently stored as necessary.
  • Fig. lc illustrates the use of folder icons 112.
  • each folder icon contains a visual cue, such as an arrow 199, for signaling whether the folder is open or closed.
  • a down- facing arrow signifies an open folder and a side-facing arrow signifies a closed folder.
  • An open folder icon displays all attribute buttons or sub-folder icons associated with that folder, whereby a closed folder icon hides all of its contents.
  • folder icons are to avoid the clutter of countless attribute buttons by only opening the minimum number of folders needed. Selecting or clicking the folder icon is one method of interchangeably opening or closing it.
  • folders icons permits a contextual navigation through the attribute view, without having to inspect each attribute individually.
  • arrows 199 advantageously change color according to selections that exist within the folder.
  • One type of behavior regards the selection of attribute icons. When, within a certain folder, one or more attribute icons are selected, the folder icon shows this by displaying, for example, a red outline around its icon, regardless of whether the folder is opened or closed.
  • Another type of behavior regards the selection of link icons. When, with a particular folder, one or more link icons are selected, this is shown by displaying the folder icon in, for example, a yellow color. If a certain folder contains selected link icons as well as selected attribute icons, both behaviors accumulate, that is, the folder icon would show, for example, yellow with, for example, a red outline.
  • each document can be indexed numerous times despite being stored in only one physical location.
  • This enables users to retrieve files according to innumerable associations, overcoming several limitations from the previously mentioned traditional file systems.
  • a word document written in April 1997 relating to copyright law, belonging to client number 8765, and comprising the text of a copyrighted novel, could be indexed four times, by its date, area of law, client matter, and topic.
  • four indexes can be created here, one for each of the above four attributes, for more efficient storage and retrieval.
  • the user is no longer pressured to sort documents according to a specific directory system, since every association can be incorporated into the system of this invention.
  • the indexing process can be further manipulated via button or icon options on the button bar 110.
  • the retrieved tab when multiple attribute icons are selected the retrieved tab only displays documents that are indexed with all of the selected attributes. Tighten icon 142 and loosen icon 140 are configured to modify this result. Specifically, if three attribute icons, for example, are selected the retrieved tab would normally only display documents indexed with all three attributes. Display 141, on the button bar, would then state "3/3" to signify that only documents matching all three of the three selected attribute icons are retrieved. The user may optionally click or select loosening icon 140 to reduce the criteria to "2/3," whereby any document matching 2 ore more of the three attributes are displayed.
  • the loosening icon can be clicked repeatedly, as low as "1/3," or all documents with at least one matching attribute. Similarly, tighten icon 142 can be clicked to reverse the effect of the loosening icon, up to a maximum of "3/3.” Logically, these icons can be used regardless of the number of attribute icons selected.
  • sort descending icon 144 Also positioned on button bar 110 are sort descending icon 144, show selected only icon 146, user sort icon 148, deselect indexes icon 150, and stop icon 152.
  • the sort descending icon 144 rearranges the folder and attribute icons in alphabetical order.
  • the show selected only icon when selected, displays only all attribute icons that are associated with a selected document or documents (i.e. all attribute buttons with link icons that are turned on).
  • user sort icon 148 displays the attribute icons in the order that the user has chosen by dragging attribute icons to their appropriate places.
  • Stop icon 152 stops any pending process, such as the retrieval of indexed documents. It is understood that additional icons that incorporate other features may be included as well.
  • FIGs. 4- 10 respectively illustrate a flow diagram and graphic illustrations of the relevant steps of the diagram.
  • the desired document or documents are selected for indexing.
  • a user may select several accounting spreadsheet files to be indexed together under one or more attributes, such as those titled 'accounting' or 'spreadsheets.'
  • the object view has a browse tab which can be used to easily navigate a computer system directory to search for these desired documents.
  • the unindexed tab can be used to check if the documents are listed there.
  • Fig. 5 illustrates what one document, shown here as document 500, would look like when selected.
  • one or more associations are created between the selected documents and the attribute buttons 114. This is simply accomplished by clicking and turning on the link icons contained in the attribute buttons.
  • Fig. 6, illustrates link icon 126 being clicked, whereby the same link icon in Fig. 5 is shown prior to being clicked. Further, with reference to Fig. 7, link icon 126 is shown turned on, which signifies that the selected files or documents are presently linked. If the user clicks the link icon a second time the attribute or attributes would be removed from their association, and the light would turn "off.”
  • FIGs. 9 and 10 Another illustration is shown with FIGs. 9 and 10, whereby the document titled “Charlie Chaplin” is indexed with attributes “Famous” and “Human” and the document titled “Eiffel tower” is indexed with attributes “Famous” and “Very High”.
  • Fig. 8 shows, according to one embodiment of the invention, how an attribute icon appears when clicked or selected. Attribute icon 800 is shown before selection and attribute icon 802 is shown selected. After the attribute icon is selected, the text on the attribute icon changes color to signify its present selected status, whereby re-clicking the attribute icon would deselect it and return the color to its normal status.
  • This process of selecting an attribute icon instantly causes the object view to display all files or documents associated with that attribute icon. Furthermore, the selection of multiple attribute icons is possible, whereby only those documents associated with all of the selected attribute icons will be retrieved. For example, with reference to the documents of FIGS. 9 and 10, the user can select the attribute icon “Famous” and retrieve both documents “Charlie Chaplin” and "Eiffel Tower.” On the other hand, the user can simultaneously select attribute icons “Famous” and "Human,” whereby only the document title “Charlie Chaplin” would be retrieved. This result occurs because only "Charlie Chaplin" is linked with both "Famous” and “Human.” The user may also use the tighten icon 142 and/or loosen icon 140, as described above, to further manipulate these results.
  • the user browses the retrieved tab in the object view to find the document he or she is searching for. Thereafter, the document can be double clicked to execute in its proper application, as detailed above. For example, if the previously mentioned document titled "Eiffel Tower" was a picture, the user could double-click it to execute the document in an application for viewing images.
  • This step concludes the indexing and retrieving process. This invention thus makes it possible for anyone to find a document quickly, even when the searching person has no prior knowledge of the existence of the document, nor its associated attributes.
  • this document can be found by requesting all “offers” that have been “sanctioned” by the “management” in “1998”, or by requesting all correspondences of employee "A” to client “C” in “February”, or by requesting all documents in "standard offer format” drafted in “1998", etc.
  • This invention retrieves every document associated with all of the attributes selected by the user.
  • An link is essentially an association between an attribute represented by an attribute icon and one or more documents.
  • One method used by this invention is a distinctive way of simplifying the index process. Simply, every attribute button and linked document is assigned a unique integer. When a particular attribute is linked to a particular document an entry is added to a Polymorphous attribute connection table (PACT) comprising both the integer of the attribute button and the integer of the document. Whenever the program needs to determine a particular link it looks at all the entries to see which files are linked to which attributes. To optimize this process the entries of the Polymorphous attribute connection table (PACT) may be additionally sorted by attribute and/or document.
  • pointers may be used to point to all entries of a particular attribute for more speedy responses.
  • the attributes and the documents to associate a particular integer with the appropriate document or attribute name, location, etc.
  • the links and attributes can be combined as one portion of the attribute button, rather than two. This would be accomplished by using additional visual cues and utilizing the right and left button of a mouse, for example, to alternate between the functionality of the link and attribute aspect respectively.
  • the left mouse button can be used to associate an attribute with selected files and the right mouse button can be used to retrieve all previously indexed files.
  • the object and attribute views can be interchanged or one view may be larger than the other.
  • the object view could have multiple instances of a particular tab view.
  • the browse tab could display two instances for dragging or manipulating files between multiple locations.
  • the interface can be modified to include additional tabs, panes, menu options or buttons.
  • the attribute buttons can be altered to appear as a tree structure.
  • the unique indexing mechanism of this invention has many alternative applications in addition to storing and retrieving documents as explained hereinafter.
  • a stored object may have internal characteristics that may be inteipreted as attributes by an embodiment of the invention and presented to the user in an appropriate form.
  • an area of the system's interface is reserved to display one or more of the attributes.
  • URL's uniform resource locators
  • the system treats a user selected URL in a way similar to an Internet browser application like Microsoft Internet Explorer or Netscape and displays the result in the reserved area of the system's interface.
  • these attributes can aid the user in determining the nature of the stored object in order to discriminate it from other stored objects with equal attributes.
  • such attributes may be exploited as data fields for additional search criteria.
  • the user can define an SQL query on the attributes.
  • Fig. 22 illustrates some graphic examples of alternative embodiments of the invention.
  • E-mail messages may be indexed in accordance with the principles of the present invention.
  • a user selects a desired email message in object display area 2202, in response to which, title and content of the selected message is displayed in display area 2204.
  • display area 2204 may display attributes of the selected graphics object and its graphical representation.
  • database objects in response to a user selected record in display area 2202, fields of the selected record are displayed in display area 2204.
  • business card objects in response to a user selected card in display area 2202, data and the picture of the owner of the card may be displayed in area 2204.
  • URL objects in response to a user selected URL in display area 2202, the contents and presentation of the selected URL may be displayed in display area 2204.
  • the system can be used to communicate the content of Internet locations.
  • a pane such as pane 102 in figure 2 is used to display attributes.
  • This pane can display the user's custom attributes, but it can also be directed to a particular Internet location.
  • This Internet location is asked to send the attributes with which the contents of that location was registered.
  • the pane then displays those obtained attributes. For example, when the Internet location would be 'www.XYZ.com,' the XYZ server would be inquired about its attributes, and a pane such as 102 would display the content of the XYZ web site in the form of representative attributes. The user could then click one or more attributes according to the nature of the information required.
  • the invention queries the server or Internet location with the set of selected attributes.
  • the server sends back an HTML-page with results, for example, all URLs within the location that match the selected attributes.
  • the result would then be displayed in a viewer window.
  • a normal browser such as Microsoft Internet Explorer or Netscape Communicator could also be used for such a purpose.
  • the attribute system of this invention can also be customized to act according to a predetermined set of rules. For example, all Microsoft Word documents could automatically be indexed with certain default attributes. Further, the name of the document or first line of text could signal what attributes should be associated with it by the program.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

L'invention concerne une application logicielle et une interface d'ordinateur destinées à indexer et à récupérer des documents informatiques. Les utilisateurs indexent leurs documents au moyen d'un nombre en principe illimité de boutons d'attributs dont chacun décrit le contenu, le contexte, l'environnement ou tout autre aspect ou paramètre intéressant du document. On associe les indexes en sélectionnant les icônes d'objets désirées et en cliquant sur une ou plusieurs icônes de liens disposées dans la partie gauche de chaque bouton d'attribut. Dès qu'un index a été associé, l'utilisateur peut cliquer à tout moment dans la partie droite du bouton d'attribut, appelé icône d'attribut, et tous les fichiers ou icônes d'objets associés avec cet attribut seront affichés dans l'onglet récupéré.
PCT/IB2000/000314 1999-02-11 2000-02-11 Systeme et procede de recuperation et de stockage de documents electroniques WO2000051021A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU29358/00A AU2935800A (en) 1999-02-11 2000-02-11 Electronic document storage and retrieval system and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US24881199A 1999-02-11 1999-02-11
US09/248,811 1999-02-11

Publications (2)

Publication Number Publication Date
WO2000051021A2 true WO2000051021A2 (fr) 2000-08-31
WO2000051021A3 WO2000051021A3 (fr) 2001-12-20

Family

ID=22940782

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2000/000314 WO2000051021A2 (fr) 1999-02-11 2000-02-11 Systeme et procede de recuperation et de stockage de documents electroniques

Country Status (2)

Country Link
AU (1) AU2935800A (fr)
WO (1) WO2000051021A2 (fr)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004008310A2 (fr) * 2002-07-11 2004-01-22 International Business Machines Corporation Procede et systeme d'extension du systeme de fichiers api
EP1260919A3 (fr) * 2001-05-22 2004-10-20 ICMS Group n.v. Méthode de mémorisation, de recherche et de consultation de données
WO2004114148A1 (fr) * 2003-06-20 2004-12-29 International Business Machines Corporation Indexage heterogene pour systemes d'annotation
EP1573483A2 (fr) * 2002-10-17 2005-09-14 The Knowledge IT Corporation Systeme de gestion de connaissance virtuelle
JP2005317027A (ja) * 2004-04-29 2005-11-10 Microsoft Corp メタデータ編集コントロール
WO2008038004A2 (fr) * 2006-09-27 2008-04-03 Lee, Yisia Young Suk Dispositif et procédé de gestion d'objets de données
CN100418094C (zh) * 2005-06-13 2008-09-10 佳能株式会社 文件管理设备及其控制方法
US7694236B2 (en) 2004-04-23 2010-04-06 Microsoft Corporation Stack icons representing multiple objects
WO2014155023A1 (fr) * 2013-03-29 2014-10-02 My Precious Life Appareil electronique et procede de recherche d'objets de donnees par filtrage des pictogrammes associes aux dits objets de donnees
US9026901B2 (en) 2003-06-20 2015-05-05 International Business Machines Corporation Viewing annotations across multiple applications
US9614880B1 (en) 2013-11-12 2017-04-04 Google Inc. Methods for real-time notifications in an activity stream
US9870420B2 (en) 2015-01-19 2018-01-16 Google Llc Classification and storage of documents
US10078781B2 (en) 2014-06-13 2018-09-18 Google Llc Automatically organizing images
US10489044B2 (en) 2005-07-13 2019-11-26 Microsoft Technology Licensing, Llc Rich drag drop user interface
US20210174456A1 (en) * 2015-02-03 2021-06-10 State Farm Mutual Automobile Insurance Company Point-of-Service Tool for Entering Claim Information

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7627552B2 (en) 2003-03-27 2009-12-01 Microsoft Corporation System and method for filtering and organizing items based on common elements
US9531722B1 (en) 2013-10-31 2016-12-27 Google Inc. Methods for generating an activity stream
US9542457B1 (en) 2013-11-07 2017-01-10 Google Inc. Methods for displaying object history information
US9509772B1 (en) 2014-02-13 2016-11-29 Google Inc. Visualization and control of ongoing ingress actions
US9536199B1 (en) 2014-06-09 2017-01-03 Google Inc. Recommendations based on device usage
US9507791B2 (en) 2014-06-12 2016-11-29 Google Inc. Storage system user interface with floating file collection

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5295242A (en) * 1990-11-02 1994-03-15 Consilium, Inc. Apparatus and method for viewing relationships in a factory management system
US5608900A (en) * 1994-06-21 1997-03-04 Internationl Business Machines Corp. Generation and storage of connections between objects in a computer network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5295242A (en) * 1990-11-02 1994-03-15 Consilium, Inc. Apparatus and method for viewing relationships in a factory management system
US5608900A (en) * 1994-06-21 1997-03-04 Internationl Business Machines Corp. Generation and storage of connections between objects in a computer network

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"ENSURING INTERNAL CONSISTENCY IN A SET OF INTERCONNECTED CLASSES" IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP., vol. 37, no. 2B, 1 February 1994 (1994-02-01), pages 697-698, XP000434004 NEW YORK, NY, US ISSN: 0018-8689 *
"PROGRAMMABLE STORAGE ICON FOR OPTICAL AND TAPE LAN/RISC-6000 APPLICATIONS" IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP., vol. 38, no. 5, 1 May 1995 (1995-05-01), pages 293-296, XP000519582 NEW YORK, NY, US ISSN: 0018-8689 *
"SELECTED OBJECT FILTER ON POP-UP MENU" IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP. NEW YORK, US, vol. 39, no. 9, 1 September 1996 (1996-09-01), pages 157-161, XP000638260 ISSN: 0018-8689 *
"SINGLE-CLICK ACTION BUTTONS" IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP., vol. 37, no. 3, 1 March 1994 (1994-03-01), page 93 XP000441391 NEW YORK, NY, US ISSN: 0018-8689 *
GREENHILL S ET AL: "Noetica: a tool for semantic data modelling" INFORMATION PROCESSING & MANAGEMENT, ELSEVIER, vol. 34, no. 6, November 1998 (1998-11), pages 739-760, XP004150299 BARKING, GB ISSN: 0306-4573 *
MAYES A ET AL: "Implementing Associations between Objects" MICROPROCESSING AND MICROPROGRAMMING, ELSEVIER SCIENCE PUBLISHERS, BV., vol. 40, no. 10, 1 December 1994 (1994-12-01), pages 811-814, XP004014261 AMSTERDAM, NL ISSN: 0165-6074 *

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7209914B2 (en) 2001-05-22 2007-04-24 Icms Group N.V. Method of storing, retrieving and viewing data
EP1260919A3 (fr) * 2001-05-22 2004-10-20 ICMS Group n.v. Méthode de mémorisation, de recherche et de consultation de données
US7516420B2 (en) 2002-07-11 2009-04-07 International Business Machines Corporation Method and system for extending the file system API
WO2004008310A3 (fr) * 2002-07-11 2004-11-11 Ibm Procede et systeme d'extension du systeme de fichiers api
US8046718B2 (en) 2002-07-11 2011-10-25 International Business Machines Corporation System for extending the file system API
CN100410931C (zh) * 2002-07-11 2008-08-13 国际商业机器公司 用于扩展文件系统应用编程接口的方法
WO2004008310A2 (fr) * 2002-07-11 2004-01-22 International Business Machines Corporation Procede et systeme d'extension du systeme de fichiers api
EP1573483A2 (fr) * 2002-10-17 2005-09-14 The Knowledge IT Corporation Systeme de gestion de connaissance virtuelle
US7729924B2 (en) 2002-10-17 2010-06-01 Knowledge It Corporation Virtual knowledge management system
EP1573483A4 (fr) * 2002-10-17 2006-10-11 Knowledge It Corp Systeme de gestion de connaissance virtuelle
WO2004114148A1 (fr) * 2003-06-20 2004-12-29 International Business Machines Corporation Indexage heterogene pour systemes d'annotation
US9026901B2 (en) 2003-06-20 2015-05-05 International Business Machines Corporation Viewing annotations across multiple applications
US8793231B2 (en) 2003-06-20 2014-07-29 International Business Machines Corporation Heterogeneous multi-level extendable indexing for general purpose annotation systems
US7694236B2 (en) 2004-04-23 2010-04-06 Microsoft Corporation Stack icons representing multiple objects
US7421438B2 (en) 2004-04-29 2008-09-02 Microsoft Corporation Metadata editing control
EP1594053A3 (fr) * 2004-04-29 2008-01-09 Microsoft Corporation Commande d'édition de métadonnées
KR101120681B1 (ko) * 2004-04-29 2012-03-23 마이크로소프트 코포레이션 메타데이터 편집 제어 방법 및 시스템
JP2012164365A (ja) * 2004-04-29 2012-08-30 Microsoft Corp メタデータ編集コントロール
JP2005317027A (ja) * 2004-04-29 2005-11-10 Microsoft Corp メタデータ編集コントロール
CN100418094C (zh) * 2005-06-13 2008-09-10 佳能株式会社 文件管理设备及其控制方法
US10489044B2 (en) 2005-07-13 2019-11-26 Microsoft Technology Licensing, Llc Rich drag drop user interface
WO2008038004A2 (fr) * 2006-09-27 2008-04-03 Lee, Yisia Young Suk Dispositif et procédé de gestion d'objets de données
WO2008038004A3 (fr) * 2006-09-27 2008-12-04 Lee Yisia Young Suk Dispositif et procédé de gestion d'objets de données
FR3003965A1 (fr) * 2013-03-29 2014-10-03 My Precious Life Procede de recherche d'objets de donnees
WO2014155023A1 (fr) * 2013-03-29 2014-10-02 My Precious Life Appareil electronique et procede de recherche d'objets de donnees par filtrage des pictogrammes associes aux dits objets de donnees
US9614880B1 (en) 2013-11-12 2017-04-04 Google Inc. Methods for real-time notifications in an activity stream
US10078781B2 (en) 2014-06-13 2018-09-18 Google Llc Automatically organizing images
US9870420B2 (en) 2015-01-19 2018-01-16 Google Llc Classification and storage of documents
US11900469B2 (en) * 2015-02-03 2024-02-13 State Farm Mutual Automobile Insurance Company Point-of-service tool for entering claim information
US20210174456A1 (en) * 2015-02-03 2021-06-10 State Farm Mutual Automobile Insurance Company Point-of-Service Tool for Entering Claim Information

Also Published As

Publication number Publication date
AU2935800A (en) 2000-09-14
WO2000051021A3 (fr) 2001-12-20

Similar Documents

Publication Publication Date Title
WO2000051021A2 (fr) Systeme et procede de recuperation et de stockage de documents electroniques
US9483169B2 (en) Computer system for automatic organization, indexing and viewing of information from multiple sources
KR101083533B1 (ko) 쉘 브라우저 내에서의 메타데이터의 사용자 변경을 위한시스템 및 방법
CA2560215C (fr) Arbre de proprietes pour navigation et attribution de metadonnees
US7409644B2 (en) File system shell
US6310633B1 (en) Method and system for organizing document information
AU2003229326B2 (en) System and method for filtering and organizing items based on common elements
US20120054210A1 (en) Method, system, and computer program product for locating network files
US20060004873A1 (en) Carousel control for metadata navigation and assignment
MXPA04006413A (es) Sistema de archivo para desplegar articulos de distintos tipos y desde diversos sitios fisicos.
CA2671781A1 (fr) Procede et systeme visuels pour une creation, une manipulation, une agregation, une application et une recherche rdf
US20070192305A1 (en) Search term suggestion method based on analysis of correlated data in three dimensions
EP1629367A1 (fr) Programme shell d'un systeme de fichiers
US7552139B2 (en) Represented object groups
JP5844279B2 (ja) 情報管理
JP4843801B2 (ja) コンピュータネットワーク上で情報をパブリッシング、組織化、アクセス及び配布するためのシステム
Buchanan et al. Supporting information structuring in a digital library
Dourish et al. Uniform document interactions using document properties
Spoerri Coordinating linear and 2d displays to support exploratory search
NZ533296A (en) File system shell
Roberts et al. Histogram-Based Visualizations FOR Large Time Dependent Datasets
Ratzlaff Augmented knowledge gathering: the design of a physical-digital interface for searching the Internet.
Bryant Using EndNote X5
Ratzlaff Augmented Knowledge Gathering
Foo Enhancing E-Journal Access In A Digital Work Environment

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

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

Ref country code: DE

Ref legal event code: 8642

AK Designated states

Kind code of ref document: A3

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

122 Ep: pct application non-entry in european phase