US20100106699A1 - Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof - Google Patents
Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof Download PDFInfo
- Publication number
- US20100106699A1 US20100106699A1 US12/573,502 US57350209A US2010106699A1 US 20100106699 A1 US20100106699 A1 US 20100106699A1 US 57350209 A US57350209 A US 57350209A US 2010106699 A1 US2010106699 A1 US 2010106699A1
- Authority
- US
- United States
- Prior art keywords
- list
- document
- user
- client apparatus
- server apparatus
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
Definitions
- the present invention relates to a client apparatus and a server apparatus that manage documents used in a workflow, a document management system, a document management method, and a medium storing a program thereof.
- An example of generally known solving means includes a workflow system.
- a workflow system a flow of work is defined in advance as a workflow, and documents necessary for the status of the defined workflow are attached to advance the process.
- a workflow “create (regular employee) ⁇ scrutinize (section chief) ⁇ approve (department chief)” is created in advance.
- an application is attached to “create” of the flow, and approvals of the section chief and the department chief are provided to the document in “scrutinize” and “approve”, respectively.
- a method is often implemented, in which a document management system and a To-Do list function thereof are used to simply associate the electronic documents and the work.
- each user can provide a flag, such as a To-Do flag, to the documents on the document management system and can also describe the work content.
- documents with flag can be listed and displayed by use of To-Do folders, etc.
- the user can set a flag to a document that needs to be processed and can describe the work content to be processed.
- the user can also check, as necessary, the list of the documents that need to be processed based on the To-Do folders. Therefore, the documents and the work that requires processing for the documents can be associated.
- Japanese Patent Laid-Open No. 2000-123071 proposes a system in which other users can add items to the To-Do list.
- Japanese Patent Laid-Open No. 2000-123071 describes consolidated management of individual tasks and group tasks in the To-Do list. However, the difference in operations between the document operation and the To-Do list management in the document management system is not particularly considered or described.
- the present invention provides a client apparatus, a server apparatus, a document management system, a document management method, and a medium storing a program capable of reducing the burden of the user and efficiently processing necessary work when a document-based operation is executed in a document management system.
- the present invention in its first aspect provides a document management system that includes a client apparatus and a server apparatus and that manages documents used in a workflow, the client apparatus comprising: a generating unit configured to generate a list associating a document, an operation for the document, and a user and to transmit the list to the server apparatus; and an acquisition unit configured to acquire information including a document, an operation for the document, and a user when the operation for the document is received from the user and to transmit the information to the server apparatus, the server apparatus comprising: a storage unit configured to receive the list from the client apparatus and to store the list; and a search unit configured to receive the information from the client apparatus and to search the storage unit for a list including information matching the information to transmit the list to the client apparatus, the client apparatus comprising: a display unit configured to receive and display the list searched by the search unit.
- the present invention in its second aspect provides a document management method executed in a document management system that includes a client apparatus and a server apparatus and that manages documents used in a workflow, the method comprising: a generating step in the client apparatus for generating a list associating a document, an operation for the document, and a user and for transmitting the list to the server apparatus; a storage step in the server apparatus for receiving the list from the client apparatus and for storing the list; an acquisition step in the client apparatus for acquiring information including a document, an operation for the document, and a user when the operation for the document is received from the user and for transmitting the information to the server apparatus; a search step in the server apparatus for receiving the information and for searching a list including information matching the received information from the list stored in the storage step to transmit the list to the client apparatus; and a display step in the client apparatus for receiving and displaying the list searched in the search step.
- the present invention in its third aspect provides a client apparatus used in a document management system that includes the client apparatus and a server apparatus and that manages documents used in a workflow, the client apparatus comprising: a generating unit configured to generate a list associating a document, an operation for the document, and a user and to transmit the list to the server apparatus; an acquisition unit configured to acquire information including a document, an operation for the document, and a user when the operation for the document is received from the user and to transmit the information to the server apparatus; and a display unit configured to receive and display the list searched by the server apparatus.
- the present invention in its fourth aspect provides a server apparatus used in a document management system that includes a client apparatus and the server apparatus and that manages documents used in a workflow, the server apparatus comprising: a storage unit configured to receive a list generated in the client apparatus and to store the list; and a search unit configured to receive information including a document, an operation for the document, and a user who performed the operation from the client apparatus and to search the storage unit for a list including information matching the information to transmit the list to the client apparatus.
- the present invention in its fifth aspect provides a computer-readable medium storing a document management program for managing documents used in a workflow in a document management system including a client apparatus and a server apparatus, the program causing a computer, which is the client apparatus, to perform functions to: generate a list associating a document, an operation for the document, and a user and transmit the list to the server apparatus; acquire information including a document, an operation for the document, and a user when the operation for the document is received from the user and transmit the information to the server apparatus; and receive and display a list searched by the server apparatus.
- the present invention in its sixth aspect provides a computer-readable medium storing a document management program for managing documents used in a workflow in a document management system that includes a client apparatus and a server apparatus and that includes a memory for receiving and storing a list generated by the client apparatus, the program causing the server apparatus to perform functions to: receive information including a document, an operation for the document, and a user who performed the operation from the client apparatus and search the memory for a list including information matching the information to transmit the list to the client apparatus.
- the burden of the user can be reduced, and necessary work can be efficiently processed when a document-based operation is executed in a document management system.
- FIG. 1 is a diagram showing a configuration of a document management system according to a first embodiment of the present invention
- FIG. 2 is a diagram showing an example of a To-Do list creation instruction screen
- FIG. 3 is a diagram showing an example of a To-Do list creation screen
- FIG. 4 is a diagram showing an example of the content of a To-Do list database
- FIG. 5 is a flow chart showing a procedure of a display process of a To-Do list according to the present embodiment
- FIG. 6 is a diagram showing an example of a display screen of the To-Do list
- FIG. 7 is a flow chart showing a procedure of a creation process of the To-Do list according to the present embodiment
- FIG. 8 is a diagram showing an example of the content of an association database of a document operation according to a second embodiment
- FIG. 9 is a flow chart showing a procedure of a display process of the To-Do list according to the present embodiment.
- FIG. 10 is a diagram showing an example of an operation change presenting screen
- FIG. 11 is a flow chart showing a procedure of an operation change process according to the present embodiment.
- FIG. 12 is a diagram showing an example of a conventional To-Do list creation screen
- FIG. 13 is a diagram showing an example of the content of a conventional To-Do list database
- FIG. 14 is a flow chart showing a procedure of a display process of a conventional To-Do list
- FIG. 15 is a diagram showing an example of a display screen of the conventional To-Do list.
- FIG. 16 is a diagram showing a configuration of an information processing apparatus applied to the document management system.
- FIG. 1 is a block diagram showing a system configuration in the embodiments according to the present invention.
- the present system is constituted by a client apparatus and a server apparatus.
- Client software 1000 is installed on the client apparatus of the document management system.
- Server software 1100 is installed on the server apparatus of the document management system.
- the software is operated on an OS of a computer (client apparatus or server apparatus) constituted by a CPU, a RAM, a ROM, an HDD, etc.
- a user interface 1001 is a user interface unit.
- the system receives a user operation through the user interface 1001 and transmits the user operation to a command control unit 1002 .
- the command control unit 1002 uses a communication control unit 1003 and a To-Do list control unit 1004 according to an operation request of the user and returns the operation result to the user interface 1001 .
- the communication control unit 1003 communicates with the server software 1100 according to a command of the command control unit 1002 .
- the To-Do list control unit 1004 controls a To-Do list according to a command of the command control unit 1002 .
- a communication control unit 1101 communicates with the client software 1000 according to a command of the document management control unit 1102 .
- the document management control unit 1102 uses a database control unit 1103 according to an operation request of the client software 1000 and returns the operation result to the client software 1000 through the communication control unit 1101 .
- the database control unit 1103 controls a document database 1104 , a To-Do list database 1105 , and a user management database 1106 according to a command of the document management control unit 1102 .
- the document database 1104 stores document information.
- the To-Do list database 1105 is a To-Do list database and stores To-Do list information.
- the user management database 1106 is a user management database and stores user information.
- FIG. 16 is a diagram showing a configuration of a general information processing apparatus used in the client apparatus or the server apparatus of the present document management system.
- a computer 1600 comprises a CPU 1601 .
- the CPU 1601 controls document processing including the processes of the embodiments and controls the execution of a printing process or a print control process based on the document processing.
- the CPU 1601 comprehensively controls the components connected to a system bus 1611 .
- the ROM for programs of the ROM 1603 or the external memory 1610 stores an operating system program (hereinafter, “OS”), etc., as a control program of the CPU 1601 .
- OS operating system program
- a ROM for fonts of the ROM 1603 or the external memory 1610 stores font data, etc., used for document processing.
- a ROM for data of the ROM 1603 or the external memory 1610 stores various data used for document processing, etc.
- a RAM 1602 functions as a main memory, a work area, etc., of the CPU 1601 .
- a keyboard controller (KBC) 1604 controls key input from a keyboard 1608 or a pointing device not shown.
- a CRT controller (CRTC) 1605 controls display by a CRT display (CRT) 1609 .
- a disk controller (DKC) 1606 controls access to the external memory 1610 by a hard disk (HD), etc., that stores various programs or applications, etc.
- a network interface 1607 executes a communication control process with an external device through a network.
- the CPU 1601 opens various windows registered in advance based on a command instructed by a mouse cursor not shown, etc., on the CRT 1609 and executes various data processing. For example, when the user executes printing, windows related to the print setting are opened, and settings, such as print setting and print mode selection, of a print processing method for the print control apparatus can be performed.
- a flow of a conventional To-Do list creation process will be described with reference to FIGS. 2 , 12 , and 13 .
- the user first uses a To-Do list creation instruction screen shown in FIG. 2 to select documents through the client software 1000 and instructs creation of a To-Do list for the documents.
- the client software 1000 displays a To-Do list creation screen shown in FIG. 12 to the user, the screen displaying a comment input field.
- the client software 1000 After the user inputs comments and notifies that all input is finished, the client software 1000 receives the notification through the user interface 1001 . Having received the notification, the client software 1000 notifies the reception and the user who created the To-Do list to the server software 1100 through the communication control unit 1003 . After receiving the notification, the server software 1100 stores the created To-Do list in the To-Do list database 1105 .
- the To-Do list database created in the To-Do list database 1105 includes information as shown in FIG. 13 .
- the target users and the target documents may be IDs that can uniquely identify the targets.
- a conventional To-Do list display method will be described with reference to FIGS. 14 and 15 .
- the user first instructs to display the To-Do list through the user interface 1001 .
- the client software 1000 reports the operation execution users to the server software 1100 .
- the server software 1100 creates a To-Do list to be displayed in the document management control unit 1102 .
- the following process is executed in the document management control unit 1102 .
- the operation execution users are acquired (step S 1401 ).
- To-Do lists are then acquired one by one from the To-Do list database 1105 , and the following process is executed between steps S 1402 to S 1405 .
- step S 1403 Whether the target users of the To-Do list are identical to the operation execution users is first checked. If they are not identical, the next checking of To-Do list is performed. If they are identical, the process proceeds to step S 1404 .
- step S 1404 the To-Do list is set as a To-Do list to be displayed. If there is one or more To-Do list in the To-Do list to be displayed after the process is executed for all To-Do lists, the list is returned to the client software 1000 . If there is no list, that fact is returned to the client software 1000 (step S 1406 ).
- the client software 1000 After receiving the display To-Do list from the server software 1100 , the client software 1000 presents the list to the user as shown in FIG. 15 .
- the user can only check the details of the To-Do list on the To-Do list displayed as in FIG. 15 .
- FIG. 7 A procedure of a To-Do list creation process in the present embodiment will now be described with reference to FIGS. 2 , 3 , 4 , and 7 .
- the steps in FIG. 7 are processed by the CPU 1601 in the client apparatus.
- the user first selects documents through the client software 1000 as shown in FIG. 2 and instructs to create a To-Do list of the documents. After receiving the request of the user through the user interface 1001 , the client software 1000 transmits the request to the server software 1100 through the communication control unit 1003 .
- the server software 1100 acquires a target operation list from the To-Do list database 1105 and a target user list from the user management database 1106 and returns the result to the client software 1000 .
- the client software 1000 displays a To-Do list creation screen as shown in FIG. 3 to the user, the screen displaying a list of the target operations and the target users.
- a target user list and a target operation list are added in the present embodiment as compared to FIG. 12 .
- the user selects, for example, “User A” and “User B” in “Target User List” for the documents and selects “Edit” in “Target Operation List” as a target operation of the users.
- An instruction for modification, etc., is described in the comment field.
- the client software 1000 After the user selects the target users and the target operations, inputs a comment, and notifies that all input is finished, the client software 1000 receives the notification through the user interface 1001 . Having received the notification, the client software 1000 generates a To-Do list in the To-Do list control unit 1004 .
- the To-Do list control unit 1004 first acquires the target users, the target operations, and the comments (step S 701 ).
- the To-Do list control unit 1004 then acquires the documents as operation targets (step S 702 ).
- the documents as operation targets are combined with the target users, the target operations, and the comments to generate a To-Do list (step S 703 ).
- the client software 1000 transmits the generated To-Do list to the server software 1100 through the communication control unit 1003 .
- the process in steps S 701 to S 703 is an example of list generation in the present embodiment.
- the server software 1100 stores the received To-Do list in the To-Do list database 1105 .
- the target operation list displays “Edit”, “Move Document”, “Copy Document”, “Delete Document”, “Print”, “Set Access Right”, “Add Tag”, etc.
- the To-Do list database created in the To-Do list database 1105 includes information as shown in FIG. 4 .
- the target users and the target documents may be IDs that can uniquely identify the targets.
- the user can select target users and target operations from the lists on the To-Do list creation screen.
- the To-Do list can simply realize a workflow system for passing work from person to person.
- the To-Do list control unit 1004 combines the documents in the To-Do list. Furthermore, as compared to FIG. 13 , an item of target operation is added to the To-Do list database in the present embodiment as shown in FIG. 4 . In this way, comments (To-Do) and personnel in an operation (workflow) for processing the documents can be set in association with the documents upon the creation of the To-Do list in the present embodiment.
- the setting can be executed in the check item as shown in FIG. 3 , and the user can very simply perform the setting operation.
- a To-Do list display method in the present embodiment will now be described with reference to FIGS. 5 and 6 .
- the To-Do list is displayed on the screen of the client according to the process shown in FIG. 5 when the user performs an operation for the documents.
- the steps in FIG. 5 are processed by the CPU 1601 in the server apparatus.
- the user first selects documents from the client software 1000 through the user interface 1001 and gives instructions for specific document operations for the documents. It is assumed here that an edit operation is selected. Having received the user operations, the client software 1000 transmits the user operations, the target documents, and the operation execution users to the server software 1100 .
- the server software 1100 creates a To-Do list to be displayed in the document management control unit 1102 .
- a process as shown in FIG. 5 is executed in the document management control unit 1102 .
- the server software 1100 first acquires the target documents, the user operations, and the operation execution users (step S 501 ).
- To-Do lists are acquired one by one from the To-Do list database 1105 , and the following search process is executed in steps S 502 to S 507 .
- Whether a target document of the To-Do list is identical to a target document of the user operation is determined (step S 503 ). If they are not identical, a loop of steps S 502 to S 507 is repeated for the next determination of the To-Do list. On the other hand, if they are identical, the process proceeds to step S 504 .
- step S 504 Whether the target operation of the To-Do list is identical to the user operation is then determined (step S 504 ). If they are not identical, the loop of steps S 502 to S 507 is repeated for the next determination of the To-Do list. On the other hand, if they are identical, the process proceeds to step S 505 .
- step S 505 Whether the target user of the To-Do list is identical to the operation execution user is then determined (step S 505 ). If they are not identical, the loop of steps S 502 to S 507 is repeated for the next determination of the To-Do list. On the other hand, if they are identical, the process proceeds to step S 506 .
- the To-Do list is set as a To-Do list to be displayed (step S 506 ).
- the list is transmitted to the client software 1000 . If there is no list, that fact is transmitted to the client software 1000 (step S 508 ).
- the client software 1000 Having received the display To-Do list from the server software 1100 , the client software 1000 presents the list to the user as shown in FIG. 6 .
- the user can select whether to advance the process, check details of the To-Do list, or to cancel a desired operation on the displayed To-Do list.
- the user can select “To-Do 1 Related to Operation” and press a button “Check To-Do” to check details of the To-Do list (such as an instruction for modification).
- the user can also press a button “Continue Operation” to advance the edit operation, etc.
- the user can also cancel a desired operation (such as edit operation) with a button “Cancel Operation”.
- a To-Do list related to the operation is automatically displayed when the user edits the document.
- the user can advance the process according to, for example, the instruction described in the comment of the To-Do list. Therefore, the user does not have to treat the To-Do list in a different operation during the operation of the document management system.
- the To-Do list automatically opens in the operation of the document management system. Therefore, the leakage of the content (such as modification) that the user wants the target user to perform in the workflow can be prevented. Only the list related to the document operation is displayed in the To-Do list, and the user can efficiently advance necessary work.
- a simple workflow system is realized by the To-Do list in the present embodiment. Therefore, a special configuration such as a workflow engine is not required, and a system for passing the work from person to person can be realized.
- a second embodiment will now be described.
- a process for creating the To-Do list is the same as in the description of the first embodiment shown in FIG. 7 .
- a To-Do list display method in the present embodiment will be described with reference to FIGS. 8 , 9 , 10 , and 11 .
- a database (table) showing the relationship between the operations as shown in FIG. 8 is added and held in the To-Do list database 1105 of the first embodiment.
- user operations and operations related to the user operations are associated.
- the user first selects documents from the client software 1000 through the user interface 1001 and instructs specific document operations for the documents. It is assumed here that a document display operation is selected. Having received the user operation, the client software 1000 transmits the user operations, the target documents, and the operation execution users to the server software 1100 .
- a To-Do list to be displayed in the document management control unit 1102 is created.
- the document management control unit 1102 executes a process as shown in FIG. 9 .
- the steps in FIG. 9 are processed by the CPU 1601 in the server apparatus.
- the server software 1100 first acquires the target documents, the user operations, and the operation execution users (step S 901 ).
- To-Do lists are acquired one by one from the To-Do list database 1105 , and the following search process is executed in steps S 902 to S 907 .
- Whether a target document of the To-Do list is identical to a target document of the user operation is first determined (step S 903 ). If they are not identical, a loop of steps S 902 to S 907 is repeated for the next determination of the To-Do list. On the other hand, if they are identical, the process proceeds to step S 904 .
- step S 904 The database ( FIG. 8 ) showing the relationship between the operations included in the To-Do list database 1105 is referenced to determine whether there is an operation related to the user operation (step S 904 ). If there is no operation, a loop of steps S 902 to S 907 is repeated for the next determination of the To-Do list. On the other hand, if there is an operation, the process proceeds to step S 905 .
- the process of step S 904 is an example of a second search in the present embodiment.
- step S 905 Whether the target user of the To-Do list is identical to the operation execution user is then determined (step S 905 ). If they are not identical, the loop of steps S 902 to S 907 is repeated for the next determination of the To-Do list. On the other hand, if they are identical, the process proceeds to step S 906 .
- the To-Do list is set as a To-Do list to be displayed (display To-Do list) (step S 906 ).
- the operation related to the list is transmitted to the client software 1000 . If there is no list, that fact is transmitted to the client software 1000 (step S 908 ).
- whether the target related operation (such as editing) is identical to the user operation serves as the determination condition in the display process of the To-Do list when the target user who processes an operation (workflow) including the document executes one process (such as displaying).
- step S 904 shown in FIG. 9 the determination process of step S 504 shown in FIG. 5 may be added to determine whether the target operation is identical to the user operation.
- a To-Do list display method in the present embodiment will now be described with reference to FIG. 11 .
- the client software 1000 determines whether there is a To-Do list in a related operation (step S 1101 ). If there is no list, the operation desired by the user is executed (step S 1104 ), and the present process ends.
- FIGS. 10 and 11 are realized in step S 904 as an example of the second search.
- FIGS. 10 and 11 illustrate an example of “second display”.
- the steps in FIG. 11 are processed by the CPU 1601 in the client apparatus.
- step S 1102 if there is a To-Do list in a related operation, that fact and the list are presented to the user as shown in FIG. 10 (step S 1102 ).
- the user can advance the process of the current operation, switch to the presented operations, or cancel the current operation on the displayed To-Do list.
- the screen shown in FIG. 10 is displayed when the user is performing a display operation.
- the user can advance the process (displaying) with a button “Continue Operation” shown in FIG. 10 .
- the user can also switch the operation to a presented operation (for example, “Edit” set to To-Do 1 of Related Operation) with a “Change Operation” button.
- the user can also cancel the desired operation with a button “Cancel Operation”.
- the user can select the current user operation and operations related to the operation in the present embodiment.
- step S 1103 If “Continue Operation” is determined in step S 1103 , the user performs the desired operation (step S 1104 ), and the process ends.
- step S 1103 If “change operation” is determined in step S 1103 , the user changes the desired operation to an operation associated with the To-Do list (step S 1105 ), and the process ends.
- step S 1103 If “Cancel Operation” is determined in step S 1103 , the user cancels the desired operation (step S 1106 ), and the process ends.
- a To-Do list of operations related to the document operation is automatically displayed. Therefore, for example, the user can advance the process according to an instruction described in a comment of the To-Do list of the designated document operation and can also advance the process according to an instruction described in a comment of the To-Do list of related operations.
- FIG. 6 may be displayed as in the first embodiment if there is no operation related to the user operation and there is an identical target operation when the determination process of step S 504 shown in FIG. 5 is added to step S 904 shown in FIG. 9 .
- both FIGS. 6 and 10 may be displayed, or one screen may display the operations.
- aspects of the present invention can also be realized by a computer of a system or apparatus (or devices such as a CPU or MPU) that reads out and executes a program recorded on a memory device to perform the functions of the above-described embodiment(s), and by a method, the steps of which are performed by a computer of a system or apparatus by, for example, reading out and executing a program recorded on a memory device to perform the functions of the above-described embodiment(s).
- the program is provided to the computer for example via a network or from a recording medium of various types serving as the memory device (e.g., computer-readable medium).
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Document Processing Apparatus (AREA)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/625,687 US9189771B2 (en) | 2008-10-23 | 2012-09-24 | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008273401A JP5355032B2 (ja) | 2008-10-23 | 2008-10-23 | クライアント装置、サーバ装置、及び、それらを用いた文書管理システム、文書管理方法、文書管理プログラム |
JP2008-273401 | 2008-10-23 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/625,687 Division US9189771B2 (en) | 2008-10-23 | 2012-09-24 | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100106699A1 true US20100106699A1 (en) | 2010-04-29 |
Family
ID=42118483
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/573,502 Abandoned US20100106699A1 (en) | 2008-10-23 | 2009-10-05 | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof |
US13/625,687 Expired - Fee Related US9189771B2 (en) | 2008-10-23 | 2012-09-24 | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/625,687 Expired - Fee Related US9189771B2 (en) | 2008-10-23 | 2012-09-24 | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof |
Country Status (2)
Country | Link |
---|---|
US (2) | US20100106699A1 (enrdf_load_stackoverflow) |
JP (1) | JP5355032B2 (enrdf_load_stackoverflow) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110184947A1 (en) * | 2010-01-26 | 2011-07-28 | Canon Kabushiki Kaisha | Information processing apparatus, information processing method, and program |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10824756B2 (en) | 2013-09-20 | 2020-11-03 | Open Text Sa Ulc | Hosted application gateway architecture with multi-level security policy and rule promulgations |
EP2851833B1 (en) | 2013-09-20 | 2017-07-12 | Open Text S.A. | Application Gateway Architecture with Multi-Level Security Policy and Rule Promulgations |
US9979751B2 (en) | 2013-09-20 | 2018-05-22 | Open Text Sa Ulc | Application gateway architecture with multi-level security policy and rule promulgations |
JP6349408B2 (ja) * | 2014-09-30 | 2018-06-27 | 富士フイルム株式会社 | パターン形成方法、レジストパターン、及び、電子デバイスの製造方法 |
US11593075B2 (en) | 2015-11-03 | 2023-02-28 | Open Text Sa Ulc | Streamlined fast and efficient application building and customization systems and methods |
US11388037B2 (en) | 2016-02-25 | 2022-07-12 | Open Text Sa Ulc | Systems and methods for providing managed services |
CN114363684B (zh) * | 2021-12-15 | 2024-06-28 | 创盛视联数码科技(北京)有限公司 | 一种文档显示方法、装置及存储介质 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6192381B1 (en) * | 1997-10-06 | 2001-02-20 | Megg Associates, Inc. | Single-document active user interface, method and system for implementing same |
US20040088313A1 (en) * | 2001-11-02 | 2004-05-06 | Medical Research Consultants | Knowledge management system |
US20050033813A1 (en) * | 2003-08-07 | 2005-02-10 | International Business Machines Corporation | Collaborative email with delegable authorities |
US20050097061A1 (en) * | 2003-10-31 | 2005-05-05 | Shapiro William M. | Offline access in a document control system |
US7035910B1 (en) * | 2000-06-29 | 2006-04-25 | Microsoft Corporation | System and method for document isolation |
US20070050368A1 (en) * | 2005-08-24 | 2007-03-01 | Canon Kabushiki Kaisha | Document distribution system and method |
US20090235182A1 (en) * | 2008-03-17 | 2009-09-17 | Ricoh Company, Ltd | System for assisting collaborative activity |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3930068B2 (ja) * | 1996-06-26 | 2007-06-13 | 株式会社東芝 | ワークフロー管理システム及びその表示方法 |
JP2000123071A (ja) | 1998-10-15 | 2000-04-28 | Hitachi Ltd | ToDoリストのタスク管理システム |
US6680675B1 (en) * | 2000-06-21 | 2004-01-20 | Fujitsu Limited | Interactive to-do list item notification system including GPS interface |
JP2004185556A (ja) * | 2002-12-06 | 2004-07-02 | Kyocera Communication Systems Co Ltd | プロジェクト管理システムおよびその方法 |
JP2006018529A (ja) * | 2004-06-30 | 2006-01-19 | Canon Software Inc | ワークフローシステムおよびワークフローシステムの制御方法およびプログラムおよび記録媒体 |
US8543413B2 (en) * | 2006-04-28 | 2013-09-24 | Cerner Innovation, Inc. | To-do lists in computerized healthcare environment |
US9922295B2 (en) * | 2008-01-17 | 2018-03-20 | International Business Machines Corporation | Method for evolving shared to-do lists into business processes |
-
2008
- 2008-10-23 JP JP2008273401A patent/JP5355032B2/ja not_active Expired - Fee Related
-
2009
- 2009-10-05 US US12/573,502 patent/US20100106699A1/en not_active Abandoned
-
2012
- 2012-09-24 US US13/625,687 patent/US9189771B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6192381B1 (en) * | 1997-10-06 | 2001-02-20 | Megg Associates, Inc. | Single-document active user interface, method and system for implementing same |
US7035910B1 (en) * | 2000-06-29 | 2006-04-25 | Microsoft Corporation | System and method for document isolation |
US20040088313A1 (en) * | 2001-11-02 | 2004-05-06 | Medical Research Consultants | Knowledge management system |
US20050033813A1 (en) * | 2003-08-07 | 2005-02-10 | International Business Machines Corporation | Collaborative email with delegable authorities |
US20050097061A1 (en) * | 2003-10-31 | 2005-05-05 | Shapiro William M. | Offline access in a document control system |
US20070050368A1 (en) * | 2005-08-24 | 2007-03-01 | Canon Kabushiki Kaisha | Document distribution system and method |
US20090235182A1 (en) * | 2008-03-17 | 2009-09-17 | Ricoh Company, Ltd | System for assisting collaborative activity |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110184947A1 (en) * | 2010-01-26 | 2011-07-28 | Canon Kabushiki Kaisha | Information processing apparatus, information processing method, and program |
Also Published As
Publication number | Publication date |
---|---|
US20130018962A1 (en) | 2013-01-17 |
US9189771B2 (en) | 2015-11-17 |
JP2010102510A (ja) | 2010-05-06 |
JP5355032B2 (ja) | 2013-11-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9189771B2 (en) | Client apparatus, server apparatus, document management system, document management method, and medium storing program thereof | |
US7890964B2 (en) | Methods and apparatus for contextual awareness in a groupware client | |
US8831967B2 (en) | Workflow management using a to-do list | |
US9086944B2 (en) | Method and system for synchronizing changes between product development code and related documentation | |
US8533795B2 (en) | Information processing apparatus, information processing method, information processing program, and computer-readable medium | |
KR20100047220A (ko) | 문서관리장치, 방법 및 프로그램 | |
US8346716B2 (en) | Document management system | |
JP2012064129A (ja) | 複数アプリケーションのgui統合方法 | |
JP2010113454A (ja) | データ照合システム | |
US12118296B2 (en) | Collaborative coauthoring with artificial intelligence | |
US20220327165A1 (en) | Information processing system, data management apparatus, and data management method | |
JP2009037366A (ja) | 情報処理装置およびワークフロー制御方法およびプログラムおよび記録媒体 | |
JP6277778B2 (ja) | 情報処理装置、情報処理システム、プログラム | |
US7996299B2 (en) | Trade services management system | |
US20240303568A1 (en) | Artificial Intelligence-Powered Aggregation of Project-Related Collateral | |
JP5499388B2 (ja) | 書類、バリデーションチェック及び開発ドキュメント作成用コンパイラ及びそれを用いた稟議システム | |
JP7082249B1 (ja) | プログラム、方法、情報処理装置 | |
EP4054166B1 (en) | Information processing apparatus, information processing program, and information processing method | |
JP2010244229A (ja) | 情報管理装置 | |
JP2008262554A (ja) | 情報処理装置、情報処理方法、情報処理プログラム及び記録媒体 | |
WO2024186713A1 (en) | Artificial intelligence-powered aggregation of project-related collateral | |
JP6588304B2 (ja) | 情報処理装置、情報処理方法、及びプログラム | |
JP2012238209A (ja) | 情報処理装置、情報処理方法、及びプログラム | |
Toelle | Advanced eDiscovery | |
JP2016103203A (ja) | ワークフローシステム、ワークフローサーバ装置、ワークフロー管理方法及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CANON KABUSHIKI KAISHA,JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WATANABE, RYUTARO;REEL/FRAME:023836/0812 Effective date: 20091001 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |