JP7768008B2 - Information management program and information management method - Google Patents

Description

The present invention relates to an information management program and an information management method.

There are information management systems that edit information displayed on a display unit and store the edited information. For example, the document management system described in Patent Document 1 edits a document displayed on a display unit. The document management system sets a storage expiration date for the edited document. When the storage expiration date has passed, the document management system changes the storage state of the document by deleting the document file from the storage device.

Japanese Patent Application Laid-Open No. 2008-52642

In the document management system described above, the storage state of a document is changed for each file, which could potentially change the storage state of necessary information within the document. Alternatively, in the document management system described above, only certain users may have the right to change the storage state of a document. For these reasons, it may be difficult for users to manage the storage state of information in the document management system described above.

The object of the present invention is to provide an information management program and method that contribute to the advantage of allowing users to easily manage the storage state of information.

The information management program according to a first aspect of the present invention is characterized in that it causes a computer of an information editing system capable of editing objects in an area displayed on a display unit via an operation unit to execute a storage process that stores history data indicating a history corresponding to an editing operation when an editing operation for editing the object in the area is performed via the operation unit, and a condition change process that changes the change condition when a condition change operation for changing the change condition of the storage state of the history data stored by the storage process is performed via the operation unit.

An information management method according to a second aspect of the present invention is an information management method using an information editing system that allows objects in an area displayed on a display unit to be edited via an operation unit, and is characterized by comprising: a storage process that, when an editing operation for editing the object in the area is performed via the operation unit, stores history data indicating a history corresponding to the editing operation; and a condition change process that, when a condition change operation for changing a change condition for the storage state of the history data stored by the storage process is performed via the operation unit, changes the change condition.

According to the first or second aspect, when a user performs a condition change operation on the operation unit, the condition change process changes the change conditions for the storage state of the history data. Therefore, the condition change process contributes to the advantage of allowing the user to easily manage the storage state of the history data.

FIG. 2 is a diagram showing the electrical configuration of the note editing system 1. FIG. 2 is a conceptual diagram of an account storage area 222. FIG. 2 is a conceptual diagram of a history storage area 224. FIG. 2 is a conceptual diagram of a condition storage area 225. FIG. 6 shows a note selection window 60. FIG. 10 is a diagram showing a page editing window 70. FIG. 9 shows a history setting window 90. 10 is a flowchart of a main process. 10 is a flowchart of an editing process. 10 is a flowchart of a management process. 10 is a flowchart of a first state change process. 10 is a flowchart of a deadline change process. 10 is a flowchart of a deadline change process. 10 is a flowchart of a second state change process.

<Outline of Note Editing System 1>
As shown in FIG. 1, the note editing system 1 has a server 2 and user terminals 3A, 3B, and 3C. The server 2 is communicatively connected to an access point 4A via a network line 4. The user terminals 3A, 3B, and 3C are each communicatively connected to the access point 4A wirelessly. The user terminals 3A to 3C are each tablet terminals, and each has the same basic configuration. When any of the user terminals 3A to 3C is not specified or is referred to collectively, they are referred to as "user terminal 3."

In this embodiment, the user of user terminal 3A is "User A." The user of user terminal 3B is "User B." The user of user terminal 3C is "User C." User C is the administrator of the note editing system 1. An administrator user is called an "administrative user," and users other than the administrator are called "general users."

<Electrical configuration of server 2>
1, the server 2 has a CPU 21, a ROM 22A, a RAM 22B, a flash memory 22C, and a communication I/F 23. The CPU 21 controls the server 2. The ROM 22A stores information required by the CPU 21 when executing various programs. The ROM 22A stores, for example, time limits corresponding to each editing attribute. The RAM 22B temporarily stores data while the CPU 21 is executing processing.

Flash memory 22C is a non-volatile storage device and includes a program storage area 221, an account storage area 222, a page storage area 223, a history storage area 224, and a condition storage area 225. The program storage area 221 stores control programs to be executed by the CPU 21. The account storage area 222 stores account information.

Page information is stored in the page memory area 223. History data is stored in the history memory area 224. Change conditions are stored in the condition memory area 225. The page information, history data, and change conditions corresponding to one note are collectively referred to as "note information." The communication I/F 23 is a communication module that enables the server 2 to communicate with user terminals 3A to 3C via the network line 4 and access point 4A.

<Electrical configuration of user terminal 3>
1, the user terminal 3 has a CPU 31, a ROM 32A, a RAM 32B, a flash memory 32C, a display 33, a touch panel 34, and a communication interface (I/F) 35. The CPU 31 controls the user terminal 3. The ROM 32A stores information required by the CPU 31 when executing various programs. The RAM 32B temporarily stores data while the CPU 31 is executing processing. The flash memory 32C stores control programs to be executed by the CPU 31, etc.

The display 33 is a liquid crystal display that displays various information under the control of the CPU 31. The touch panel 34 is provided on the surface of the display 33 and detects the contact position of a pen or finger on the display 33. When the touch panel 34 detects an operation by the user, it outputs a signal corresponding to the detected operation to the CPU 31. The communication I/F 35 is a communication module that enables the user terminal 3 to communicate with the server 2 via the network line 4 and the access point 4A.

<Basic operation of note editing system 1>
As shown in Fig. 1, the note editing system 1 is configured so that multiple users A, B, and C use their respective user terminals 3A, 3B, and 3C to share notes via a server 2. A note is made up of one or more page areas 100 (see Fig. 6). The page areas 100 are configured to be displayed on a display 33. In the note editing system 1, multiple users A, B, and C can edit objects in the page areas 100 using their respective user terminals 3A, 3B, and 3C.

In this embodiment, object types include strokes, markers, text, shapes, and images. Strokes are lines such as straight and curved lines. Markers are lines for coloring. Text is a string of letters, numbers, symbols, etc. placed within a text block (not shown). Shapes are two-dimensional or three-dimensional figures. Images are still images or videos. Editing an object refers to adding an object, deleting an object, moving an object, changing the font of an object, changing the color of an object, changing the size of an object, etc.

In the note editing system 1, when a user performs an operation via the touch panel 34 on the user terminal 3, the CPU 31 transmits operation information to the server 2. The operation information indicates the content of the operation performed. When the CPU 21 on the server 2 receives the operation information from the user terminal 3, it performs an operation according to the received operation information.

Types of operations on the touch panel 34 include a note selection operation, a page selection operation, an edit operation, a permission setting change operation, a retention period change operation, and a delete operation. A note selection operation is an operation that allows the user to select one or more notes. A page selection operation is an operation that allows the user to select one or more page areas 100.

An edit operation is an operation that allows a user to edit objects in the page area 100. A permission setting change operation is an operation that allows a user to change permission settings. A retention period change operation is an operation that allows a user to change the retention period. A delete operation is an operation that allows a user to delete history data.

The operation information corresponding to each of the note selection operation, page selection operation, editing operation, permission setting change operation, retention period change operation, and deletion operation is called "note selection information," "page selection information," "editing information," "permission setting change information," "period change information," and "deletion information." Each piece of information indicates information such as the operation content and ID.

For example, when a user performs an editing operation on user terminal 3, CPU 31 transmits the editing information to server 2. When CPU 21 receives the editing information, it stores history data in accordance with the received editing information and updates the note. In this case, CPU 21 transmits display information to user terminals 3A to 3C in accordance with the updated note. The display information indicates the display content of the latest page area 100 (see Figure 6).

When the CPU 31 of each user terminal 3A-3C receives the display information, it displays the latest display content of the page area 100 (see Figure 6) based on the received display information. As a result, the display content of the page area 100 on the display 33 of each user terminal 3A-3C is shared within the note editing system 1.

<Account information>
2, account information for each user is stored in the account storage area 222. In the example shown in Fig. 2, account information A1, A2, and A3 are stored in the account storage area 222. The account information indicates user identification information, and in this embodiment indicates an ID, password, and ID type.

In account information, a password and ID type are associated with each user's ID. In the example shown in Figure 2, in account information A1, user A's ID "User A", password "AAAA", and ID type "general" are associated with each other. In account information A2, user B's ID "User B", password "BBBB", and ID type "general" are associated with each other. In account information A3, user C's ID "User C", password "CCCC", and ID type "administrator" are associated with each other.

The ID is information used to distinguish one user from other users. The password is used when logging in to the note editing system 1. The ID type indicates whether the ID is an administrator ID or a general ID. In Figure 2, an administrator ID is indicated as "Administrator" and a general ID is indicated as "General".

The administrator ID is the ID of the administrative user (user C in this embodiment). The administrator ID is given the authority to delete history data from the history storage area 224 in advance. Furthermore, the administrator ID is given the authority to set whether or not to grant a general ID the authority to delete history data from the history storage area 224. A general ID is an ID other than the administrator ID. If the administrator ID does not give permission, the general ID does not have the authority to delete history data from the history storage area 224.

The note editing system 1 is configured so that one or more of the multiple IDs are pre-registered as administrator IDs. The administrator ID may be changed later. General IDs may be further divided into multiple ID types.

<Page information>
Although not shown, page information is stored in the page storage area 223 (see FIG. 1) for each page area 100 according to each note. The page information indicates the object (latest display information) in the page area 100 (see FIG. 6), the creator of the page area 100, etc.

<Historical data>
As described above, in the note editing system 1, for one note, multiple users each edit objects in the page area 100. For this reason, the note editing system 1 is configured so that history data is stored in the history storage area 224.

As shown in FIG. 3, history data is stored in the history storage area 224 for each page area 100 for each note. In this embodiment, history data is stored for each editing operation. In the example shown in FIG. 3, history data H1, H2, H3, H4, and H5 are stored in the history storage area 224 for each page of the notebook NA.

The history data indicates a history corresponding to editing operations (referred to as "editing history"), and in this embodiment indicates the edit date and time, editor ID, edit position, edit attribute, and edit content. The edit date and time indicates the time when one editing operation was completed. For example, "March 31, 2022, 7:10" in history data H1 indicates that the editing operation corresponding to history data H1 was completed at 7:10 on March 31, 2022. The editor ID indicates the ID of the user who performed the editing operation. For example, "User B" in history data H1 indicates that the editing operation corresponding to history data H1 was performed by user B.

The edit position indicates the position within the page area 100 (see Figure 6) of the object edited by the edit operation using coordinate data. For example, "(X1, Y1)" in history data H1 indicates that the edit operation corresponding to history data H1 was performed at position (X1, Y1) within the page area 100. Although not shown, for example, the origin of the coordinates (0, 0) is located in the upper left corner of the page area 100 (see Figure 6). The left-right direction of the page area 100 corresponds to the X-axis direction. The up-down direction of the page area 100 corresponds to the Y-axis direction.

The editing attribute indicates the type of object being edited. In this embodiment, the editing attribute is one of stroke, marker, text, shape, and image. The "image" in history data H1 in Figure 3 indicates that the editing operation corresponding to history data H1 was performed on an image.

The edit content indicates the edit content performed on the object. In this embodiment, the edit content is any of the following: adding an object, deleting an object, moving an object, changing the font of an object, changing the color of an object, changing the size of an object (enlarging or reducing), etc. The "add" in history data H1 in Figure 3 indicates that an object was added to the page area 100 by the editing operation corresponding to history data H1.

<Change conditions>
As shown in Figure 4, the change conditions are conditions required to change the storage state of history data, and in this embodiment, they include a maintenance period and permission setting. The maintenance period is set (stored) in the maintenance period column in the condition storage area 225. The maintenance period is set for each editing attribute in the condition storage area 225 according to each note. In this embodiment, only the administrative user has the authority to change whether or not a maintenance period is set and the length of the maintenance period by performing a maintenance period change operation.

The retention period indicates the period for which the stored state of history data is maintained unless a deletion operation is performed by the user. In other words, the stored state of history data that has passed the retention period is not maintained. In other words, the stored state of history data that has passed the retention period is changed. In this embodiment, history data that has passed the retention period is deleted from the history storage area 224.

In the example shown in Figure 4, the retention periods for each of the editing attributes of stroke, marker, text, shape, and image are set to "60 days," "30 days," "no time limit," "90 days," and "1 day." "No time limit" does not mean that the history data will not be stored in the history storage area 224 shown in Figure 3, but rather that the storage state of the history data will be maintained indefinitely unless a deletion operation is performed.

If all history data were to be accumulated in the history storage area 224 and the storage state of the history data were to be maintained, the remaining storage capacity of the history storage area 224 would decrease, which could result in a decrease in the performance of the note editing system 1, such as slowing down the operation of the note editing system 1. By deleting history data that has passed its retention period from the history storage area 224, the note editing system 1 contributes to the advantage of preventing a decrease in the remaining storage capacity of the history storage area 224 and preventing a decrease in the performance of the note editing system 1.

The settable upper limit for the retention period is called the "Upper Limit" (see the notes section in Figure 4). The upper limit for strokes is not limited to a specific number, but in this embodiment it is "60 days." The upper limit for markers is not limited to a specific number, but in this embodiment it is "60 days." The upper limit for text is not limited to a specific number, but in this embodiment it is "none." The upper limit for shapes is not limited to a specific number, but in this embodiment it is "none." The upper limit for images is not limited to a specific number, but in this embodiment it is "30 days."

In other words, in this embodiment, the upper limit for the deadline corresponding to an image is shorter than the upper limit for the deadline corresponding to strokes, markers, text, and shapes. The upper limit for the deadline corresponding to strokes and markers is shorter than the upper limit for the deadline corresponding to text and shapes. The upper limit for the deadline corresponding to text and shapes are the same.

If the data capacity per file of history data is relatively large, the remaining storage capacity of the history storage area 224 is likely to decrease due to the accumulation of history data. Generally, the data capacity of images per file tends to be larger than the data capacity of strokes, markers, text, and shapes per file. The data capacity of strokes and markers per file tends to be larger than the data capacity of text and shapes per file. The data capacity of strokes and markers per file is approximately the same. The data capacity of text and shapes per file is approximately the same.

As described above, in this embodiment, the upper limit on the expiration date is configured to be shorter for editing attributes that tend to result in larger data volumes per file. Therefore, the upper limit on the expiration date contributes to the advantage of preventing the remaining storage capacity of the history storage area 224 from decreasing due to the accumulation of history data.

In this embodiment, an image in one file corresponds to one image. A stroke in one file corresponds to one stroke. A marker in one file corresponds to one marker. Text in one file corresponds to the text in one text block. A shape in one file corresponds to one shape.

The permission setting is set (stored) in the permission setting column shown in Figure 4 in the condition storage area 225. The permission setting is set for each note in the condition storage area 225. The permission setting indicates whether users other than the administrator are authorized to change the storage status of history data. In this embodiment, only the administrator has the authority to change the permission setting from "Allowed" to "Not Allowed" using the permission setting change operation.

In the example shown in Figure 2, a permission setting that gives users other than the administrator the authority to change the storage state of history data is indicated by "Allowed," and a permission setting that does not give users other than the administrator the authority to change the storage state of history data is indicated by "Not Allowed." The permission setting corresponding to note NA shown in Figure 4 is "Not Allowed." The permission setting corresponding to note NB is "Allowed."

When the permission setting is "Not permitted," only the administrative user (user C in this embodiment) has the authority to delete history data through the delete operation. When the permission setting is "Allowed," in addition to the administrator, general users (users A and B in this embodiment) have the authority to delete history data through the delete operation. Changing the retention period and changing the permission setting are collectively referred to as "history settings."

<Note Selection Window 60>
The note selection window 60 shown in Figure 5 is displayed when a user logs in to the note editing system 1. The note selection window 60 includes a note selection area 61, a page selection area 62, and a settings button 63. The note selection area 61 displays one or more options. The options indicate notes that have already been created. In the example shown in Figure 5, options 61A and 61B for note NA and note NB are displayed in the note selection area 61.

The page selection area 62 displays thumbnails corresponding to the page area 100 (see Figure 6). In the example shown in Figure 5, thumbnails 62A, 62B, and 62C are displayed in the page selection area 62. Thumbnail 62A corresponds to the page area 100 (see Figure 6) of the first page of the note NA. Thumbnail 62B corresponds to the page area of the second page of the note NA. Thumbnail 62C corresponds to the page area of the third page of the note NA. The settings button 63 is selected when setting history, etc.

An example of a note selection operation will now be described. For example, the user selects one option in the note selection area 61. This allows the user to select one or more notes. In the example shown in Figure 5, the dashed line indicates that option 61A is selected.

An example of a page selection operation will be described below. For example, the user selects one thumbnail in the page selection area 62. This causes the user to select the page area 100 corresponding to the selected thumbnail.

<Settings Selection Window 80>
The setting selection window 80 shown in Fig. 5 is displayed when the setting button 63 is selected. The setting selection window 80 includes an ID display area 81, a language setting area 82, a history setting area 83, and a logout button 84. The ID display area 81 displays the user's own ID. In the example shown in Fig. 5, the administrator ID "User C" is displayed in the ID display area 81. The language setting area 82 is selected when switching languages.

The history setting area 83 is selected when making history settings. The history setting area 83 is configured to be displayed or selectable in the setting selection window 80 only when logged in with an administrator ID (e.g., user C). In other words, when logged in with a general ID (e.g., user A or user B), the history setting area 83 is configured not to be displayed or selectable in the setting selection window 80. The logout button 84 is selected when logging out of the note editing system 1.

<Page Edit Window 70>
The page editing window 70 shown in Fig. 6 is displayed when the thumbnail 62A is selected in the page selection area 62 shown in Fig. 5. The page editing window 70 includes a main area 71, multiple edit buttons 72, a history button 73, and a history display area 74. The main area 71 displays one or more page areas 100 selected by a page selection operation. In the example shown in Fig. 6, the page area 100 includes an object 711 and an object 712. The object 711 is a single image depicting a mountain. The object 712 is a three-stroke shape "123."

The multiple edit buttons 72 are selected when editing an object in the page area 100. In the example shown in FIG. 6, the multiple edit buttons 72 include buttons 72A, 72B, 72C, 72D, 72E, 72F, 72G, and 72H.

Button 72A is selected to add a stroke to the page area 100. Button 72B is selected to erase an object from the page area 100. Button 72C is selected to add a marker to the page area 100. Button 72D is selected to add text to the page area 100.

Button 72E is selected to add a shape to the page area 100. Button 72F is selected to add an image to the page area 100. Button 72G is selected to change the color of the stroke, text, or shape in the page area 100. Button 72H is selected to change the thickness of the stroke in the page area 100.

The history button 73 is selected to toggle between displaying and hiding the history display area 74 in the page editing window 70. Figure 6 shows an example of the page editing window 70 when the history button 73 is selected and the history display area 74 is displayed.

The history display area 74 displays a group of edit histories or a list of edit histories. An edit history group is a group of one or more edit histories organized according to user, edit date and time, edit attributes, etc. In the example shown in FIG. 6, the history display area 74 displays edit history groups 741, 742, 743 and edit histories 741A, 742A, 742B, and 742C. For example, edit history group 741 shows a summary of edit histories corresponding to edit date and time "3/31 7:20" and editor ID "User A." When the expand mark 7421 is selected, edit histories 742A, 742B, and 742C are expanded from edit history group 742.

An example of an editing operation will now be described. For example, to add object 711 to page area 100, the user selects button 72F. The user selects an image file representing object 711. The user then selects the position within page area 100 where object 711 is to be added. As a result, object 711 is added to page area 100.

An example of an editing operation will be described. For example, to add object 712 to page area 100, the user selects button 72A. The user adds object 712 to page area 100 so that the stroked line has the shape of "123." This adds object 712 to page area 100.

An example of a deletion operation will be described. For example, to delete history data corresponding to edit history 742A, the user selects the history button 73. This causes the history display area 74 to be displayed. The user selects the expansion mark 7421. This causes edit history 742A to be displayed. The user selects edit history 742A. The user selects the delete button (not shown). This causes the history data corresponding to edit history 742A to be deleted.

<History Settings Window 90>
A history setting window 90 shown in Fig. 7 is displayed when the history setting area 83 shown in Fig. 5 is selected. The history setting window 90 includes a permission setting switching button 91 and a maintenance period setting area 92.

The permission setting switch button 91 indicates whether the permission setting is "allowed" or "prohibited." In this embodiment, when the permission setting switch button 91 is located on the left, it indicates that the permission setting is "prohibited," and when the permission setting switch button 91 is located on the right, it indicates that the permission setting is "allowed." The permission setting switch button 91 is operated to switch the permission setting from one of "allowed" and "prohibited" to the other.

The maintenance period setting area 92 displays information related to the maintenance period setting, and in this embodiment includes an edit attribute display area 921, a check box 922, a maintenance period display area 923, and a pull-down mark 924. The edit attribute display area 921 displays edit attributes. In this embodiment, the edit attribute display area 921 displays the object name as the edit attribute, and from top to bottom displays strokes, markers, text, shapes, and images.

Check box 922 is provided to correspond to the editing attribute display area 921. Check box 922 is selected when changing the maintenance deadline from the default deadline length, or when returning the maintenance deadline to the default deadline length. The default deadline length is stored in ROM 22A shown in Figure 1. The default deadline length may be the deadline upper limit corresponding to each editing attribute, may be shorter than the deadline upper limit corresponding to each editing attribute, or may be "no deadline."

In the example shown in Figure 7, the check box 922 corresponding to the text is not checked, and the check boxes 922 corresponding to the stroke, marker, shape, and image are checked. In other words, the retention period corresponding to the text is set to the default expiration length, and the retention period corresponding to the stroke, marker, shape, and image is set to an expiration length that has been changed from the default expiration length.

The maintenance period display area 923 is provided to correspond to the editing attribute display area 921, and displays the maintenance period currently set for each editing attribute. In the example shown in Figure 7, the maintenance periods corresponding to stroke, marker, text, shape, and image are set to "60 days," "30 days," "no time limit," "90 days," and "1 day," respectively. A pull-down mark 924 is provided to correspond to the maintenance period display area 923. The pull-down mark 924 is selected when changing the maintenance period.

