JP7124567B2 - Document management device and document management program - Google Patents

Description

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

Japanese Patent Laid-Open No. 2002-200000 discloses a method for restricting access to shared resources on a network without requiring administrators to change access rights each time. , set the time limit attribute for the access permitted/disabled time period, and when the user accesses the file, folder, or drive, the time limit attribute is set for the file, folder, or drive, and the current time is within the time limit, access to the file, folder, or drive is prohibited.

Japanese Patent Application Laid-Open No. 2002-200000 discloses a document management server that aims to provide a document management system, an information processing device, a document management method, and a program that automatically controls access to only limited users in an access right function. When a client terminal requests access to a document managed by its own device, determines whether or not the access right to the document is within the validity period set in advance for each entry, and It is disclosed to allow access to documents in some cases.

Japanese Patent Application Laid-Open No. 2002-200000 discloses that an access right to a document file is set according to each user's status. and a document information DB that stores security level information set in a document file, and based on the current location information of the user and the security level information set in the document file when a user requests access to the document file, and an access permission/inhibition determination unit that determines permission/inhibition of access to the document file.

In Patent Document 4, the object is to obtain a file access control method and control system that can protect confidential information of customers and management information necessary for operation, and access restrictions for maintenance and operation of customer systems are disclosed. A management server and an access-restricted server as a customer system are connected to each other, the access-restricted server has an access-restricted agent and a security-restricted file, and the access-restricted management server manages an operation schedule. The information and the access restriction information are used to control the access right to the security target file in the access restriction target server, and the access restriction agent controls the security target file as instructed by the access restriction management server. It is disclosed that the user's reference, change, deletion, and execution access rights are added to allow access to the file only at the time defined in the operation schedule management information.

JP-A-2000-267922 JP 2009-163570 A JP 2018-013875 A JP 2005-038124 A

Access rights to documents are managed. For example, access rights to documents are controlled according to time limits set for the documents. However, no consideration is given to the events set in the schedule for each user.
SUMMARY OF THE INVENTION It is an object of the present invention to provide a document management apparatus and a document management program that can associate user access rights to documents or folders at the date and time of an event.

The gist of the present invention for achieving this object lies in the following inventions. The "claims" below are the claims as originally filed.
The invention according to claim 1 comprises document storage means for storing documents, and recording means for recording the content of access rights associated with each event type set in a schedule, and the combination of the event type, date and time, and user. and access right storage means for storing the user's access right to the document or folder at the date and time in association with the event type.

The invention according to claim 2 is the document management apparatus according to claim 1, wherein a variable is used as the date and time recorded by the recording means.

In the invention according to claim 3, the event type includes an event type related to attendance, and the access right storage means, when the variable is a date and time related to attendance, receives an attendance management device managing attendance of the user 3. The document management apparatus according to claim 2, wherein the date and time of the event type related to the attendance is acquired, and the access right of the user is determined.

The invention of claim 4 is the document management apparatus according to claim 1, wherein the access right storage means determines the access right according to the attribute of the document or folder.

In the invention according to claim 5, the recording means records the content of the access right in association with the event type and the attribute, and the access right storage means stores the access right in accordance with the event type and the attribute. 5. The document management apparatus of claim 4, wherein the document management device determines.

According to the sixth aspect of the present invention, a computer stores document storage means for storing documents, the content of access rights associated with each event type set in the schedule, and the combination of the event type, date and time, and user. and a document management program for functioning as access right storage means for storing the user's access right to the document or folder at the date and time in association with the event type.

According to the document management device of claim 1, it is possible to associate the user's access right to the document or folder at the date and time when the event takes place.

According to the document management apparatus of claim 2, date and time can be used as variables.

According to the document management apparatus of claim 3, the user's access right can be determined according to the date and time of the event type related to the user's attendance.

According to the document management apparatus of claim 4, access rights can be determined according to the attributes of documents or folders.

According to the document management apparatus of claim 5, access rights can be determined according to event types and attributes.

According to the document management program of claim 6, it is possible to associate the user's access right to the document or folder at the date and time when the event takes place.

2 is a conceptual module configuration diagram of a configuration example of the present embodiment; FIG. 1 is an explanatory diagram showing a system configuration example using this embodiment; FIG. 6 is a flow chart showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example data structure of a schedule information table; FIG. 4 is an explanatory diagram showing an example data structure of a facility reservation information table; FIG. 10 is an explanatory diagram showing an example data structure of an event/access right correspondence table; FIG. 4 is an explanatory diagram showing an example data structure of an access right information table; 6 is a flow chart showing an example of processing according to the present embodiment; 6 is a flow chart showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example of processing according to the present embodiment; FIG. 4 is an explanatory diagram showing an example of processing according to the present embodiment; 1 is a block diagram showing a hardware configuration example of a computer that implements the embodiment; FIG.

An example of a preferred embodiment for realizing the present invention will be described below with reference to the drawings.
FIG. 1 shows a conceptual module configuration diagram of a configuration example of this embodiment.
A module generally refers to a component such as software (computer program) or hardware that can be logically separated. Therefore, modules in this embodiment refer not only to modules in a computer program, but also to modules in a hardware configuration. Therefore, the present embodiment provides a computer program for functioning as those modules (a program for causing the computer to execute each procedure, a program for causing the computer to function as each means, a program for causing the computer to function as each function). It also serves as an explanation of the program, system and method for realizing However, for the convenience of explanation, the terms "stored", "stored", and equivalent terms are used, but when the embodiment is a computer program, these terms are stored in a storage device or stored in a storage device. It means to control to store in the device. Also, modules may correspond to functions one-to-one. may consist of multiple programs. Also, multiple modules may be executed by one computer, and one module may be executed by multiple computers by computers in a distributed or parallel environment. Note that one module may include other modules. Further, hereinafter, "connection" is used not only for physical connection but also for logical connection (data transfer, instruction, reference relationship between data, login, etc.). The term "predetermined" means that it is determined before the target process, and not only before the process according to the present embodiment starts, but also after the process according to the present embodiment starts. Also, if it is before the target process, it is used including the meaning that it is determined according to the situation/state at that time or according to the situation/state up to that time. When there are a plurality of "predetermined values", they may be different values, or two or more values (including, of course, all values) may be the same. Also, the description "if A, do B" is used in the sense of "judge whether it is A, and if it is judged to be A, do B". However, this excludes the case where it is not necessary to judge whether or not it is A. In addition, when things are listed like "A, B, C", etc., unless otherwise specified, it is an exemplary list, and includes cases where only one of them is selected (for example, only A).
In addition, a system or device is configured by connecting a plurality of computers, hardware, devices, etc. by communication means such as a network (including one-to-one correspondence communication connection), or a single computer, hardware, device The case where it is realized by etc. is also included. The terms "apparatus" and "system" are used interchangeably. Of course, "system" does not include what is merely a social "mechanism" (social system) that is an artificial arrangement.
In addition, for each process performed by each module or for each process when multiple processes are performed within a module, the target information is read from the storage device, and after the processing is performed, the processing result is written to the storage device. be. Therefore, the description of reading from the storage device before processing and writing to the storage device after processing may be omitted. The storage device here may include a hard disk, a RAM (Random Access Memory), an external storage medium, a storage device via a communication line, a register in a CPU (Central Processing Unit), and the like.

The document management apparatus 100 according to the present embodiment sets document or folder access rights for users according to the type of event. As shown in the example of FIG. , a schedule creation module 110, a schedule recording module 115, an access right setting module 120, an access right storage module 125, a document storage module 130, a document storage module 135, a document acquisition module 140, a document update module 145, and an access right determination module 150. is doing.
In the document management apparatus 100, for example, when there are two persons (user A and user B) who have access rights to a document, if user A is at home and user B is at work, only user A can access the document. You can prevent it from happening. In other words, the content of access rights can be set according to the content of the event. Also, for example, it is possible to disable access on the anniversary of the company's founding and enable reading and writing when the monthly report is updated.

