JP7211067B2 - Data management device and data management program - Google Patents

Description

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

In Patent Document 1, when recording a meeting and displaying the content of the meeting at a later date, the problem is to display the content of the meeting based on the recording in an easy-to-read manner for the user. and a display device for displaying at least one of documents and images among the stored conference information objects, wherein the period of the conference is divided into a plurality of time zones. a storage processing unit that associates each divided time zone with a meeting information object and stores the meeting information object in a storage device, and a calculation processing part that calculates the degree of excitement in each time zone of the meeting based on the stored meeting information object; , a conference information display system including a display processing unit that displays the stored conference information objects in a chronological arrangement on a display device with a degree of consolidation according to the degree of excitement in each time period.

JP 2018-73237 A

In order to share data such as documents, a folder that can be accessed by multiple people is used. Folders are hierarchized and managed using subfolders. Users need to understand folder hierarchies to locate data. For example, if this hierarchy becomes complicated, the number of hierarchies to be followed to reach desired data increases, making it difficult for the user to search for data.
On the other hand, maps and other diagrams that show the positional relationship for each region make it easy to visually grasp the positional relationship, and by associating the information, it is easy to find the target object from the positional relationship. easier to find things.
SUMMARY OF THE INVENTION It is an object of the present invention to provide a data management device and a data management program capable of searching for data triggered by the positional relationship shown for each region.

The gist of the present invention for achieving this object lies in the following inventions. The "claims" below are the claims as originally filed.
According to the first aspect of the present invention, there is provided a first display control means for controlling to display on a screen a diagram showing a positional relationship and divided into regions, and displaying an image representing data in the regions on the diagram. and a second display control means for controlling to display the image on the area.

The invention according to claim 2 is the data management device according to claim 1, wherein the position where the image is to be displayed can be further specified within the range of the specified area in the figure.

The invention according to claim 3 is the data management device according to claim 2, wherein the image display position cannot be specified outside the specified area.

According to a fourth aspect of the invention, the receiving means receives an instruction to display a mark on a part of the drawing, and when the mark is created, notifies the user who shares the drawing of the creation of the mark. 2. The data management apparatus according to claim 1, further comprising means for notifying that

According to the invention of claim 5, a rule is set that defines the type of data to be arranged near the mark, and the second display control means controls the display of the image according to the rule. The data management device described in .

The invention according to claim 6 is the data management device according to claim 4, wherein the notification means notifies the user when data is arranged near the mark.

A seventh aspect of the present invention is the data management device according to claim 1, wherein the second display control means changes the image according to one or more of the capacity, importance, and version upgrade of the data. is.

The invention of claim 8 is the data management device according to claim 1, wherein the second display control means displays the order in which the user browses the data on the diagram.

The invention according to claim 9 is the data management device according to claim 8, wherein the second display control means displays the browsing order by symbols.

The invention according to claim 10 is the data management device according to claim 1, wherein the reception means restricts the position of the image to be newly arranged according to the enlargement or reduction of the drawing.

According to the eleventh aspect of the invention, a first display control means for controlling a computer to display on a screen a diagram showing a positional relationship and divided by area, and data being represented on the area on the diagram It is a data management program for functioning as reception means for receiving an instruction to display an image for each of the regions, and second display control means for controlling to display the image on the region.

According to the data management device of claim 1, it is possible to search for data using the positional relationship shown for each region as a trigger.

According to the data management device of claim 2, it is possible to limit the position where the data is arranged within the range of the designated area.

According to the data management device of claim 3, it is possible to make it impossible to designate any area other than the designated area as the position to arrange the data.

According to the data management device of claim 4, it is possible to notify other users that a mark has been created.

According to the data management device of claim 5, it is possible to limit the types of data to be arranged near the mark.

According to the data management device of claim 6, it is possible to notify the user that the data is arranged near the mark.

According to the data management device of claim 7, one or more of data volume, importance, and version upgrade can be known from the image.

According to the data management device of claim 8, it is possible to know the order in which the data were browsed.

According to the data management device of claim 9, the order in which the data was browsed can be known from the symbols.

According to the data management device of claim 10, by enlarging or reducing the drawing, the position of the image to be newly arranged can be restricted.

According to the data management program of claim 11, data can be searched for based on the positional relationship indicated for each region.

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; 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; 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 map management table and a placeable/impossible area management table; 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; 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 data structure of a document management table; 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 landmark management table; FIG. 4 is an explanatory diagram showing an example data structure of a hierarchical landmark management 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; 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; 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 data structure of a log management table; 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; 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; 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 drive, 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 information processing apparatus 100 according to the present embodiment has a function of displaying an image representing data shared by a plurality of people. It has a storage module 110 , a shared data storage module 115 , a data management module 120 and a display control module 125 . For example, it may be used as a user interface in a document sharing device that handles a large number of documents.
Generally, in a document sharing device, an object called a folder (or directory) has been used so that a user can easily find a document that he/she wants to refer to. Documents and subfolders can be registered in this folder. A user searches for a desired document by tracing it on a user interface using a tree hierarchy display in which child folders or documents are grouped with folder icons and the hierarchy is viewed on a plane.
As the number of documents to be managed increases, the folder hierarchy becomes complicated. In addition, the number of hierarchies that must be traced to reach the desired document is increased, making it difficult for the user to find the desired document.

The instruction receiving module 105 is connected to the positional relationship diagram display control module 130 and the shared data display control module 135 of the display control module 125 . The instruction receiving module 105 instructs to display an image representing data ("shared data" or personal data of the user) on a part of the diagram showing the positional relationship. accept. In addition, this "figure" shows positional relationship, and may be divided for every area. Then, the instruction receiving module 105 receives, for each area on the drawing, an instruction to display an image representing the data.
Here, the "diagram showing the positional relationship" is a diagram that can be accessed by multiple people (specifically, it can be displayed on the user terminals of the multiple people), and that multiple people have a common understanding of the positional relationship. It is a diagrammatic representation of what exists. For example, there are maps, route maps, floor maps, and floor plans. These may be actual maps or the like, or may be maps or the like in virtual space (fantasy, games, etc.). As a common understanding here, it may be a map that is already known, or a map that is not specifically known, but common sense in maps (for example, it is not possible to build buildings on the sea) ) is shared. Also, the drawing may be a plan view or a three-dimensional view. Note that the "diagram showing the positional relationship" does not include a data configuration diagram such as a tree configuration diagram.
The “portion on the drawing” indicates a position within the drawing, and may be a point that can be represented by coordinates or an area having an area.
Data is text data, numerical data, graphic data, image data, video data, audio data, etc., or a combination thereof, subject to storage, editing, retrieval, etc., and exchanged as individual units between systems or users. Anything that can be done, including things similar to these. For example, it corresponds to a document (also called a file). 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. In the following, a document will be used as an example of data.
"Shared data" may be data shared by two or more users. In addition, the sharing user can browse the same diagram (map, etc.). Therefore, the same data is arranged at the same position on the drawing.
The "image representing data" may be an image representing the data, such as a reduced image (thumbnail image) of the data, an icon, or the like. Hereinafter, an icon will be exemplified as an "image representing data".
Also, as "acceptance of instruction", for example, an instruction by a user's operation using a mouse, keyboard, touch panel, voice, line of sight, gesture, or the like is accepted. Also, this instruction may be received via a communication line.

The instruction receiving module 105 receives "specifying the position where the image is to be displayed in the drawing". In this figure, there are two types: within the specified area and outside the specified area.
In other words, the instruction receiving module 105 "designates a position where the image is to be displayed within the designated area within the drawing" or "designates a position where the image is to be displayed outside the designated region within the drawing.""specify" will be accepted.
Here, for example, when a map is used as a diagram, the "designated area range" corresponds to the land area. In this case, the data will be placed on land.
For example, when a map is used as a diagram, the sea, rivers, etc. correspond to "areas other than the specified area". In this case, as will be described later, it is handled as if data cannot be placed in areas such as seas and rivers.
Further, the instruction receiving module 105 may receive an instruction to display a mark on a part of the drawing.
Here, the "marker" is also called a mark or a landmark, and is a mark (reference) of a position where data is to be displayed on the drawing.

In addition, the instruction receiving module 105 may limit the position of the image to be newly arranged according to the enlargement or reduction of the drawing. For example, if there are no gaps between images (when multiple images are already densely arranged on the diagram), no new images can be added between them, but if the diagram is enlarged, , there is a gap between the images, so the addition of a new image may be allowed. Conversely, if there is no gap between the images due to the reduction, it may not be permitted to place a new image between the images.

The positional relationship diagram storage module 110 is connected to the positional relationship diagram display control module 130 of the display control module 125 . The positional relationship diagram storage module 110 stores information about diagrams. For example, it manages the shape of a diagram, an area where an image can be displayed in the diagram, an area where an image cannot be displayed in the diagram, and the like. Specifically, it will be described later with reference to FIG.
The shared data storage module 115 is connected with the data management module 120 . The shared data storage module 115 manages locations such as URLs where data is stored (or data itself), images representing data, positions on maps, logs of data browsing, and the like. . Specifically, it will be described later with reference to FIGS. 16 and 31. FIG.
The data management module 120 is connected to the shared data storage module 115 and the shared data display control module 135 of the display control module 125 . Data management module 120 manages data in shared data storage module 115 . For example, the layout position specified by the user's operation is stored in the shared data storage module 115 , the data for which the viewing instruction is directed is read, and the data is passed to the shared data display control module 135 .

The display control module 125 has a positional relationship diagram display control module 130 , a shared data display control module 135 and a notification module 140 . The display control module 125 performs processes such as drawing, arranging images on the drawing, viewing data, and the like. The display device may be one provided in the information processing device 100, or may be a display device of a user terminal connected via a communication line.
The positional relationship diagram display control module 130 is connected to the instruction receiving module 105 and the positional relationship diagram storage module 110 . The positional relationship diagram display control module 130 controls to display on the screen a diagram showing the positional relationship and divided into regions.

Shared data display control module 135 is connected to instruction reception module 105 and data management module 120 . The shared data display control module 135 controls the image to be displayed on the map area (part of the map).
When the instruction receiving module 105 receives "specify the position where the image is to be displayed within the specified area within the drawing", the shared data display control module 135 determines whether the image is to be displayed within the specified area. The image can be displayed at the specified position. As in the above example, when a map is used as a diagram, this corresponds to arranging data on the land area.
Then, the shared data display control module 135 makes it impossible to designate an area other than the designated area as a position for displaying an image. In other words, when the instruction receiving module 105 receives "to designate a position where an image is to be displayed outside the designated area in the drawing", the shared data display control module 135 displays the image at the designated position. It is possible to prevent the image from being displayed.
Here, for example, when a map is used as a diagram, the "area other than the specified area" corresponds to the sea, rivers, etc., which are parts other than the land. In this case, data cannot be placed in areas such as seas and rivers.

Further, when the instruction reception module 105 receives an instruction to display a mark, the shared data display control module 135 displays the mark in a part of the drawing.
A rule is set that defines the type of data to be arranged near the mark, and the shared data display control module 135 controls the display of the image according to the rule.
Here, as a "rule", for example, prepare a table that associates a mark with a type of data, extract the type of data placed near the mark, and determine if the type matches the type in the table. If it does, the placement is permitted, and if it does not match, a message or the like is displayed to the effect that the data cannot be placed, and the placement of the data is not permitted.

Also, the shared data display control module 135 may change the image according to one or more of data volume, importance, and version upgrade.
Here, "changing the image" means linking the data and the image display. If it is, it corresponds to raising the altitude of the mountain.
In the case of a document, the number of pages may be included as the "capacity of data".
Also, the shared data display control module 135 may display the order in which the user viewed the data on the diagram.
For example, the shared data display control module 135 may display the viewing order by symbols.
Here, the "symbol" (also referred to as a symbolic diagram) includes, for example, a footprint symbol. By tracing the footprints in order, the data can be traced in the order in which they were browsed.

The notification module 140 notifies the user sharing the drawing of the creation of the landmark when the landmark is created.
The notification module 140 may also notify the user when data is placed near the landmark.
The notification module 140 may also notify the user when the drawing has been viewed. Here, "when a diagram is browsed" corresponds to the case where an application that stores data using a diagram is opened.

FIG. 2 is an explanatory diagram showing a system configuration example using this embodiment.
Information processing device 100A, information processing device 100B, user terminal 210A, user terminal 210B, user terminal 210C, user terminal 210D, and data management device 250 are connected via communication line 290, respectively. The communication line 290 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 information processing device 100 and the data management device 250 may be implemented as a cloud service.
The data management device 250 has a positional relationship diagram storage module 110B and a shared data storage module 115B.

For example, the user terminals 210A and 210B belong to the same group and share documents using the information processing device 100A. The user terminals 210C and 210D belong to the same group, and share documents using the information processing device 100B. As a diagram used in the same group, for example, a map or the like that the group members commonly recognize regarding the positional relationship is adopted.
The information processing device 100B has the shared data storage module 115, the data management module 120, and the display control module 125 of the information processing device 100 (that is, has the positional relationship diagram storage module 110 and the shared data storage module 115). ), and the positional relationship diagram storage module 110B and the shared data storage module 115B of the data management device 250 are used via the communication line 290 as the positional relationship diagram storage module 110 and the shared data storage module 115. . The data management device 250 may also have the functions of the positional relationship diagram storage module 110 and the shared data storage module 115 for a plurality of information processing devices 100 . In that case, it is used when the plurality of information processing apparatuses 100 handle common diagrams and data.
Even if there are many common documents, the user can directly access the desired document because the document is placed on a map that group members commonly recognize, such as a map. become. That is, place the document in a diagram suitable for storing in association with visual features, such as a map. Then, when viewing a document, the user can search for the document by swiping on the map (an operation of sliding a finger while touching the screen among the operations in the multi-touch interface). Also, when the document is moved to another place on the map, the information of the move destination is left at the place before the move.

FIG. 3 is a flowchart showing an example of processing according to this embodiment. It shows an overview of the processing.
In step S302, first, a map (an example of a diagram) is created according to the operation of a user (eg, leader, etc.) in the group.
In step S304, a document (an example of data) is registered on the map according to the operation of the user in the group. That is, an icon (an example of an image representing data) of the document is arranged on the map.
In step S306, the document is moved according to the user's operation within the group.

FIG. 4 is a flowchart showing an example of processing according to this embodiment. FIG. 4 shows an example of processing in step S302 in the flowchart shown in the example of FIG. 3. FIG.
In step S402, it is determined whether or not a map has been created. If the map has been created, the process proceeds to step S404. Otherwise, the process proceeds to step S408.
In step S404, it is determined whether or not the document is registered in the displayed map. If it is registered, the process proceeds to step S406, otherwise the process proceeds to step S410.
In step S406, menus for map creation, document registration, and movement are displayed.
In step S408, a map creation menu is displayed.
At step S410, a menu for map creation and document registration is displayed.

FIG. 5 is a flowchart showing an example of processing according to this embodiment.
In step S502, the user's menu selection is determined, and in the case of "map creation", the process proceeds to step S504, in the case of "document registration", the process proceeds to step S516, and in the case of "move", the process proceeds to step S522.
In step S504, the map creation method is determined, and in the case of "template selection", the process proceeds to step S506, in the case of "random creation", the process proceeds to step S510, and in the case of "freehand creation", the process proceeds to step S512. When the user selects to create a map, the positional relationship diagram display control module 130 displays a UI (User Interface, specifically, a dialog box) for allowing the display device to select how to create a map (boundary). etc.).

In step S506, the template is displayed. Display a plurality of maps as a type prepared in advance.
For example, a list of map templates may be selected based on the addresses or locations of members of the group to which the operator belongs or the group whose map is being created. . For example, a map containing the member's address may be selected, a map of the route from the member's address to the commuting destination (for example, a route map) may be selected, or the member's work address may be selected. If there is one place of work, the map of the route from the station nearest to the place of work to the place of work may be selected. Documents can be easier to remember by using maps that members are familiar with.
In step S508, the template desired by the user is selected from the templates displayed in step S506.

In step S510, a map is created randomly. In the case of random, a random map is created in the information processing apparatus 100 using an algorithm used in an existing map creation tool or the like, and presented to the user.
In step S512, a map is created according to the user's operation. In the case of freehand, the UI parts (pen etc.) necessary for the user to create a map are provided. The user uses this to create an enclosed boundary (map).
In step S514, a map is arranged. If it is a part of the entire map, the created map is placed on the screen, and the process returns to step S504 (or any of the previously selected method, step S506, step S510, or step S512). , to map other parts. Specifically, when the user determines a map by pressing an OK button or the like, the map is placed on the display device (screen) at a place where no map exists by the user's drag-and-drop operation or the like.
Note that a map (whole or partial map) may have a maximum area. That is, the number of documents that can be laid out on a certain map and the area per document are determined in advance, and only maps with an area within the range of "the number of documents that can be laid out x the area per document" can be created. .
Also, the name and coordinate information of the created map may be stored in the positional relationship diagram storage module 110 so that the positional relationship diagram display control module 130 can refer to them later.
Also, an area where documents can be arranged and an area where documents cannot be arranged may be set on the map. For example, it may be set according to a user's operation, or a predetermined area (for example, land) may be set as the "area where documents can be placed", and other areas (for example, rivers, seas, etc.) It may be set as "a region in which documents cannot be placed".

In step S516, a position on the map is designated according to the user's operation. Detailed processing of step S516 will be described later using the flowchart shown in the example of FIG.
In step S518, a document is designated.
In step S520, the document is placed on the map.
In step S522, a document on the map is selected.
In step S524, a position on the map is designated according to the user's operation. Detailed processing of step S524 will be described later using the flowchart shown in the example of FIG.
In step S526, the document is moved to the specified position.

