JP2010061345A - Document management program, and document management apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management program and a document management apparatus for managing the relationship between document life cycles. <P>SOLUTION: A life cycle definition DB 20 stores a plurality of states that a document can take and a life cycle definition that defines state transition conditions of the document. With respect to at least one of the plurality of states of a specified life cycle definition in the life cycle definition DB 20, a generation and registration section 120 in a life cycle definition processing unit 12 of a document management apparatus 10 generates information that defines a plurality of lower-level states included in the state, and information that represents the state transition conditions of the plurality of lower-level states. Further, the generation and registration section 120 generates a new life cycle definition that includes information related to the lower-level states generated together with the information included in the specified life cycle definition, and registers it in the life cycle definition DB 20, as a lower-level life cycle definition of the specified life cycle definition. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a document management program and a document management apparatus.

  There is a technique for managing a document in accordance with the life cycle of the document as a “life cycle” of the document (eg, creation, editing, publishing, storage, etc.).

  For example, in the technique described in Patent Document 1, an electronic document is printed to be a paper document, the paper document is scanned to be an electronic document, and a duplicate electronic document is generated in that order. In the life cycle of the state transition document, an integrated document including access restriction information indicating access right to each generation of document and generation information indicating generation of the document is generated, and the access right in each generation is managed. .