The document storage module 130 is connected with the access right setting module 120 , the document storage module 135 , the document acquisition module 140 and the document update module 145 . The document storage module 130 stores the document by storing the document by the document storage module 135 . Then, the document is passed to the document acquisition module 140 , and the document is updated by the document update module 145 , or the access right of the document is set by the access right setting module 120 . Documents (also called files) are text data, numerical data, graphic data, image data, video data, audio data, etc., or a combination thereof, and are subject to storage, editing, retrieval, etc. and can be exchanged as individual units, including those similar to these. Specifically, the document includes a document created by a document creation program (so-called word processing software), an image read by an image reading device (scanner or the like), a web page, and the like.

The schedule record module 115 is connected to the user management module 105 , schedule creation module 110 , access right setting module 120 and access right storage module 125 . The schedule recording module 115 records the content of access rights associated with each event type, and the combination of the event type, date and time, and user. Here, an "event" is a schedule to be set in the schedule. "Event type" is the type of event, and attendance information related to the user's attendance (representing the status of attendance), "task information" representing the tasks that the user completes and meetings that the user participates in, and for a specific day regardless of the user Contains calendar information set by Attendance information includes, for example, non-work hours, stay-at-home, vacation, etc. Task information includes monthly report update, monthly report meeting participation, etc., and calendar information includes foundation day, equipment inspection date, and the like. In addition, as the "contents of access rights associated with each event type", for example, (1) "not accessible" for "outside working hours", (2) "read (read)" for "monthly report update" ), Write allowed", (3) "Read allowed" for "Participate in monthly report meeting", (4) "Access not allowed" for "When at home", (5) "When on vacation" and (6) "Only Read is allowed" for "Monthly Aggregation". As the "group of event type, date and time, and user", for example, there is schedule information in the schedule management device. Specifically, the event type is "monthly report update", the date and time is "09:00 on April 1st to 09:00 on April 2nd", and the group of users who updated the monthly report is "Minoru Tanaka and Kazuko Sato". There is
Alternatively, a variable may be used as the date and time recorded by the schedule recording module 115 . "Date and time as a variable" does not indicate a specific day or time, for example, the start time of work, the end time of work, or every month. In other words, since the contents of the variable date and time differ depending on the case or situation, it can be considered that the specific date or time is not recorded in the schedule recording module 115 .

The access right storage module 125 is connected to the schedule recording module 115 , the access right setting module 120 and the access right determination module 150 . The access right saving module 125 associates and saves the user's access right to the document or folder at the date and time according to the event type. Folders (also called directories) are places where documents are stored. Granting access rights to a folder means granting the same access rights to documents in the folder.
In addition, when the variable is the date and time related to attendance, the access right storage module 125 acquires the date and time of the event type related to attendance from the attendance management device that manages the attendance of the user, and determines the user's access right. You may do so. Here, for example, there is "telecommuting" as the "event type related to attendance". For example, if the "event type related to attendance" is "working from home", the "event type date and time related to attendance" will be the working hours (e.g. Become.

The access rights storage module 125 may also determine access rights according to document or folder attributes. Here, the "document or folder attribute" includes, for example, a "flag indicating whether or not it is confidential". For example, if the "attribute of document or folder" is "confidential" and the event type is "at home", the access right may be associated with "not accessible".
Further, the schedule recording module 115 may record the contents of access rights in association with event types and attributes.
The access rights storage module 125 may then determine access rights according to the event type and attributes.

The user management module 105 is connected with the schedule recording module 115 . The user management module 105 manages users subject to schedules and access rights.
The schedule creation module 110 is connected with the schedule recording module 115 . The schedule creation module 110 creates a schedule, which is a set of dates and users who are participants, and causes the schedule recording module 115 to record the schedule.
Access right setting module 120 is connected to schedule recording module 115 , access right saving module 125 and document saving module 130 . The access right setting module 120 creates an access right for a combination of a schedule and a document, and stores it in the access right saving module 125 .