<Main processing>
When a user logs in to the note editing system 1, the CPU 21 shown in Fig. 1 reads out a control program from the program storage area 221 shown in Fig. 1. The CPU 21 executes the read out control program to start the main processing shown in Fig. 8. In the main processing, control relating to processing of history data will be mainly described, and illustrations and descriptions of control relating to sharing of notes by multiple users will be omitted.

In this embodiment, when a user logs in to the note editing system 1, the CPU 31 transmits login information to the server 2. The login information includes information such as an ID and password. Even if multiple users are logged in to the note editing system 1 at the same time, the CPU 31 is configured to identify the user who performed each operation based on the login information.

When the main processing starts, the CPU 21 determines whether a note selection operation has been performed based on whether note selection information has been received from the user terminal 3 (S10). In this embodiment, when the user performs a note selection operation in the note selection window 60 shown in FIG. 5, the CPU 31 transmits the note selection information to the server 2. The note selection information includes information for identifying the note selected by the user.

If the CPU 21 has not received note selection information from the user terminal 3, it determines that a note selection operation has not been performed (S10: NO). In this case, the CPU 21 returns the process to the determination in S10. If the CPU 21 has received note selection information from the user terminal 3, it determines that a note selection operation has been performed (S10: YES). In this case, the CPU 21 obtains note data corresponding to the selected note from the flash memory 22C shown in FIG. 1 based on the note selection information (S20).

The CPU 21 performs an editing process (S30). In the editing process, the CPU 21 edits objects in the page area 100 (see Figure 6) and stores history data in the history storage area 224 shown in Figure 3 in accordance with the editing operation. The CPU 21 performs a management process (S40). In the management process, the CPU 21 changes the change conditions for the storage state of the history data in the condition storage area 225 based on the permission setting change operation or the maintenance period change operation, and deletes the history data based on the maintenance period. The CPU 21 performs a first state change process (S50). In the first state change process, the CPU 21 deletes history data from the history storage area 224 based on the delete operation.

Based on the note selection information transmitted from the user terminal 3, the CPU 21 determines whether a note selection operation has been performed to select another note (S60). The other note is a note different from the note selected in the processing of S10.

If a note selection operation to select another note has not been performed (S60: NO), the CPU 21 returns to S30. In this case, the CPU 21 repeats S30, S40, and S50 for the currently selected note.

If a note selection operation is performed to select another note (S60: YES), the CPU 21 returns to S20. In this case, the CPU 21 obtains note data corresponding to the other note from the flash memory 22C shown in FIG. 1 (S20), and performs S30, S40, and S50 for the other note.

<Editing process>
9, when the editing process is started, the CPU 21 determines whether an editing operation has been performed based on whether editing information has been received from the user terminal 3 (S31). In this embodiment, when the user performs an editing operation in the page editing window 70 shown in Fig. 6, the CPU 31 transmits the editing information to the server 2. The editing information indicates the editing content and includes information for generating history data.

If the CPU 21 has not received editing information from the user terminal 3, it determines that an editing operation has not been performed (S31: NO). In this case, the CPU 21 returns the process to the main process shown in FIG. 8. If the CPU 21 has received editing information from the user terminal 3, it determines that an editing operation has been performed (S31: YES). In this case, the CPU 21 generates history data based on the editing information (S32).

In the processing of S32, for example, when the CPU 21 receives editing information, it obtains the information from a real-time clock (not shown) and sets the obtained time as the editing date and time. The CPU 21 sets the ID indicated by the editing information as the editor ID. The CPU 21 identifies the editing attribute and editing position based on the editing content in the editing information. The CPU 21 stores the generated history data in association with the corresponding note page in the history storage area 224 (S33). In this case, the CPU 21 stores the generated history data in the history storage area 224 so that it accumulates, rather than overwriting the already stored history data. The CPU 21 returns the processing to the main processing shown in FIG. 8.

<Management process>
10, when the management process is started, the CPU 21 refers to the account storage area 222 shown in Fig. 2 and determines whether the currently logged-in ID is an administrator ID (in this embodiment, the ID of user C) (S41). If the currently logged-in ID is not an administrator ID (S41: NO), the CPU 21 proceeds to S48.

If the logged-in ID is an administrator ID (S41: YES), the CPU 21 determines whether a maintenance deadline change operation has been performed based on whether deadline change information has been received from the user terminal 3 (S42). In this embodiment, when the user performs a maintenance deadline change operation in the history setting window 90 shown in FIG. 7, the CPU 31 sends the deadline change information to the server 2. The deadline change information includes information for identifying the edit attribute whose maintenance deadline has been changed and the length of the maintenance deadline after the change.

If the CPU 21 has not received expiration date change information, it determines that a maintenance expiration date change operation has not been performed (S42: NO). In this case, the CPU 21 proceeds to the determination of S45. If the CPU 21 has received expiration date change information, it determines that a maintenance expiration date change operation has been performed (S42: YES). In this case, the CPU 21 performs expiration date change processing (S43). In the expiration date change processing, the CPU 21 stores the length of the changed maintenance expiration date based on the expiration date change information in the maintenance expiration date section corresponding to the edit attribute in the condition storage area 225 shown in Figure 4.

The CPU 21 sends a maintenance period change notification to the user terminal 3 of the logged-in general user (S44). The CPU 21 sends a maintenance period change notification to the user terminal 3 of the logged-out general user the next time the general user logs in. The maintenance period change notification indicates the changes to the maintenance period. For example, the maintenance period change notification may say, "The maintenance period for image history data has been changed from 30 days to 1 day."

If the maintenance period change notification is not sent to general users, it would be difficult for them to know whether the maintenance period has changed. In this embodiment, the maintenance period change notification is sent to the user terminal 3 of the general user, making it easy for general users to know whether the maintenance period has changed and what the change is.

The CPU 21 determines whether a permission setting change operation has been performed based on whether permission setting change information has been received from the user terminal 3 (S45). In this embodiment, when the user performs a permission setting change operation in the history setting window 90 shown in FIG. 7, the CPU 31 sends the permission setting change information to the server 2. The permission setting change information includes information for identifying the changed permission settings.

If the CPU 21 has not received permission setting change information, it determines that a permission setting change operation has not been performed (S45: NO). In this case, the CPU 21 proceeds to processing at S48. If the CPU 21 has received permission setting change information, it determines that a permission setting change operation has been performed (S45: YES). In this case, the CPU 21 stores the changed permission settings based on the permission setting change information in the permission setting area corresponding to the selected note in the condition storage area 225 shown in FIG. 4 (S46).

The CPU 21 sends a permission setting change notification to the user terminal 3 of the logged-in general user (S47). The CPU 21 sends a permission setting change notification to the user terminal 3 of the logged-out general user the next time the general user logs in. The permission setting change notification indicates the changes to the permission settings. The permission setting change notification may, for example, say, "General users can now delete history data" or "General users can no longer delete history data."

If permission setting change notifications were not sent to general users, it would be difficult for them to know whether or not the permission settings have changed. In this embodiment, permission setting change notifications are sent to the user terminals 3 of general users, making it easier for general users to know whether or not the permission settings have changed and what the changes are.

