JP5240086B2 - Data management program - Google Patents

Description

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

  In a database backup, a differential backup that records information indicating changes in the contents of the database may be performed. For example, a full backup that records the entire contents of the database may be performed once, and a differential backup may be performed for the change in the contents of the database from the time when the full backup was performed.

  Patent Document 1 discloses a data recording system including a library device that includes a full data backup volume that backs up full data that is the entire database, and a differential backup volume that backs up differential data that is a database update. . In the system described in Patent Document 1, backup of full data to a full backup volume is performed every time a plurality of backups of differential data to a differential back volume are performed. When the next generation full backup is completed, this system releases the differential backup data area in the library device, and when recording new full backup data, it is on a volume where backup data of a generation older than the specified generation is recorded. The area is reused by overwriting.

  Patent Document 2 discloses a technique for managing a database by storing management information of each object registered in a database and backing up a management table part that is updated as needed. In the technique described in Patent Document 2, a copy of the contents of the management table at that time is saved as snapshot information at each preset backup timing, and the contents of the management table at that time are stored in the previous backup. By comparing with the snapshot information created at the timing, the change contents of the database between the previous time and the current time are obtained, and backup information representing the change contents is created and stored.

JP-A-11-194964 JP 2001-344139 A

  When performing differential backup of a database every preset period, the storage capacity required for backup is smaller than when performing full backup every time. However, when performing differential backup every time, when acquiring the contents of a database at an arbitrary time, it is necessary to perform processing for reproducing the contents of the database at the time using information on the differential backup. On the other hand, when performing a full backup every time, when acquiring the contents of a database at an arbitrary time, the entire contents of the database at that time can be acquired simply by acquiring information about the full backup at that time. Therefore, it is not necessary to perform the reproduction process as described above. Therefore, when acquiring the contents of the database at an arbitrary time, the time required for processing is shorter when performing a full backup than when performing a differential backup.

  An object of the present invention is to reduce the storage capacity required for data recording and record the change of data each time as compared with the case where the entire data is recorded every time when the update of data to be managed is recorded. It is an object of the present invention to provide a data management program and a data management apparatus that can shorten the time taken to acquire data contents at an arbitrary time as compared with the case.

According to the first aspect of the present invention, there is provided a history of personnel information updated including information representing members belonging to a group included in an organization and a document management rule updated including a document management rule based on the group. A step of storing a history in a storage unit with a version, a step of storing a document to be managed in the storage unit, a step of associating the document with the document management rule, Correlating each version with a version of the personnel information corresponding to the validity period of each version of the document management rule, receiving a specification of the document management rule, and history of the specified document management rule Along with the output, output the personnel information of the version corresponding to each version of the document management rule to be output A data management program for causing and a step that, a.
Further, in the invention according to claim 2 , in the invention according to claim 1, when storing the history of the updated personnel information in the storage means, according to the degree of change of the personnel information due to the update, or the entire information of personnel information after the update cause stored in the storage means, determining step of determining a difference amount information that put in this update cause stored in the storage means, Ru and further the computer to execute a.

The invention according to claim 3 is the invention according to claim 2 , wherein, in the determination step, when the value indicating the degree of change is equal to or less than a preset threshold value, the difference information is stored in the first storage unit. Decide what to do.

The invention according to claim 4 is the invention according to claim 3 , wherein, in the determination step, when the value indicating the degree of change is larger than the threshold, the overall information is stored in the second storage unit. decide.

The invention according to claim 5, in the invention according to claim 2, the value representing the degree of pre-Symbol change is determined based on the number of the members for which the change Te updates smell the personnel information.

The invention according to claim 6 is the invention according to claim 4 , wherein when the designation of a certain period is accepted, the second information stored in the second storage means is the newest before the designated period among the whole information in the second storage means. Using the overall information stored in the means and the difference information stored in the first storage means between the time when the overall information is stored in the second storage means and the specified time. The computer is further caused to execute a generating step of generating personnel information at the designated time.

Invention, in the invention according to claim 6, comprising the steps of: referring to the document management rules representing the user relating to the rules a said document management rules groups in the tissue, before Symbol generation step according to claim 7 in using the generated the personnel information, and an output step of identifying a user corresponding to the group represented before SL document management rules, outputs in association with the document management rules specified user, Is further executed by the computer.

According to the invention according to claim 1 or 7, it is possible to specify which user in the organization was involved in the operation of the document at the designated time.
Further, according to the invention according to claim 2, while reducing the storage capacity required for recording the data as compared with the case of recording every time the entire data when recording the update data of the managed data changes in Compared with the case where the minute is recorded every time, the time taken to acquire the data contents at an arbitrary time can be shortened.

According to the invention according to claim 3, when it can be considered that the benefit of reducing the storage capacity by recording the difference information is greater than the disadvantage of having to perform the process of reproducing the data contents using the difference information Difference information can be recorded.

According to the fourth aspect of the invention, the time taken to acquire the data contents at any time can be shortened by recording the entire information rather than the disadvantage of requiring a larger storage capacity than when the difference information is recorded. Overall information can be recorded when the benefit of what can be done is considered greater.

According to the invention which concerns on Claim 5 , when the data is updated according to the scale of the change of the member in an organization, the value showing the grade of the change of the data before an update and the data after an update can be determined.

According to the invention which concerns on Claim 6 , the whole content of the data of the management object in the designated time can be acquired.