FIG. 6 is a flowchart showing an example of processing according to this embodiment.
In step S602, the position designated by the user's operation is accepted.
In step S604, it is determined whether or not the document can be placed at the specified position (for example, land on the map). If yes, the process ends (step S699). proceed to
In step S606, it is presented that the document cannot be arranged at the specified position, and the process returns to step S602.

FIG. 7 is an explanatory diagram showing an example of the data structure of the map management table 700 and the placeable/impossible area management table 750. As shown in FIG. As a result of map creation (steps S504 to S514), a map management table 700 and a placeable/impossible area management table 750 are created and stored in the positional relationship diagram storage module 110. FIG.
FIG. 7A is an explanatory diagram showing an example data structure of the map management table 700. As shown in FIG.
The map management table 700 has a map ID column 705 , a creator column 710 , a user group column 715 , a creation date column 720 and a map content column 725 . The map ID column 705 stores information (map ID: IDentification) for uniquely identifying a map in this embodiment. The creator column 710 stores the creator (for example, user ID) of the map. The user group column 715 stores groups (for example, group IDs) that use the map. The creation date and time column 720 stores the creation date and time of the map (year, month, day, hour, minute, second, seconds or less, or a combination thereof). The map content column 725 stores the content of the map. For example, data indicating the contents of a map include bitmap images (bmp, gif, jpg, etc.), vector data indicating boundaries of the map, and the like.

FIG. 7B is an explanatory diagram showing an example of the data structure of the arrangeable/impossible area management table 750. As shown in FIG.
The placeable/impossible area management table 750 has a map ID column 755, a document placeable area column 760, and a document placeable area column 770. The document placeable area column 760 includes (X1, Y1) columns 762, It has a (X2, Y2) column 764 , and the document placement impossible area column 770 has a (X3, Y3) column 772 and a (X4, Y4) column 774 . The map ID column 755 stores map IDs. The document arrangement possible area column 760 stores the document arrangement possible area on the map. The (X1, Y1) column 762 stores coordinates (X1, Y1). The (X2, Y2) column 764 stores coordinates (X2, Y2). The document placement impossible area column 770 stores the document placement impossible area on the map. The (X3, Y3) column 772 stores coordinates (X3, Y3). The (X4, Y4) column 774 stores coordinates (X4, Y4). For example, the (X1, Y1) column 762 and (X3, Y3) column 772 indicate the upper left coordinates of the rectangular area, and the (X2, Y2) column 764 and (X4, Y4) column 774 indicate the right coordinate of the rectangular area. It shows the bottom coordinate.

8 to 11 show an example of processing for creating a map.
FIG. 8 is an explanatory diagram showing an example of processing according to this embodiment.
A user terminal 800 has a screen 810 . For example, the screen 810 displays a message/alert display area 820 , a map/document display area 830 and a menu area 840 , and the menu area 840 displays a map creation button 842 and a document registration button 844 .
When the user of the information processing apparatus 100 logs in, the positional relationship diagram display control module 130 displays an image on the user terminal 800 according to existing maps, document coordinate information, name information, etc. stored in the positional relationship diagram storage module 110. Display as a map. The display form may be 2D or 3D.
The positional relationship diagram display control module 130 displays on the screen 810 a UI part (map creation button 842) that triggers map creation. UI parts are generally buttons, context menus, etc., but are not limited to these.

FIG. 9 is an explanatory diagram showing an example of processing according to this embodiment.
6 shows a display example in step S504 in the flowchart shown in the example of FIG. 5. FIG.
When map creation button 842 is pressed 910 by the user, message/alert display area 820 displays, for example, "Which method do you want to create an area?" A creation method selection menu 920 is displayed. In the map creation method selection menu 920, one of "template selection" (step S506), "random" (step S510), and "freehand" (step S512) can be selected. In this example, "template selection" is selected.

FIG. 10 is an explanatory diagram showing an example of processing according to this embodiment.
When the map is completed, as shown in the example of FIG. 10, message/alert display area 820 displays, for example, "Is this map acceptable?" (Area) 1010, OK button 1020, and Cancel button 1030 are displayed. When the OK button 1020 is selected, the created map (area) 1010 is stored in the positional relationship diagram storage module 110 . When the cancel button 1030 is selected, the created map (area) 1010 is discarded (or as a correction target), and the processes after step S504 are repeated.
For example, in the case of “template selection”, the user selects a desired map from templates and presses the OK button 1020 . When the cancel button 1030 is pressed, the map of the next template is displayed.

FIG. 11 is an explanatory diagram showing an example of processing according to this embodiment.
The map (part) completed in FIG. 10 is arranged in the entire map (here, map/document display area 830 (so-called blank map)) according to the user's operation. Please select a location.” is displayed, and a map (area) 1110 , an OK button 1120 and a Cancel button 1130 are displayed in the map/document display area 830 .
For example, a map (area) 1110 is placed in an area where no map has yet been placed. At this point, if the OK button 1120 is pressed, the layout of the map (area) 1110 is completed.

12 and 13 show an example of processing for arranging documents.
FIG. 12 is an explanatory diagram showing an example of processing according to this embodiment.
The shared data display control module 135 displays on the screen 810 a UI part (document registration button 844 ) that triggers document placement. UI parts are generally buttons, context menus, etc., but are not limited to these.
When the document registration button 844 is pressed 1210 by the user, the message/alert display area 820 displays, for example, "Please select a place to place the document."
Then, when the user selects on the map, the pin display processing 1220 of the pin 1230 is performed in the map/document display area 830 . Further, when the operation 1210 of pressing the document registration button 844 is performed, a UI (for example, a dialog) for arranging the document on the map may be displayed.
Specifically, according to the user's operation, the map is moved by swiping and enlarged to a desired size. Then, when the document registration button 844 is pressed 1210, a place to place the document is selected (tapped) by the user's operation, and a pin 1230 is displayed at that place.

FIG. 13 is an explanatory diagram showing an example of processing according to this embodiment.
The message/alert display area 820 displays, for example, "Please select a place to place the document."
The map/document display area 830 displays a document selection dialog 1310 that is a list of documents (and may prompt the user to enter the document name), and displays the selected document icon 1320 in the document selection dialog 1310 as It is displayed at the position of pin 1230 .
In the example of FIG. 13, as the document icon 1320, the media type icon and the document name are displayed at the position of the pin 1230 shown in the example of FIG.
In addition, the size of the content may be indicated.

14 and 15 show an example of processing for moving a document.
FIG. 14 is an explanatory diagram showing an example of processing according to this embodiment.
A map creation button 842 , a document registration button 844 and a move button 1446 are displayed in the menu area 840 .
When the move button 1446 is pressed 1410 by the user, the message/alert display area 820 displays, for example, "Please select a move destination."
When the user presses down document icon 1320 in map/document display area 830 and then presses down document icon 1420, destination pin 1440 is displayed at that position. Then, the document icon 1320 is displayed at the position of the destination pin 1440 .

FIG. 15 is an explanatory diagram showing an example of processing according to this embodiment. The shared data display control module 135 moves the placed document to another place, and when the user selects the place where the document was before the move, the shared data display control module 135 displays the name of the document that previously existed at that place, and the user can After selecting the document name, an arrow or the like may be displayed to indicate where the document has been moved. Note that when the document is moved, a source icon (mark) 1510 is displayed at the source location.
Specifically, when the user selects the source icon (mark) 1510 after the document icon 1320 has been moved to the position of the destination pin 1440 shown in the example of FIG. 14, the document name display area 1560 is displayed. . Then, when the document name display area 1560 is pressed 1550 by the user, a move arrow 1520 indicating that the document name display area 1560 has been moved from the source icon (mark) 1510 to the document icon 1320 is displayed.

The shared data display control module 135 causes the shared data storage module 115 to store the name, coordinates, and content information of the document when the user selects a place to place the document and designates the document name and content. For example, the document management table 1600 is stored. FIG. 16 is an explanatory diagram showing an example data structure of the document management table 1600. As shown in FIG. The document management table 1600 has a map ID column 1605, a document ID column 1610, a document storage location (URL) column 1615, a map placement position column 1620, a document name column 1625, and a document icon column 1630. The location column 1620 has an X column 1622 and a Y column 1624 . The map ID column 1605 stores map IDs. The document ID column 1610 stores information (document ID) for uniquely identifying a document in this embodiment. The document storage location (URL) column 1615 stores the document storage location (URL). The map placement position column 1620 stores the placement position of the document on the map. The X column 1622 stores the X coordinate of the layout position. The Y column 1624 stores the Y coordinate at the layout position. The document name column 1625 stores the document name of the document. The document icon field 1630 stores the icon of the document.

A place where a document can be placed may be limited to a place where no document has been placed yet, or may be the same place as a document already placed. In this case (moving to the same location), it may be regarded as adding a version of the document or replacing the contents.
Also, when arranging documents, access rights may be set for each document.
If the place where the document is to be placed is already filled, the map may be enlarged to create a gap to place the document.

The positional relationship diagram display control module 130 and the shared data display control module 135 display (redraw) the maps and documents stored by the positional relationship diagram storage module 110 and the shared data storage module 115 in the map/document display area 830. do.
Documents may be displayed in different colors according to thumbnails, document names, media type images, and degrees of importance.
As a method of moving the drawing, there is a swipe or a touched place as a new center, but it is not limited to this. Pinch-in/pinch-out can be considered as a method of enlarging/reducing the drawing, but the method is not limited to this.
After the image has been enlarged to some extent, it may be changed to another display mode. For example, the document may initially be displayed as icons on a 2D map, but when enlarged, the document may be represented as 3D buildings and versions displayed.
Also, at first, the tree hierarchy is displayed as in the conventional case, but when the hierarchy becomes deeper, it may be switched to the map display.
If access rights are set for documents, documents without read access rights may not be displayed.

The landmark processing will be described using the examples of FIGS. 17 to 28. FIG.
Since each user can freely place documents on the map, even documents grouped according to specific criteria (for example, weekly report of a group member for a certain week) are placed in different places, and related documents cannot be found. It becomes difficult to find.
Therefore, in the present embodiment, landmarks are used to make it easier to find related documents (compared to the case where landmarks are not used).
A mark called a landmark is placed on the map and used as a starting point for document registration. For example, a document may be placed only near the landmark. This allows users to easily find relevant documents by searching around landmarks.

FIG. 17 is a flowchart showing an example of processing according to this embodiment.
In step S1702, it is determined whether or not the received user operation is an operation for creating a landmark. If the operation is for creating a landmark, the process proceeds to step S1704. Otherwise, there is an operation for creating a landmark. wait until
In step S1704, designation of the layout position of the landmark is accepted according to the user's operation.
In step S1706, information relating to landmarks is accepted according to user's operation.
In step S1708, landmarks are generated. For example, a landmark management table 1800 is generated.
In step S1710, groups that can use the landmark are extracted.
In step S1712, the members of the group are notified that a landmark has been created. For example, a table in which group IDs and user IDs are associated with each other may be prepared in advance, and the user who is the notification destination may be extracted from the group using the table.

FIG. 18 is an explanatory diagram showing an example data structure of the landmark management table 1800. As shown in FIG. The landmark management table 1800 is stored in the shared data storage module 115. FIG. The landmark management table 1800 has a landmark ID column 1805 and a landmark information column 1810. The landmark information column 1810 includes a name column 1812, a position column 1814, a shape column 1816, an icon column 1818, and a color column 1820. , size column 1822 , creator column 1824 , registrable group column 1826 , and arrangeable document column 1828 . The landmark ID column 1805 stores information (landmark ID) for uniquely identifying a landmark in this embodiment. The landmark information column 1810 stores landmark information (a name column 1812 to a placeable document column 1828). The name column 1812 stores the name of the landmark. The position column 1814 stores the position where the landmark is arranged. The shape column 1816 stores the shape of the landmark (circle, ellipse, rectangle, polygon, etc.). The icon column 1818 stores the icon of the landmark. The color column 1820 stores the color of the landmark. The size column 1822 stores the size of the landmark. The creator column 1824 stores the creator of the landmark. The registrable group column 1826 stores groups in which documents can be placed near the landmark. The placeable document field 1828 stores the types of documents that can be placed near the landmark. Types of documents that can be placed near the landmark include, for example, documents whose document name includes "weekly report", whose creator is a predetermined user, and whose creation date and time are within a predetermined period. and so on.