Document storage module 135 is connected to document storage module 130 . The document storage module 135 receives a document to be managed and stores it in the document storage module 130 .
The document acquisition module 140 is connected to the document storage module 130 and access right determination module 150 . The document acquisition module 140 acquires documents in the document storage module 130 according to user's operation. When a document acquisition request is received, an inquiry is made to the access right determination module 150 as to whether the operation is possible, and the document is manipulated based on the determination result.
The document update module 145 is connected to the document storage module 130 and access right determination module 150 . The document update module 145 edits the document in the document storage module 130 according to the user's operation. When a request for editing a document is received, the access right determination module 150 is inquired about whether the operation is possible, and the document is manipulated based on the determination result.
The access right determination module 150 is connected to the access right storage module 125 , the document acquisition module 140 and the document update module 145 . The access right determination module 150 uses the information in the access right storage module 125 to determine whether the target user can operate the document from the document acquisition module 140 or the document update module 145 at that time. .

FIG. 2 is an explanatory diagram showing a system configuration example using this embodiment.
Document management device 100, schedule management device 200, document storage device 210, attendance management device 220, user terminal 290A, user terminal 290B, and user terminal 290C are connected via communication line 299, respectively. The communication line 299 may be wireless, wired, or a combination thereof, and may be, for example, the Internet, an intranet, etc. as a communication infrastructure. Also, the functions of the document management device 100, the schedule management device 200, the document storage device 210, and the attendance management device 220 may be implemented as cloud services.
Note that the document storage device 210 may be used as an alternative to the document storage module 130 and document storage module 135 .
As an alternative to the schedule creation module 110 and the schedule recording module 115, the schedule management device 200 or the attendance management device 220 may be used. The schedule management device 200 manages information on user schedules. The attendance management device 220 manages information related to the user's attendance (date and time of event type related to attendance, etc.).
A user of the user terminal 290 accesses documents in the document storage device 210 under access management by the document management device 100 . For access management, the document management apparatus 100 acquires information on the user's schedule from the schedule management apparatus 200 or acquires information on attendance from the attendance management apparatus 220 .

FIG. 3 is a flowchart showing an example of processing according to this embodiment.
In step S302, the schedule information of the target user is acquired. For example, the schedule information table 400 is acquired. Also, for example, the facility reservation information table 500 in which the user participates may be acquired.

FIG. 4 is an explanatory diagram showing an example data structure of the schedule information table 400. As shown in FIG. The schedule information table 400 has a user ID column 405, a date and time column 410, an event type column 415, a location column 420, a related document column 425, and the like. The user ID column 405 stores information for uniquely identifying a user (user ID: IDentification) in this embodiment. The date and time column 410 stores the date and time when the event in the user's schedule occurs (year, month, day, hour, minute, second, seconds or less, or a combination thereof, or a variable). is doing. The event type column 415 stores the event type (foundation anniversary, telecommuting, monthly report, etc.). The place column 420 stores the place where the event is held (where the user is). The related document column 425 stores documents related to the event.

FIG. 5 is an explanatory diagram showing an example data structure of the facility reservation information table 500. As shown in FIG.
The facility reservation information table 500 includes a conference room ID column 505, a conference room name column 510, a conference room location column 515, a reservation person ID column 520, a reservation date and time column 525, an event type column 530, a participant ID column 535, and a related document column. 540. The conference room ID column 505 stores information (conference room ID) for uniquely identifying the conference room in this embodiment. The conference room name column 510 stores the name of the conference room. The conference room location column 515 stores the location of the conference room. The reserver ID column 520 stores the user ID of the person who reserved the conference room. The reservation date and time column 525 stores the date and time when the conference room was reserved. The event type column 530 stores the type of event held in the conference room. The participant ID column 535 stores user IDs of participants in the event. The related document column 540 stores documents related to the event.

In step S304, the event type in the schedule is extracted. Specifically, the information in the event type column 415 of the schedule information table 400 is extracted.
In step S306, the content of the access right associated with the event type is extracted. For example, the contents of access rights may be extracted using the event/access right correspondence table 600 .