JP 2006260481 A

  Incidentally, a plurality of electronic documents related to each other may be managed according to one common life cycle. As described above, it is desired that some electronic documents among a plurality of electronic documents managed according to a common life cycle should be managed in accordance with a life cycle including a finer state than a state included in the common life cycle. There is.

  An object of the present invention is to provide a document management program and a document management apparatus for managing the relationship between information defining a life cycle of an electronic document and information defining a life cycle including a more detailed state than the life cycle. For the purpose.

  According to the first aspect of the present invention, information defining a plurality of states that can be taken by the electronic document stored in the storage means, and the state of the electronic document transits from one of the plurality of states to another state. A computer capable of referring to document state definition information including information defining a condition for performing at least one of the plurality of states defined by the first document state definition information stored in the storage unit, Generate information that defines a plurality of sub-states included in the state and information that defines a condition in which the document state transitions from one sub-state to the other sub-state of the plurality of sub-states A generation step of generating second document state definition information including the generated information and information included in the first document state definition information; the second document state definition information; 2 document status And a step of storing in the storage means information indicating that the definition information is lower-level document state definition information with respect to the first document state definition information. is there.

  According to a second aspect of the invention, in the first aspect of the invention, in response to a change request specifying the change target document state definition information and the content of the change, the change target document state definition information is read from the storage means. A first change step of acquiring and changing at least a part of the definitions of the plurality of states and the transition conditions in the document state definition information to be changed based on the content of the change specified by the change request; When the lower document state definition information is stored in the storage unit with respect to the document state definition information to be changed, the lower document state definition information is changed to the contents of the change in the first change step. And causing the computer to further execute a second change step for making a change based on the second change step.

  The invention according to claim 3 is the invention according to claim 2, wherein the transition condition included in the document state definition information is a condition that represents a transition timing from the one state to another state. In the first change step, the time represented by the transition condition in the document state definition information to be changed is changed, and in the second change step, the time represented by the transition condition in the lower document state definition information. The time is changed to the time after the change in the first change step.

  The invention according to claim 4 is the invention according to claim 3, wherein, in the second change step, when the state related to the change of the timing includes a plurality of lower states, the plurality of lower states The timing for transitioning from one lower state to another lower state is changed.

  The invention according to claim 5 is the invention according to claim 2, wherein the transition condition included in the document state definition information is a condition related to attribute information of an electronic document, and the change is performed in the first change step. The electronic document represented by the transition condition in the subordinate document state definition information is changed in the second modification step by changing a condition related to the attribute information of the electronic document represented by the transition condition in the target document state definition information. Is changed to the condition after the change in the first change step.

  The invention according to claim 6 is the invention according to claim 2, wherein in the first change step, a state that an electronic document can take is added to the document state definition information to be changed, and the added state is The document state definition information is further changed to include information to be defined and information for defining a condition for transition from the added state to another state. In the second change step, the subordinate document state definition information is changed. Then, a change is made to the document state definition information further including the information added to the change target document state definition information in the first change step.

  The invention according to claim 7 is the invention according to any one of claims 1 to 6, wherein the information defining the plurality of states included in the document state definition information represents the authority to use the document in each state. Document state definition information associated with the requested electronic document in response to a request for using the electronic document associated with one of the document state definition information stored in the storage means, and the document Document state definition information positioned higher in the hierarchical structure constituted by a plurality of document state definition information in the storage unit than the state definition information is acquired from the storage unit, and the document state definition information in each acquired document state definition information Referring to the identifying step for identifying the state of the electronic document to be requested and the usage authority in each state identified in the identifying step, the interest of the requested document A determining step of determining the possibility, the further the computer to execute.

  According to an eighth aspect of the invention, information defining a plurality of states that can be taken by the electronic document stored in the storage means, and the state of the electronic document transits from one of the plurality of states to another state. And at least one of the plurality of states defined by the first document state definition information is included in the state. Information that defines a plurality of substates and information that defines a condition in which the document state transitions from one substate to another substate among the plurality of substates Generating means for generating second document state definition information including information and information included in the first document state definition information, the second document state definition information, and the second document state definition Information is defined in the first document status A document management apparatus characterized by comprising, a means for storing in the storage means and the information indicating that the document state definition information of a lower relative information.

  According to the invention which concerns on Claim 1 or 8, the relationship between the information which defines the life cycle of an electronic document and the information which defines the life cycle containing a more detailed state than the life cycle can be managed.

  According to the second aspect of the present invention, when the document state definition information is changed, the document state definition information that is a lower level of the document state definition information can be changed so as to be consistent with the contents of the change of the document state definition information. .

  According to the invention of claim 3, when changing the state transition timing of the electronic document represented by the document state definition information, the state of the document represented by the document state definition information which is a lower order of the document state definition information The transition time can be changed to the time after the change of the document state definition information.

  According to the invention of claim 4, when the state transition timing of the electronic document represented by the document state definition information is changed, the lower state included in the document state definition information that is the lower order of the document state definition information The time of state transition can be changed.

  According to the fifth aspect of the present invention, when the condition relating to the attribute information of the electronic document represented by the document state definition information is changed, the electronic document represented by the document state definition information which is a lower level of the document state definition information is changed. The condition relating to the attribute information can be changed to the changed condition for the document state definition information.

  According to the invention of claim 6, when the state of the electronic document is added in the life cycle represented by the document state definition information, the above-described added state is added to the document state definition information which is a lower level of the document state definition information. Can be changed to represent a lifecycle that includes

  According to the invention of claim 7, for an electronic document associated with the document state definition information, a document superior to the document state definition information together with the usage authority represented by the document state definition information associated with the electronic document. Whether or not the electronic document can be used can be determined with reference to the usage authority represented by the state definition information.

  FIG. 1 shows an example of the configuration of a document management apparatus 10 according to one embodiment of the present invention. The document management apparatus 10 refers to the life cycle definition DB (database) 20 and the user information DB 40 and manages the documents stored in the document DB 30. The document management apparatus 10 includes a life cycle definition processing unit 12 and a document processing unit 14.

  The life cycle definition processing unit 12 executes processing related to data stored in the life cycle definition DB 20. The life cycle definition DB 20 is a database that stores information that defines the life cycle of a document (hereinafter referred to as “life cycle definition”). The life cycle definition includes information that defines states that the document can take in the life cycle of the document, and information that defines conditions under which the document state transitions from one state to another state.

  With reference to FIG. 2, an example of the life cycle definition in this embodiment will be described. FIG. 2 shows an example of data contents of the life cycle definition DB 20. Each of the records r1, r2, r3, r4 in the table of the example of FIG. 2 is an information record representing the contents of one life cycle definition. In the life cycle definition DB 20 in the example of FIG. 2, each item of the life cycle definition name, state, access right, state transition condition, administrator, and upper life cycle definition ID is associated with the life cycle definition ID (identifier). It is registered.

  The life cycle definition ID is life cycle definition identification information unique in the life cycle definition DB 20. The life cycle definition name is a name given to the life cycle definition. The life cycle definition name is given by, for example, a user who instructs registration of the life cycle definition. Alternatively, for example, when the life cycle definition processing unit 12 registers the life cycle definition in the life cycle definition DB 20, the life cycle definition name may be automatically given according to a preset rule.

  The state represents a state that the document can take in the life cycle of the document represented by the life cycle definition. For example, in the table of the example of FIG. 2, “created”, “reviewed”, “published”, and “stored” states are registered in the “state” item of the life cycle definition ID: LS1. This indicates that in the life cycle represented by the life cycle definition of the life cycle definition ID: LS1, the document can take one of the states “created”, “review”, “published”, and “stored”. Further, the item “state” in the table of the example of FIG. 2 represents the order of state transition of the document. In the example of FIG. 2, in the “state” item of a record corresponding to one life cycle definition, the document state transitions in the order from the state described in the upper line to the state described in the lower line. And

  The access right is set in association with each state in the document life cycle, and represents the use right for the document in that state. The access right is represented by, for example, a combination of the type of operation (viewing, updating, printing, deleting, etc.) on the document and the identification information of the user or group permitted to execute the type of operation.

  The state transition condition is a condition in which the document state transitions from one state to another state in the document life cycle. In the table of the example of FIG. 2, the date of transition from the state to the next state is registered in the state transition condition item in association with each state. For example, the state transition condition “2008/6/15” associated with the “created” state of the life cycle definition LS1 changes the document state from “created” to “reviewed” on June 15, 2008. Represents what to do. In the following description, the date of transition from the first state to the second state may be referred to as the “due date” of the first state. For example, “the date of the“ creation ”state of the life cycle definition LS1 is 2008/6/15”. Note that the state transition condition “2008/12/31” associated with the state “storage” that the document last takes in the lifecycle definition LS1 in the table of the example of FIG. 2 represents the date on which the document is discarded. And In the example of FIG. 2, the state transition condition represents a date of transition from the first state to the second state, but a state transition condition that represents time in addition to the date may be set.

  In the item of administrator, identification information of a user who is an administrator of the corresponding life cycle definition is registered. Here, the administrator of the life cycle definition represents a user who has the authority to make changes to the life cycle definition. For example, a user who instructs registration of a life cycle definition is set as an administrator of the life cycle definition.

  In the present embodiment, the life cycle definition includes a state and a state transition condition included in another life cycle definition, and may include a lower state representing a more detailed state for at least a part of the state. . In the following description, such a life cycle definition is referred to as a “lower” life cycle definition with respect to the other life cycle definitions. Conversely, the other life cycle definition is said to be a “upper” life cycle definition relative to the lower life cycle definition. In the life cycle definition DB 20 in the example of FIG. 2, the life cycle definition ID of the higher life cycle definition is registered in the item of the higher life cycle definition ID in the life cycle definition of the corresponding record. In the example of FIG. 2, the life cycle definition LS1 is higher than the life cycle definitions LS2 and LS4, and the life cycle definition LS2 is higher than the life cycle definition LS3.

  Further, an example of the upper / lower relationship between the life cycle definitions in the present embodiment will be described with reference to FIG. FIG. 3 is a diagram schematically showing each life cycle definition in the life cycle definition DB 20 when the life cycle definition DB 20 has the data contents of the example of FIG. As shown in FIG. 3, a plurality of life cycle definitions having a higher / lower relationship with each other form a hierarchical structure. Note that the items of the upper life cycle definition in the table of the example of FIG. 2 are the life cycle definitions positioned directly higher in the hierarchical structure of the life cycle definition illustrated in FIG. 3 than the life cycle definition of the corresponding record. Represents the ID. In the following description, the term “upper life cycle definition” represents a life cycle definition positioned directly above in a hierarchical structure with respect to a certain life cycle definition. Further, the term “lower life cycle definition” represents a life cycle definition that is positioned directly below in a hierarchical structure with respect to a certain life cycle definition.

  Referring to FIG. 2 and FIG. 3, the life cycle definition LS1 “product A specification” does not have an upper life cycle definition. On the other hand, “product A specification” is an upper life cycle definition of the life cycle definition LS2 “component A specification” and life cycle definition LS4 “component B specification”. “Component A Specification” and “Component B Specification” are the same states as “Product A Specification” (“Created”, “Review”, “Published”, and “Storage”). And the state transition condition, the “created” state has its own lower state and lower state state transition conditions. Specifically, in the “component A specification”, a state transition condition (including “draft creation” and “correction” as subordinate states of the “creation” state and transition from the “draft creation” state to the “correction” state ( Date) is set to "2008/5/1". Also, in the “component B specification”, the lower status of the “created” state is “first half created” and “second half created”, and the state transition condition (due date) for transition from the “first half created” state to the “second half created” state ) Is "2008/5/10". Note that the due date of the “modified” state in “component A specification” and the “second half creation” state in “component B specification” are the “created” state in the upper life cycle definition “product A specification” Is set to the same date as the date of 2008/6/15. As described above, the lower life cycle definition inherits the state and state transition condition of the upper life cycle definition as it is, and includes at least a part of the lower states of the state.

  Further, the life cycle definition LS3 “for component A specification” is a lower life cycle definition of “for component A specification”. “For parts A specification” includes the same status as “for component A specification” (“Draft creation”, “Modification”, “Review”, “Publication”, and “Storage”) and state transition conditions. Furthermore, “personal correction” and “upper length correction” are included as subordinate states of the “correction” state. “Part A specification” is a lower life cycle definition of “Component A specification”, and “Product A specification” is a higher life cycle definition of “Component A specification”. It can be said that it is a subordinate life cycle definition.

  FIG. 3 also shows an example of a document (association document) managed according to each life cycle definition. For example, the documents Doc1 and Doc2 are associated with the life cycle definition “for component A specification”, the document Doc14 is associated with the life cycle definition “for component A specification”, and the document Doc21 is associated with the life cycle definition “component B specification”. Associated with “For Specification”. “Component A specification”, “Part A specification”, and “Component B specification” have different life cycle definitions, but they are all lower life than “Product A specification”. Cycle definition. Therefore, these three life cycle definitions each include the same state and state transition conditions as those for “product A specification”. For this reason, the document associated with each of these three life cycle definitions changes state according to the life cycle defined in each associated life cycle definition, and is defined in the upper life cycle definition “product A specification”. State transition is made according to the life cycle.

  The table in the example of FIG. 2 is only an example of the data contents of the life cycle definition DB 20. The mode of expression of values set for each item is not limited to the mode illustrated in FIG. 2, and the registered items are not limited to the items illustrated in the table of FIG. The life cycle definition DB 20 includes at least life cycle definition identification information, information defining states included in the life cycle, information defining state transition conditions, and information representing upper / lower relationships between life cycle definitions. Should be registered. Further, for example, if there are items necessary for management purposes, such as the date and time when the life cycle definition is registered or changed, items different from the items in the table of the example of FIG. 2 may be registered.

  Returning to the description of FIG. 1, the life cycle definition processing unit 12 includes a generation registration unit 120 and a change unit 122. The generation registration unit 120 generates a life cycle definition according to a user instruction and registers it in the life cycle definition DB 20. For example, the generation registration unit 120 generates a new life cycle definition that is not subordinate to other life cycle definitions and registers the new life cycle definition in the life cycle definition DB 20. At this time, the item of the upper life cycle definition ID of the record of the corresponding life cycle definition DB 20 is set to “Null (none)”. Further, for example, the generation registration unit 120 replaces a part of the state included in the life cycle definition with a plurality of lower states based on the life cycle definition registered in the life cycle definition DB 20, that is, the lower life A cycle definition may be generated and registered in the life cycle definition DB 20. At this time, the generation registration unit 120 sets the ID of the registered life cycle definition in the item of the upper life cycle definition ID in the record of the life cycle definition DB 20 corresponding to the generated lower life cycle definition.

  The changing unit 122 changes the life cycle definition registered in the life cycle definition DB 20 in accordance with a user instruction. When the life cycle definition to be changed has a lower life cycle definition, the changing unit 122 further changes the lower life cycle definition so as to maintain consistency with the change made to the life cycle definition to be changed. Add

  The document processing unit 14 performs processing according to the life cycle definition stored in the life cycle definition DB 20 on the document stored in the document DB 30. The document processing unit 14 includes a life cycle control unit 140. The life cycle control unit 140 performs processing related to the life cycle of the document to be processed. For example, the life cycle control unit 140 acquires the life cycle definition associated with the document to be processed from the life cycle definition DB 20, and specifies the state of the document to be processed in the acquired life cycle definition. Then, the processing target document is processed according to its state. For example, when the life cycle definition DB 20 has the data contents of the table illustrated in FIG. 2, the document processing unit 14 determines whether or not the process can be executed according to the access right associated with the specified document state. .

  The document DB 30 is a database that stores electronic document files, and may be configured by a general file system. In the present embodiment, the document DB 30 stores a document attribute table that associates each document with attribute information of the document. FIG. 4 is a diagram illustrating an example of a document attribute table stored in the document DB 30. In the document attribute table in the example of FIG. 4, document attributes that are attribute information of each document are registered in association with the document ID of each document. The document ID is identification information unique to each document to be managed by the document management apparatus 10. In the example of FIG. 4, each item of a life cycle definition ID and a file path name is registered as a document attribute. In the item of the life cycle definition ID, a life cycle definition ID of the life cycle definition associated with the document is registered. Each document is managed according to a life cycle definition associated with the document. The file path name represents the storage position in the document DB 30 of the electronic file of the document. In addition, the value of the life cycle definition ID in the table of the example of FIG. 4 represents the life cycle definition ID of each life cycle definition illustrated in FIGS.

  The user information DB 40 is a database that stores information of users registered in advance as users who use the documents in the document DB 30. The user information DB 40 stores, for example, the name and password of the user in association with the identification information of each user. Further, the user information DB 40 stores information related to user groups. For example, the user information DB 40 stores identification information of users belonging to the group in association with the identification information of each group. The document processing unit 14 refers to the user information DB 40 and determines whether to access the document. For example, when an access right that permits execution of a certain process is set for a specific user group, the document processing unit 14 refers to the user information DB 40 and the user who has requested the document processing is assigned to the group. It is determined whether or not the user can belong by determining whether or not the user belongs.

  Each database of the life cycle definition DB 20, the user information DB 40, and the document DB 30 may be included in the document management apparatus 10, or may be included in another information processing apparatus connected to the document management apparatus 10 via a network. It may be.

  Hereinafter, an example of processing performed in the document management apparatus 10 will be described.

  FIG. 5 is a flowchart illustrating an example of a procedure of life cycle definition registration processing performed by the generation registration unit 120 of the life cycle definition processing unit 12. For example, when receiving a life cycle definition registration request from a user via an input device (not shown), the generation registration unit 120 starts the processing of the procedure illustrated in FIG.

  Referring to FIG. 5, first, the generation registration unit 120 determines whether or not the registration request from the user requests registration of a lower life cycle definition of the life cycle definition registered in the life cycle definition DB 20. (Step S10).

  If it is not a registration request for a lower life cycle definition (NO in step S10), the generation registration unit 120 receives input of information specifying the contents of the new life cycle definition, and generates a new life cycle definition according to the received input information. And registered in the life cycle definition DB 20 (step S20). In step S20, the generation registration unit 120 uses, for example, “life cycle definition name”, “state”, “access right”, and “state transition” in the table of the example of FIG. 2 as information for specifying the contents of the life cycle definition. Input of information specifying the contents of each item of “condition” is accepted. Then, in the life cycle definition DB 20, a record including a value of each item represented by the received input information is newly generated. Further, the generation registration unit 120 assigns a new life cycle definition ID to the newly generated life cycle definition, and sets it as the value of the item of the life cycle definition ID of the record of the corresponding life cycle definition DB 20. Here, the value of the item of the upper life cycle definition ID is set to “Null”. This is because it is registration of a new life cycle definition that is not subordinate to other life cycle definitions. The value of the administrator item sets identification information of the user who made the registration request. After step S20, the process of the procedure in the example of FIG.

  On the other hand, when the registration request is a registration request for a lower life cycle definition (YES in step S10), the generation registration unit 120 accepts the designation of the ID of the registered life cycle definition, and the life cycle definition of the designated ID. Is acquired from the life cycle definition DB 20 (step S12). Next, designation of one of the states included in the acquired life cycle definition is received, and a lower state included in the designated state is generated (step S14). Information specifying the contents of the lower state is acquired from a user input via an input device (not shown). For example, the generation registration unit 120 receives input of the number of lower states, the name of each lower state, the access right associated with each lower state, and the state transition condition between the lower states.

  When the lower state is generated for the specified state, the generation / registration unit 120 determines whether to generate a lower state for the other states included in the life cycle definition acquired in step S12 (step S16). This determination is made based on, for example, whether or not a user input instructing generation of a lower state is accepted for another state.

  When the lower state is generated for another state (YES in step S16), the lower state is generated for the other state (step S14), and the determination in step S16 is performed again.

  When the lower state is not generated for other states (NO in step S16), the generation registration unit 120 creates a record corresponding to the lower life cycle definition including information about the lower state generated in step S14 in the life cycle definition DB 20 (Step S18). Here, for example, the generation registration unit 120 duplicates the state of the life cycle definition, the access right, and the state transition condition specified in step S12, and the state in which the lower state is generated in step S14 among the states. Generate a life cycle definition record that is replaced with the generated lower state. Then, a new life cycle definition ID is assigned and this record is registered in the life cycle definition DB 20. In the upper life cycle definition ID item of this record, the life cycle definition ID of the life cycle definition specified in step S12 is set. When step S18 ends, the process of the procedure in the example of FIG. 5 ends.

  The rough cycle definition DB of the example of FIG. 2 is constructed by the generation registration unit 120 of the life cycle definition processing unit 12 performing the process of the example of FIG. 5 in response to a registration request from the manager of each life cycle definition. Is done. For example, in the example of FIG. 2, first, the procedure of the example of FIG. 5 is performed in response to a registration request for the life cycle definition of “product A specification” for user1 who is a project leader related to the creation of the specification of product A. The process is executed, and a record of life cycle definition ID: LS1 is registered in the life cycle definition DB 20. After that, by the processing of the procedure of the example of FIG. 5 according to the registration request of the lower life cycle definition by the leaders user2 and user4 of the user group engaged in the creation of the specifications of the component A and the component B of the specifications of the product A , “For product A specification”, lower life cycle definitions “for component A specification” and “for component B specification” are respectively registered in the life cycle definition DB 20. In addition, by the processing of the procedure in the example of FIG. 5 according to the registration request of the user group leader user3 who creates the specification of the part A included in the component A, the lower lifecycle definition “parts” for “component A specification” "For A specification" is registered.

  When the life cycle definition is registered in the life cycle definition DB 20 as described above, the document processing unit 14 of the document management apparatus 10 generates a document managed according to each life cycle definition in accordance with a user document generation request. Then, the generated document file is registered in the document DB 30, and the document attribute of the generated document is registered in the document attribute table (see FIG. 4) of the document DB 30. This document attribute includes the life cycle definition ID specified by the user's document generation request. For example, when a user in charge of creating a specification for component A designates a life cycle definition “for component A specification” and requests a new creation of a document according to this, the document processing unit 14 follows the request for the document “ Doc1 "is newly generated and registered in the document DB 30. At this time, the document processing unit 14 associates with the document ID: Doc1 of the newly created document in the document attribute table (see FIG. 4) of the document DB 30 and the life of the specified life cycle definition “for component A specification”. Register document attributes including cycle definition ID.

  Hereinafter, an example of processing performed by the document processing unit 14 for a document associated with a life cycle definition will be described with reference to FIG. In the following description, it is assumed that the data contents of the example of FIG. 2 are registered in the life cycle definition DB 20 and the document attribute table of the example of FIG. 4 is registered in the document DB 30.

  The document processing unit 14, for example, when the document management apparatus 10 receives a document processing request specifying the document ID and processing content of the requested document from the user via an input device (not shown), as shown in FIG. Start processing the example procedure.

  First, the life cycle control unit 140 of the document processing unit 14 refers to the document attribute table of the document DB 30 and sets the life cycle definition ID associated with the document ID of the requested document as the attention life cycle definition ID (step S30). ). Next, the life cycle control unit 140 acquires the record of the attention life cycle definition ID from the life cycle definition DB 20 (step S32), and adds the acquired record to the life cycle definition list (step S34). The life cycle definition list is a list for temporarily storing life cycle definitions used in later processing. Next, it is determined whether or not the life cycle definition of the attention life cycle definition ID has an upper life cycle definition (step S36). This determination is made based on, for example, whether or not a value other than “Null” is set in the upper life cycle definition ID item of the record acquired in step S32. When the upper life cycle definition exists (YES in step S36), the upper life cycle definition ID is set as a new attention life cycle definition ID (step S46), and the processes in and after step S32 are repeated.

  The life included in the path that goes back to the highest hierarchy from the hierarchical structure that the life cycle definition constitutes, starting from the life cycle definition associated with the requested document by the loop process including steps S32, S34, S36, and S46 The cycle definition is saved in the lifecycle definition list. For example, if the document “Doc14” (see FIG. 4) associated with the life cycle definition LS3 “for component A specification” in the life cycle definition DB 20 in the example of FIG. 3, the hierarchical structure of the life cycle definition illustrated in FIG. 3 starting from “for component A specification” is traced back to “for product A specification” in the highest hierarchy, and the life cycle definition list includes “part A specification”. Three life cycle definitions are stored: “for use”, “for component A specification”, and “for product A specification”.

  Returning to the description of the flowchart of FIG. 6, when there is no upper life cycle definition of the life cycle definition of the attention life cycle definition ID (NO in step S36), the process proceeds to step S38. At this point, the life cycle definition list includes the life cycle definition associated with the requested document and all life cycle definitions corresponding to the higher order of the life cycle definition. In step S38, the life cycle control unit 140 specifies the state of the requested document in each life cycle definition in the life cycle definition list. For example, by referring to the state transition condition of the life cycle definition in the list, the due date of each state in the life cycle definition is acquired and compared with the current date and time, thereby specifying the state of the requested document.

  A specific example of the process in step S38 in the case of the above example in which the request target document is the document “Doc14” will be described. For example, when the current date is 2008/5/7, compare this with the due date of each state of the life cycle definition “for part A specification” associated with the requested document. It is after “May 1, 2008” and before the date “May 15, 2008” in the “Personal Correction” state. At this time, the life cycle control unit 140 specifies that the state in the life cycle definition “for part A specification” of the document “Doc14” to be requested is the “correct person” state. Furthermore, the life cycle control unit 140 identifies the state of the requested document in the other life cycle definitions “for component A specifications” and “for product A specifications” in the list. The “modification” state in “for component A specification” is a lower state of the “modification” state in the upper life cycle definition “for component A specification”, and this “modification” state is a further upper life cycle definition “ This is a subordinate state of the “Created” state in “Product A Specification”. Therefore, the life cycle control unit 140 indicates that the state of “for component A specification” of the requested document “Doc14” is “modified”, and the state of “for product A specification” is “created”. Is identified.

  After step S38, the logical product of the access rights associated with each identified state is obtained (step S40). Then, in the logical product of the obtained access rights, it is determined whether or not the requested user is permitted to execute the requested process (step S42). If permitted (YES in step S42), the document processing unit 14 executes the requested process on the requested document (step S44). If not permitted (NO in step S42), information indicating that execution of the requested process is not permitted is output (step S48). In step S48, for example, information indicating that the process cannot be executed is displayed on a display device (not shown).

  After step S44 or step S48, the process of the procedure illustrated in FIG. 6 ends.

  According to the processing of the procedure in the example of FIG. 6, whether or not the processing can be executed is determined by referring not only to the life cycle definition itself associated with the requested document, but also to the access right set in the upper life cycle definition. It is determined. In addition, in order to determine whether to execute the process based on the logical product of the access rights, for example, the access rights in the state in the life cycle definition associated with the requested document are permitted to the user who made the process request. Even a process that is being executed is not permitted if it is not permitted in the upper life cycle definition. In other words, in the procedure of the example of FIG. 6, even when an access right exceeding the range of the access right in the upper life cycle definition is set in the lower life cycle definition, it is within the range of the access right in the upper life cycle definition. Only the execution of the process is permitted.

  In the above, the example of the registration process of the life cycle definition and the process of the document according to the registered life cycle definition was demonstrated. Hereinafter, an example of change processing for a registered life cycle definition will be described.

  FIG. 7 is a flowchart illustrating an example of a procedure of life cycle definition change processing performed by the changing unit 122 of the life cycle definition processing unit 12. For example, when the document management apparatus 10 receives a change request for specifying the life cycle definition ID of the life cycle definition to be changed from the user via the input device (not shown), the changing unit 122 performs the procedure of the example of FIG. Start processing.

  Referring to FIG. 7, first, the changing unit 122 acquires the life cycle definition to be changed specified by the change request from the life cycle definition DB 20 (step S <b> 70). Next, the changing unit 122 changes the contents of the life cycle definition to be changed (step S72). Details of the processing in step S72 will be described later.

  When the content of the life cycle definition to be changed is changed, the changing unit 122 overwrites and saves the content of the changed life cycle definition in the life cycle definition DB 20 (step S74). That is, in the life cycle definition DB 20, the content of the record corresponding to the life cycle definition to be changed is rewritten with the changed content. Thereafter, the life cycle definition immediately below the change target life cycle definition in the hierarchical structure of the life cycle definition is searched (step S76). This search is performed, for example, by extracting from the life cycle definition DB 20 a record having the value of the life cycle definition ID of the life cycle definition to be changed as the value of the item of the higher life cycle definition ID.

  As a result of the search in step S76, when there is a life cycle definition immediately below the change target life cycle definition, the changing unit 122 sets one of the search result lower life cycle definitions as a new change target. (Steps S78, S80). Then, the process of the example of FIG. 7 is recursively called and executed for the new life cycle definition to be changed (step S82). After step S82, the changing unit 122 determines whether or not all of the lower life cycle definitions in the search result of step S76 have been processed (step S84). If there is an unprocessed lower life cycle definition (NO in step S84), one of the unprocessed lower life cycle definitions is set as a new change target (step S80), and the processes in and after step S82 are repeated.

  If all the lower life cycle definitions in the search result in step S76 have been processed (YES in step S84), or if no lower life cycle definition exists in the search in step S76 (NO in step S78), the changing unit 122 Ends the process of the procedure in the example of FIG.

  In the process of the example of FIG. 7, when a change is made to one life cycle definition by the recursive process in step S82, all life cycle definitions that are subordinate to the life cycle definition are processed. Even changes are made.

  FIG. 8 shows an example of a detailed procedure in step S72 of FIG.

  Referring to FIG. 8, when step S72 of FIG. 7 is started, first, the changing unit 122 determines whether or not the life cycle definition to be changed is specified by the change request from the user ( Step S720). If it is specified by the change request from the user (YES in step S720), the contents of the life cycle definition to be changed are changed according to the instruction from the user (step S722). If not specified by the change request from the user (NO in step S720), the current change target life cycle definition is the change target newly set in step S80 of FIG. At this time, in step S724, the changing unit 122 changes the contents of the life cycle definition to be changed according to the changes made to the upper life cycle definition of the current life cycle definition to be changed. In step S724, the changing unit 122 changes the life cycle definition so as to be consistent with the contents of the change in the upper life cycle definition. After step S722 or step S724, the process proceeds to step S74 in FIG.

  When the life cycle definition having the lower life cycle definition is changed by the life cycle definition changing process illustrated in FIGS. 7 and 8, the lower life cycle definition is automatically changed so as to be consistent with the contents of the change. The

  Note that the change unit 122 determines whether or not the user who made the change request is the administrator of the life cycle definition to be changed before starting the execution of the processing of the procedure in the example of FIG. The process of the procedure of the example of FIG. 7 may be started only when

  A specific example of the life cycle definition changing process will be described with reference to FIGS. 9 and 10. In the following description with reference to FIGS. 9 and 10, it is assumed that the data contents of the example of FIG. 2 are registered in the life cycle definition DB 20.

  First, referring to FIG. 9, a specific example when the user makes a change request for the life cycle definition using an input device (not shown) with the life cycle definition LS2 “component A specification” in the example of FIG. An example will be described. First, the changing unit 122 starts the process of the example of FIG. 7 and acquires the record r2 (see FIG. 2) of the life cycle definition LS2 from the life cycle definition DB 20 (step S70). Since the life cycle definition LS2 to be changed is specified by the change request by the user, the changing unit 122 changes the content in accordance with the instruction from the user (step S72 in FIG. 7, step in FIG. 8). S720, S722). In this example, in the life cycle definition LS2, an input device (not shown) indicates that the date (state transition condition) of the “draft creation” state is changed from “2008/5/1” to “2008/5/20”. Suppose that In accordance with this instruction, the changing unit 122 sets the date “2008/5/1” in the “draft creation” state among the values of the item “state transition condition” in the record r2 in the corresponding life cycle definition DB 20 to “2008”. / 5/20 "(arrow a in FIG. 9).

  Since the life cycle definition LS2 has the lower life cycle definition LS3 “for component A specification”, the change unit 122 changes the lower life cycle definition LS3 to a new change target after making changes to the life cycle definition LS2. 7 is recursively called and executed (steps S78, S80, S82). In this recursive process, the life cycle definition LS3 to be changed is not specified in the user's change request. Therefore, the changing unit 122 changes the life cycle definition LS3 to be changed in accordance with the contents of the change in the upper life cycle definition LS2 (step S72 in FIG. 7 and steps S720 and S724 in FIG. 8). In this example, in accordance with the change of the date in the “draft creation” state in the upper life cycle definition LS2, the date in the “draft creation” state of the life cycle definition LS3 to be changed is similarly changed from “2008/5/1” to “2008 / 5/20 "(arrow a in FIG. 9). The new date “May 20th” in the “Draft” state is after the date “May 15th 2008” in the “Person correction” state, which is the next state. There is a conflict in the definition of the due date for each state. Therefore, the changing unit 122 also changes the due date of the “individually modified” state (which is one lower state of the “modified” state in the higher lifecycle definition LS2) next to the “draft created” state in the lifecycle definition LS3. . At this time, with respect to the ratio between the period of the “personal correction” state and the period of the “upper correction” state (which is another lower state of the “correction” state), the ratio before the change is generally maintained so as to maintain the ratio. The date of “personal correction” is changed from “2008/5/15” to “2008/5/28” (arrow b in FIG. 9).

  As another specific example, a specific example in which the user makes a life cycle definition change request with the life cycle definition LS1 “product A specification” in FIG. 2 as a change target will be described with reference to FIG. . In this example, it is assumed that the user has instructed to change the date of the “created” state from “2008/6/15” to “2008/7/3” in the lifecycle definition LS1. First, due to the life cycle definition change process (FIGS. 7 and 8) for the life cycle definition LS1 to be changed specified by the change request by the user, the due date in the “created” state in the corresponding record r1 of the life cycle definition DB 20 Is changed to “2008/7/3” (arrow c in FIG. 10). Then, the date of transition to the “review” state in the life cycle definition LS2 is similarly changed by the life cycle definition change process that is recursively called by the lower life cycle definition LS2 of the life cycle definition LS1. That is, in the corresponding record r2 of the life cycle definition DB 20, the due date of the “modified” state, which is the last state among the subordinate states of the “created” state, is rewritten to “2008/7/3” (arrow in FIG. 10). c). Along with this, for the due date of the “draft creation” state, which is the first of the sub-states of the “creation” state, the ratio between the period of the “draft creation” state and the period of the “correction” state before the change is changed. It is changed so that it is generally maintained. In the example of FIG. 10, the changing unit 122 changes the date of transition from the “draft creation” state to the “correction” state from “2008/5/1” to “2008/5/8” (arrow d in FIG. 10). ).

  Furthermore, since the life cycle definition LS2 has a lower life cycle definition LS3 “for part A specification”, the changing unit 122 recursively executes the life cycle definition changing process (FIGS. 7 and 8) with this as a change target. . For the life cycle definition LS3, the date of transition to the “review” state is changed to “2008/7/3” in the same way as the change in the upper life cycle definition LS2 (arrow c in FIG. 10). The date of the “state” is changed to “2008/5/8” (arrow d in FIG. 10). Further, in accordance with these changes, the date of the “personal correction” state is changed from “2008/5/15” to “2008/5/27” (arrow e in FIG. 10). By changing the date of the “personal correction” state, the ratio between the period of the “personal correction” state and the period of the “advance correction” state is maintained (roughly) at the ratio before the change process. In addition, for the life cycle definition LS4 “for component B specification” which is another lower life cycle definition of the life cycle definition LS1, the changing unit 122 recursively performs the life cycle definition changing process (FIGS. 7 and 8). Call and execute. In the change process for the life cycle definition LS4, first, the same change as the change of the date of the “created” state in the upper life cycle definition LS1 (the date of transition to the “review” state is set to “2008/7/3”) (Arrow c in FIG. 10). Then, by changing the date of transition from the “created first half” to the “created second half” in the “created” state from “2008/5/10” to “2008/5/20” (arrow f in FIG. 10). ), So that the ratio between the period in the “first half creation” state and the period in the “second half creation” state is approximately the same as the ratio before the change.

  In the above specific example described with reference to FIGS. 9 and 10, when the life cycle definition is changed according to the change of the upper life cycle definition (step S720 in FIG. 8), the changing unit 122 first sets the upper life cycle. If the same change as the due date of each state in the definition is made, and the period of the state including the lower state is shortened or extended accordingly, the ratio of the period of each lower state before the change is generally maintained. Change the due date of the subordinate state. As a result, the contents of the lower life cycle definition are changed so as to be consistent with the change in the upper life cycle definition.

  The specific examples referring to FIGS. 9 and 10 are merely examples of changes in the lower life cycle definition that are consistent with the changes in the upper life cycle definition. If the changed lower life cycle definition includes the same state and state transition condition as the changed upper life cycle definition, the lower life cycle definition may be changed by a method different from the above specific example. For example, in the change process of the lower life cycle definition, the change of the due date of the lower state in order to maintain the ratio of the period of each lower state before the change is performed only by making the same change as the change of the due date in the upper life cycle definition. It is good also as what is not performed.

  In another example of changing the life cycle definition, a state in the life cycle definition may be added. For example, when a state is added in the upper life cycle definition, a state and a state transition condition similar to the state added in the upper life cycle are added in the recursive change process for the lower life cycle definition. For example, referring to FIG. 11 schematically showing another example of the contents of each life cycle definition, the life cycle definition “for component A specifications” illustrated in FIGS. As a subordinate state of the “created” state, in addition to the “draft created” state and the “modified” state, it is assumed that a change is made to add a “preliminary” state after the “modified” state. At this time, the “preliminary” state added in the upper life cycle definition is added to the lower life cycle definition “for component A specification”. In the example of FIG. 11, for the “correction” state whose period has been shortened by the addition of the “preliminary” state, the due date of the lower state “personal correction” is not changed, but each substate “personal correction”, “ The ratio of the “upper length correction” period may be maintained before and after the change.

  In the example of the embodiment described above, the due date of each state is set as the state transition condition in the life cycle definition. In another example of the state transition condition, a condition based on the document attribute may be defined. For example, a change in the value of a specific item of the document attribute may be a condition for transition of the document state. For example, the document attribute may include information indicating whether a specific user has approved the document. In this case, for example, it is possible to specify the user identification information of the manager who gives approval to the document according to the life cycle definition, and to set that the approval of the identification information by the user is given as the state transition condition. In the document processing unit 14, specification of the document state according to the life cycle definition of this example (for example, step S38 in FIG. 6) is performed by, for example, checking whether or not the identification information specified by the state transition condition in the document attribute is approved by the user. It is done by judging. Moreover, in the change of the life cycle definition of this example, it is possible to change the user who gives approval, for example. In this case, a change is made to rewrite the approver's identification information in the state transition condition of the upper life cycle definition. Similarly, by changing the approver's identification information for the lower life cycle definition, consistency with the change in the upper life cycle definition is maintained.

  In the various processing examples described above, the life cycle definition ID associated with each document is acquired with reference to the document attribute table stored in the document DB 30. In another example of processing, each electronic document file in the document DB 30 may be acquired in response to designation of the storage location of each document, and a life cycle definition ID included as attribute information in the electronic document file may be acquired. . In still another example, information that associates a document with a life cycle definition may be stored in the life cycle definition DB 20, and the life cycle definition associated with each document may be specified with reference to this information.

  The document management apparatus 10 exemplified above is typically realized by executing a program describing functions or processing contents of each unit of the document management apparatus 10 described above on a general-purpose computer. In the computer, for example, as shown in FIG. 12, a CPU (central processing unit) 80, a memory (primary storage) 82, various I / O (input / output) interfaces 84, and the like are connected via a bus 86 as hardware. Circuit configuration. Also, a disk drive 90 for reading portable non-volatile recording media of various standards such as an HDD (Hard Disk Drive) 88, a CD, a DVD, and a flash memory via the I / O interface 84, for example, to the bus 86. Connected. Such a drive 88 or 90 functions as an external storage device for the memory. A program in which the processing content of the embodiment is described is stored in a fixed storage device such as the HDD 88 via a recording medium such as a CD or DVD or via a network, and is installed in a computer. The program stored in the fixed storage device is read into the memory and executed by the CPU, whereby the processing of the embodiment is realized.