Also, landmarks may have a parent-child relationship. FIG. 19 is an explanatory diagram showing an example data structure of the hierarchical landmark management table 1900. As shown in FIG. The hierarchical landmark management table 1900 has a landmark ID column 1905 , a parent landmark ID column 1910 and a child landmark ID column 1915 . The landmark ID column 1905 stores landmark IDs. The parent landmark ID column 1910 stores the landmark ID that is the parent of the landmark. The child landmark ID column 1915 stores landmark IDs that are children of the landmark.

FIG. 20 is a flowchart showing an example of processing according to this embodiment. It shows an example of processing when arranging a document on a map with landmarks.
In step S2002, it is determined whether or not there is a landmark, and if there is a landmark the process proceeds to step S2004, otherwise the process proceeds to step S2010.
In step S2004, features of the document to be registered are extracted. Features to be extracted include, for example, the document name, creator, date and time of creation, data volume, and the like.

In step S2006, it is determined whether or not there is a landmark to which the document should be placed.
In step S2008, landmarks to be recommended are presented.
In step S2010, the document is arranged according to the user's registration instruction. In step S2010, the same processing as the processing after step S516 in the flowchart shown in the example of FIG. 5 is performed.

FIG. 21 is a flowchart showing an example of processing according to this embodiment.
In step S2102, it is determined whether or not the document has been placed near the landmark. If the document has been placed, the process advances to step S2104.
In step S2104, groups that can use the map are extracted. The use group column 715 of the map management table 700 shown in the example of FIG. 7 may be used.
In step S2106, groups that can use the landmark are extracted. The registerable group column 1826 of the landmark management table 1800 shown in the example of FIG. 18 may be used.

At step S2108, it is determined at step S2106 whether or not a group that can use the landmark has been extracted.
In step S2110, members of the group are notified that the document has been placed near the landmark.
In step S2112, members of the group extracted in step S2104 are notified that the document has been placed near the landmark.

FIG. 22 is an explanatory diagram showing an example of processing according to this embodiment.
The shared data display control module 135 displays on the screen 810 a UI part (landmark creation button 2248) that triggers landmark creation. UI parts are generally buttons, context menus, etc., but are not limited to these.
In the menu area 840, for example, a map creation button 842, a landmark creation button 2248, and a document registration button 844 are displayed.
When the user presses 2210 the create landmark button 2248, the message/alert display area 820 displays, for example, "Please select a place to place a landmark."
When the user designates a position for displaying a landmark, pin display processing 2220 is performed to display a pin 2230 at that position.

FIG. 23 is an explanatory diagram showing an example of processing according to this embodiment.
An example of processing for setting information about landmarks will be described.
The message/alert display area 820 displays, for example, "Please enter a landmark name."
A landmark name setting area 2310 is displayed in the map/document display area 830 , and an OK button 2312 and a cancel button 2314 are displayed in the landmark name setting area 2310 .
For example, “20170228 weekly report” is set as the landmark name in the landmark name setting area 2310 .
Alternatively, groups (or users) that can be placed near the landmark may be set.
Also, in addition to the place where the landmark is to be created and the name of the landmark, the shape, icon, color, size, etc. of the landmark may be set. When the OK button 2312 is pressed by the user, the shared data storage module 115 stores information about the landmark.
The shape of the landmark may be circular, elliptical, rectangular, or the like, or may be freely determined by the user.
Also, a landmark may be created so as to overlap a place where a landmark already exists, or a landmark (sub-brand mark) completely included in an existing landmark may be created.
Additionally, an existing landmark may be selected so that the area of that landmark can be resized.

FIG. 24 is an explanatory diagram showing an example of processing according to this embodiment. An example of displaying a landmark 2410 on the map after the processing shown in the examples of FIGS. 22 and 23 will be described.
The message/alert display area 820 displays, for example, "Landmark created."
Landmarks 2410 are displayed in the map/document display area 830 . A landmark name “20170228 Weekly Report” is displayed around the landmark 2410 .
The shared data display control module 135 displays landmarks on the map based on information such as position information, name, and shape stored in the shared data storage module 115 . As a method of displaying landmarks, the landmark name and the color of the range of the landmark are displayed in a different color from the ground color, but the method is not limited to this.

FIG. 25 is an explanatory diagram showing an example of processing according to this embodiment. An example of arranging a document near a landmark will be described.
The message/alert display area 820 displays, for example, "Please specify a landmark for document registration." Select where the landmark exists when registering the document. Specifically, a landmark 2410 is selected by the user's selection operation 2510, and a pin 2520 is displayed at that position.

FIG. 26 is an explanatory diagram showing an example of processing according to this embodiment.
A document icon 2620 is displayed on the pin 2520 (within the landmark 2410) shown in the example of FIG. Then, the message/alert display area 820 displays, for example, "The document has been registered."

FIG. 27 is an explanatory diagram showing an example of processing according to this embodiment. A parent-child relationship may be given between landmarks.
For example, a landmark (weekly report) 2710 is an area in which a weekly report is placed, and a sub-brand mark (20170228 weekly report) 2720, which is a child of the landmark (weekly report) 2710, is an area in which a certain week's weekly report is placed. there is
As for the landmark names, the sub-brand mark names may be made visible only by enlarging the map to some extent.

FIG. 28 is an explanatory diagram showing an example of processing according to this embodiment. FIG. 10 shows a display example of a URL of a landmark. FIG.
When a landmark (weekly report) 2710 is selected (long-pressed, etc.) by the user 2810, a document storage location display area 2830 is displayed (2820). For example, the document storage location display area 2830 displays “Name: Weekly Report, URL: http://aaa.com/landmark-0001/”. This indicates the URL in which the document (weekly report) arranged in the landmark (weekly report) 2710 is stored. The reason why the URL is displayed is to show other users where the document is registered. In other words, this URL is notified to other users by e-mail or the like to have them store the weekly report. If the weekly report is stored at that URL, the icon of that document is displayed on the map (within the landmark).
Also, when the user selects a landmark and gives a download instruction, the shared data display control module 135 may collectively download all documents belonging to the landmark.
In addition, the shared data display control module 135 may additionally input a landmark to which the document belongs when arranging the document. Of course, the designation of landmarks may be mandatory or optional.

FIG. 29 is a flowchart showing an example of processing according to this embodiment.
In step S2902, features of the document (capacity, importance, upgrade (version)) are extracted.
In step S2904, the document icon displayed on the map is changed according to the feature. For example, when two versions of one document are created, a building (for example, building) is displayed at the position where the document icon is located, and the document is displayed on each floor of the building (the first version of the document is on the first floor, the second version is on the second floor). Version documents, etc.) may be arranged. Then, each time the version of the document overlaps, the height of the building may be increased on the map. Also, the size of the document icon may be changed according to the capacity of the document. For example, as the size of the document increases, the size of the document icon may also increase. Also, the color of the document icon may be changed according to the degree of importance. For example, the greater the severity, the darker the red color.

FIG. 30 is a flowchart showing an example of processing according to this embodiment.
In step S3002, the log of the target user is extracted. At least extract browsing logs. For example, it may be extracted from the log management table 3100 .
In step S3004, the footprint symbols are displayed according to the viewing order. Draw footstep symbols between the document icons on the map according to the order of viewing. That is, when document B is browsed after document A is browsed, a footprint symbol pointing from document A to document B is drawn between document A and document B. FIG.

Since each user can freely place documents on the map, even documents grouped by specific criteria will be placed in different places (especially if the aforementioned landmarks are not used). be). Therefore, it becomes difficult to find related documents. For example, there is a member's weekly report.
Therefore, in this embodiment, footprints are displayed according to the viewing order. Specifically, it displays the route of browsing (accessing) documents on the map by users in the group as "footprints". This makes it easy to follow your footsteps and find relevant documents.

FIG. 31 is an explanatory diagram showing an example data structure of the log management table 3100. As shown in FIG. The log management table 3100 has a log ID column 3105 , a date and time column 3110 , a user ID column 3115 and a browsed document ID column 3120 . A log management table 3100 is stored in the shared data storage module 115 . The log ID column 3105 stores information (log ID) for uniquely identifying a log (for example, viewing operation) in the present embodiment. The date and time column 3110 stores the date and time when the log was recorded. In the present embodiment, the user ID column 3115 stores information (user ID) for uniquely identifying the user who operated the log. The browsed document ID column 3120 stores the browsed document ID that is the target of the log.

FIG. 32 is an explanatory diagram showing an example of processing according to this embodiment.
A map creation button 842, a document registration button 844, and a footprint display button 3250 are displayed in the menu area 840, and these are viewed by a certain user ("Taro Fuji" in the example of FIG. 32).
The positional relationship diagram display control module 130 displays on the screen 810 a UI part (footprint display button 3250) that triggers the display of footprints. For example, map/document display area 830 displays user setting area 3260 , document icon 3272 , document icon 3274 , and document icon 3276 . UI parts are generally buttons, context menus, etc., but are not limited to these.
When the user presses 3210 the footprint display button 3250, the message/alert display area 820 displays, for example, "Please select a user." is displayed. When the triangular mark on the right end of the user setting area 3260 is selected, a list of users is displayed and a target user (also called a target user) is selected 3220 .

FIG. 33 is an explanatory diagram showing an example of processing according to this embodiment. FIG. 33 shows a footprint display example when the operation shown in the example of FIG. 32 is performed.
The message/alert display area 820 displays, for example, "Taro Fuji's footsteps".
Map/document display area 830 displays footprint 3322 between document icon 3272 and document icon 3274 and footprint 3324 between document icon 3274 and document icon 3276 . Of course, in the log management table 3100, it is recorded that "Taro Fuji" browsed the documents in this order. log) should be extracted.
In addition, it is also possible to obtain information on documents for which a specific operation (browsing, downloading, registration, etc.) was performed during a certain period of time from the operation history of the target user.
Then, the acquired document information is sorted in ascending order of operation date and time, and a line segment to the coordinates of the next accessed document is displayed on the diagram in order from the document with the oldest operation date and time.
For example, a line may be simply drawn, or images of footprints may be superimposed and displayed around the line.
In addition, the older the footprint, the higher the transparency of the footprint (the older the document, the lighter the footprint).
Additionally, selecting a document may show the target user's footsteps leading up to accessing the document.

Also, as a derivative form, when a certain document and another document are highly related, the relationship between them may be used as a "road" and coordinates may be displayed by connecting line segments. Note that an existing similar document search (such as Elastic search) may be used to search for documents with a high degree of relevance. A similarity threshold may be set, and only roads satisfying the threshold may be displayed.
Only documents that meet certain conditions may be highlighted (eg, by changing the color), or documents that do not meet the conditions may not be displayed.

When arranging documents on the map, do not duplicate document icons. Therefore, the number of documents that can be arranged in a narrow area is limited. In other words, since each user can freely place documents, there are cases where places where documents or landmarks are desired to be placed are already filled.
Therefore, in the present embodiment, a document can be arranged even in such an area. Specifically, the map is enlarged to generate a gap so that the document can be arranged.
For example, this is effective when document B is to be placed next to document A, but there is no vacant space around document A.
By moving the document, a vacant lot can be created. Therefore, the map is enlarged. Of course, the size of the document icon does not change even if the map is enlarged or reduced.
Further, if a document or the like is arranged in a gap and the figure is reduced and displayed, the information of the document or the like to be displayed increases, and the icons and document names are overlapped to impair the visibility. Therefore, in order not to impair the visibility even if there are many documents placed in the gaps, even if the display is reduced, the documents placed in the enlarged display are not displayed on the map when the map is reduced. there is
The shared data display control module 135 causes the shared data storage module 115 to store the scale (X times) at which the document was laid out, and the shared data display control module 135 keeps the scale until it reaches that scale (or above that scale). (until), so that the document icon is not displayed. Specifically, the shared data display control module 135 associates the scale of the map when the document was laid out with the document to be laid out, and causes the shared data storage module 115 to store them.
Then, when the drawing is enlarged or reduced by the user, the shared data display control module 135 compares the current scale value with the scale value when the document was laid out, and the current scale value becomes equal to or greater than the scale value when the document was laid out. Display the document icon on the map when

FIG. 34 is a flowchart showing an example of processing according to this embodiment.
In step S3402, it is determined whether or not an enlargement operation has been performed. If an enlargement operation has been performed, the process advances to step S3404. Otherwise, the process waits until an enlargement operation is performed.
In step S3404, the map is enlarged and displayed. Increase the space between the document icons according to the enlargement. In other words, the size of the document icon remains the same (state before enlargement processing), and the map can be enlarged. As a matter of course, the layout position of the document on the screen also changes according to the enlargement of the map.
In step S3406, the layout of the document with respect to the space between the document icons is received.

In step S3408, the document is laid out.
In step S3410, it is determined whether or not there has been a reduction operation, and if there has been a reduction operation, the process advances to step S3412, otherwise the process waits until there is a reduction operation.
In step S3412, the map is reduced and displayed.
In step S3414, the document arranged in step S3408 is not displayed (the document is erased from the screen). Conversely, if the magnification is the same as when the document was laid out, that document is displayed.

FIG. 35 is an explanatory diagram showing an example of processing according to this embodiment.
In the map/document display area 830, a document icon 3502, a document icon 3504, a document icon 3506, a document icon 3508, a document icon 3510, and a document icon 3512 are displayed. For example, even if the user thinks that ``I want to place the document here 3520'' between the document icon 3502 and the document icon 3504, there is no space in this state (since the document placement area is narrow), so the document is placed. It is not possible.

FIG. 36 is an explanatory diagram showing an example of processing according to this embodiment.
From the state shown in the example of FIG. 35, the user performs an enlargement operation 3610 on the map. The user then presses 3620 the document registration button 844 . When the user selects between document icon 3502 and document icon 3504 and performs document registration operation 3630, pin 3640 is displayed at that location.

FIG. 37 is an explanatory diagram showing an example of processing according to this embodiment.
37 shows a display example when the operation shown in the example of FIG. 36 is performed. A document icon 3712 is displayed 3710 between the document icons 3502 and 3504 .

FIG. 38 is an explanatory diagram showing an example of processing according to this embodiment.
FIG. 37 shows an example of a case where the map is reduced and displayed after the display shown in the example of FIG. 37 is performed. That is, the document icon 3712 is not displayed in the same manner as the display shown in the example of FIG. 35, which is the state before document registration.
However, when the enlargement ratio becomes equal to or higher than the magnification shown in the example of FIG. 36 (FIG. 37) from this state, the document icon 3712 is displayed between the document icons 3502 and 3504. FIG.

The hardware configuration of the computer on which the program of this embodiment is executed is, as shown in FIG. 39, 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 3901 is used as a processing unit (calculating unit), and a RAM 3902, ROM 3903, and HDD 3904 are used as storage devices. As the HDD 3904, for example, an HDD (Hard Disk Drive), a flash memory SSD (Solid State Drive), or the like may be used. A CPU 3901 that executes programs such as the instruction reception module 105, the data management module 120, the display control module 125, the positional relationship diagram display control module 130, the shared data display control module 135, and the notification module 140, and the RAM 3902 that stores the programs and data. , a ROM 3903 storing programs and the like for starting up the computer, an HDD 3904 as an auxiliary storage device having functions as the positional relationship diagram storage module 110, the shared data storage module 115, etc., a keyboard, a mouse, and a touch panel. A reception device 3906 that receives data based on the user's operation (including motion, voice, line of sight, etc.) on a screen, microphone, camera (including line-of-sight detection camera, etc.), and an output device such as a CRT, liquid crystal display, speaker, etc. 3905, a communication line interface 3907 for connecting to a communication network such as a network interface card, and a bus 3908 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. 39 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, an application specific integrated circuit (ASIC), a reconfigurable integrated circuit (field-programmable gate array: FPGA), etc.). A part of the modules may be in an external system and connected via a communication line, or a plurality of systems shown in FIG. 39 may be connected via a communication line and 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.

DESCRIPTION OF SYMBOLS 100... Information processing apparatus 105... Instruction receiving module 110... Positional relationship diagram storage module 115... Shared data storage module 120... Data management module 125... Display control module 130... Positional relationship diagram display control module 135... Shared data display control module 140... Notification module 210 User terminal 250 Data management device 290 Communication line

Claims (8)

a first display control means for controlling to display on the screen a diagram showing a positional relationship and classified by region;
receiving means for receiving, for each region, an instruction to display an image representing data in the region on the map;
a second display control means for controlling to display the image on the area;
with
The first display control means displays a map as the diagram based on the addresses or locations of the members of the group to which the operator belongs.
Data management device. In the diagram, the position to display the image can be further specified within the specified area,
The data management device according to claim 1. Disabling designation as a position to display the image outside the designated area,
3. The data management device according to claim 2. The first display control means displays a map including the member's address,
The data management device according to claim 1. The first display control means displays a map of a route from the address of the member to the commuting destination,
The data management device according to claim 1. The first display control means displays a map including the address of the member's workplace,
The data management device according to claim 1. The first display control means displays a map of a route from the nearest station to the workplace of the member,
The data management device according to claim 1. the computer,
a first display control means for controlling to display on the screen a diagram showing a positional relationship and classified by region;
receiving means for receiving, for each region, an instruction to display an image representing data in the region on the map;
functioning as a second display control means for controlling to display the image on the area ;
The first display control means displays a map as the diagram based on the addresses or locations of the members of the group to which the operator belongs.
Data management program.

Images