FIG. 6 is an explanatory diagram showing an example data structure of the event/access right correspondence table 600 . The event/access right correspondence table 600 has an event type column 605 and an access right column 610 . The event type column 605 stores event types. The access rights column 610 stores the access rights of documents or folders used in the event type.
For example, the access right for a document or folder used in the event type "non-work hours" is "not accessible", and the access right for a document or folder used in the event type "monthly report update" is "readable, writable". , the access rights for documents or folders used for the event type "participation in the monthly report meeting" are "readable and writable", and the access rights for documents or folders used for the event type "at home" are "access The access rights for documents or folders used in the event type "Exit" are "Readable, Writable", and the access rights for documents or folders used in the event type "Monthly Aggregation" are " readable, writable".

In step S308, the document used for the event is extracted.
In step S310, the document extracted in step S308 is associated with the schedule information acquired in step S302 and the access right information based on the content of the access right extracted in step S306. For example, an access right information table 700 is generated.

FIG. 7 is an explanatory diagram showing an example data structure of the access right information table 700. As shown in FIG.
The access right information table 700 has a document ID column 705, a document name column 710, a creation date and time column 715, a creator ID column 720, and an access right column 725. The access right column 725 includes an access right number column 730, It has an access right name column 735 , a date and time column 740 , a user ID column 745 and an authority column 750 . The document ID column 705 stores information (document ID) for uniquely identifying a document in this embodiment. The document name column 710 stores the document name of the document. The creation date and time column 715 stores the date and time when the document was created. The creator ID column 720 stores the user ID of the person who created the document. The access rights column 725 stores access rights to the document. The number of access rights column 730 stores the number of access rights. The data combinations of the access right name column 735 to the authority column 750 continue after this by the number of access rights in the access right number column 730 . The access right name column 735 stores the name of the access right. The date and time column 740 stores the date and time (the period of the target event) when the access right is issued. The user ID column 745 stores user IDs to which access rights are granted to the document. The authority column 750 stores the granted access authority.

In step S312, it is determined whether or not there is another target user, and if there is, the process returns to step S302, otherwise the process ends (step S399).

FIG. 8 is a flowchart showing an example of processing according to this embodiment. It shows an example of processing when the document acquisition module 140 receives a document acquisition request.
In step S802, a document acquisition request by a user's operation is accepted.
In step S804, access rights for the target document are acquired. Get the access rights set on the document to determine if there are access rights that can be retrieved. Specifically, it is sufficient to obtain the access right information table 700 corresponding to the document.

In step S806, the date and time is determined. If it is within the schedule, the process proceeds to step S808, and if it is outside the schedule, the process proceeds to step S814. That is, it is determined whether the current date and time correspond to the date and time set in the access right. Specifically, it is determined whether or not the current date and time correspond to the date and time column 740 of the access right information table 700 .
In step S808, participant determination is performed, and if the participant is a participant, the process proceeds to step S810, and if the outsider, the process proceeds to step S814. In other words, it is determined whether the user is set as an access right. Specifically, the user ID column 745 of the access right information table 700 is used for determination.
In step S810, authority determination is performed, and if "there is an acquisition right", the process proceeds to step S812, and if "there is no acquisition right", the process proceeds to step S814. In other words, it is determined whether or not the access right granted to the user is the right to obtain the document. Specifically, the authority column 750 of the access authority information table 700 is used for determination.

In step S812, the document is provided. That is, if all steps S806 to S810 are satisfied, the document is provided as obtainable.
In step S814, it notifies that acquisition is not possible. In other words, if any of steps S806 to S810 does not apply, it is notified that acquisition is not possible. As the notification, a user interface such as a pop-up displayed in response to the document acquisition request may be used.

FIG. 9 is a flowchart showing an example of processing according to this embodiment. An example of processing when the document update module 145 receives a document update request (editing instruction, etc.) is shown.
In step S902, a document update request by a user's operation is accepted.
In step S904, access rights for the target document are obtained. Get the access rights set on the document to determine if it has access rights that allow updating. Specifically, it is sufficient to obtain the access right information table 700 corresponding to the document.