It is a block diagram which shows the example of a structure of a document management system. It is a block diagram which shows the example of the outline of an internal structure of a document management server. It is a figure which shows the example of the content of a document management table. It is a figure which shows the example of the content of a rule management table. It is a figure which shows the example of the content of a document and rule fixed table. It is a figure which shows the example of the content of organization information. It is a figure which shows the example of the content of difference information. It is a figure which shows the example of the content of a virtual version management table. It is a figure which shows the example of the content of a rule and organization fixed table. It is a flowchart which shows the example of the procedure of the process which an organization information processing part performs. It is a flowchart which shows the example of the procedure of the process which interprets the rule content of the application rule of the designated document in the designated date. It is a flowchart which shows the example of the procedure of the process which specifies the application rule of the designated document in the designated date. It is a flowchart which shows the example of the procedure of the process which determines the organization information used for interpretation of an application rule. It is a flowchart which shows the example of the procedure of the process which calculates | requires the log | history of a rule. It is a flowchart which shows the example of the partial procedure of the process which calculates | requires the log | history of a rule. It is a flowchart which shows the example of the partial procedure of the process which calculates | requires the log | history of a rule. It is a figure which shows the example of the content of the log | history of a rule. It is a block diagram which shows the example of the hardware constitutions of a computer.

  Hereinafter, an embodiment of the present invention will be described by taking a document management server for managing documents used in an organization such as a company or a local government as an example.

  FIG. 1 is a diagram illustrating an example of a schematic configuration of a system including a document management server. 1 includes a document management server 10, a personnel information management server 20, and client terminals 30-1, 30-2,... (Hereinafter collectively referred to as a client terminal 30) connected to each other via a network 40. Have a configuration.

  The client terminal 30 is a terminal device that uses a document managed by the document management server 10. For example, the client terminal 30 executes various operations (edit, print, delete, etc.) on the document managed by the document management server 10 in accordance with a user instruction.

  The personnel information management server 20 is a server device that manages information related to members (users) of an organization that uses the system of the example of FIG. The personnel information management server 20 includes, for example, a database storing identification information of each user, users belonging to each group included in the organization, business roles of each user in the organization, and the like.

  The document management server 10 manages documents used in the organization. FIG. 2 shows a schematic example of the internal configuration of the document management server 10. A part of the functions of the document management server 10 functions as a data management apparatus according to an embodiment of the present invention.

  Referring to FIG. 2, the document management server 10 includes a document repository 100, a rule repository 110, an organization information repository 120, a document processing unit 130, a rule registration / editing unit 140, a rule history processing unit 160, and an organization information processing unit 170. Prepare.

  The document repository 100 stores documents to be managed by the document management server 10. Further, the document repository 100 stores a document management table in which information related to documents stored in the document repository 100 is registered.

  FIG. 3 shows an example of the contents of the document management table. In the document management table in the example of FIG. 3, document attribute information representing the attribute of the document is registered in association with the document ID that is the document identification information. In the table of the example of FIG. 3, the items of document attribute information include sub items of document version, creation date / time, file name, document type, and status. The document version represents the version (version) of the document, and a plurality of document versions can exist for one document ID. In the system of this example, one document is specified by a combination of a document ID and a document version. The creation date and time represents the date and time when the document of the corresponding document version was created. The file name is a name given to the corresponding document file. In this example, the same file name is assigned to documents having the same document ID. The document type represents the type of the corresponding document. In the example of FIG. 3, the value of the document type is set based on the use of the document in the organization, such as “contract”, “estimate”, and “receipt”. The value of the status item represents one of the possible states of the document between the generation and disposal of the document. In the example of FIG. 3, the value of the state corresponds to one stage or operation of the business flow performed on the document in the organization. Here, the flow of work is, for example, work on a document in a work such that the document is “created”, “approved” by the manager, and then “fixed (stored in a state of being kept)”. Means the flow of

  The form of the document management table is not limited to the form illustrated in FIG. For example, the document attribute information may include other information of the lower items illustrated in FIG. For example, information representing the creator of the document, information representing the storage location of the document in the document repository 100, and the like may be registered as part of the document attribute information. Further, for example, in the example of FIG. 3, the document ID and the file name have a one-to-one correspondence, and therefore registration of either the document ID or the file name in the document management table may be omitted. When the document ID is omitted, the file name may be used as document identification information.

  Referring to FIG. 2 again, the rule repository 110 stores information related to rules that represent rules for document operation. The rule repository 110 stores a rule management table and a document / rule fixed table.

  FIG. 4 shows an example of the contents of the rule management table. In the example table of FIG. 4, a rule version, a document type, a creation date and time, and a rule content are registered in association with a rule ID that is rule identification information. There can be a plurality of rule versions for one rule ID. In the system of this example, one rule is specified by a combination of the rule ID and the rule version. The document type represents the document type of the document operated according to the corresponding rule, and corresponds to the document type described above with reference to FIG. In this example, the same document type is associated with a rule having the same rule ID. The creation date represents the date when the rule of the corresponding rule version was created. The rule content represents the content of the rule when operating the document to which the corresponding rule is applied. In the table of the example of FIG. 4, in the rule contents item, access privilege, status, access privilege mask, state transition condition, and trigger subordinate items are registered.

  In the access right item, the content of the access right for the application target document is set. The content of the access right is represented, for example, by information associating information representing an execution subject of an operation with respect to a document and an operation type permitted or prohibited for the execution subject. In the system of this example, as information representing an execution subject of an operation on a document, a user ID that is user identification information, a group ID that is identification information of a user group, or role identification information that represents a user's business role A role ID is used.

  In the state item, states that can be taken by the application target document are registered, and this “state” corresponds to the “state” of the document described above with reference to FIG. The value of the status item is expressed as a set of status values that can be taken by the document to which the rule is applied (for example, {"Creating", "Proofing", "Approved", "Fixed"}, etc.). May be.

  The access right mask is information that is set for each possible state of the application target document and is used to determine the access right of the document having the state. For example, when the document to which the rule is applied is in a specific state, a logical operation is performed on the above-described access right set as the access right for the application target document and the access right mask set for the state. The access right obtained by performing the AND operation is used to restrict access to the document.

  The state transition condition represents a condition for the application target document to transition from one state to another state. The state transition condition may be set, for example, a date and time for transition from one state to the next state. Alternatively, for example, a state transition condition may be that a specific subject (represented by a user ID, group ID, or role ID) performs a specific type of operation on a document.

  The trigger represents the content of processing executed by the document management server 10 when a certain condition is satisfied with respect to the application target document. For example, the trigger is represented by a set of a process execution condition and the content of the process to be executed. For example, the processing execution condition may be that a specific type of operation has been executed on the document to be applied, or that a specific type of operation has been executed by a specific subject. Further, for example, the processing execution condition may be expressed by the date and time or the elapsed time from a certain time. Examples of processing to be executed include transmission of notification information such as e-mail to a specific user or a user of a specific group or role, and FAX (facsimile) transmission to a preset destination.

  The information defining the rule content described above includes information about the user. For example, in the definition of the access right and the access right mask, the execution subject of the operation is represented by a user ID, a group ID, or a role ID. Further, when a specific subject is defined to execute a specific type of operation as a state transition condition or a trigger process execution condition, the subject is also represented by a user ID, a group ID, or a role ID. . Furthermore, for example, as a processing content executed by a trigger, a user ID, a group ID, or a role ID may be specified and notification information may be transmitted to the corresponding user. As described above, the user, group, and role included in the information that defines the rule contents are hereinafter referred to as “participants” of the rule.

  In addition, the aspect of the rule content is not limited to that described above with reference to FIG. When other rules in the example of FIG. 4 are used for document operation, the rules may be registered as rule contents in the rule management table. If there is no need for the operation of the document, the setting of some of the subordinate items of the rule contents may be omitted.

  FIG. 5 is a table showing an example of the contents of the document / rule fixed table stored in the rule repository 110. In principle, in the system of this example, a rule that is applied to a document at a certain time is a rule ID (FIG. 4) corresponding to the document type (FIG. 2) of the document at that time (creation date and time). The rule with the latest rule version. The document / rule fixed table is a table representing exceptions of rules applied to a document. In the example of FIG. 5, a set of rule ID and rule version is registered in the document / rule fixed table in association with a set of document ID and document version. For example, the second line of the table in the example of FIG. 5 shows that the document ID is “Doc1” and the document version is “1.0” regardless of the latest version of the rule corresponding to the document type of the document. This indicates that a rule with a rule ID “Rule2” and a rule version “1.0” is applied and operated.

  Returning to the description of FIG. 2, the organization information repository 120 stores organization information based on the information acquired from the personnel information management server 20. The organization information in the system of this example includes information on users, groups, and roles that can be involved in rules applied to document operations. Organization information is an example of data to be managed by the data management apparatus according to the embodiment of the present invention.

  FIG. 6 shows an example of the contents of the organization information. FIG. 6A is an example of a table in which group IDs of groups included in an organization are associated with user IDs of users belonging to the groups. FIG. 6B is an example of a table in which role IDs of roles representing roles in the organization are associated with user IDs of users having each role. In the following description, it is assumed that the organization information includes the user ID of the user belonging to each group and the user ID of the user having each role, as in the examples of FIGS. 6 (a) and 6 (b). Moreover, the organization information may include information associated with each user, each group, and each role in addition to the content information illustrated in FIG. For example, information that associates each user ID with the name and contact information (e-mail address, telephone number, FAX number, etc.) of the user may be included. Furthermore, for example, information that associates a group ID or role ID with the name or contact information of the group or role may be included.

  The organization information is used for interpretation of rules in the rule history processing unit 160 described in detail later. Here, “interpretation” of a rule means that when information representing the rule content includes a group ID or a role ID, a user corresponding to the group or role represented by the ID is specified.

  The organization information in the organization information repository 120 does not necessarily have the same content as the information in the database of the personnel information management server 20. The database of the personnel information management server 20 may also include information that is not necessary for document management, such as information related to personnel evaluation of each user. The organization information is generated based on the extracted information by extracting only information necessary for document management purposes from the database of the personnel information management server 20.

  Referring to FIG. 2 again, the organization information repository 120 stores the latest organization information, snapshot, difference information, virtual version management table, and rule / organization fixed table.

  The latest organization information is organization information corresponding to the information that the document management server 10 last acquired from the personnel information management server 20. The latest organization information includes information on users of each group and each role as in the example of FIG. 6 described above.

  A snapshot is a copy of the latest organization information at a certain time. Here, a certain “time” is, for example, a date and hour, minute, and second (eg, June 16, 00: 5: 30), date and time (eg, June 16, 00:05), Alternatively, it is expressed by a date (for example, June 16). In the following description, “date and time” or “date” is used as a word representing a certain “time”, but these words are examples of the expression of “time” and should not be interpreted in a limited manner. For example, in the following explanation, the part representing “time” by the word “date and time” is expressed as “time” in which “hour, minute, and second” are specified, or “time” in which only the date is specified without specifying time. It may be replaced with the expression. In addition, in the part representing “time” by the word “date”, an expression of “time” in which hour, hour, minute and second are specified may be used instead. The snapshot is generated by the tissue information processing unit 170 described in detail later.

  The difference information is information representing a difference between the latest organization information at a certain time and the organization information generated from the information acquired from the personnel information management server 20. The difference information is also generated by the tissue information processing unit 170 described in detail later.

  As will be described later, in the document management server 10 of this example, when the update of the database of the personnel information management server 20 is reflected in the latest organization information in the organization information repository 120, a snapshot or difference information is generated. In other words, the snapshot or the difference information is generated when the latest organization information in the organization information repository 120 is synchronized with the organization information corresponding to the contents of the database of the personnel information management server 20. Then, identification information is generated and assigned to each of the snapshot and the difference information. In the following description, the identification information given to the snapshot and the difference information is called “virtual organization version”. Here, the term “virtual” is used because the generation timing of the snapshot or difference information in the document management server 10 is the generation timing of a new version of information in the database of the personnel information management server 20 (that is, personnel This is because it may be determined independently from the data update timing of the information management server 20.

  FIG. 7 is a table showing an example of the content of the difference information. The table in the example of FIG. 7 includes items of a virtual organization version, a target ID, an operation, and an argument ID. The content of the difference information of the corresponding virtual organization version is represented by the combination of the target ID, the operation, and the argument ID. The target ID represents identification information of a subject related to the difference, and is represented by a user ID, a group ID, or a role ID in this example. The operation represents a mode of change of the subject represented by the target ID. The argument ID represents the ID of a group or role involved in the change when the target ID is a user ID. For example, referring to the two rows corresponding to the virtual organization version “20090201” in the table of the example of FIG. 7, the first row shows that the user “user10” (target ID) is assigned from the group “GroupK” (argument ID) to “ Deletion ”(operation). The second line indicates that the user “user10” (target ID) is “added” (operated) to the group “GroupX” (argument ID). That is, the two rows represent that the user “user10” has moved from the group “GroupK” to another group “GroupX”. Further, referring to the third row of the row corresponding to the virtual organization version “20090214”, it can be seen that the user “user17” (target ID) is “added” (operated) to the role “Role3” (argument ID). In other words, it can be seen that the user “user17” has played the role of the role “Role3”. Furthermore, the first row of the five rows corresponding to the virtual organization version “20090301” represents that the group “GroupZ” (target ID) has been “created” (operated). That is, it represents that a new group “GroupZ” has been created in the organization. Here, the argument ID is set to be empty.

  Referring to FIG. 2 again, the virtual version management table in the organization information repository 120 is a table for managing snapshots and difference information. FIG. 8 shows an example of the contents of the virtual version management table. In the table in the example of FIG. 8, the application date, the presence / absence of a snapshot, and reference information to data contents are registered in association with the virtual organization version. The application date represents a date on which the organization information represented by the snapshot or the difference information to which the corresponding virtual organization version is assigned becomes valid. The application date may be, for example, the date when the latest organization information in the organization information repository 120 is synchronized with the contents of the database of the personnel information management server 20, that is, when the snapshot or the difference information is generated. In the case of this example, the application date does not necessarily match the date when the database is updated in the personnel information management server 20. Alternatively, instead of the date when the snapshot or the difference information is generated, the date when the database of the personnel information management server 20 is updated may be used as the application date of the snapshot or the difference information reflecting the update. . The presence / absence of a snapshot indicates the presence / absence of a snapshot to which a corresponding virtual organization version is assigned. When there is no snapshot, the virtual organization version is given to the difference information. The reference information to the data contents represents the storage position in the organization information repository 120 of the snapshot or difference information to which the corresponding virtual organization version is assigned.

  The aspect of the virtual version management table is not limited to the example of FIG. For example, it is not necessary to register “presence / absence” of the snapshot of the virtual organization version as long as the information indicating the snapshot or the difference information is registered for each virtual organization version. Further, for example, instead of registering reference information to the data content, the data content itself of the corresponding snapshot or difference information may be registered.

  FIG. 9 shows an example of the contents of the rule / organization fixed table stored in the organization information repository 120. In the system of this example, the organization information used for the interpretation of the rule is in principle at the time within the validity period of the rule version of the rule (the period from the creation date of the rule version to the creation date of the next rule version). Organization information corresponding to the virtual organization version. The rule / organization fixed table represents an exception of organization information used for interpretation of rules. In the example of FIG. 9, a virtual organization version is registered in association with a set of rule ID and rule version. For example, the second row of the table in the example of FIG. 9 shows that when interpreting a rule whose rule ID is “Rule1” and whose rule version is “1.1”, the virtual organization version “ Indicates that the organization information corresponding to “20090214” is used.

  Referring to FIG. 2 again, the document processing unit 130 performs processing related to the document. For example, a document newly created at the client terminal 30 is received from the client terminal 30 via the network 40, the received document is stored in the document repository 100, and document attribute information of the document is registered in the document management table. In addition, the document processing unit 130 includes an access management unit 132. The access management unit 132 performs access restriction on the document. For example, the access management unit 132 determines whether to allow access to the requested document in response to an access request to the document from the client terminal 30. The determination of whether access is possible is made based on the interpretation result of a rule history processing unit 160 (to be described later) that interprets a rule applied to the requested document.

  The rule registration / editing unit 140 registers and edits information in the rule repository 110. For example, an instruction by a user or a system administrator is received via the client terminal 30 and the network 40 or an input device (not shown) of the document management server 10, and a new rule is added to the rule management table according to this instruction. Register or change the contents of a registered rule. Further, the contents of the document / rule fixed table may be changed in accordance with an instruction from a user or a system administrator.

  The rule history processing unit 160 performs processing related to the rule history. The rule history processing unit 160 includes a rule interpretation unit 162. The rule interpretation unit 162 refers to the rule repository 110 and the organization information repository 120 and interprets the content of the rule. For example, with respect to the rule content including the group ID or role ID, a process of specifying a user belonging to the group or a user having the role is performed.

  For example, the rule history processing unit 160 receives past date / time and document designation, identifies a rule that has been applied to the designated document at the date / time designated, and the rule interpretation unit 162 identifies the rule content of the identified rule. Output the interpreted result. In addition, for example, a specification of a rule ID may be received, and a process for obtaining a change history of the rule content of the specified rule ID may be performed. Also, the rule history processing unit 160, for example, when the document processing unit 130 receives a document access request from the client terminal 30, a rule applied to the requested document in response to a request from the document processing unit 130. May be returned to the document processing unit 130 by the rule interpretation unit 162.

  The organization information processing unit 170 performs a process of recording (storing) information in the organization information repository 120. For example, the organization information generated based on the information acquired from the personnel information management server 20 is recorded in the organization information repository 120 as the latest organization information. Further, when recording the latest organization information, the snapshot or difference information described above is generated, and a virtual organization version is assigned and recorded in the organization information repository 120. Also, for example, an instruction from a user or an administrator may be received via an input device (not shown), and processing for editing the contents of the rule / organization fixed table in the organization information repository 120 may be performed.

  The example of the configuration of the document management server 10 has been described above. Hereinafter, an example of a procedure of processing executed by the document management server 10 will be described.

  FIG. 10 is a flowchart illustrating an example of a procedure of processing executed by the organization information processing unit 170. The organization information processing unit 170 executes the processing of the procedure in the example of FIG. 10 periodically or at a timing instructed by a system administrator or the like.

  Referring to FIG. 10, first, the organization information processing unit 170 refers to a database provided in the personnel information management server 20 via the network 40 (step S10). Next, it is determined whether or not there is a change from the information corresponding to the latest organization information stored in the organization information repository 120 in the database of the personnel information management server 20 (step S12). This determination is performed by, for example, confirming whether the users of each group and the users of each role included in the latest organization information are registered as corresponding users of the group and role in the database of the personnel information management server 20. Just do it.

  If the result of determination in step S12 is that there is no change, processing is terminated, and if there is a change, processing proceeds to step S14.

  In step S <b> 14, the organization information processing unit 170 updates the latest organization information in the organization information repository 120 according to the contents of the database of the personnel information management server 20. For example, in the table in the example of FIG. 6A or 6B, the user ID associated with the group ID or role ID is changed, or the group ID or role ID is added or deleted.

  Next, the organization information processing unit 170 determines whether or not the present time is preset by an administrator or the like as the time for recording the snapshot (step S16). The time when the snapshot is recorded is, for example, a time corresponding to the division of the operation period of the organization (for example, fiscal year, etc.), and the content of the database of the personnel information management server 20 is large due to a significant personnel change. It is set at a time when it is known in advance that it will be changed. As the setting mode, for example, the date and time may be used, or an elapsed period from a preset reference time (such as when the previous snapshot was recorded) may be used.

  When it is time to record the snapshot (YES in step S16), the organization information processing unit 170 records a copy of the updated latest organization information in the organization information repository 120 as a snapshot (step S24). At this time, the organization information processing unit 170 generates and assigns a virtual organization version to the snapshot.

  When it is not time to record the snapshot (NO in step S16), the organization information processing unit 170 obtains the degree of change of the organization information (step S18). In step S18, in this example, a value representing the degree of change in the organization information is obtained based on the number of users whose group or role has changed before and after the update of the latest organization information in step S14. For example, the ratio of the number of users who have changed groups or roles with respect to the total number of users in the system of this example is obtained, and the obtained ratio is used as the value representing the degree of change in the organization information. Or it is good also considering the number itself of the user who changed in the group or the role as the value showing the degree of change of organization information.

  If the value representing the degree of change obtained in step S18 is equal to or less than a preset threshold value (YES in step S20), the organization information processing unit 170 generates difference information and records it in the organization information repository 120. (Step S22). For example, regarding a user who has moved between groups, the user ID of the user who has moved is the target ID, the operation is “delete”, the argument ID is the group ID of the group before the transfer, and the user ID of the user who has moved As the difference information, the ID is generated, and the operation is “add” and the argument ID is the group ID of the group after the change (see FIG. 7). Further, the organization information processing unit 170 generates and assigns a virtual organization version to the generated difference information.

  If the value representing the degree of change obtained in step S18 exceeds the threshold (NO in step S20), snapshot recording is performed in step S24. A virtual organization version is given to this snapshot.

  When the difference information is recorded (step S22) or the snapshot is recorded (step S24), the organization information processing unit 170 registers the difference information or the snapshot in the virtual version management table (see FIG. 8) (step S26). ). In step S26, for example, the organization information processing unit 170 first generates one entry corresponding to the virtual organization version assigned to the difference information or the snapshot in the virtual version management table. In the generated entry, the value of each item of the application date, presence / absence of snapshot, and reference information to the data contents is registered. After step S26, the process of the procedure in the example of FIG. 10 ends.

  In the processing of the procedure in the example of FIG. 10 described above, when the latest organization information is updated, it is a preset snapshot recording time (YES in step S16) or represents the degree of change in organization information. When the value exceeds a preset threshold value (NO in step S20), a snapshot is recorded (step S24). On the other hand, if it is not the snapshot recording time (NO in step S16) and the value indicating the degree of change in the organization information is equal to or smaller than the threshold (YES in step S20), difference information is recorded (step S22). In other words, in the process of the procedure in the example of FIG. 10, a snapshot is recorded when the change in the organization information is considered large before and after the update of the latest organization information, and the difference is obtained when the change in the organization information is considered small. Record information.

  Further, in the processing of the procedure in the example of FIG. 10, the larger the threshold (step S20) for determining whether to record the snapshot or the difference information, the more the difference information is recorded. The smaller the is, the more often snapshots are recorded. If the difference information is recorded more than the snapshot, the organization information repository 120 uses less storage capacity. On the other hand, in the later-described processing for generating organization information corresponding to the virtual organization version, the processing speed is faster if more snapshots are recorded than the difference information. Therefore, this threshold value is set in advance by the system administrator in consideration of the storage capacity of the organization information repository 120 and the calculation amount of the organization information generation processing described later, for example, according to the scale of the organization and the management policy. . For example, when the degree of change of organization information is expressed by the ratio of the number of users who have changed to all users, a value in the range of 2.0% to 5.0% is set as a threshold value. For example, when the degree of change of organization information is represented by the number of users who have changed, for example, the number of people according to the size of the organization may be set as a threshold.

  The rule is interpreted in the document management server 10 using the organization information recorded in the organization information repository 120 as in the above example.

  FIG. 11 is a flowchart illustrating an example of a procedure of processing for interpreting rule contents at a certain past time for a certain document. For example, when receiving a user or administrator instruction via the client terminal 30 and the network 40 or via an input device (not shown) of the document management server 10, the rule history processing unit 160 performs the procedure of the example of FIG. Start processing.

  Referring to FIG. 11, the rule history processing unit 160 acquires the designated document and the designated date and time (step S30). The rule history processing unit 160, for example, specifies the document ID of the document specified by the user or the administrator and the date and time specified by the user or the administrator from the input device (not shown) of the client terminal 30 or the document management server 10, respectively. And get as the specified date.

  When the specified document and the specified date / time are acquired, the rule history processing unit 160 specifies a rule to be applied to the specified document at the specified date / time (step S32).

  FIG. 12 shows an example of a detailed procedure in step S32 of FIG. When step S32 of FIG. 11 is started, processing of the procedure of the example of FIG. 12 is started.

  Referring to FIG. 12, the rule history processing unit 160 refers to the document management table (see FIG. 3) of the document repository 100, and acquires the document version of the designated document at the designated date and time (step S320). For example, among the document versions associated with the document ID of the designated document, a version whose creation date is before the designated date and is closest to the designated date may be acquired.

  Next, the rule history processing unit 160 refers to the document / rule fixing table (see FIG. 5) of the rule repository 110, and the combination of the document ID of the designated document and the document version acquired in step S320 is a document / rule fixing table. Is registered (step S322).

  If a combination of the document ID and document version of the specified document exists in the document / rule fixed table (YES in step S322), it is registered in the document / rule fixed table in association with the pair of the document ID and document version. The rule specified by the set of rule ID and rule version is applied to the designated document (step S324).

  When the combination of the document ID and document version of the designated document does not exist in the document / rule fixed table (NO in step S322), the rule history processing unit 160 designates the document in the document management table (see FIG. 3) of the document repository 100. The document type associated with the document ID of the document is acquired (step S326). Then, the rule management table (see FIG. 4) of the rule repository 110 is referred to, and the rule of rule ID and rule version corresponding to the acquired combination of the document type and the specified date and time is set as a rule to be applied to the specified document (step S328). . In step S328, for example, among the rules of the rule ID associated with the document type acquired in step S326, the rule version having the creation date and time before the specified date and time and closest to the specified date and time may be set as the application rule. .

  After the application rule is specified in step S324 or step S328, the process of the procedure in the example of FIG. 12 ends, and the process proceeds to step S34 of FIG.

  Referring to FIG. 11 again, in step S34, the rule history processing unit 160 refers to the organization information repository 120, and sets the rule ID and rule version pair of the applied rule in the rule / organization fixed table (see FIG. 9). It is determined whether or not it has been done.

  If the application rule exists in the rule / organization fixed table (YES in step S34), the virtual organization version associated with the rule ID / rule version pair of the application rule in the rule / organization fixed table is acquired as the processing target. (Step S36).

  If the applied rule does not exist in the rule / organization fixed table (NO in step S34), the rule history processing unit 160 refers to the virtual version management table (see FIG. 8) in the organization information repository 120, and at the specified date and time. A virtual organization version is acquired as a processing target (step S38). Here, for example, a virtual organization version whose application date is before the specified date and time and is closest to the specified date and time may be acquired.

  When the virtual organization version to be processed is acquired in step S36 or step S38, the rule history processing unit 160 determines organization information used for interpretation of the application rule (step S40).

  FIG. 13 is a flowchart illustrating an example of a detailed procedure of step S40 of FIG. When the process of step S40 of FIG. 11 is started, the process of the procedure of the example of FIG. 13 is started.

  When the processing of the procedure in the example of FIG. 13 is started, the rule history processing unit 160 first refers to the virtual version management table (see FIG. 8) to determine whether a snapshot exists in the processing target virtual organization version. Is determined (step S400).

  If there is a snapshot (YES in step S400), a snapshot corresponding to the virtual organization version to be processed is acquired and used as organization information used for interpretation of the application rule (step S416). For example, the snapshot is acquired from the storage position of the organization information repository 120 represented by the reference information using the reference information to the data contents registered in association with the virtual organization version to be processed in the virtual organization version management table. do it.

  When there is no snapshot (NO in step S400), the rule history processing unit 160 acquires the latest snapshot before the virtual organization version to be processed (step S402). In step S402, for example, in the virtual version management table, the virtual organization version having the application date before the application date of the processing target virtual organization version and having the snapshot exists, the application date is the processing target virtual organization. A snapshot corresponding to the virtual organization version closest to the version may be acquired.

  Next, the rule history processing unit 160 acquires difference information generated between the application date of the snapshot acquired in step S402 and the application date of the processing target virtual organization version (step S404). Here, for example, a virtual organization version having a creation date and time between the snapshot application date acquired in step S402 and the specified date is extracted from the virtual version management table and associated with each of the extracted virtual organization versions. The difference information for each virtual organization version may be acquired from the organization information repository 120 using the reference information.

  Then, the rule content of the applied rule is referred to in the rule management table of the rule repository 110, and the user ID, group ID, and role ID included in the information defining the rule content are acquired as participants of the applied rule (step S406). .

  Further, a product set of a set of target IDs included in the difference information acquired in step S404 and a set of participants of the application rule is obtained (step S408).

  If the product set is not empty (NO in step S410), the difference information including the elements in the product set as the target ID is applied to the snapshot acquired in step S402 (step S412). Here, “apply” the difference information to the snapshot means that the organization information represented by the snapshot is changed in accordance with the change of the organization information represented by the difference information. For example, in the case of the difference information in the example of FIG. 7, it means that the organization information represented by the snapshot is changed according to the combination of the target ID, the operation, and the argument ID included in the difference information. As a specific example, when the difference information is the difference information of the virtual organization version “20090214” in the table of the example of FIG. 7, the user ID is selected from the user IDs associated with the group ID “GroupM” in the snapshot to be processed. “User25” is “deleted” (see the fourth row in the table of FIG. 7). Then, “user25” is “added” to the user ID associated with the group ID “GroupY” (see the fifth row in the table of FIG. 7). Further, “user17” is “added” to the user ID associated with the role ID “Role3” (see the sixth line in the table of FIG. 7). The rule history processing unit 160 uses the organization information obtained as a result of the processing in step S412 as organization information used for interpreting the application rule.

  If the product set is empty (YES in step S410), the snapshot acquired in step S402 (the latest snapshot before the processing target virtual version) is used as organization information used for interpretation of the application rule (step S414). The intersection set is empty, which means that the organization information was not changed for the participants of the applied rule between the time when the latest snapshot was generated before the virtual version to be processed and the virtual version to be processed. Means that. Therefore, in this case, the change in the organization information represented by the difference information does not affect the interpretation of the application rule. For this reason, if the product set is empty, the difference information is not applied to the snapshot.

  When the organization information used for interpretation of the application rule is determined in step S412, S414, or S416, the procedure of the example of FIG. 13 ends, and the process proceeds to step S42 of FIG.

  Referring to FIG. 11 again, in step S42, the rule interpretation unit 162 of the rule history processing unit 160 interprets the application rule using the organization information determined in step S40. For example, referring to the organization information determined in step S40 for the part represented by the group ID or role ID in the application rule, the user ID of the user belonging to the group ID or the user ID of the user having the role ID Identify.

  Then, the rule history processing unit 160 outputs the result of interpretation in step S42 (step S44). In step S44, for example, the interpretation result is displayed on the display device (not shown) of the client terminal 30 or the document management server 10 of the user who has instructed the start of the process of the example of FIG. For example, the user ID of each user corresponding to the group ID or role ID included in the rule content is displayed together with the rule content of the rule applied to the specified document at the specified date and time. For example, when displaying the access right included in the rule content, a list of user IDs of users who are permitted to perform the operation may be displayed for each type of operation permitted. Further, instead of the output of the aspect exemplified above, or together with the output of the aspect exemplified, the interpretation result may be recorded in the rule repository 110.

  After step S44, the process of the procedure in the example of FIG. 11 ends.

  As described above, the processing of the example described with reference to FIGS. 11 to 13 obtains information representing the specific contents of the rules for operating the designated document at the designated date and time. That is, according to the result of the interpretation in step S42 in FIG. 11, not only the information about the participation of the group or the role in the operation of the designated document, but also how the user of the specific user ID is involved in the operation of the designated document. Information representing that is obtained. For example, in the rule contents of the applied rule, when the access right for giving the authority to perform the “view” operation and the “edit” operation is defined for the user of a certain group or role, the result of step S42 in FIG. Information indicating which user ID of the user can perform the “browsing” operation and the “editing” operation on the designated document is obtained.

  In the process of the example described with reference to FIGS. 11 to 13, a past date is accepted as the designated date, but the rule history processing unit 160 may interpret a rule applied to the designated document at the current date. . For example, when the document processing unit 130 receives a document access request from the client terminal 30, the document processing unit 130 requests the rule history processing unit 160 to interpret the application rule using the requested document as the specified document and the current date and time as the specified date and time. In the case of this example, the rule history processing unit 160 acquires the latest organization information in the organization information repository 120 without performing the processing of step S38 when the process proceeds to NO in step S34 in the procedure of the example of FIG. Thus, the organization information used for interpreting the application rule is used, and the processing in step S42 and subsequent steps is executed. In step S44, the application rule interpretation result is output to the document processing unit 130. Using the result of this interpretation, the access management unit 132 of the document processing unit 130 restricts access to the document.

  Hereinafter, an example of a processing procedure for obtaining a change history of the rule contents of one rule ID will be described with reference to FIGS. 14 to 16. The rule content can be changed by, for example, rewriting part of it by an administrator or the like and registering it in the rule management table of the rule repository 110 as a new rule version. Or, for example, even if the information itself defining the rule content is not changed, but there is a change in the organization information for the participant of the rule, the user ID corresponding to the group ID or role ID included in the definition of the rule content Can be changed. In the processing of the procedures in the examples of FIGS. 14 to 16 described below, for a certain rule, a change history of the rule content due to registration of a new version and a change history of the rule content due to a change in organization information are obtained.

  For example, the rule history processing unit 160 specifies a rule ID from a user or an administrator via the client terminal 30 and the network 40 or via an input device (not shown) of the document management server 10, and the rule of the rule ID 14 is started, the process of the procedure in the example of FIG. 14 is started. Alternatively, for example, when the document management server 10 receives an instruction for specifying a document and obtaining a history of rules applied to the document, the processing of the procedure in the example of FIG. 14 may be started.

  First, referring to FIG. 14, the rule history processing unit 160 acquires a designated rule ID that is a rule ID of a rule whose history is to be obtained (step S50). When the user or administrator specifies a rule ID, the rule ID may be acquired as the specified rule ID. When a document is specified, the document type of the specified document is acquired from the document management table (see FIG. 3) of the document repository 100, and the rule ID associated with the acquired document type is the rule management table of the rule repository 110. What is necessary is just to acquire from (refer FIG. 4) and make it specification rule ID.

  Next, the rule history processing unit 160 refers to the rule management table of the rule repository 110, acquires one rule version of the specified rule ID, and pays attention to the rule specified by the set of the rule version and the specified rule ID. A rule is set (step S52). In this example, when there are a plurality of rule versions of the specified rule ID in step S52, one of the unprocessed rule versions with the oldest creation date is selected and acquired.

  When the attention rule is obtained, the rule history processing unit 160 determines whether or not the attention rule is registered in the rule / organization fixed table in the organization information repository 120 (step S54). Here, it is only necessary to confirm whether or not the set of the rule ID and rule version of the rule of interest is registered in the rule / organization fixed table.

  When the noticed rule exists in the rule / organization fixed table (YES in step S54), the rule history processing unit 160, in the rule / organization fixed table, the virtual organization associated with the pair of the rule ID and rule version of the noticed rule The version is acquired as the focused tissue version (step S56).

  Then, the rule history processing unit 160 generates organization information at the time of the target organization version (step S58). FIG. 15 shows an example of a detailed procedure in step S58 of FIG. When the process of step S58 of FIG. 14 is started, the process of the procedure of the example of FIG. 15 is started.

  Referring to FIG. 15, the rule history processing unit 160 refers to the virtual version management table in the organization information repository 120 and determines whether there is a snapshot corresponding to the target organization version (step S580).

  If there is a snapshot (YES in step S580), a snapshot of the target organization version is acquired from the organization information repository 120 (step S596). This snapshot is the organization information at the time of the target organization version. The rule history processing unit 160 records the organization information at the time of the target organization version in a temporary storage unit (not shown; hereinafter referred to as “temporary storage”) of the document management server 10. In the temporary storage, the organization information generated in the process of the procedures of the examples of FIGS. 14 to 16 and the virtual organization version corresponding to the organization information are stored in association with each other. The organization information stored in the temporary storage may be used when the organization information is generated again after the organization information is recorded. In addition, in the process of the procedure in the example of FIGS. 14 to 16, the organization information stored temporarily and the corresponding virtual organization version are overwritten and saved each time organization information is generated. The temporary storage is initialized and emptied by the rule history processing unit 160 at the start of processing of the procedure in the example of FIG.

  If there is no snapshot (NO in step S580), the rule history processing unit 160 determines whether the virtual organization version corresponding to the organization information stored temporarily is older than the target organization version (step S582).

  When the virtual organization version corresponding to the organization information stored temporarily is older than the target organization version (YES in step S582), a snapshot is generated between the virtual organization version corresponding to the organization information stored temporarily and the target organization version. It is determined whether or not it exists (step S584). The determination in step S584 refers to, for example, the virtual version management table, and determines the virtual organization version having an application date between the application date of the virtual organization version corresponding to the organization information stored temporarily and the application date of the target organization version. Of these, it may be performed by checking whether or not there is a snapshot.

  When a snapshot exists between the virtual organization version corresponding to the organization information stored temporarily and the target organization version (YES in step S584), or the virtual organization version corresponding to the organization information stored temporarily is the target organization When it is newer than the version (NO in step S582), the rule history processing unit 160 acquires the latest snapshot from the organization information repository 120 before the target organization version (step S586). Then, difference information from the acquired snapshot to the target organization version is further acquired from the organization information repository 120 (step S588), and this difference information is applied to the snapshot acquired in step S586 (step S590). The rule history processing unit 160 temporarily stores the organization information as a result of step S590 as organization information at the time of the target organization version.

  When there is no snapshot between the virtual organization version corresponding to the organization information stored temporarily and the target organization version (NO in step S584), the rule history processing unit 160 displays the virtual corresponding to the organization information stored temporarily. Difference information associated with the virtual organization version between the organization version and the target organization version is acquired from the organization information repository 120 (step S592). Then, the acquired difference information is applied to the organization information stored temporarily (step S594), and the organization information as a result of this application is stored in the temporary storage as organization information at the time of the target organization version. If NO is determined in step S584, the organization information stored temporarily represents the entire organization information that is newer than the latest snapshot before the target organization version. Therefore, by applying the difference information associated with the virtual organization version from the virtual organization version corresponding to the organization information in the temporary storage to the attention organization version to the organization information in the temporary storage, at the time of the attention organization version Organization information can be obtained.

  When the organization information at the time of the target tissue version is obtained in step S590, S594, or S596, the processing of the procedure in the example of FIG. 15 ends, and the processing proceeds to step S60 of FIG.

  Referring to FIG. 14 again, in step S60, rule interpretation unit 162 of rule history processing unit 160 interprets the attention rule using the organization information obtained in the process of step S58. Then, the rule contents as a result of interpretation are recorded in the rule repository 110 (step S62). In step S62, the rule history processing unit 160 generates identification information of the rule contents to be recorded, and records the generated identification information in association with the rule contents obtained as a result of the interpretation in step S60. The rule content identification information may be, for example, a character string including the current rule version to be processed and the target organization version. Hereinafter, the identification information associated with the rule contents obtained as a result of interpretation using the organization information is referred to as “virtual rule version”. The term “virtual” is used here because “virtual rule version” represents a type of “version” that is different from the “rule version” set by rewriting the information indicating the rule contents by the user or administrator. .

  After step S62, if there is an unprocessed rule version of the specified rule ID (YES in step S92), the process from step S52 is repeated, and if there is no unprocessed rule version (NO in step S92), FIG. The process of the example 14 procedure is terminated.

  The example of processing (steps S56 to S62) when the attention rule exists in the rule / organization fixed table (YES in step S54) has been described above. Hereinafter, an example of processing in a case where the attention rule does not exist in the rule / organization fixed table (NO in step S54) will be described.

  When the attention rule does not exist in the rule / organization fixed table, the rule history processing unit 160 first acquires the effective period of the attention rule (step S64). For example, if the effective period of the attention rule is determined as the period from the creation date and time of the rule version of the attention rule to the creation date and time of the rule version having the creation date and time closest to the creation date and time after the creation date and time of the rule version of the attention rule Good.

  Next, the rule history processing unit 160 sets the virtual organization version at the beginning of the effective period of the attention rule as the attention organization version (step S66). By referring to the virtual version management table in the organization information repository 120, the virtual organization version having the closest application date before the start of the effective period of the attention rule may be acquired and set as the attention organization version. Here, the start of the effective period of the attention rule is the creation date and time of the rule version of the attention rule.

  When the target organization version is determined, the rule history processing unit 160 generates organization information at the time of the target organization version (step S68) and the generated organization information in the same manner as the processes of steps S58, S60, and S62 described above. Each processing of the attention rule using (Step S70) and the recording of the rule contents as a result of the interpretation (Step S72) are performed. Thereafter, the processing proceeds to step S74 in FIG.

  Referring to FIG. 16, the rule history processing unit 160 determines whether there is an unprocessed virtual organization version during the effective period of the noticed rule (step S74). This determination is made, for example, by referring to the virtual version management table in the organization information repository 120, and there is a virtual organization version having an application date during the effective period of the attention rule that has not generated corresponding organization information. This can be done by confirming whether or not to do so.

  If there is no unprocessed virtual organization version (NO in step S74), the process proceeds to step S92 in FIG. 14 (determining whether there is an unprocessed rule version).

  If there is an unprocessed virtual organization version (YES in step S74), one of the unprocessed virtual organization versions is set as the target organization version (step S76). In this example, when there are a plurality of unprocessed virtual organization versions, the one with the oldest creation date is selected as the target organization version.

  If there is a snapshot in the target organization version (YES in step S78), the snapshot is set as organization information corresponding to the target organization version (step S80), and is stored in the temporary storage.

  If there is no snapshot in the target organization version (NO in step S78), the difference information associated with the target tissue version is applied to the organization information stored temporarily (step S86).

  Next, the rule history processing unit 160 obtains a product set of the target ID of the difference information of the target organization version and the participant of the target rule (Step S88). If the product set is empty (YES in step S90), the process from step S74 is repeated, and if the product set is not empty (NO in step S90), the process proceeds to step S82.

  After step S80 or when the process proceeds to NO in step S90, the rule interpretation unit 162 of the rule history processing unit 160 interprets the contents of the attention rule using the organization information stored temporarily (step S82). Then, a virtual rule version is assigned to the rule content resulting from the interpretation, and the virtual rule version and the rule content resulting from the interpretation are associated with each other and recorded in the rule repository 110 (step S84). After step S84, the processes after step S74 are repeated.

  In the loop process including steps S74 to S90 in the example of FIG. 16, the not-yet-executed virtual organization versions in the effective period of the attention rule are set to the attention tissue versions in order from the oldest (step S76). Therefore, the target tissue version in the loop processing is a virtual organization version immediately after the target tissue version at the time of the previous loop processing execution. In the loop process, the organization information corresponding to the target tissue version is recorded in the temporary storage regardless of the presence or absence of the snapshot of the target tissue version (steps S78, S80, and S86). When the loop processing is executed for one attention rule for the first time, the temporary storage stores organization information at the time of the initial organization virtual version of the attention rule (steps S64 to S64 in FIG. 14). S72). As described above, when the loop process is executed, the organization information stored temporarily is always the organization information corresponding to the virtual organization version immediately before the target organization version. Therefore, when the difference information is associated with the target tissue version (NO in step S78), the difference information is applied to the organization information stored temporarily to generate the organization information at the time of the target tissue version ( Step S86).

  In the process of the example of FIG. 16, if the product set of the difference information of the target tissue version and the participant of the target rule is empty (YES in step S90), the organization information corresponding to the target tissue version is used. The interpretation of the noticed rule (step S82) and the recording of the rule contents as a result of the interpretation (step S84) are not executed. This is because when the product set is empty, the rule contents do not change (for example, the user corresponding to the group or role does not change) in accordance with the change of the organization information indicated by the difference information of the target organization version. .

  As a result of the processing of the procedures in the examples of FIGS. FIG. 17 shows an example of a change history of the rule contents recorded as a result of the processing of the procedures in the examples of FIGS. In the example table of FIG. 17, the change history of the rule content represents the virtual rule version and the interpretation result of the rule content in association with each other. In FIG. 17, only the interpretation result of the content of the access right among the subordinate items of the rule content is illustrated, and the interpretation result of the content of the other subordinate items is omitted. The information in one line of the table in the example of FIG. 17 is a process of recording the result of interpreting the rule contents using the organization information corresponding to the target organization version in the rule repository 110 (steps S62, S72 in FIG. 14, and FIG. Information recorded in step S84). Referring to the row of the virtual rule version “Rule5_1.0_20090201” in the table of the example of FIG. 17, in the interpretation result of the contents of the access right, the group with the group ID “GroupF” representing the subject authorized to execute the “view” operation The user IDs {user102, user105, user108, user109} of users belonging to are included. Furthermore, the user IDs {user200, user212, user214, user215, user216} of users belonging to the group with the group ID “GroupG” representing the subject authorized to execute the “view” operation and the “edit” operation are included in the interpretation result. It is.

  Each virtual rule version illustrated in FIG. 17 includes a character string representing a rule ID, a rule version, and a virtual organization version used for interpreting the rule contents. For example, the virtual rule version “Rule5_1.0_20090201” is a result of interpreting the rule having the rule ID “Rule5” and the rule version “1.0” using the organization information at the time of the virtual organization version “20090201”. It is given to the rule contents. The virtual rule version “Rule5_1.0_20090214” is the same as the above example corresponding to the combination of the rule ID “Rule5” and the rule version “1.0”, and the organization information at the time of the different virtual organization version “20090214”. It is given to the rule content as a result of interpretation using.

  The rule history processing unit 160 may output the change history of the rule contents recorded in the rule repository 110 in accordance with an instruction from the user or the administrator after the processing of the procedures in the examples of FIGS. For example, the change history of the rule contents may be transmitted to the client terminal 30 of the user who has instructed the execution of the processes of FIGS. 14 to 16, or may be transmitted by e-mail to a destination designated by the user or the administrator. Also good. Further, for example, a table such as the example of FIG. 17 may be displayed on a display device (not shown) of the document management server 10. Alternatively, printing may be performed by a printing apparatus connected to the document management server 10.

  In the example of the above-described embodiment, when the organization information processing unit 170 updates the latest organization information in the organization information repository 120, is a value indicating the degree of change of organization information in the update equal to or less than a preset threshold value? Whether to record the difference information or the snapshot is determined depending on whether or not (see steps S20, S22, and S24 in FIG. 10). In an example of another embodiment, two thresholds for determination are set, and three types of thresholds are set according to the relationship between a value indicating the degree of change and two thresholds (first threshold <second threshold). Processing may be executed. For example, the difference information is recorded when the value indicating the degree of change is equal to or less than a first threshold, and the snapshot is recorded when the value exceeds the second threshold. When the value indicating the degree of change exceeds the first threshold and is equal to or less than the second threshold, the system administrator is notified (for example, by e-mail or the like), and either the difference information or the snapshot Or receives an instruction from the administrator, and records the difference information or snapshot in accordance with the instruction from the administrator. In this example, after notifying the administrator, if there is no instruction from the administrator within a preset period, the snapshot or difference information is set to be recorded without waiting for the administrator's instruction. You may keep it.

  Further, in the processing of the example of the above-described embodiment, the generation of organization information with reference to the virtual version management table is performed in relation to the rules (FIGS. 11 to 13 and FIGS. 14 to 16). Organization information that refers to the virtual version management table may be generated regardless of the rules. For example, when a past date is designated, organization information is generated by the following procedure. First, the virtual organization version at the designated date and time is acquired from the virtual version management table. Then, the processing related to the rules (steps S406, S408, S410, S412, and S414) in the procedure of the example of FIG. 13 is omitted, and after step S404, the difference information acquired in step S404 is applied to the snapshot acquired in step S402. When the process is performed, organization information corresponding to the virtual organization version is generated.

  In the example of the above-described embodiment, at least a part of information related to a user deleted from the database of the personnel information management server 20 (that is, a user who is no longer a member of the organization) You may delete from the difference information and snapshot which have). This is because information about users who are no longer members of the organization may include information that does not need to be retained. For example, the organization information processing unit 170 of the document management server 10 is deleted from the database of the personnel information management server 20 when checking the change of the contents of the database of the personnel information management server 20 (steps S10 and S12 in FIG. 10). A user is specified, and at least a part of information related to the user is deleted from the latest organization information, snapshot, and difference information. As the information to be deleted, for example, information that is not necessary for generating the rule history, such as the contact information of the user, is selected. Information necessary for generating the rule history, such as the user ID, name, affiliation group, and role, may be left without being deleted. You may make it receive the setting by an administrator etc. about which information is deleted (or which information is left) among the information regarding the user who is no longer a member of the organization. In addition, after specifying the user deleted from the personnel information management server 20, the information related to the user may be deleted after waiting for a preset period.

  In the above, the example of the embodiment in the case where the organization information is the data to be managed has been described. However, the process of recording difference information or snapshot according to the degree of change of the data before and after the update of the data to be managed (see FIG. 10), and the process of generating data corresponding to the virtual version (FIG. 13, (See FIG. 15 and the like) may be similarly applied to a database storing other data of organization information.

  The document management server 10 described above is typically realized by executing a program describing functions or processing contents of the respective units of the document management server 10 described above on a general-purpose computer. As shown in FIG. 18, for example, the computer has a CPU (central processing unit) 80, a memory (primary storage) 82, various I / O (input / output) interfaces 84, and the like connected via a bus 86. It has a circuit configuration. In addition, a hard disk drive (HDD) 88, a disk drive 90 for reading various types of portable non-volatile recording media such as a CD, a DVD, and a flash memory is connected to the bus 86 via, for example, an I / O interface 84. 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.

  In the above, an example in which the function of the document management server 10 is realized by one computer has been described. However, the function of the document management server 10 described above may be realized by being distributed to a plurality of computers.

  10 document management server, 20 personnel information management server, 30 client terminal, 40 network, 80 CPU, 82 memory, 84 I / O interface, 86 bus, 88 HDD, 90 disk drive, 100 document repository, 110 rule repository, 120 organization Information repository, 130 Document processing unit, 132 Access management unit, 140 Rule registration / editing unit, 160 Rule history processing unit, 162 Rule interpretation unit, 170 Organization information processing unit

Claims (7)

On the computer,
A history of updated personnel information including information representing members belonging to a group included in the organization and a history of updated document management rules including document management rules based on the group are stored with respective versions. a step of storing the unit,
And storing the documents managed in the storage means,
Associating the document with the document management rules ;
Each version of the previous SL document management rules, the steps characterizing response thereto respectively pair version of the human resources information corresponding to the validity period of each version of the document management rules,
Receiving the specification of the document management rules;
Outputting a history of the specified document management rule, and outputting a version of personnel information associated with each version of the output document management rule;
A data management program characterized in that Whether to store the entire information of the updated personnel information in the storage unit according to the degree of change in the personnel information due to the update when the history of the updated personnel information is stored in the storage unit Deciding whether to store the difference information in this update in the storage means;
The data management program according to claim 1, further causing the computer to execute.   3. The determination according to claim 2, wherein, in the determination step, when the value representing the degree of change is equal to or less than a preset threshold value, it is determined to store the difference information in a first storage unit. Data management program.   4. The data management according to claim 3, wherein, in the determining step, when the value indicating the degree of change is larger than the threshold value, it is determined to store the entire information in a second storage unit. 5. program. Value representing the degree of pre-Symbol changes, the determined based on the number of the members for which the change in the updating of personnel information, the data management program according to claim 2, characterized in that. When designation of a certain period is accepted, the entire information stored in the second storage unit most recently before the specified period among the entire information in the second storage unit, and the entire information is the second information. A generation step of generating personnel information at the specified time period using the difference information stored in the first storage means between the time stored in the storage means and the specified time period;
More data management program according to claim 4, wherein the benzalkonium be executed on the computer. A step of referring to the document management rules representing a user involved in a by the rules before SL document management rules groups in the tissue,
Using the personnel information generated in said generating step, to identify the user corresponding to the group represented in the document management rules, and outputting in association with the document management rules specified user ,
More data management program according to claim 6, wherein the to execute Turkey on the computer.

Images