The CPU 21 performs a second state change process (S48). The CPU 21 returns the process to the main process shown in FIG. 8. In the second state change process, the CPU 21 deletes history data whose retention period has expired from the history storage area 224. For example, the CPU 21 references the condition storage area 225 shown in FIG. 4 and identifies the retention period corresponding to one editing attribute. The CPU 21 references the edit date and time corresponding to one editing attribute in the history storage area 224 shown in FIG. 3. The CPU 21 identifies, from the history data corresponding to one editing attribute, history data for which the retention period corresponding to the one editing attribute has expired since the history data was stored in the history storage area 224. The CPU 21 deletes the identified history data from the history storage area 224 shown in FIG. 3. For other editing attributes, the CPU 21 deletes the identified history data from the history storage area 224 in the same way as for the one editing attribute.

In the example shown in Figure 3, one editing attribute is an image, and the other editing attribute is a stroke. The current time is one day after the editing date and time of 7:10 on March 31, 2022. In this case, the CPU 21 identifies history data H1 from the history data corresponding to the image as history data for which one day has passed since the history data was stored in the history storage area 224. The CPU 21 deletes history data H1 from the history storage area 224.

As of one day after the edit date and time of 7:10 AM on March 31, 2022, there is no history data corresponding to the stroke that is older than 90 days since it was stored in the history storage area 224. In this case, the CPU 21 does not delete history data H2 to H5 corresponding to the stroke from the history storage area 224, and maintains the storage status of history data H2 to H5.

For example, "one day has passed" may mean that 24 hours have passed since the history data was stored in the history storage area 224, or that a reference time (e.g., midnight) has passed on the following day, starting from the day the history data was stored in the history storage area 224. Furthermore, "when the maintenance deadline has passed" may mean the exact point in time when the maintenance deadline has passed, or any point in time after the maintenance deadline has passed.

<First state change process>
11, when the first status change process is started, the CPU 21 refers to the account storage area 222 shown in FIG. 2 and determines whether the currently logged-in ID is an administrator ID (S51). If the currently logged-in ID is an administrator ID (S51: YES), the CPU 21 proceeds to the determination in S53. In the example shown in FIG. 2, when user C is logged in, the ID type is "administrator," so the CPU 21 determines that the currently logged-in ID is an administrator ID.

If the currently logged-in ID is not an administrator ID (S51: NO), the CPU 21 proceeds to the determination in S52. In the example shown in Figure 2, when User A or User B is logged in, the ID type is "general," so the CPU 21 determines that the currently logged-in ID is not an administrator ID.

The CPU 21 references the condition storage area 225 and determines whether the permission setting is "permitted" (S52). If the permission setting is "prohibited" (S52: NO), the CPU 21 returns the process to the main process shown in FIG. 8.

If the permission setting is "allowed" (S52: YES), the CPU 21 determines whether a deletion operation has been performed based on whether deletion information has been received from the user terminal 3 (S53). In this embodiment, when the user performs a deletion operation in the history display area 74 shown in FIG. 6, the CPU 31 transmits the deletion information to the server 2. The deletion information includes information for identifying the history data to be deleted.

If the CPU 21 has not received the deletion information, it determines that a deletion operation has not been performed (S53: NO). In this case, the CPU 21 returns the process to the main process shown in FIG. 8.

If the CPU 21 receives the deletion information, it determines that a deletion operation has been performed (S53: YES). In this case, the CPU 21 deletes the target history data from the history storage area 224 based on the deletion information (S54). The CPU 21 then returns the process to the main process shown in FIG. 8.

<Effects of the embodiment>
In the above embodiment, when the user performs an operation to change the maintenance period or the permission setting, the change conditions for the storage status of the history data are changed by the process of S43 or S46. Therefore, the process of S43 or S46 contributes to the advantage that the user can easily manage the storage status of the history data.

For example, there may be editing attributes that a user wants to delete in a short period of time, and editing attributes that a user wants to maintain in a long-term storage state. If the retention period were the same for all editing attributes, it would be difficult to maintain the storage state of the history data for the period desired by the user, depending on each editing attribute. For example, if history data is deleted in a shorter period of time than the user wants, it would be difficult for the user to check the history data and restore the history. For example, if the storage state of the history data is maintained for a longer period of time than the user wants, the remaining storage capacity of the history storage area 224 may decrease, which could result in a decrease in performance of the note editing system 1. Alternatively, an increase in the number of history data items could make it difficult for the user to manage the history data. In the above embodiment, in the process of S43, the retention period is changed depending on the editing attribute of the history data. Therefore, the process of S43 contributes to the advantage of allowing the user to easily manage the retention period depending on the editing attribute.

In the S43 process, the retention period for history data corresponding to strokes or markers is changed without an upper limit. In the S43 process, the retention period for history data corresponding to text or shapes is changed to within 90 days. In the S43 process, the retention period for history data corresponding to images is changed to within 30 days. In other words, in the S43 process, the upper limit for the changeable retention period differs depending on each editing attribute. Therefore, the S43 process contributes to the advantage of being able to set retention periods within different time limits depending on the editing attribute.

In the processing of S48, history data whose retention period has expired is deleted from the history storage area 224. Therefore, the processing of S48 contributes to the advantage of preventing a decrease in the remaining storage capacity of the history storage area 224 due to the accumulation of history data.

If the permission setting is "allowed," the history data is deleted from the history storage area 224 by user A or user B in the process of S54. In other words, the storage status of the history data is changed by a "general" user. On the other hand, if the permission setting is "not allowed," the history data is not deleted from the history storage area 224 by user A or user B in the process of S54. In other words, deletion operations by "general" users are not accepted, and the storage status of the history data is not changed by "general" users. The permission setting is changed in the process of S46 when user C, i.e., the administrative user, performs a permission setting change operation. Therefore, the process of S46 contributes to the advantage of preventing history data from being deleted from the history storage area 224 by a general user without the administrative user's intention.

<Correspondence between embodiments and inventions>
In the above embodiment, the display 33 corresponds to the "display unit" of the present invention. The page area 100 corresponds to the "area" of the present invention. The note editing system 1 corresponds to the "information editing system" of the present invention. The CPU 21 corresponds to the "computer" of the present invention. The processing of S33 corresponds to the "storage processing" of the present invention. The processing of S43 and the processing of S46 each correspond to the "condition change processing" of the present invention. The permission setting change operation or the deadline change operation corresponds to the "condition change operation" of the present invention.

Editing attributes correspond to the "attributes" of the present invention. The retention period corresponds to the "deadline" of the present invention. For example, a stroke corresponds to the "first attribute" of the present invention. For example, 60 days corresponds to the "first deadline" of the present invention. For example, an image corresponds to the "second attribute" of the present invention. For example, 30 days corresponds to the "second deadline" of the present invention. The processing of S48 corresponds to the "deletion processing" of the present invention.

The administrator ID corresponds to the "first ID" of the present invention. User terminal 3C corresponds to the "first terminal" of the present invention. The touch panel 34 of user terminal 3C corresponds to the "first operation unit" of the present invention. The general ID corresponds to the "second ID" of the present invention. User terminal 3A or user terminal 3B corresponds to the "second terminal" of the present invention. The touch panel 34 of user terminal 3A or the touch panel 34 of user terminal 3B corresponds to the "second operation unit" of the present invention. The processing of S41 corresponds to the "ID determination processing" of the present invention. The processing of S54 corresponds to the "status change processing" of the present invention. The deletion operation corresponds to the "status change operation" of the present invention.

<Modification>
The present invention may be modified in various ways from the above embodiment. For example, in the above embodiment, the user terminal 3 is not limited to a tablet terminal, but may be a smartphone, a personal computer, a dedicated terminal, etc. The user terminal 3 may be equipped with a mouse, a keyboard, etc. instead of or in addition to the touch panel 34.