In step S906, the date and time is determined, and if it is within the schedule, the process proceeds to step S908, and if it is outside the schedule, the process proceeds to step S914. That is, it is determined whether the current date and time correspond to the date and time set in the access right. Specifically, it is determined whether or not the current date and time correspond to the date and time column 740 of the access right information table 700 .
In step S908, the participant is determined, and if the participant is a participant, the process proceeds to step S910, and if the outsider, the process proceeds to step S914. In other words, it is determined whether the user is set as an access right. Specifically, the user ID column 745 of the access right information table 700 is used for determination.
In step S910, authority determination is performed, and if "with update authority", the process proceeds to step S912, and if "without update authority", the process proceeds to step S914. In other words, it is determined whether or not the access right granted to the user is the right to obtain the document. Specifically, the authority column 750 of the access authority information table 700 is used for determination.

In step S912, the document is updated. In other words, if all steps S906 to S910 are satisfied, the document is updated as being updatable.
In step S914, it notifies that update is not possible. In other words, if any of steps S906 to S910 does not apply, it is notified that updating is not possible. As the notification, a user interface such as a pop-up displayed in response to the document update request may be used.

FIG. 10 is an explanatory diagram showing an example of processing according to this embodiment.
It shows an example in which two access rights are set for the monthly report document 1000 . The example in FIG. 10 displays the two access rights.
On the monthly report-access right setting screen 1010, an access right name column 1015, a schedule column 1020, and a right table 1035 are displayed.
The schedule column 1020 has a repeat check column 1025 and a date and time column 1030 .
Authority table 1035 has user column 1037 and authority column 1039 . A user column 1037 displays users. The authority column 1039 displays the access authority that the user has to the monthly report document 1000 .
The monthly report-access right setting screen 1010 shows the details of the access rights granted to the monthly report document 1000. Minoru Tanaka and Kazuko Sato are given access rights between 9:00 on the 1st and 9:00 on the 2nd of every month ( event: monthly report update), indicating that the access right to write to the monthly report document 1000 has been granted.

On the monthly report-access right setting screen 1050, an access right name column 1055, a schedule column 1060, and a right table 1075 are displayed.
The schedule column 1060 has a repeat check column 1065 and a date and time column 1070 .
Authority table 1075 has user column 1077 and authority column 1079 . A user column 1077 displays users. The authority column 1079 displays the authority that the user has for the monthly report document 1000 .
The monthly report-access right setting screen 1050 shows the details of the access rights granted to the monthly report document 1000. Minoru Tanaka and Kazuko Sato were given access rights from 11:00 on March 5, 2018 to March 5, 2018. From 11:00 on March 5, 2018 to 12:00 on March 5, 2018, to Kiyoshi Takahashi and Kazuko Suzuki for granting write-enabled access rights to Monthly Report Document 1000 from 11:00 on March 5, 2018 to 12:00 on March 5, 2018. It shows that the read-only access right to the monthly report document 1000 has been granted until the time (event: monthly report meeting).

Note that the contents of the access right name column 1015 and the access right name column 1055 may be obtained from the access right name column 735 . The contents of the schedule column 1020 and schedule column 1060 may be obtained from the date and time column 740 . The contents of the user column 1037 and user column 1077 may be obtained from the user ID column 745 . The contents of the authority column 1039 and the authority column 1079 may be obtained from the authority column 750 .

FIG. 11 is an explanatory diagram showing an example of processing according to this embodiment. The schedule management device 200 manages the schedule by displaying the schedule display screen 1100 of each user on the user terminal 290, for example.
On the schedule display screen 1100, schedule information (summary) 1110 for February 2, X and schedule information (summary) 1120 for February 13, X are set. Specifically, (1) subject, (2) schedule (date and time, repetition setting (pattern)), (3) participants (not only individuals but also group designations if a user group can be used as the document management apparatus 100). is also possible). That is, the schedule information (details) 1115 of the schedule information (outline) 1110 and the schedule information (details) 1125 of the schedule information (outline) 1120 are specified. Specifically, as the schedule information (details) 1115, "subject: monthly report update, date and time: pattern (first Monday of every month from 10:00 to 12:00), participants: Tanaka, Ito, Suzuki, and Takahashi" are set. , and as schedule information (details) 1125, "Subject: Founding anniversary (holiday), date and time: 2/13 00:00-23:59 (pattern: none), participants: all employees" are set. .