It is a figure which shows the structural example of a document management apparatus. It is a figure which shows the example of the data content of life cycle definition DB. It is the figure which showed typically an example of the data content of life cycle definition DB illustrated in FIG. It is a figure which shows an example of the document attribute table memorize | stored in document DB. It is a flowchart which shows the example of the procedure of the process which the production | generation registration part of a life cycle definition process part performs. It is a flowchart which shows the example of the procedure of the process which a document process part performs. It is a flowchart which shows the example of the procedure of the process which the change part of a life cycle definition process part performs. It is a flowchart which shows the example of the partial procedure of the process which the change part of a life cycle definition process part performs. It is a figure for demonstrating one specific example of a life cycle definition change process. It is a figure for demonstrating another one specific example of a life cycle definition change process. It is a figure for demonstrating another one specific example of a life cycle definition change process. It is a figure which shows the example of the hardware constitutions of a computer.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Document management apparatus, 12 Life cycle definition process part, 14 Document process part, 20 Life cycle definition DB, 30 Document DB, 40 User information DB, 80 CPU, 82 Memory, 84 I / O interface, 86 bus, 88 HDD, 90 disk drive, 120 generation registration unit, 122 change unit, 140 life cycle control unit.

Claims (8)

Information defining a plurality of states that can be taken by the electronic document stored in the storage means, information defining a condition in which the state of the electronic document transits from one of the plurality of states to another state, To a computer that can refer to document status definition information including
For at least one of the plurality of states defined by the first document state definition information stored in the storage means, information defining a plurality of lower states included in the state, and the document state is the plurality of states Information defining a condition for transitioning from one lower state to another lower state among the lower states, and the generated information and information included in the first document state definition information And generating a second document state definition information including:
The second document state definition information and information indicating that the second document state definition information is lower document state definition information than the first document state definition information are stored in the storage unit. Step to
A document management program characterized by causing In response to the change request specifying the document state definition information to be changed and the content of the change, the document state definition information to be changed is acquired from the storage unit, and based on the content of the change specified by the change request A first changing step for changing at least a part of the definitions of the plurality of states and the transition conditions in the document state definition information to be changed;
When lower document state definition information is stored in the storage unit with respect to the document state definition information to be changed, the lower document state definition information is based on the content of the change in the first change step. A second change step for making changes,
The document management program according to claim 1, further causing the computer to execute. The transition condition included in the document state definition information is a condition that represents a transition time from the one state to another state,
In the first change step, the time represented by the transition condition in the document state definition information to be changed is changed,
In the second change step, the time represented by the transition condition in the lower document state definition information is changed to the time after the change in the first change step.
The document management program according to claim 2, wherein: In the second change step, when the state related to the change of the timing further includes a plurality of lower states, the state is changed from one lower state to the other lower state among the plurality of lower states. Change the time,
The document management program according to claim 3. The transition condition included in the document state definition information is a condition related to attribute information of an electronic document,
In the first change step, the condition relating to the attribute information of the electronic document represented by the transition condition in the document state definition information to be changed is changed,
In the second change step, the condition relating to the change in the attribute information of the electronic document represented by the transition condition in the lower document state definition information is changed to the condition after the change in the first change step.
The document management program according to claim 2, wherein: In the first changing step, a state that an electronic document can take is added to the document state definition information to be changed, information defining the added state, and a condition for transitioning from the added state to another state. Change the document status definition information further including the information to be defined,
In the second change step, the document state definition information further includes information added to the document state definition information to be changed in the first change step with respect to the lower document state definition information. Make changes,
The document management program according to claim 2, wherein: The information defining the plurality of states included in the document state definition information includes information indicating the use authority of the document in each state,
In response to a request for using an electronic document associated with one of the document state definition information stored in the storage means, the document state definition information associated with the requested electronic document and the document state definition information On the other hand, the document state definition information positioned higher in the hierarchical structure constituted by the plurality of document state definition information stored in the storage unit is acquired from the storage unit, and the request target in each of the acquired document state definition information A specific step of identifying the state of the electronic document of
A determination step of determining whether or not the request target document can be used with reference to the use authority in each state specified in the specifying step;
The document management program according to claim 1, further causing the computer to execute. Information defining a plurality of states that can be taken by the electronic document stored in the storage means, information defining a condition in which the state of the electronic document transits from one of the plurality of states to another state, Information for defining a plurality of lower-level states included in the state with respect to at least one of the plurality of states defined by the first document state definition information. And information defining a condition for transition of the document state from one lower state to the other lower state of the plurality of lower states, and the generated information and the first document Generating means for generating second document state definition information including information included in the state definition information;
The second document state definition information and information indicating that the second document state definition information is lower document state definition information than the first document state definition information are stored in the storage unit. Means to
A document management apparatus comprising:

Images