In the above embodiment, the note editing system 1 is composed of a server 2 and multiple user terminals 3. In contrast, the note editing system 1 may also be composed of a server 2 and a single user terminal 3. In other words, the note editing system 1 does not have to be configured so that multiple users can share notes. In this case, the note editing system 1 may not include a server 2 and may be composed of a single user terminal 3. When the note editing system 1 is composed of a single user terminal 3, the CPU 31 may execute the main processing. In this case, the condition storage area 225 does not need to store the permission settings, and the CPU 31 may omit the processing of S41, S44, S45, S46, S47, S51, and S52.

In the above embodiment, the note editing system 1 may change the processing content of the expiration date change process of S43. For example, as shown in FIG. 12, when the expiration date change process is initiated, the CPU 21 determines, based on the expiration date change information, whether the data capacity of the history data corresponding to the editing attribute for which the maintenance expiration date change operation was performed is equal to or less than a first reference capacity (S431). The first reference capacity is a predetermined threshold value, and is pre-stored in the ROM 22A shown in FIG. 1. The first reference capacity may be set, for example, based on the storage capacity of the history storage area 224.

The data size of the history data corresponding to the edited attributes for which the maintenance period change operation was performed may be the total data size of the history data corresponding to the edited attributes for which the maintenance period change operation was performed, or it may be the individual data size of the history data corresponding to the edited attributes for which the maintenance period change operation was performed.

If the data volume of the history data corresponding to the edited attribute for which the maintenance period change operation was performed is equal to or less than the first reference volume (S431: YES), the CPU 21 changes the maintenance period to within the first upper limit (S432). The CPU 21 then returns the process to the management process shown in FIG. 10.

If the data volume of the history data corresponding to the edited attribute for which the maintenance period change operation was performed is greater than the first reference volume (S431: NO), the CPU 21 changes the maintenance period to within the second upper limit (S433). The second upper limit is shorter than the first upper limit. The CPU 21 returns the process to the management process shown in FIG. 10. The maintenance period is configured so that the stored state of the history data is maintained for a certain period of time after the history data is stored in the process of S33. Therefore, the history data is not deleted immediately after being stored in the process of S33.

According to the expiration date change process shown in FIG. 12, if the data volume of the history data is larger than the first reference volume, the maintenance date is set within the second expiration date limit. In this case, even if the longest expiration date is set as the maintenance date, the maintenance date will be shorter than the first expiration date limit. Therefore, the expiration date change process has the advantage of being able to prevent the remaining storage capacity of the history storage area 224 from decreasing due to the accumulation of history data, compared to when the first expiration date limit is set as the maintenance date regardless of the data volume of the history data. In this case, the process of S431 corresponds to the "capacity determination process" of this invention.

For example, as shown in FIG. 13, when the expiration date change process begins, the CPU 21 determines whether there are multiple pieces of history data for which a maintenance expiration date change operation has been performed (S434). The multiple pieces of history data for which a maintenance expiration date change operation has been performed are referred to as "first history data" and "second history data." The first history data and second history data do not need to belong to the same editing attribute. The first history data and second history data may be defined as history data that belong to the same editing attribute.

If the first history data and the second history data do not exist (S434: NO), the CPU 21 returns the process to the management process shown in FIG. 10. In other words, if only one piece of history data exists, the CPU 21 does not change the retention period for that piece of history data. Therefore, for example, when one piece of history data is stored, the retention period for the stored history data is not changed. The retention period is configured so that the stored state of the history data is maintained for a certain period of time after the history data is stored in the process of S33. Therefore, the history data is not deleted immediately after being stored in the process of S33. If the first history data and the second history data exist (S434: YES), the CPU 21 compares the data capacity of the first history data and the second history data and determines whether the data capacity of the first history data is less than or equal to the data capacity of the second history data (S435).

If the data capacity of the first history data is less than or equal to the data capacity of the second history data (S435: YES), the CPU 21 changes the maintenance period for the first history data to within the first upper limit (S436). The CPU 21 changes the maintenance period for the second history data to within the second upper limit (S437). The CPU 21 returns the process to the management process shown in FIG. 10.

If the data volume of the first history data is greater than the data volume of the second history data (S435: NO), the CPU 21 changes the maintenance period for the second history data to within the first upper limit (S438). The CPU 21 changes the maintenance period for the first history data to within the second upper limit (S439). The CPU 21 returns the process to the management process shown in FIG. 10.

In other words, based on the comparison result in S435, the CPU 21 may change the maintenance period for the first history data or the second history data, whichever has the smaller data capacity, within the first upper limit. Based on the comparison result in S435, the CPU 21 may change the maintenance period for the first history data or the second history data, whichever has the larger data capacity, within the second upper limit. If the data capacity of the first history data and the second history data is the same, the CPU 21 may change the maintenance period for the first history data and the second history data, respectively, within the first upper limit, or may change it within the second upper limit.

According to this, the retention period is set within the second upper limit for the larger data volume of the first or second history data. In this case, even if the longest period is set as the retention period, it will still be shorter than the first upper limit. Therefore, the expiration change process has the advantage of being able to prevent the remaining storage capacity of the history storage area 224 from decreasing due to the accumulation of history data, compared to when the first upper limit is set as the retention period regardless of the data volume of the history data. In this case, the process of S435 corresponds to the "capacity comparison process" of this invention.

When the number of multiple history data items reaches a predetermined number, or when the total data capacity of the multiple history data items reaches a predetermined capacity, the CPU 21 may perform processing in S431. In this case, the CPU 21 may rank the multiple history data items according to a predetermined rule, such as by data capacity or edit date and time. Furthermore, the CPU 21 may change the retention period for ranked history data items that are higher than the predetermined rank within a first upper limit, and may change the retention period for ranked history data items that are lower than the predetermined rank within a second upper limit.

In the above embodiment, "changing the storage state of history data" means deleting history data. In contrast, "changing the storage state of history data" may also mean reducing the data volume of history data. For example, in the second state change process of S48, the CPU 21 may reduce the data volume of history data whose retention period has expired. Data volume reduction may be achieved by compression, lowering image resolution, thinning out dots contained in strokes, or the like. The amount of data volume reduction is not limited to a specific amount or percentage. In this way, the second state change process contributes to the advantage of being able to prevent the remaining storage capacity of the history storage area 224 from decreasing due to the accumulation of history data. In this case, the process of S48 corresponds to the "reduction process" of the present invention.

Furthermore, if the permission setting is "Allowed," general users, in addition to administrative users, may have the authority to reduce the data volume of history data through a reduction operation. In this case, in the processing of S53, the CPU 21 may determine whether a reduction operation has been performed instead of or in addition to whether a reduction operation has been performed. If a reduction operation has been performed, the CPU 21 may reduce the data volume of history data. A reduction operation is an operation for reducing history data. A reduction operation is, for example, an operation of selecting a reduction button (not shown) instead of the delete button during a delete operation. In this case, the reduction operation corresponds to the "status change operation" of the present invention.

In the above embodiment, the note editing system 1 may change the processing content of the second state change process. For example, as shown in FIG. 14, when the second state change process is started, the CPU 21 performs a maintenance expiration determination process (S481). In the maintenance expiration determination process, the CPU 21 references the history storage area 224 and determines whether or not there is history data whose maintenance expiration has passed. If there is no history data whose maintenance expiration has passed (S481: NO), the CPU 21 returns the process to the management process shown in FIG. 10.