FIG. 12 is an explanatory diagram showing an example of processing according to this embodiment.
Three access rights (access right information 1210, access right information 1220, and access right information 1230) are given to the document 1200. FIG. The access right information 1210 is the conventional access right (not the access right according to this embodiment), the access right for the operator can be set, and is permanently controlled by this access right until the access right is changed. is.
As access rights according to the present embodiment, access right information 1220 is given according to the schedule information (details) 1115 and access right information 1230 is given according to the schedule information (details) 1125 . Access right information 1220 and access right information 1230 are access rights associated with schedules. For example, the access right information 1220 indicates that Suzuki and Takahashi can edit only during the monthly report update period. In this way, since it is associated with the schedule, there is no need to change access rights before and after the monthly update period.

FIG. 13 is an explanatory diagram showing an example of processing according to this embodiment. It is assumed that the document in the document storage module 130 will be accessed from outside the company, such as when working at home or on a business trip. For example, it prevents access outside working hours.
The schedule information (summary) 1330 is added on February 4, X, to the schedule display screen 1100 shown in the example of FIG. That is, the schedule information (details) 1335 of the schedule information (outline) 1330 is specified. Specifically, as the schedule information (details) 1335, "Subject: Telecommuting, Date: 2/4 Start of work - End of work (Pattern: None), Participant: Tanaka" is set. Here, "work start time" and "work end time" are variables, and the contents (specific times) are defined by the attendance management device 220 .
The attendance management device 220 stores an attendance information table 1350. The attendance information table 1350 has a name column 1355, a date column 1360, a working hours column 1365, and a remarks column 1370. The name column 1355 stores names (user IDs). The date column 1360 stores dates. The working hours column 1365 stores working hours. Specifically, it stores the time when work starts and the time when work ends. The remarks column 1370 stores remarks. This example indicates that on February 4, X, Tanaka works from home from 9:00 to 18:00. This date and time is referenced to determine when access is possible. In this example, the work schedule is used as it is for the accessible time. may be determined.

FIG. 14 is an explanatory diagram showing an example of processing according to this embodiment.
An example is shown in which access right information 1210, access right information 1220, access right information 1230, and access right information 1410 (that is, four access rights) are given to the document 1200. FIG. The access right information 1410 indicates "Schedule: Telecommuting, Participant access right, and Details: Write: Permitted, Read: Permitted". Then, the user (specifically, the user ID), the date and time period for working from home are determined by the schedule display screen 1100 or the attendance information table 1350 shown in the example of FIG.

As shown in FIG. 15, the hardware configuration of the computer on which the program according to the present embodiment is executed is a general computer, specifically a personal computer, a computer that can serve as a server, and the like. That is, as a specific example, a CPU 1501 is used as a processing unit (calculating unit), and a RAM 1502, ROM 1503, and HD 1504 are used as storage devices. As the HD 1504, for example, a hard disk, an SSD (Solid State Drive) which is a flash memory, or the like may be used. A CPU 1501 that executes programs such as the schedule creation module 110, the schedule recording module 115, the access right setting module 120, the access right saving module 125, the document storage module 135, the document acquisition module 140, the document update module 145, the access right determination module 150, and the like; , a RAM 1502 for storing programs and data thereof, a ROM 1503 for storing a program for starting up the computer, and an auxiliary storage device HD 1504 having functions as a user management module 105, a document storage module 130, and the like. , a keyboard, a mouse, a touch screen, a microphone, a camera (including a line-of-sight detection camera, etc.), etc., based on a user's operation (including motion, voice, line-of-sight, etc.), a reception device 1506 that receives data, a CRT, and a liquid crystal display. , an output device 1505 such as a speaker, a communication line interface 1507 for connecting to a communication network such as a network interface card, and a bus 1508 for connecting them to exchange data. A plurality of these computers may be connected to each other via a network.

