WO2000073909A1 - Procede de gestion des fichiers electroniques et support lisible par ordinateur pour enregistrement du fichier de gestion electronique - Google Patents

Procede de gestion des fichiers electroniques et support lisible par ordinateur pour enregistrement du fichier de gestion electronique Download PDF

Info

Publication number
WO2000073909A1
WO2000073909A1 PCT/JP2000/001630 JP0001630W WO0073909A1 WO 2000073909 A1 WO2000073909 A1 WO 2000073909A1 JP 0001630 W JP0001630 W JP 0001630W WO 0073909 A1 WO0073909 A1 WO 0073909A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic file
electronic
program
events
management method
Prior art date
Application number
PCT/JP2000/001630
Other languages
English (en)
Japanese (ja)
Inventor
Hiroyuki Tobita
Toshiaki Bamba
Shigeru Korekoda
Original Assignee
Cadix 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
Application filed by Cadix Inc. filed Critical Cadix Inc.
Priority to AU31933/00A priority Critical patent/AU3193300A/en
Publication of WO2000073909A1 publication Critical patent/WO2000073909A1/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

  • the present invention relates to a method for managing electronic files.
  • it relates to a method for managing the relationship between electronic files.
  • Explorer is a file operation program that can copy, move, delete, and rename electronic files.
  • the explorer manages the attributes of the electronic file, such as the name of the electronic file, the update date, the creator, and the like. Users manage electronic files based on the attributes managed by Explorer, based on their customs and experience.
  • the relevance of each electronic file is not sufficiently managed, and the user manages and uses the relevance of the file based on experience and the like.
  • This management burden is one of the factors that reduces the time users spend on their original tasks and reduces the efficiency of development work.
  • FIG. 13 is an explanatory diagram showing an example of how an electronic file is updated or diverted. As shown in this figure, the contents of the electronic file 1 are updated sequentially as the development progresses (elapse of time), such as the electronic file la, the electronic file 1b, and so on.
  • the process of creating the electronic file 2 using the contents of the electronic file 1a is also executed in parallel. This is the so-called “diversion” of electronic files. Further, the contents of the electronic file 2 are sequentially updated like the electronic file 2a, the electronic file 2b, and the like, similarly to the electronic file 1.
  • the electronic file 2 is a diverted version of the electronic file 1a, but as time elapses, the content of the electronic file 1a of the parent file that is the diverted source is changed, and the file name is changed. It may have been changed. Therefore, the diversion relationship of each file tends to be complicated, and the management work between electronic files, including diversion and diversion relationship, is very complicated.
  • the present invention has been made in view of such a problem, and an object of the present invention is to realize an electronic file management method capable of grasping a relationship including a diversion / reuse relationship of an electronic file without imposing a management burden on a user. It is to be.
  • a method for managing an electronic file comprising: a collecting step of detecting an event relating to the electronic file and collecting the detected event in a database;
  • An electronic file management method comprising: providing a user with information including a relationship between electronic files based on the contents of a database in which events are collected.
  • the collection is performed by an electronic file operation program.
  • the electronic file operation program it is possible to collect events related to the operation of electronic files without increasing the burden on users.
  • An electronic file management method according to a second aspect of the present invention, wherein the providing step includes an ancestor display step of displaying an ancestor file from which a predetermined electronic file is diverted in response to a user request. It is.
  • An electronic file management method according to a third aspect of the present invention, wherein the providing step includes a descendant display step of displaying a descendant file to which a predetermined electronic file is diverted in response to a request from a user. It is.
  • a fourth aspect of the present invention is the electronic file management method, wherein the descendant display step displays a tree structure having the predetermined file as a root.
  • a computer-readable recording medium that stores a program for managing an electronic file, detects an event related to the electronic file, and collects the detected event in a database.
  • a storage medium readable by a computer that stores a program that provides a user with information including the relationship between electronic files based on the contents of a database that has collected, and a program that executes. .
  • a sixth aspect of the present invention is a method for managing an electronic file, comprising: a collecting step of detecting an event relating to the operation of the electronic file and collecting the detected event in a database; And a providing step of providing information regarding the operation history of the electronic file to the user.
  • the operation history can be provided to the user.
  • a seventh aspect of the present invention is the electronic file management method, wherein the information on the operation history of the electronic file includes the number of events generated by the executed operation for each period.
  • the user can grasp the progress of work on the electronic file.
  • An eighth aspect of the present invention provides a computer-readable recording medium that stores a program for managing an electronic file, detects an event related to an operation of an electronic file, and collects the detected event in a database.
  • This is a computer-readable recording medium that stores a program that provides a user with information on the operation history of an electronic file based on the contents of a database that collects events, and a program that executes.
  • FIG. 1 is a flowchart showing the operation of electronic file management in the present embodiment.
  • FIG. 2 is an explanatory diagram of the storage table.
  • FIG. 3 is an explanatory diagram of the family register table.
  • FIG. 4 is an explanatory diagram of the configuration table.
  • FIG. 5 is an explanatory diagram of the event history table.
  • FIG. 6 is an explanatory diagram of a table showing examples of events to be collected and operations performed in accordance with those events.
  • FIG. 7 is an explanatory diagram illustrating a software configuration of the electronic file operation program.
  • FIG. 8 is a flowchart illustrating an operation of the information providing program.
  • FIG. 9 is an explanatory diagram illustrating a display example of information by the information providing program.
  • FIG. 10 is a flowchart showing the operation of the information providing program.
  • FIG. 11 is an explanatory diagram illustrating a display example of information by the information providing program.
  • Figure 12 is a histogram that displays the number of events generated by operations performed on electronic files over time.
  • FIG. 13 is an explanatory diagram illustrating an example of a state of updating and diverting an electronic file.
  • the present invention manages electronic files in the following two steps. A schematic diagram of these two steps is shown in FIG.
  • step S111 of FIG. 1 events generated by operating the electronic file are collected in a database. Also, in step S1-2, based on the collected events, information including the diversion and diversion of the electronic file is provided to the user.
  • a characteristic of the first embodiment is that the event performed in step S1-1 is collected. Collection using an electronic file operation program. As described above, as a conventional electronic file operation program, for example, Microsoft Explorer or the like is known.
  • the electronic file operation program described in the first embodiment is a program for moving / copying / deleting an electronic file in the same manner as the explorer.
  • a characteristic of this electronic file operation program is that events that occur with the operation of the electronic file are stored in a predetermined database as appropriate. As described above, in the first embodiment, since the electronic file operation program automatically accumulates events in the database with the electronic file operation, the user does not need to perform any special operation for file management. do not have to.
  • the database handled in the present embodiment is composed of four types of tables. These tables are a storage tape tray 100, a family register tape tray 102, a constituent tape tray 104, and an event history table 106. Illustrations of these tables are shown in Figures 2, 3, 4, and 5.
  • the storage table 100 is a table for storing information of each electronic file. As shown in FIG. 2, each entry of the storage tape storage 100 is an electronic file or folder. That is, this storage table 100 stores not only electronic files but also information on so-called folders. Each entry contains the following items. That is, the items are "sequence number”, “storage ID”, “format”, “state”, “offline”, “creation date and time”, “update date and time”, “reference date and time”, “reference count” and "update count”.
  • the “sequence number” is a serial number assigned to each entry in this template.
  • the “storage ID” is the ID of the electronic file or folder indicated by the entry. D.
  • Form indicates whether the entry indicates an electronic file or a folder. For a folder, the value of this item is “Folder”, and for an electronic file, the value of this item is “File”.
  • “Status” indicates whether the electronic file or folder is currently connected to the system. Specifically, the value of this item is “ONL I NE” when connected and usable, and “ ⁇ FF-LI NE” when disconnected and unavailable. In addition, the value of this item is “RE PLI CAT I ⁇ N” when a copy is provided in another system, etc., and “VO I D” when the copy has already been deleted.
  • Offline refers to the name of storage that is currently disconnected and unavailable. For example, this corresponds to the case where an FD or the like has been removed from the drive device. In this case, the name of the FD that is extracted is the value of this item.
  • “Creation date and time” indicates the date and time when the electronic file or folder was created. In FIG. 2, the information on the time is omitted and only the date is described. However, it is preferable that the information on the time is also included in the storage table 100.
  • Update date and time indicates the date and time when the electronic file or folder was last updated.
  • information relating to the input time, in which only the date is described be included in the storage table 100 in the same manner as the above-mentioned creation date.
  • Referenced date indicates the date and time when the electronic file or folder was last referenced. Again, it is desirable to include information about the time.
  • Reference count refers to the number of times the electronic file or folder has been created since it was created. Represents the number of times
  • Numberer of updates indicates the number of updates since the electronic file or folder was created.
  • the family register table 102 is a table for storing information of each electronic file. As shown in FIG. 3, each entry of the family register table 102 has items of “sequence number”, “ID”, “parent ID”, “format”, and “creation event”.
  • Sequence number is a sequential number assigned to each entry in this table.
  • ID is the ID of the electronic file or folder indicated by the entry.
  • the “parent ID” is the above-mentioned ID of the “diversion source” of the electronic file indicated by the entry.
  • the diversion source is, for example, when an electronic file is created by copying another electronic file, it means that the contents of the electronic file of the copy source are diverted.
  • the original electronic file that was the source of the data of the electronic file is considered to be “diverted source” and is indicated by “parent ID”.
  • this table contains data indicating the electronic file that was the source of the contents of a certain electronic file.
  • this table is called the family register table 102 because it represents the characteristics of a certain electronic file. The case of “diversion” will be described in detail in the actual storage operation.
  • Form indicates whether the entry indicates an electronic file or a folder. If it is a folder, the value of this item is "Fol "PC screen 30", and in the case of an electronic file, the value of this item is "file”.
  • “Creation event” refers to the event that directly caused the creation of the electronic file or folder. If the electronic file was created by copying, the value of this item would be “co py”, and if it was created by moving, it would be “mo V e”. In addition, when newly created, the value of this item is “create”. In the case of new creation, the value of the parent ID is 0, as described above, because there is no electronic file of the parent as the diversion source.
  • the configuration table 104 is a table representing the tree structure of each electronic file or folder. That is, the configuration table 104 is a table for storing information on the hierarchical structure in the file system. As shown in FIG. 4, each entry of the configuration table 104 has items of “sequence number”, “node ID”, “parent ID”, and “type”.
  • Sequence number is a sequential number assigned to each entry in this table.
  • Node ID is the ID of the electronic file or folder indicated by the entry 1, and is the ID on the file system. That is, in a file system having a tree-structured hierarchical structure, electronic files and folders correspond to nodes in the tree structure. The ID on the file system for identifying each node is a node ID.
  • Parent ID is the ID of the folder that is the parent of the electronic file or folder indicated by the entry. In other words, in a tree structure, each node, except for the root, always has a "parent" node. This item is the ID of this parent node. It goes without saying that a parent can be a folder.
  • Form indicates whether the entry indicates an electronic file or a folder. For a folder, the value of this item is “Folder”, and for an electronic file, the value of this item is “File”.
  • the event history table 106 is a table that stores all events that occur as a result of a file operation in the file system. As shown in FIG. 5, each entry in the event history table 106 has items of “sequence number”, “node ID”, “occurrence time”, “format”, and “content”.
  • Sequence number is a sequential number assigned to each entry in this table.
  • Node ID is the ID of the node where the event indicated by the entry has occurred. 1.4.3 Time of occurrence
  • “Occurrence time” is the time at which the event indicated by the entry 1 has occurred.
  • Form indicates the type of event indicated by the entry. The types of events collected in the present embodiment will be described later in detail.
  • Content is the content of the event indicated by the entry. For example, if it is a copy, the copy source and the electronic file name of the copy destination are described.
  • FIG. 6 is a diagram illustrating examples of events handled by the electronic file operation program and operations performed by the electronic file operation program according to the events in the present embodiment.
  • 2.1 create create is an event that occurs when a new electronic file or folder is created.
  • the electronic file operation program operates each table as follows.
  • the electronic file operation program first adds an entry of a newly created electronic file or folder to the storage table 100.
  • the electronic file operation program similarly adds an entry of a newly created electronic file or folder to the family register table 102.
  • the newly created electronic file is not a diversion of the existing electronic file, so the parent ID value is “0” as described above.
  • the electronic file operation program also adds a newly created electronic file or folder entry to the configuration table 104.
  • the electronic file operation program also adds an entry of the occurred event to the event history table 106.
  • the "format” is “create”
  • the "content” describes the name of the created electronic file or folder.
  • the electronic file operation program first adds an entry of a newly copied electronic file or folder to the storage table 100 in principle.
  • the copy destination is an existing electronic file with the same name
  • the existing entry is updated.
  • the copy source and the copy destination are specified.
  • the copy destination electronic file etc. already exists, the existing electronic file etc. will be replaced with the copy source electronic file. It is.
  • the electronic file operation program adds an entry of a newly created electronic file or folder to the family register table 102.
  • the new entry added has a “parent ID” for the copy source. In other words, A child entry is created.
  • the family register table 102 has a plurality of entries such as electronic files with the same name, which are identified by a sequence number or the like.
  • the electronic file operation program adds an entry of a newly created electronic file or folder to the configuration table 104 in the same manner as the storage table 100. Similarly, if the copy destination is an existing electronic file with the same name, the existing entry is updated.
  • the electronic file operation program also adds an entry of the occurred event to the event history table 106.
  • the “format” is “co py”
  • the “contents” describe the names of the electronic files or folders at the copy source and the copy destination.
  • moVe is an event that occurs when an electronic file or folder is moved.
  • the electronic file operation program operates each table as follows.
  • the electronic file operation program first adds the entry of the newly moved electronic file or folder to the storage table 100 in principle, and deletes the entry of the source electronic file, etc. I do. However, if the copy destination is an existing electronic file with the same name, the existing entry is updated.
  • the electronic file operation program adds an entry of a newly created electronic file or folder to the family register table 102.
  • the content of the new entry added is basically the same as the source electronic file.
  • the electronic file operation program executes the above-mentioned storage for the configuration table 104.
  • an entry of a newly created electronic file or folder is added, and an entry of a source electronic file or the like is deleted.
  • the copy destination is an existing electronic file with the same name, the existing entry is updated.
  • the electronic file operation program also adds an entry of the occurred event to the event history table 106.
  • the “format” is “move”
  • the “contents” are the names of the source and destination electronic files or folders.
  • d e 1 e t e is an event that occurs when an electronic file or folder is deleted.
  • the electronic file operation program operates each table as follows.
  • the electronic file operation program first updates the contents of the deleted electronic file or folder entry in the storage table 100, and does not delete the entry itself. This is to keep a record that it has been deleted.
  • the electronic file operation program similarly updates the contents of the deleted electronic file or folder entry in the family register table 102.
  • the electronic file operation program deletes the deleted electronic file or folder entry from the configuration table 104. This is because it no longer exists in the file system and cannot be used.
  • the electronic file operation program also adds an entry of the event that has occurred to the event history table 106.
  • the format is “de1ete”
  • the “content” is the name of the deleted electronic file or folder.
  • c1ose is an event that occurs when reference is ended.
  • the electronic file operation program writes the event entry into the event history table 106. Add one.
  • the "format” is “open” or “c1ose”
  • the "content” describes the name of the electronic file to be referenced.
  • the electronic file operation program updates the “reference count” of the corresponding entry of the storage table 100 and the like.
  • the electronic file operation program does not perform other stapling operations for open and close.
  • edit st a rt is an event that occurs when editing of an electronic file is started, and “ed it end” is an event that occurs when editing is completed. Regardless of which of the following events occurs, the electronic file operation program adds an entry of the occurred event to the event history table 106.
  • the “format” is “edit st art” or “edit end”, and the “content” describes the name of the electronic file to be edited.
  • the electronic file operation program locks silently by updating the “content” of the corresponding entry 1 of the storage table 100 to “editing” or the like, and Make the contents of the electronic file inoperable. With this, exclusive control of the file is performed.
  • the electronic file operation program restores the “content” of the corresponding entry in the storage table 100 to the original value, and releases the implicit lock.
  • the electronic file operation program does not perform any other table operations for open and close.
  • s ave is an event that occurs when an electronic file is saved, and s ave as is an event that occurs when an electronic file is saved under another name.
  • the electronic file operation program adds an entry of the occurred event to the event history table 106.
  • the “type” is “sa V e” or “sa V eas”
  • “Contents” describes the name of the electronic file to be saved.
  • the electronic file manipulation program updates the corresponding entry in the storage table 100.
  • the electronic file operation program updates the corresponding entry in the storage table 100, and if not, the new electronic file. Add a new entry for the file.
  • the electronic file manipulation program can collect various other events other than the events described above. For example, when an electronic file operating program other than the electronic file operating program is used in parallel, a new electronic file may be found in the file system separately from the electronic file operating program. In such a case, an event called find is generated, and the processing is performed by the electronic file operation program. The processing of this fi n d is the same as the above create
  • FIG. 7 is an explanatory diagram showing the software configuration of the electronic file operation program. The software configuration will be described based on this diagram.
  • an event is first detected by the event detection unit 10.
  • the detected event is transmitted to the central event handler section 12.
  • the central event handler unit 12 determines an operation for each table as described above according to each transmitted event, and instructs each operation to the management unit.
  • the management unit is composed of a storage management unit 14, a family register management unit 16, a configuration management unit 18, and a history management unit 20.
  • the storage management unit 14 operates the storage table 100 based on an instruction from the central event handler unit 12. Further, the family register management unit 16 operates the family register table 102 based on the instruction of the central event handler unit 12. Further, the configuration management unit 18 operates the configuration table 104 based on an instruction from the central event handler unit 12. Similarly, the history management unit 20 is a central event handler. The event history table 106 is operated based on the instruction of the unit 12.
  • the user is provided with information including the relationship of diversion and diversion of electronic files.
  • the program for this provision is called the information provision program.
  • the information provided by the information providing program includes (1) ancestor / descendant information indicating a diversion / diversion relationship of the electronic file, and (2) history information of the electronic file.
  • a group of electronic files that is a diversion source electronic file of a predetermined electronic file, and a group of further diversion source electronic files of the diversion source electronic file are referred to as “ancestors”.
  • the ancestor of an electronic file is the electronic file that is the source of the electronic file or the set of electronic files that is the source of any electronic file included in the ancestor.
  • the information providing program creates an HTML file including the following contents.
  • FIG. 8 is a flowchart showing the operation of the information providing program when providing such information.
  • step S8-1 in FIG. 8 first, the information providing program searches the family register table 106 for an electronic file specified by the user, and finds the parent electronic file from the parent ID. Further, in step S8-2, the information providing program searches the storage table 100 for the electronic file specified by the user, and determines the date and time when the parent electronic file was diverted from the creation date and time. You can know.
  • step S8_3 the information providing program searches the storage table 100 for the parent electronic file and finds the date and time when the parent electronic file was last updated from the update date and time. be able to.
  • step S8-4 the information providing program searches the family register table 102 for the electronic file of the parent, and can determine from the parent ID whether the grandfather's electronic file exists. If the grandfather's electronic file exists, the processing from step S81-11 is continued for the parent's electronic file.
  • step S8-5 an HTML file is created based on the extracted information and provided to the user.
  • the user can browse this information using a browser.
  • An example of information display is shown in FIG.
  • three types of electronic files are shown: a parent's electronic file, a grandfather's electronic file, and a great-grandfather's electronic file.
  • information on the date of diversion and the date of last update are also displayed.
  • a group of electronic files to which a predetermined electronic file is diverted, and further to the diverted electronic file are referred to as “descendants”.
  • a descendant of an electronic file is an electronic file to which the electronic file is diverted, or a set of electronic files to which any of the electronic files included in the descendant is diverted.
  • the information providing program When a user requests the display of a descendant's electronic file for a given electronic file, the information providing program creates an HTML file containing the following contents.
  • FIG. 10 is a flowchart showing the operation of the information providing program when providing such information.
  • step S10-1 in FIG. 10 first, the information providing program searches the family register table 106 for an entry including the electronic file designated by the user as the parent ID.
  • Such a search can be performed quickly by using a DBMS (database management system).
  • DBMS database management system
  • each table described above is constructed using ORACLE (ORACLE is a registered trademark of ORACLE Corporation) which is one of DBMS. Therefore, the above search can be performed quickly by using the functions of the leverage DBMS.
  • the present invention can be implemented even if the above table is configured without using the DBMS.
  • step S10-2 the information providing program searches the storage table 100 for each electronic file that is a descendent of the search, and, based on the creation date and time, the parent electronic file (instructed by the user). Electronic file) can be known.
  • step S10-3 the information providing program searches the storage table 100 for each of the descendant electronic files, and, based on the update date and time, the date and time when the descendant electronic file was last updated. You can know.
  • step S10-4 the information providing program determines whether or not there is an electronic file having each of the descendant electronic files as a parent ID, that is, an electronic file that is a grandchild of the designated electronic file. From the family register table 102 You. If there are more grandchild electronic files, the processing from step S10-1 is continued for the electronic files of each of the retrieved children.
  • step S10-5 an HTML file is created based on the extracted information and provided to the user. Users can browse this information using a browser.
  • An example of information display is shown in Fig. 11.
  • one child's electronic file, one grandchild's electronic file, two great-grandchildren's electronic files, and two great-grandchildren's electronic files, totaling 6 Types of electronic files are shown.
  • information on the diverted date and the last update date is also displayed.
  • the display indicating the tree structure is displayed in order to display the state in which such branching has occurred to the user in an easily understandable manner. As shown in Fig. 11, the tree display makes it possible to visually and clearly understand what diversion and diversion relationship (so-called parent-child relationship) exists between electronic files.
  • all events generated by operations related to the electronic file are stored in the event history table 106. Therefore, it is possible to know what kind of operation has been performed on a predetermined electronic file or on a group of electronic files in a certain folder.
  • the information providing program searches the history of operations performed on such an electronic file based on a request from the user, and creates an HTML file. Users can browse this using a browser.
  • Various methods are conceivable for displaying the operation history of the electronic file. For example, it is conceivable to present the number of predetermined operations in a certain period in a table. If the form is easy to visually grasp, the number of operations should be displayed in a histogram, etc. Are also preferred. Displaying a histogram makes it easier to grasp the number of operations for each period.
  • knowing the operation on a certain electronic file can contribute to predicting when the electronic file will be completed.
  • the density at which operations on electronic files are performed rises over time, it is judged that development has entered a good state.
  • the density is decreasing, it can be judged that the development has reached the end. Therefore, presenting the past history to the user has the effect of making it easier to predict the future.
  • FIG. 12 An example of such a histogram display is shown in Figure 12.
  • the horizontal axis is the passage of time
  • the vertical axis is the number of all events that occurred by operations performed on the electronic file (group) per unit period.
  • the number of all events is displayed, but it is also preferable to display only a limited number of types.
  • a graph such as a histogram
  • a histogram was created using only the number of all events that occurred without considering the type of operation in particular. Changes, and it is easier to grasp the extent of development progress, and it is easier to predict future progress.
  • the accuracy of prediction can be further improved by displaying the size of the electronic file and the like.
  • Recording media include those capable of magnetically or optically recording digital data, such as floppy disks, CDROMs, and hard disks, as well as those that physically store data, such as MOs, DVDs, flash memories, and SRAMs. Any recording medium that can be recorded and played back may be used.
  • information on the relevance of electronic files can be provided.
  • an electronic file that is related to the electronic file can be easily searched, so that quicker development can be performed.

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)

Abstract

Cette invention concerne un procédé de gestion de fichiers électroniques permettant d'appréhender des relations, dont le rapport entre le processus d'appropriation d'un fichier électronique et son appropriation. A l'opération S1-1, les événements engendrés par la mise en oeuvre de fichiers électroniques sont recueillis dans la base de données. Un programme de gestion de fichiers électroniques accumule automatiquement des événements dans la base de données en réponse aux utilisations des fichiers électroniques. Par voie de conséquence, l'utilisateur n'a pas besoin de recourir à des opérations spéciales pour la gestion des fichiers. A l'opération S1-2, des informations sur les rapports entre le processus d'appropriation de fichiers électroniques et leur appropriation proprement dite sont fournies au client conformément aux événements recueillis.
PCT/JP2000/001630 1999-05-27 2000-03-17 Procede de gestion des fichiers electroniques et support lisible par ordinateur pour enregistrement du fichier de gestion electronique WO2000073909A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU31933/00A AU3193300A (en) 1999-05-27 2000-03-17 Electronic file management method and computer-readable recorded medium on whichprogram for managing electronic file is recorded

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP11147516A JP2000339206A (ja) 1999-05-27 1999-05-27 電子ファイル管理方法及び電子ファイルを管理するプログラムを格納したコンピュータ読み取り可能な記録媒体
JP11/147516 1999-05-27

Publications (1)

Publication Number Publication Date
WO2000073909A1 true WO2000073909A1 (fr) 2000-12-07

Family

ID=15432114

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2000/001630 WO2000073909A1 (fr) 1999-05-27 2000-03-17 Procede de gestion des fichiers electroniques et support lisible par ordinateur pour enregistrement du fichier de gestion electronique

Country Status (3)

Country Link
JP (1) JP2000339206A (fr)
AU (1) AU3193300A (fr)
WO (1) WO2000073909A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4199193B2 (ja) * 2002-09-30 2008-12-17 富士通株式会社 関連情報管理方法、プログラム及び装置
JP2005267339A (ja) * 2004-03-19 2005-09-29 Fuji Xerox Co Ltd ファイル管理システム、ファイル情報提示方法
JP2006079418A (ja) 2004-09-10 2006-03-23 Fujitsu Ltd 記憶制御装置、制御方法及びプログラム
JP2009199356A (ja) * 2008-02-21 2009-09-03 Osaka Univ ファイルイベント相関生成装置、管理装置、及びコンピュータプログラム
JP5515914B2 (ja) * 2010-03-19 2014-06-11 富士通株式会社 ファイル管理プログラム、ファイル管理装置及びファイル管理方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0363734A (ja) * 1989-07-31 1991-03-19 Fuji Xerox Co Ltd ファイル管理運用方式
JPH05313969A (ja) * 1992-05-13 1993-11-26 Hitachi Ltd ファイル一覧表示方法
JPH06243132A (ja) * 1993-02-19 1994-09-02 Fuji Xerox Co Ltd 文書編集管理装置
JPH0962658A (ja) * 1995-08-21 1997-03-07 Hitachi Inf Syst Ltd 文書間リンク処理システム
JPH09223055A (ja) * 1996-02-14 1997-08-26 Nippon Steel Corp ツリー表示方法及びツリー表示装置
JPH09288671A (ja) * 1996-04-22 1997-11-04 Hitachi Ltd ドキュメント作成支援装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0363734A (ja) * 1989-07-31 1991-03-19 Fuji Xerox Co Ltd ファイル管理運用方式
JPH05313969A (ja) * 1992-05-13 1993-11-26 Hitachi Ltd ファイル一覧表示方法
JPH06243132A (ja) * 1993-02-19 1994-09-02 Fuji Xerox Co Ltd 文書編集管理装置
JPH0962658A (ja) * 1995-08-21 1997-03-07 Hitachi Inf Syst Ltd 文書間リンク処理システム
JPH09223055A (ja) * 1996-02-14 1997-08-26 Nippon Steel Corp ツリー表示方法及びツリー表示装置
JPH09288671A (ja) * 1996-04-22 1997-11-04 Hitachi Ltd ドキュメント作成支援装置