If history data exists that has exceeded its retention period (S481: YES), the CPU 21 performs a capacity determination process (S482). In the capacity determination process, the CPU 21 determines whether the data volume of the history data that has exceeded its retention period is equal to or less than a second reference capacity. The second reference capacity is a predetermined threshold value that is pre-stored in the ROM 22A shown in FIG. 1. The second reference capacity may be set, for example, based on the storage capacity of the history storage area 224.

If the data volume of the history data whose retention period has expired is equal to or less than the second reference volume (S482: YES), the CPU 21 performs a first reduction process (S483). In the first reduction process, the CPU 21 reduces the history data whose retention period has expired by a first percentage. If the data volume of the history data whose retention period has expired is greater than the second reference volume (S482: NO), the CPU 21 performs a second reduction process (S484). In the second reduction process, the CPU 21 reduces the history data whose retention period has expired by a second percentage. The second percentage is greater than the first percentage. The first percentage and second percentage are predetermined values and are stored in advance in the ROM 22A shown in FIG. 1.

According to the second status change process shown in FIG. 14, if the data volume of the history data is greater than the second reference volume, the data volume of the history data that has passed its retention period is reduced by a greater amount than the first rate. Therefore, the second status change process contributes to the advantage of being able to suppress the reduction in remaining storage capacity due to the accumulation of history data, compared to when the data volume of the history data is reduced by the first rate regardless of the size of the data volume of the history data. In this case, the process of S482 corresponds to the "capacity determination process" of this invention.

In the second state change process shown in FIG. 14, the CPU 21 may change the processing content of the maintenance expiration determination process of S481. For example, in the maintenance expiration determination process of S481, the CPU 21 may determine whether there is multiple pieces of history data whose maintenance expiration has passed. Multiple pieces of history data whose maintenance expiration has passed are referred to as "first history data" and "second history data." If there is no multiple pieces of history data whose maintenance expiration has passed (S481: NO), the CPU 21 returns the processing to the management process shown in FIG. 10. If there is multiple pieces of history data whose maintenance expiration has passed (S481: YES), in the capacity determination process of S482, the CPU 21 may compare the data capacity of the first history data and the second history data to determine whether the data capacity of the first history data is less than or equal to the data capacity of the second history data.

If the data volume of the first history data is less than or equal to the data volume of the second history data (S482: YES), the CPU 21 may reduce the data volume of the first history data by a first percentage and reduce the data volume of the second history data by a second percentage in a first reduction process of S483. If the data volume of the first history data is greater than the data volume of the second history data (S482: NO), the CPU 21 may reduce the data volume of the second history data by a first percentage and reduce the data volume of the first history data by a second percentage in a second reduction process of S484.

In other words, based on the comparison result in the capacity determination process of S482, the CPU 21 may reduce the data volume of the smaller of the first and second history data by a first percentage, and may reduce the data volume of the larger of the first and second history data by a second percentage. If the data volumes of the first and second history data are the same, the CPU 21 may reduce the data volume of the first and second history data by either the first percentage or the second percentage.

In this way, the larger data volume of either the first or second history data is reduced by a greater amount than the first rate. Therefore, the second state change process contributes to the advantage of being able to suppress the reduction in remaining storage capacity due to the accumulation of history data, compared to when the data volume of the history data is reduced by the first rate regardless of the data volume of the history data. In this case, the process of S482 corresponds to the "capacity comparison process" of this invention.

The deadline limits for each editing attribute are not limited to the above embodiment. For example, the deadline limits for each editing attribute may be configured to be different or the same, regardless of whether the editing attribute is likely to result in a large data volume per file. More specifically, the deadline limit for an image may be longer than or the same as any or all of the deadline limits for strokes, markers, text, and shapes. The deadline limits for strokes and markers may be longer than or the same as any or all of the deadline limits for text and shapes. The deadline limits for text and shapes may be different from each other. It is not necessary to set a deadline limit for any editing attribute.

Images may be classified as still images or videos using editing attributes. In this case, the data size of a single video file is likely to be larger than the data size of a single still image file. For this reason, the upper limit for the time limit corresponding to a video may be shorter than the upper limit for a still image. The upper limit for the time limit corresponding to a video may be longer than the upper limit for a still image, or may be the same.

Object types may include types other than strokes, markers, text, shapes, and images. Object types may include some of the following types: strokes, markers, text, shapes, and images, for example, only text.

In the above embodiment, there is a one-to-one correspondence between object types and editing attributes. However, there does not have to be a one-to-one correspondence between object types and editing attributes. For example, text and shape may be combined to form a single editing attribute. Markers and strokes may be combined to form a single editing attribute.

In the above embodiment, the CPU 21 may, for example, instead of processing S48, determine whether the data capacity to be determined has exceeded a third reference capacity. The data capacity to be determined may be the total data capacity of multiple notes, the individual data capacity of multiple notes, the total data capacity of the history data stored in the history storage area 224, or the individual data capacity of the history data corresponding to each note or each page of the history data stored in the history storage area 224. The third reference capacity is a threshold value and is stored in the flash memory 22C shown in FIG. 1. The third reference capacity may be set, for example, based on the storage capacity of the history storage area 224. The administrative user may perform an operation to change the third reference capacity.

If the data capacity of the target of judgment is equal to or less than the third reference capacity, the CPU 21 may maintain the storage state of the history data. If the data capacity of the target of judgment exceeds the third reference capacity, the CPU 21 may delete the history data. In this case, the CPU 21 may delete the history data in order, starting with the history data with the oldest edit date and time. The CPU 21 may delete the history data in order, starting with the history data with the largest data capacity. The CPU 21 may delete the history data in order, starting with the history data with the smallest data capacity.

In the above embodiment, the CPU 21 may omit some of the main processing. For example, the CPU 21 may omit one or both of S44 and S47. The CPU 21 may omit one of S43 and S46. In other words, in the note editing system 1, the change conditions may include only one of the retention period and permission setting. For example, if the retention period is not included in the change conditions, the CPU 21 may omit S48. For example, if the permission setting is not included in the change conditions, the CPU 21 may omit S52. In this case, the CPU 21 may also omit S51. In other words, the note editing system 1 may be configured to allow history data to be deleted by a delete operation regardless of whether the user is an administrator.

In the above embodiment, history data may be stored in the history storage area 224 for each of multiple editing operations. The history data may indicate some of the editing date and time, editor ID, editing location, editing attributes, and editing content, or may indicate other information. The other information may be, for example, the editing location. The editing location is the location on Earth of the user terminal 3 when the editing operation was performed.

In the above embodiment, the CPU 21 generates the history data in the processing of S32. Alternatively, the CPU 31 may generate the history data. In this case, the CPU 31 may transmit the history data to the server 2 together with the editing information.

Instead of CPUs 21 and 31, microcomputers, ASICs (Application Specific Integrated Circuits), FPGAs (Field Programmable Gate Arrays), etc. may be used as processors. Main processing may be distributed among multiple processors. Non-transitory storage media such as ROM 22A and 32A and flash memory 22C and 32C may be storage media capable of retaining information regardless of the storage period. Non-transitory storage media may not include temporary storage media (e.g., transmitted signals). For example, the control program may be downloaded (i.e., transmitted as a transmission signal) from a server connected to a network (not shown) and stored in ROM 22A and 32A or flash memory 22C and 32C. In this case, the control program may be stored in a non-transitory storage medium such as an HDD provided in the server.