Of the above-described embodiments, with respect to the computer program, a computer program, which is software, is loaded into the system of this hardware configuration, and the software and hardware resources cooperate to perform the above-described embodiment. is realized.
Note that the hardware configuration shown in FIG. 15 shows one configuration example, and the present embodiment is not limited to the configuration shown in FIG. I wish I had. For example, some modules may be configured with dedicated hardware (for example, Application Specific Integrated Circuit: ASIC), etc., and some modules are in an external system and connected via a communication line. Further, a plurality of systems shown in FIG. 15 may be connected to each other by communication lines so as to cooperate with each other. In addition to personal computers, mobile information communication devices (including mobile phones, smartphones, mobile devices, wearable computers, etc.), information appliances, robots, copiers, faxes, scanners, printers, multifunction devices (scanners, printers, It may be incorporated in an image processing apparatus having two or more functions such as a copier, a facsimile machine, or the like.

The program described above may be stored in a recording medium and provided, or the program may be provided by communication means. In that case, for example, the program described above may be regarded as an invention of "a computer-readable recording medium on which the program is recorded."
"Program-recorded computer-readable recording medium" refers to a computer-readable recording medium recording a program, which is used for program installation, execution, program distribution, and the like.
As a recording medium, for example, a digital versatile disc (DVD), which is a standard established by the DVD Forum, "DVD-R, DVD-RW, DVD-RAM, etc." Standard "DVD + R, DVD + RW, etc.", compact disc (CD), read-only memory (CD-ROM), CD recordable (CD-R), CD rewritable (CD-RW), Blu-ray disc ( Blu-ray (registered trademark) Disc), magneto-optical disk (MO), flexible disk (FD), magnetic tape, hard disk, read-only memory (ROM), electrically erasable and rewritable read-only memory (EEPROM (registered trademark) )), flash memory, random access memory (RAM), SD (Secure Digital) memory card, and the like.
Then, the whole or part of the program may be recorded on the recording medium and stored or distributed. Also, by communication, for example, a wired network used for a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet, an intranet, an extranet, etc., or a wireless communication. It may be transmitted using a transmission medium such as a network or a combination thereof, or may be carried on a carrier wave.
Furthermore, the program may be part or all of another program, or may be recorded on a recording medium together with a separate program. Moreover, it may be divided and recorded on a plurality of recording media. Also, it may be recorded in any form, such as compression or encryption, as long as it can be restored.

100 Document management device 105 User management module 110 Schedule creation module 115 Schedule recording module 120 Access right setting module 125 Access right storage module 130 Document storage module 135 Document storage module 140 Document acquisition module 145 Document Update module 150 Access right determination module 200 Schedule management device 210 Document storage device 220 Attendance management device 290 User terminal 299 Communication line

Claims (5)

document storage means for storing a document;
recording means for recording the content of access rights associated with each event type set in the schedule, and the combination of the event type, date and time, and user;
access right storage means for associating and storing the user's access right to the document or folder at the date and time according to the event type ;
Using a variable as the date and time recorded by the recording means;
Document management device. The event type includes an event type related to attendance,
When the variable is the date and time related to attendance, the access right storage means acquires the date and time of the event type related to the attendance from the attendance management device that manages the attendance of the user, and determines the access right of the user. do,
The document management device according to claim 1 . the access right storage means determines access rights according to the attributes of the document or folder;
The document management device according to claim 1. the recording means records the content of the access right in association with the event type and the attribute;
The access right storage means determines access rights according to the event type and the attribute.
The document management device according to claim 3 . the computer,
document storage means for storing a document;
recording means for recording the content of access rights associated with each event type set in the schedule, and the combination of the event type, date and time, and user;
functioning as an access right storage means that associates and stores the user's access right to the document or folder at the said date and time according to the event type ;
Using a variable as the date and time recorded by the recording means;
Document management program.

Images