Also Published As

Publication number Publication date
AU3193300A (en) 2000-12-18
JP2000339206A (ja) 2000-12-08

Similar Documents

Publication Publication Date Title
US5553216A (en) Structured database system together with structure definition frame storing document body data
US5715413A (en) Dragging and dropping with an instantiation object
US5754840A (en) System, method, and computer program product for developing and maintaining documents which includes analyzing a patent application with regards to the specification and claims
JP4308587B2 (ja) 文書群管理装置
JP3639410B2 (ja) コンピュータ・システムおよびコンピュータ・システムを操作する方法
JPH09128380A (ja) 文書蓄積管理システム
AU2005259999A1 (en) Methods and systems for managing data
JP2004046796A (ja) ディレクトリ管理プログラム、オブジェクト表示プログラム、ディレクトリ管理方法及びディレクトリ管理装置
JP2005515557A (ja) 法典の履歴版及び現行版を提供する動的な法律データベース
US5586239A (en) Computer controlled graphics display system for supporting information classification
JP2009129017A (ja) 文書移行支援システム、監視装置、文書移行支援装置、方法、およびプログラム
JP2003337728A (ja) データファイル履歴管理方法およびその装置
KR20030075501A (ko) 특허 데이터베이스로 부터 대상 특허의 가계 경로를 빠른시간내에 분석하여 제공하는 방법
US20080140608A1 (en) Information Managing Apparatus, Method, and Program
WO2000073909A1 (fr) Procede de gestion des fichiers electroniques et support lisible par ordinateur pour enregistrement du fichier de gestion electronique
JP4199193B2 (ja) 関連情報管理方法、プログラム及び装置
JPH10143418A (ja) 文書情報更新監視装置および文書情報の更新監視方法
JPH08137887A (ja) 情報記憶検索装置
JP2006048521A (ja) 文書検索装置及びその制御方法、並びに制御プログラム
JPH0934906A (ja) 図書管理装置
US20020062305A1 (en) Database management systems
JPH0736684A (ja) ドメイン指向部品管理方法
JPH05108457A (ja) ハイパーテキスト情報管理装置
JPH0546451A (ja) フアイル検索装置
JP3058086B2 (ja) データの版管理方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU BR CA CN KR NZ RU SG US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

WWE Wipo information: entry into national phase

Ref document number: 09720735

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2000909697

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWW Wipo information: withdrawn in national office

Ref document number: 2000909697

Country of ref document: EP