Even if a claim as originally filed contains a dependent claim (referred to as a "target dependent claim") that does not cite another citable dependent claim (referred to as a "non-cited dependent claim"). This is because, for example, the target dependent claim does not formally cite the non-cited dependent claim in order to avoid a claim that alternatively cites two or more other claims (a so-called multiple claim) or a claim that alternatively cites two or more other claims (a so-called multiple-multiple claim). Therefore, even if a target dependent claim exists in the claims as originally filed, inventions related to the target dependent claim that cites the non-cited dependent claim are not excluded from the disclosure of the present application. For example, inventions related to claims 1, 2, 5, and 7 in the claims as originally filed are not excluded from the disclosure of the present application. More specifically, when executing the modified deadline change process at S43, the CPU 21 may also execute the modified second status change process at S48. In other words, the above embodiment and the modified versions may be combined with each other to the extent that no contradictions arise.

1: Note editing system 3, 3A, 3B, 3C: User terminal 21: CPU
22A: ROM
22B: RAM
22C: Flash memory 33: Display 34: Touch panel

Claims (10)

The object in the area displayed on the display unit is input to a computer of an information editing system that can be edited via an operation unit.
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
and when a condition change operation for changing a change condition for the storage state of the history data stored by the storage process is performed via the operation unit, executing a condition change process for changing the change condition ;
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
The computer,
executing a capacity comparison process for comparing the data capacities of the first history data, which is the history data for which the condition change operation was performed via the operation unit, and the second history data, which is different from the first history data;
In the condition change process,
Based on the comparison result of the capacity comparison process, for the first history data or the second history data, whichever has a smaller data capacity, the term is changed within a first term as the change condition, and for the first history data or the second history data, whichever has a larger data capacity, the term is changed within a second term that is shorter than the first term as the change condition.
An information management program characterized by: The object in the area displayed on the display unit is input to a computer of an information editing system that can be edited via an operation unit.
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Execute
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
The computer,
executes a capacity determination process for determining whether the data capacity of the history data for which the condition change operation has been performed via the operation unit is equal to or less than a predetermined threshold;
In the condition change process,
When the capacity determination process determines that the data volume of the history data is equal to or smaller than the threshold, the change condition is to change the deadline within a first deadline, and when the capacity determination process determines that the data volume of the history data is greater than the threshold, the change condition is to change the deadline within a second deadline that is shorter than the first deadline.
An information management program characterized by: The object in the area displayed on the display unit is input to a computer of an information editing system that can be edited via an operation unit.
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Execute
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
The computer,
a capacity comparison process for comparing the data capacity of the first history data, which is the history data whose expiration date has passed, and the data capacity of the second history data, which is different from the first history data;
a reduction process for reducing the data volume of the first history data or the second history data, whichever has a smaller data volume, by a first percentage based on a comparison result of the volume comparison process, and reducing the data volume of the first history data or the second history data, whichever has a larger data volume, by a second percentage that is larger than the first percentage;
An information management program characterized by executing the above. The object in the area displayed on the display unit is input to a computer of an information editing system that can be edited via an operation unit.
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Execute
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
The computer,
a capacity determination process for determining whether the data capacity of the history data whose expiration date has passed is equal to or less than a predetermined threshold;
a reduction process of reducing the data volume of the history data by a first percentage when the capacity determination process determines that the data volume is equal to or less than the threshold, and reducing the data volume of the history data by a second percentage that is greater than the first percentage when the capacity determination process determines that the data volume is greater than the threshold;
An information management program characterized by executing the above. 3. The information management program according to claim 1, further comprising a deletion process for deleting the history data whose expiration date has passed. the information editing system allows the object to be edited via a first operation unit provided in a first terminal logged into the information editing system using a first ID that has been given in advance authority to change the storage state of the history data, and allows the object to be edited via a second operation unit provided in a second terminal logged into the information editing system using a second ID that has not been given authority to change the storage state of the history data;
The computer,
executes an ID determination process to determine whether the ID used to log in to the information editing system is the first ID;
when the ID is determined to be the first ID by the ID determination process and the condition change operation is performed via the first operation unit, in the condition change process, changing the change condition to whether or not to perform a permission setting to accept a state change operation for changing the storage state of the history data via the second operation unit;
If the ID is determined to be the second ID by the ID determination process, the condition change process is not executed,
The computer,
executing a state change process for changing the storage state of the history data;
The state change process includes:
When the state change operation is performed via the first operation unit, the storage state of the history data is changed;
When the permission setting is not performed, the state change operation is not accepted via the second operation unit,
The information management program according to claim 1 or 2 , characterized in that, when the permission setting is made and the state change operation is performed via the second operation unit, the storage state of the history data is changed. 1. An information management method using an information editing system that allows an object in an area displayed on a display unit to be edited via an operation unit, comprising:
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
a condition change process for changing a change condition for the storage state of the history data stored by the storage process when a condition change operation for changing the change condition is performed via the operation unit,
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
a capacity comparison process for comparing the data capacity of first history data, which is the history data for which the condition change operation was performed via the operation unit, and second history data different from the first history data, with each other;
In the condition change process,
Based on the comparison result of the capacity comparison process, for the first history data or the second history data, whichever has a smaller data capacity, the term is changed within a first term as the change condition, and for the first history data or the second history data, whichever has a larger data capacity, the term is changed within a second term that is shorter than the first term as the change condition.
An information management method comprising: 1. An information management method using an information editing system that allows an object in an area displayed on a display unit to be edited via an operation unit, comprising:
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Equipped with
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
a capacity determination process for determining whether the data capacity of the history data for which the condition change operation is performed via the operation unit is equal to or less than a predetermined threshold;
In the condition change process,
When the capacity determination process determines that the data volume of the history data is equal to or smaller than the threshold, the change condition is to change the deadline within a first deadline, and when the capacity determination process determines that the data volume of the history data is greater than the threshold, the change condition is to change the deadline within a second deadline that is shorter than the first deadline.
An information management method comprising: 1. An information management method using an information editing system that allows an object in an area displayed on a display unit to be edited via an operation unit, comprising:
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Equipped with
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
a capacity comparison process for comparing the data capacity of the first history data, which is the history data whose expiration date has passed, and the data capacity of the second history data, which is different from the first history data;
a reduction process for reducing the data volume of the first history data or the second history data, whichever has a smaller data volume, by a first percentage based on a comparison result of the volume comparison process, and reducing the data volume of the first history data or the second history data, whichever has a larger data volume, by a second percentage that is larger than the first percentage;
An information management method comprising: 1. An information management method using an information editing system that allows an object in an area displayed on a display unit to be edited via an operation unit, comprising:
a storage process for storing history data indicating a history corresponding to an editing operation when the editing operation for editing the object is performed in the area via the operation unit;
When a condition change operation for changing a change condition of the storage state of the history data stored by the storage process is performed via the operation unit, a condition change process for changing the change condition is performed.
Equipped with
In the condition change process, when the condition change operation is performed via the operation unit, a time limit for maintaining the stored state is changed as the change condition in accordance with an attribute of the history data edited by the editing operation;
a capacity determination process for determining whether the data capacity of the history data whose expiration date has passed is equal to or less than a predetermined threshold;
a reduction process of reducing the data volume of the history data by a first percentage when the capacity determination process determines that the data volume is equal to or less than the threshold, and reducing the data volume of the history data by a second percentage that is greater than the first percentage when the capacity determination process determines that the data volume is greater than the threshold;
An information management method comprising: