JP7437046B2 - Year history production method, program, year history production device, and year history production system - Google Patents

Description

The present disclosure relates to a year history production method, a program, a year history production device, and a year history production system, and particularly relates to a year history production method, a program, a year history production device, and a year history production system for producing a year history composed of a plurality of articles.

As a method for creating a year history using a computer, for example, the year history production system disclosed in Patent Document 1 (Japanese Unexamined Patent Publication No. 2001-290913) collects basic materials for creating a year history and creates article data based on the collected materials. and register it in the article database, extract the necessary information from the article database and create a chronology, set era divisions based on the basic materials and the chronology, and create a temporary table of contents for the chronological text. For each item in the provisional table of contents, necessary information is extracted from the article database and edited in the style of the main text manuscript, a visual manuscript corresponding to the main text manuscript is created, and the contents of the main text manuscript and visual manuscript are reviewed. Then, the text manuscript and visual manuscript are compared to organize and edit the manuscript, create a manuscript for the material edition and chronology, and create a chronological history by designing and laying out the whole.

Japanese Patent Application Publication No. 2001-290913

When creating a chronology, there is a desire to create a chronology that includes a wealth of articles with appropriate content for the chronology. However, in Patent Document 1, only the person in charge of the year history collects basic materials from each department within the company and registers them in the article database, so the articles that make up the year history are limited to the scope of collection by the person in charge of the year history. It's difficult to respond.

Therefore, an object of the present disclosure is to provide a method, program, device, and system for creating a year history that can create a year history that is rich in articles.

The present disclosure provides a chronological history production method performed by an information processing device. The information processing device includes a processor and a storage unit that stores a plurality of article data forming a year history.

The year history production method includes a step in which the processor outputs article data constituting the year history on a display so that it can be viewed, a step in which the processor accepts an article data posting operation from a viewer who has posting authority, and a step in which the processor edits the article data. a step of accepting, from an authorized editor, an editing operation of a year history using article data posted by a posting operation; and a processor including the article data posted according to the accepted editing operation. and a step of executing a year history editing process.

Preferably, the chronology production method further includes a step of determining whether the viewer has posting authority based on the viewer's attributes.

Preferably, the chronological history includes the chronological history of an organization made up of a plurality of members, and the viewer's attributes include information regarding the viewer as a member of the organization to which the viewer belongs.

Preferably, the information regarding the viewer as a member of the organization includes information indicating the division or division of the organization to which the viewer belongs.

Preferably, the information regarding the viewer as a member of the organization includes information indicating the viewer's position in the organization.

Preferably, the chronological history stored in the storage unit includes a plurality of types of chronological history, and the various chronological histories include an annual history for each number of years that have passed since the organization was established, or a chronological history of a department or division of the organization.

Preferably, the plurality of article data stored in the storage unit include article data shared between different types of chronology.

Preferably, the article data includes document data and image data or audio data including video data related to the document data.

Preferably, the year history has a plurality of layers in which one or more article data are arranged in each layer, and the article data is associated with a search tag for searching the article data, and the article data is associated with a search tag for searching the article data. The associated tag indicates the layer in which the article data is placed among the multiple layers.

Preferably, the one or more pieces of article data arranged in each hierarchy have an order in which they are displayed on the display, and the tag associated with the article data corresponds to the hierarchy in which the article data is arranged among the plurality of hierarchies. It shows the order of the article data in the order of one or more article data arranged in the hierarchy.

Preferably, the step of accepting the posting operation includes the step of the processor outputting a GUI that includes a viewing object in which the article data is visualized so that the article data can be viewed, and a posting object that accepts the posting operation, and the step of accepting the editing operation includes , the processor outputs a GUI including an article object for visualizing article data posted by a posting operation received via the posting object, and an editing object for accepting an editing operation by an editor.

In another aspect of the present disclosure, a chronological history production program for realizing the above-described chronological history production method when executed by an information processing device is provided.

In another aspect of the present disclosure, a chronology production device for executing the above-described chronology production method is provided.

In another aspect of the present disclosure, a year history production system includes a server and a terminal that communicates with the server via a network, and the server includes a storage means for storing a plurality of article data forming a year history, and a year history production system. means for transmitting screen information to a terminal to enable viewing of the constituent article data; means for editing the chronological history so as to include posted article data according to the chronological history editing operation information received from the terminal; has. The terminal includes an operating means for accepting user operations on the terminal, a means for displaying a screen based on the screen information received from the server on a display of the terminal, and a means for receiving articles from a user who has posting authority via the operating means. A means for accepting a data posting operation, a means for transmitting posted article data to a server, a means for accepting a chronological history editing operation from a user with editing authority via an operation means, and a chronological history editing operation that has been accepted. and means for transmitting operation information to the server.

According to the present disclosure, a posting operation for article data is accepted from a viewer who has posting authority, and a year history is edited to include the article data based on the accepted posting operation. Therefore, articles posted by viewers with posting authority are expected to have appropriate content, and articles that make up the year's history can be collected not only from editors but also from viewers. It is possible to easily create a chronological history that includes a wealth of articles.

FIG. 1 is a network configuration diagram according to the present embodiment. FIG. 2 is a diagram schematically showing a functional configuration of a year history production provided by the server according to the present embodiment. FIG. 2 is a diagram schematically showing the structure of historical data according to the present embodiment. FIG. 2 is a diagram schematically showing the structure of article data according to the present embodiment. FIG. 2 is a diagram schematically showing an example of a year history production sequence according to the present embodiment. 12 is a flowchart illustrating an example of processing of comments regarding article data by a viewer according to the present embodiment. It is a figure showing an example of the screen of the browsing Web page concerning this embodiment. FIG. 2 is a diagram schematically showing the relationship between the year history, articles, and users according to the present embodiment. It is a figure showing an example of user data concerning this embodiment. It is a diagram showing an example of a home screen of the chronological history production system according to the present embodiment. FIG. 2 is a diagram showing an example of an article posting screen of the annual history production system according to the present embodiment. FIG. 2 is a diagram showing an example of an editing screen of the chronological history production system according to the present embodiment. FIG. 7 is a diagram showing another example of the editing screen of the chronological history production system according to the present embodiment. It is a figure showing an example of a my page screen concerning this embodiment.

Each embodiment will be described below with reference to the drawings. In the following description, the same parts and components are given the same reference numerals. Their names and functions are also the same. Therefore, these descriptions will not be repeated. First, terms used in this embodiment will be explained.

“History” is information representing the history of the organization, and includes a plurality of article data. The article data may include text data, image (video, still image) data related to the text data, other text data, data such as pictures or tables, and audio data.

An "organization" corresponds to a group consisting of multiple members who are related to each other. Organizations may include, but are not limited to, businesses, schools, local governments, and the like.

"Users" include users of the history, including members and non-members of the organization, who can view or edit the history. More specifically, there are users who have the authority to post article data (hereinafter referred to as posting authority), users who have the authority to edit the history using article data (hereinafter referred to as editing authority), and users who have the authority to post article data (hereinafter referred to as editing authority). This includes users who have both editing privileges and users who can only view. Hereinafter, a user who views the history will be referred to as a "browser," and a user who has editing authority will be referred to as an "editor."

In this embodiment, a scene in which, for example, a chronological history of a company is produced as the chronological history of an organization will be described as an example, but the embodiment can be similarly applied to other types of organizations.

<A. Configuration>
FIG. 1 is a network configuration diagram according to this embodiment. Although the year history production system according to the present embodiment is realized using a platform provided using a cloud-type server, the server is not limited to a cloud-type server, and may be an on-premises server.

Referring to FIG. 1, the network configuration includes a server 300, which is an example of a cloud-based information processing device, and terminals 100 and 200, which correspond to information processing devices such as computers. Terminal 100 and terminal 200 each communicate with server 300 on the cloud via various communication networks such as networks NW1 and NW2 including an intranetwork. Terminals 100 and 200 may each include a stationary desktop computer, a portable laptop computer, a tablet computer, a smartphone, or the like. In this embodiment, the terminal 100 represents a computer that can be operated by a viewer among the users, and the terminal 200 represents a computer that can be operated by an editor among the users. Additionally, viewers and editors can also share the same terminal through system login management or authentication functions.

The server 300 includes a CPU (Central Processing Unit) 301, a memory 302 including a ROM (Read Only Memory) and a RAM (Random Access Memory), a display 303, and an operation unit 304 such as a keyboard and a mouse for accepting user operations on the server 300. , a communication I/F (abbreviation for Interface) 306 for communicating with the terminals 100 and 200, an HDD (Hard Disk Drive) 307 which is an example of a non-volatile storage device, and a memory I/F 309.

An external storage medium 308 is detachably attached to the memory I/F 309, and data and programs stored in the attached storage medium 308 are read and written under the control of the CPU 301. The storage medium 308 includes, for example, a CD-ROM (Compact Disc Read-Only Memory), a memory card, and the like. The display 303 and the operation unit 304 may be provided as a touch panel 305 configured integrally with them.

Referring to FIG. 1, a terminal 100 includes a processor 101 such as a CPU, a memory 102 including a volatile memory such as a ROM or a RAM, and a non-volatile memory such as an HDD, a display 103, a keyboard for accepting user operations, It includes an operation unit 104 such as a mouse, a communication circuit 106 for communicating via the network NW2, and a memory I/F 109. The display 103 and the operation unit 104 may be provided as an integrated touch panel 105.

A storage medium 110 such as a memory card is removably attached to the memory I/F 109, and data and programs stored in the attached storage medium 110 are read and written under the control of the processor 101. The storage medium attached to the memory I/F 109 is not limited to a memory card or the like, and may be, for example, a CD-ROM.

Referring to FIG. 1, terminal 200 includes a processor 201 such as a CPU, a memory 202 including volatile memory such as ROM or RAM, and non-volatile memory such as HDD, a display 203, a keyboard for accepting user operations, It includes an operation unit 204 such as a mouse, a communication circuit 206 for communicating via the network NW1, and a memory I/F 209. The display 203 and the operation unit 204 may be provided as an integrated touch panel 205.

A storage medium 210 such as an external memory card is removably attached to the memory I/F 209, and data and programs stored in the attached storage medium 210 are read and written under the control of the processor 201. The storage medium attached to the memory I/F 209 is not limited to a memory card, and may be, for example, a CD-ROM.

The server 300 and the terminals 100, 200 may have an audio device such as a speaker capable of outputting audio, or a printer or printer driver that prints data such as history and articles.

<B. Functional configuration of server 300>
FIG. 2 is a diagram schematically showing the functional configuration of the annual history production provided by the server 300 according to the present embodiment. In this embodiment, the year history production function is realized by CPU 301 of server 300 executing application program 326 on HDD 307. Note that the method for realizing the function is not limited to a program, and may be realized by a combination of a program and a circuit.

Referring to FIG. 2, as the above-mentioned functions, the CPU 301 functions as a viewing web page management unit 311, an editing web page management unit 312, and a user management unit 313 that manages users to perform editing processing. It includes an editing section 317 that creates a chronological history, and a comment management section 316 that manages user comments regarding the chronological history. The editing section 317 includes a chronological history management section 314 that edits chronological data and manages the chronological history data on the HDD 307, and an article management section 315 that edits article data constituting the chronological history and manages the article data on the HDD 307. In relation to each of these parts, the HDD 307 stores multiple types of historical data 320, a plurality of article data 321 constituting the historical data 320, comment data 323 indicating users' evaluations of articles, and manages system users. , user management data 324 for each user, my page data 325 in which information for each user is registered, and an application program 326.

The viewing web page management unit 311, the editing web page management unit 312, the user management unit 313, the editing unit 317, and the comment management unit 316 are objects generated when the application program 326 is executed by the CPU 301, for example. It can be implemented as a module.

(b1. Composition of annual history data 320)
FIG. 3 is a diagram schematically showing the structure of year history data 320 according to the present embodiment. The historical data 320 has multiple hierarchies in which one or more article data 321 are arranged in each hierarchy. Referring to FIG. 3B, the plurality of hierarchies include first to fifth hierarchies identified by hierarchy IDs (01 to 05). Note that the number of layers is not limited to five.

Referring to FIG. 3A, year history data 320 includes a header 327 and a data group. For the year history, the header 327 includes a year history ID for identifying the year history, a year history name which is a title, and an update indicating the time when the year history data 320 of the year history was updated (changed) by the editing process executed by the editing unit 317. Including year, month, and date. The data group includes a hierarchy setting flag 40 linked to a header 327 and data of a plurality of hierarchy settings. The plurality of hierarchy setting data indicates the hierarchy in which each of the plurality of article data 321 constituting the annual history data 320 is arranged. More specifically, each article data 321 has five hierarchies shown in FIG. 44 and the historical hierarchy 5 setting 45, and the text of the article data 321 placed in the hierarchy is indicated by, for example, "layer name".

Referring to (A) in FIG. 3, multiple types of annual history data 320 include a "general 50-year history" that is an anniversary history consisting of articles for the general public including company members and non-members, and a "general 50-year history" of the company. It includes three types: ``50 Year History for Executives'', which is an anniversary history consisting of articles for executives, and ``Digest 50 Year History'', which is an anniversary history consisting of articles in a digest version of the company's history.

The types of chronology data 320 are not limited to these, but include anniversaries for each number of years since the company was established, chronological histories of company departments or divisions (general affairs, accounting, human resources, sales, etc.), and combinations thereof. It may also be the year history of .

Referring to FIG. 3, for example, the year history data 320 identified by the header 327 having the year history ID "0001" is named "General 50 Year History" and is linked to the year history ID "0001". The hierarchy setting flag 40 indicates that the year history data 320 is composed of five hierarchies. More specifically, the article data 321 constituting five hierarchies includes article data 321 identified by the layer 1 identification code (0001 01 0001) of the historical layer 1 setting 41, and layer 2 identification of the historical layer 2 setting 42. The article data 321 identified by the code (0001 02 003 0001), the article data 321 identified by the layer 3 identification code (0001 03 003 001 001) of the chronological layer 3 setting 43, and the layer 4 of the chronological layer 4 setting 44 It includes article data 321 identified by the identification code (0001 04 003 001 001 001) and article data 321 identified by the layer 5 identification code (0001 05 003 001 001 001 001) of the year history layer 5 setting 45.

The article data 321 constituting the general 50-year history data 320 is arranged in the first to fifth layers, but the number of layers in the year history data 320 is not limited to this. According to the hierarchy setting flag 40, for example, the 50th anniversary history for executives has four hierarchies, the first to fourth hierarchies, and the digest 50th anniversary history has three hierarchies, the first to third hierarchies. Note that the first to fifth layers are consistent with the divisions that make up the history, such as chapters, sections, and items.

(b2. Structure of article data 321)
FIG. 4 is a diagram schematically showing the structure of article data 321 according to this embodiment. Referring to FIG. 4, article data 321 includes data 151-153. The data 151 includes the posting ID that identifies the article data 321, the title of the posted article, the text data of the posted article, the date and time when it was first registered as an article constituting the year history data 320, the poster (user) ID and name, and the article. It includes the target date indicating the date and time of the event (event), the update date and time of the article, the updater ID of the user who updated the article, and the updater name. The data 152 includes data 154 corresponding to a search tag for searching the article data 321.

For example, since the data 154 in FIG. 4 indicates (0001 05 003 001 001 001 001 001) as the year history selection 1 display code, the article data 321 is the fifth layer of the year history data 320 whose year history ID is “0001”. In the order showing the arrangement of one or more article data 321 identified by the identification code (0001 05 003 001 001 001 001), it is indicated that it is located in the 0001st order. That is, when one or more article data 321 arranged in the fifth layer of the year history data 320 whose year history ID is "0001" is displayed on a display etc., the article data 321 is The first item to be searched and displayed (output) is specified.

In this way, the data 154 as a tag associated with the article data 321 includes the layer in which the article data 321 is placed among the multiple layers of the historical data 320, and one or more article data items placed in the layer. 321 indicates the order of the article data 321 in the output order (search order).

In this embodiment, article data 321 can be shared between different types of chronicles. For example, when the article data 321 is shared between different types of chronology, the data 152 includes data 154 about the other type of chronology data 320, chronology selection 2 display code, chronology selection 3 display code, chronology selection Included as 4 display code and year history selection 5 display code. Data 153 is when the corresponding article data 321 is displayed in a scroll view for each of the year history selection 1 display code, year history selection 2 display code, year history selection 3 display code, year history selection 4 display code, and year history selection 5 display code. , a flag indicating whether or not to display the post title of the data 151 is shown.

<C. Annual history production sequence＞
FIG. 5 is a diagram schematically showing an example of the year history production sequence according to the present embodiment. FIG. 5 mainly shows the processing performed by the server 300 as an annual history production sequence using the cloud platform. As the processing executed by the server 300, the left side of FIG. 5 shows the processing based on the user operation accepted via the viewer's operation unit 104, and the center shows the process based on the user operation accepted via the editor's operation unit 204. The right side shows the transition of data in the HDD 307.

Editing authority is set for the editor by the user management unit 313 based on the user management data 324 . When the user operates the terminal 200 to log in to the chronicle production system, the user management unit 313 compares the login data with the user management data 324, and based on the result of the verification, determines whether the user has editing authority. . The editing web page management unit 312 provides the editing web page only to the editor, who is a user who has been authenticated for editing authority, and the editing unit 317 executes editing processing based on the user operation received from the editor.

Furthermore, the user management unit 313 sets viewing authority or article posting authority for the user based on the user management data 324 . When the user operates the terminal 100 to log in to the annual history production system, the user management unit 313 determines from the login data whether the user has permission to view or post the annual history, and the viewing web page management unit 311 The chronological history viewing web page is provided only to viewers who have been authenticated for viewing authority, and the editorial department 317 accepts posting of article data only from viewers who have been authenticated for posting authority. In FIG. 5, it is assumed that the user operating terminal 100 is a viewer, and the user operating terminal 200 is an editor.

Referring to FIG. 5, editing unit 317 of server 300 creates hierarchically structured base data of chronological data 320 (step S0). Article data 321 that will be posted after that will be placed in one of the layers of this hierarchical structure.

The editor operates the terminal 200, and the viewer operates the terminal 100 to log into the chronicle production system on the cloud platform.

The editing web page management unit 312 creates an editing web page including the article data 321 posted and stored in the HDD 307 and sends it to the terminal 200, and the terminal 200 receives the web page and displays the screen shown by the web page. A screen based on the information is displayed on the display 203.

The editor processes the historical data 320 or article data 321 on the terminal 200 via the operation unit 204 based on the historical data 320 or article data 321 displayed on the editing screen displayed on the display 203. Enter the user operation to do so.

The chronological history management unit 314 receives the editor's operation transmitted from the terminal 200, and creates the chronological history data 320 based on the received editor's operation (step S1). For example, the hierarchy of the year history data 320 is set. Based on the editor's operations, the year history management unit 314 deletes the year history data 320 (step S2), corrects the year history data 320 (step S3), manages the hierarchy of the year history data 320 (step S4), and uses each year history data 320. Authority management (step S5) and batch import of article data 321 into historical data 320 (step S6) are performed. The processing contents by the chronology management unit 314 are reflected in the chronology data 320 of the HDD 307 (step S7).

Further, the article management unit 315 receives an editor's operation transmitted from the terminal 200, and creates, modifies, deletes, or batch imports the article data 321 based on the received editor's operation (steps S10, S11, S12, S13). The processing content by the article management unit 315 is reflected in the article data 321 of the HDD 307 (step S14).

The article management unit 315 sets the article data 321 to a locked state or an unlocked state based on a user operation (steps S15, S16, S17). For example, the article data 321 is set in a locked state to prevent unintentional changes or modifications after editing is completed, and is set in an unlocked state during editing.

The editing unit 317 manages the configuration of the historical data 320 by arranging locked article data 321 in each layer of the historical data 320 based on the user operation received from the terminal 200 (step S18). The editing unit 317 sets the year history data 320 to a locked state or an unlocked state based on the user's operation (steps S20, S21). The annual history data 320 is set to a locked state when editing is completed, such as by arranging article data 321 in each layer.

When the viewer operates the terminal 100, the user management unit 313 determines whether the viewer has posting authority based on the user management data 324 in accordance with the operation (step S30). Here, as described above, it is determined that the viewer has posting authority.

When the terminal 100 receives an operation requesting viewing historical data from the user, the terminal 100 transmits the operation details to the server 300. Upon receiving a viewing request operation from the terminal 100 (step S31), the viewing web page management unit 311 creates a web page for visually displaying the locked year history data 320, and transmits it to the terminal 100 (step S31). S32). The terminal 100 displays a screen on the display 103 based on the screen information indicated by the web page of the historical data 320 received from the server 300.

The viewer performs an operation to post the article data 321 to the historical data 320 via the operation unit 104 of the terminal 100. The editing web page management unit 312 creates an editing web page for visually outputting the posted content based on the posting operation received from the terminal 100 (step S33), and transmits it to the terminal 200. The posted content corresponds to candidate article data that is a candidate for the article data 321. The candidate article data includes, for example, media related to the viewed article (data such as images (videos, still images), sentences, pictures or tables, audio, etc.). Along with the posted content, viewers may also submit evaluations (comments, reactions) regarding the article.

The editing web page management unit 312 creates a web page for visually displaying the candidate article data received from the viewer's terminal 100, and transmits it to the editor's terminal 200.

The terminal 200 displays a screen based on the screen information indicated by the web page received from the server 300 on the display 203 and transmits the contents of the editor's operation received via the operation unit 204 to the server 300.

When the article management unit 315 determines that the candidate article data has been approved by the editor as article data 321 based on the editor's operation content received from the terminal 200, the article management unit 315 stores the approved candidate article data as the article data 321 on the HDD 307. (steps S22, S23). The article management unit 315 sends a message to the viewer who posted the candidate article data notifying him of approval or rejection (not approved) (step S23a). At this time, the comment received from the viewer may also be judged to be approved or rejected, and a message notifying the user may be sent.

The comment management unit 316 registers the candidate article data and the comment as well as a notification of approval or rejection in the viewer's my page data 325. By viewing the my page data 325, the viewer can check the posted content, comments, and the approval or rejection determination results.

The approved candidate article data described above is handled as article data 321 to be edited in steps S10 to S13.

Further, in the present embodiment, the annual history production system can also perform processing (steps S33, S35) of managing a glossary in which unique terms within the company are registered based on user operations from the terminal 100.

The chronology production system further performs a process of extracting media image or audio data related to the article data 321 and outputting the image or audio data for viewing or viewing on the viewer's terminal 100 (step S36); The process includes a process of visually outputting analysis data indicating a ranking view on the terminal 100 (step S37) and a process of managing the viewer's my page (steps S38, S39).

The processing related to viewing glossary data, media data, and analysis data may include processing for determining that the viewer is authorized to access these data.

(c1. Specific example of comment processing)
FIG. 6 is a flowchart illustrating an example of processing of comments regarding article data by a viewer according to the present embodiment. FIG. 7 is a diagram showing an example of a screen of a viewing web page according to the present embodiment. The process in FIG. 6 specifically shows the process for comments in steps S33, S22, S23, and S23a in FIG. Referring to FIG. 7, the screen displayed on the display 103 of the terminal 100 based on the browsing web page includes an object OB1 for visually displaying the article data 321 constituting the historical data 320, and an object OB1 for visually displaying the article data 321 that constitutes the historical data 320. This corresponds to a GUI (Graphical User Interface) consisting of an object OB2 for accepting operations for posting.

The object OB1 includes text data and image data objects of the article data 321. The GUI further includes an object OB3 that visually shows comments posted by the viewer regarding the object OB1.

The viewer views the historical data 320 (article data 321) on the GUI of FIG. 7, operates the object OB2 via the operation unit 104, and inputs a comment regarding the article data 321 indicated by the object OB1 (step T1). The input comment is not immediately reflected in the article data 321, but is in a status of waiting for approval (step T2). The editor determines whether or not to approve the posted comment (step T3), and if it is approved (approved in step T4), the comment is set as a comment for the article data 321, and is also set as an object in the GUI. If a comment that can be output visually as OB3 (step T5) is rejected without being approved (rejected in step T4), the comment management unit 316 displays a message that the comment has been rejected in the viewer's my page data 325. is registered and managed (step T6). Further, if approved, the approval may be registered in the my page data 325.

(c2. Relationship with history, articles, and users)
FIG. 8 is a diagram schematically showing the relationship between the year history, articles, and users according to the present embodiment. The multiple article data 321 (articles A, B, C, D, M, S) are compiled by the editorial department 317 into multiple types of chronological data 320 (30-year history for general employees, 30-year history for managers, and 30-year history for executives). are placed in one of the hierarchies. In Figure 8, article data 321 for articles A, B, C, and D are shared among three types of chronology (30-year history for general employees, 30-year history for managers, and 30-year history for executives), and article data 321 for article M The article data 321 is shared between two types of chronology (30-year history for managers and 30-year history for executives), and the article data 321 of article S is used to configure only the 30-year history for executives.

The user management data 324 includes, for each user, an account, an attribute of the user, and a type of history for which the user with the attribute has posting authority. The user management unit 313 acquires an account from the combination of user ID and password accepted at the time of login, collates the account with the user management data 324, and determines the account based on the verification result. For example, if the user management unit 313 determines that the acquired account indicates a general employee account, it determines that the user has posting authority only for the 30-year history for general employees, and the acquired account indicates a managerial account. If it is determined that the user has posting authority for the 30-year history for general employees and the 30-year history for managers, and if it is determined that the acquired account indicates an executive account, the user will be able to post the 30-year history for general employees and the 30-year history for managers. It is determined that he has the authority to post the annual history and 30-year history for executives.

In this way, the user management unit 313 determines whether or not the viewer has posting authority for the year history based on the attributes acquired based on the user management data 324, that is, information regarding the viewer as a member of the organization (company) to which the viewer belongs. can do. More specifically, the presence or absence of posting authority can be determined based on the viewer's position in the organization (regular employee, manager, executive, etc.) as an attribute.

The user management unit 313 also provides information indicating the department or department of the organization to which the viewer belongs (for example, accounting department, sales department, human resources department, development department, research department, etc.) or information indicating the organization or department to which the viewer belongs, as an attribute. Based on the length of the period (one year or more, less than one year, etc.), it is possible to determine whether or not the user has posting authority. Moreover, it is not limited to the posting authority, and whether or not the user has the viewing authority may be similarly determined based on the user's attributes.

FIG. 9 is a diagram showing an example of user data 91 according to this embodiment. User management data 324 includes user data 91 for each user. Referring to FIG. 9, user data 91 includes the user's identifier (member ID and member name), attributes (department, position identifier, etc.), and the update date of the data. The update date indicates that the user data 91 represents the latest attributes of the user. According to the user data 91 in FIG. 9, it is shown that the user is an executive and belongs to a plurality of departments indicated by affiliations 1, 2, and 3. Based on this, for example, it can be determined that the user has viewing authority and posting authority for the 30-year history for general employees and the 30-year history for executives.

In the present embodiment, a user who is determined to have viewing authority for a chronological history is also determined to have an article posting authority for the chronological history, but the method for determining authority is not limited to this. For example, it may be determined that the user only has viewing authority based on the user's attributes. For example, in the case of a public history that is made available for viewing by users outside the company who are not members of the company, it is determined that these users only have viewing authority.

<D. Display screen example>
In this embodiment, examples of screens displayed on the displays of the terminals 100 and 200 will be described.

(d1. Home screen)
FIG. 10 is a diagram showing an example of a home screen of the year history production system according to the present embodiment. In FIG. 10, the home screen is displayed on the display 203 of the terminal 200, for example, but the home screen can also be displayed on the display 103 of the terminal 100. The home screen is created as a web page by the CPU 301 of the server 300 and sent to the terminals 100, 200, and the terminals 100, 200 display the screen shown in FIG. 10 on their displays based on the screen information of the web page received from the server 300. .

Referring to FIG. 10, the home screen includes an object 70 that accepts the user's article data posting operation, a tab 71 indicating that it is a home screen, and a tab 72 that is displayed according to the authority of the user who has logged in at the terminal 100. , a tab 73 showing links to members (other users), and a tab 74 operated for various settings. The tabs 72 include a tab that is operated to view the historical data 320, a tab that is operated to refer to the in-house glossary, and a tab that can be operated by a user with editing authority.

The home screen further includes an object 75 that accepts a user operation to search for posted articles, and an object 75a that outputs article data 321 recently posted for each year of history in a viewable manner. An object 76 that displays various media in a viewable manner, an object 77 that visualizes and displays comments from other users on articles posted by the user who is logged in, and objects 78 and 79 that visualize and display information related to rankings. include.

Object 75 is operated to search article data 321. The information input based on the search operation is sent to the server 300, and the server 300 searches the HDD 307 for article data 321 having data 154 (search tag) indicating a value that matches the information based on the search operation. , to be displayed on the display 103 of the terminal 100.

An object 78 indicates information on which a plurality of pieces of historical data 320 are ranked based on the number of times the article has been viewed, and an object 79 indicates information on which a plurality of pieces of article data 321 are ranked based on the number of times the article has been viewed. When the terminal 100 receives a user operation for the object 75, it executes a command corresponding to the object 75 incorporated in the web page, and displays a child screen (not shown) on the display 103 that accepts the user operation to narrow down the search conditions. Display.

(d2. Article submission screen)
FIG. 11 is a diagram showing an example of an article posting screen of the annual history production system according to the present embodiment. When an object 70 on the home screen (FIG. 10) displayed on the terminal 100 is operated, the browsing web page management unit 311 of the server 300 displays the article posting screen based on the user operation received from the terminal 100. A page is created and sent to the terminal 100. The terminal 100 displays the article posting screen of FIG. 11 on the display 103 based on the screen information indicated by the web page received from the server 300.

Referring to FIG. 11, the article posting screen includes various objects that accept posting operations from the user. More specifically, the article submission screen includes a text box 80 for inputting the title of the article, a box 86 for inputting the tag given to the article, and a right pane 88R and 88R for inputting the article text. and a left pane 88L.

The left pane 88L includes a text box 81 for inputting main text, a tab 82 for accepting operations for selecting files such as images to be posted in the article, and a tab 84 for accepting operations for specifying the post destination of the article. It also includes a tab 85 that accepts an input operation for the year, month, and day when the event indicated by the article occurred. The right pane 88R includes an area for displaying a preview of the content input in the left pane 88L, and a button 89 operated to post the article input in the left pane 88L. When the button 89 is operated, the CPU 101 transfers the article data based on the content input in the left pane 88L to the server 300, and the server 300 transfers the article data (corresponding to candidate article data) received from the terminal 100 to the HDD 307. Store in.

Tab 84 displays a list of created and unlocked historical data, and selects the type of historical history to which you want to add an article, and the location (hierarchy (chapter, section, display) and display order in that hierarchy) in which you want to add the article. Accepts the specified operation. In FIG. 11, two types of chronology (50-year history for public use and 50-year history for internal use) are designated as posting destinations.

In this manner, the article posting screen of FIG. 11 constitutes a GUI that includes an object in which article data in the right pane 88R is visualized so that it can be viewed, and an object of the button 89 that accepts a posting operation.

(d3. Edit screen - Article search)
FIG. 12 is a diagram showing an example of an editing screen of the year history production system according to the present embodiment. The editing screen is displayed on the terminal 200 of a user (editor) who has editing authority. For example, when the "editing room" tab of tab 72 in FIG. 10 is operated, the screen on the display 203 changes to the screen shown in FIG. The screen changes to the screen shown in FIG.

Referring to FIG. 12, the editing screen includes a menu 193 which is a search object showing narrowing options for narrowing down and searching for article data 321 to be edited from among a plurality of article data 321 stored in HDD 307; , and narrowed search results based on the options checked in menu 193. For example, in FIG. 12, as a narrowed search result, a mark 191 or mark 192 indicating whether each of the one or more searched article data 321 is unapproved or approved by the editor, and the posting of the article data 321 Post destination information 194 indicating the destination. The posting destination information 194 is the posting destination specified in the tab 84 of FIG. 11, and includes the type of chronological history, the chapter of the chronological history, the section in the chapter, and the display order in the hierarchy of the section.

In the editing screen of FIG. 12, when the editor determines that the posted article data 321 with the mark 191 (unapproved) is appropriate content for composing a year history, the editor operates the mark 197, i.e. The article data 321 is clicked to be selected for editing. The unapproved article data 321 marked with the mark 191 in FIG. 12 is selected by the editor as the article data 321 constituting a year history among the article data that was posted on the article submission screen in FIG. 11 and stored in the HDD 307, for example. This corresponds to something that has not been approved (for example, candidate article data).

(d4. Edit screen - configuration management)
FIG. 13 is a diagram showing another example of the editing screen of the annual history production system according to the present embodiment. In the editing screen of FIG. 13, a web page created by the editing web page management unit 312 is transmitted to the terminal 200. Terminal 200 displays the screen of FIG. 13 on display 203 based on the screen information indicated by the web page received from server 300. On the screen of FIG. 13, the editor uses the operation unit 204 to, for example, change the clicked article data 321 indicated by the mark 97 of FIG. , and place the article data 321. The server 300 receives the operation from the terminal 200, and the editing unit 317 edits the historical data 320 based on the received operation.

Referring to FIG. 13, the editing screen includes a button 60 that is operated to arrange and correct year history data 320 with article data 321, a button 61 that is operated to finish editing, and a button 61 that is operated to finish editing. and a configuration area that displays a schematic configuration of the year history data 320. The configuration area shows the structure of the year history data 320 made up of layers (chapter 50, section 51, subsection 52, and subheading 53). In the composition area, the editor drags the article data 321 with the mouse mark 62 via the operation unit 204 while referring to the destination information 194 (FIG. 12) corresponding to the article data 321 posted. Arrange in hierarchy. When the editor arranges the posted article data 321 in the configuration area and operates the button 60, the chronology management unit 314 arranges the chronology data 320 in the HDD 307 into articles in its hierarchical structure based on the operation content accepted in the configuration area. The data 321 is updated to be added.

In this way, the editing screen of FIG. 13 is an article object that visualizes and displays article data posted by the viewer's (user) posting operation received via the posting object of FIG. 11 near the mouse mark 62. and an editing object (mouse mark 62) that accepts an editor's operation. The editor can intuitively perform editing operations by moving the article data 321 between layers by dragging. Further, the editing operation is not limited to adding posted article data 321. For example, the editing operation may include an operation of moving existing article data 321 in each layer in the configuration area to another layer by a drag operation, or an operation of exchanging article data 321 between layers.

(d5. My page screen)
FIG. 14 is a diagram showing an example of a my page screen according to this embodiment. The server 300 creates a web page based on the my page data 325 for each user and sends it to the terminal 100. Terminal 100 displays the screen of FIG. 14 on display 103 based on the screen information of the web page received from server 300.

Referring to FIG. 14, the user's My Page screen includes a tab 98 that shows the number of viewed and unviewed pages of the historical data 320 that the user has permission to view, and article data 321 posted by the user that is narrowed down from the HDD 307. It includes a tab 99 for setting narrowing conditions for searching, and an area 96 for displaying a list of article data 321 searched according to the narrowing conditions set in the tab 99.

When the user clicks on the approved article data 321 in the area 96 using the mouse mark 97, the user can modify the article data 321 and post it again. Furthermore, by clicking on the unapproved article data 321 in the area 96 using the mouse mark 97, the user can correct the article data 321, post the corrected article data 321 again, and wait for approval.

<E. Program>
The server 300 implements the above-described processing by executing the application program 326. In the server 300, storage media that store the application program 326 include, for example, the memory 302, the HDD 307, and the storage medium 308. The storage medium 308 is, for example, a CD-ROM (Compact Disc - Read Only Memory), a DVD-ROM (Digital Versatile Disk - Read Only Memory), a USB (Universal Serial Bus) memory, a memory card, an FD (Flexible Disk), a hard disk, SSD (Solid State Drive), magnetic tape, cassette tape, MO (Magnetic Optical Disc), MD (Mini Disc), IC (Integrated Circuit) card (excluding memory card), optical card, mask ROM, EPROM, EEPROM (Electronically Includes various types of non-volatile storage media, such as Erasable Programmable Read-Only Memory. Further, the application program 326 can also be provided to the server 300 by downloading via various networks such as the Internet.

The function of the server 300 for the chronology production process may be provided in the terminal 100 or the terminal 200. In that case, the processors 101 and 201 execute the application program 326 to realize the year history creation process. Storage media that store application program 326 include, for example, memories 102, 202, storage media 110, 210, and the like. The storage medium in which the application program 326 is stored includes the various types of storage media described above. Further, the application program 326 can also be provided to the terminals 100, 200 by downloading via various networks such as the networks NW1 and NW2.

In the embodiment, an example of a configuration is shown in which necessary processing is achieved by a CPU or a processor executing a program. However, some or all of the provided processing may be implemented using a dedicated hardware circuit (for example, It may be implemented using a dedicated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array).

<F. Application example of embodiment>
In this embodiment, a mechanism is provided in which the members of the organization participate in the creation of the organization's annual history and have them evaluate it. For example, in a scene where a company history is created, this mechanism is realized by the following functions.

First, create the first company history, and share the created company history with a specified range of people who have viewing privileges (e.g., employees who have been with the company for one year, employees in managerial positions or higher, etc.). Publish to users. The user browses the articles that make up the company's history, and if there are other articles, photos, videos, etc. to be added, the user operates the terminal 100 to post them.

Further, the employee who viewed the company history operates the terminal 100 to evaluate the contents of the company history, for example, quantitatively with a score (out of 100), and the server 300 receives the evaluation score from the terminal 100. The company collects the data, calculates the average value, and publishes the calculated value on the company website together with the company history as an approval coefficient for the company history by employees. Items to be disclosed may include whether the company history content is correct, the degree of sufficiency of the company history content, and the reliability of the company history content.

Furthermore, employees view the text of articles in the company history and submit new article manuscripts (equivalent to candidate article data) based on the results of the viewing. In that case, the editor (editor-in-chief) who operates the terminal 200 checks the manuscript of the posted article and makes a decision to approve or reject it based on the check results. Approved posted articles are made public to employees who have viewing authority as article data that constitutes the company's history. Furthermore, other employees can view the published article content and post comments and impressions.

Such a production system provides an environment in which the company's history can be amplified (grown) independently by publishing the company's history and adding articles posted by employees who have viewed the company's history to the company's history.

In addition, as mentioned above, if a system for employees to evaluate and approve company history is introduced into the company history production scene, for example, the company will be able to evaluate the correctness and sufficiency of the company history created by the company. By announcing on the website that we are an organization that has created and published a corporate history that has a 90-point employee approval rating, we provide both internal and external parties with an index to evaluate corporate governance. You can also.

The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims rather than the above description, and it is intended that all changes within the meaning and range equivalent to the claims are included.

100,200 terminal, 300 server, 311 viewing web page management department, 312 editing web page management department, 313 user management department, 314 history management department, 315 article management department, 316 comment management department, 317 editorial department, 320 year history data, 321 article data, 323 comment data, 324 user management data, 326 application program, NW1, NW2 network.

Claims (13)

A method for creating a chronological history of an organization performed by an information processing device, the method comprising:
The information processing device includes:
a processor;
a storage unit that stores a plurality of article data forming the annual history,
The production method is
a step in which the processor outputs article data constituting the annual history on a display so that it can be viewed;
a step in which the processor determines whether the viewer has posting authority based on the viewer's attributes including the length of the viewer's affiliation with the organization;
a step in which the processor receives an article data posting operation from a viewer determined to have posting authority;
a step in which the processor receives, from an editor with editing authority, an editing operation for a year history using the article data posted by the posting operation;
a step in which the processor executes an editing process for the year history so that it includes the posted article data according to the received editing operation;
The processor collects and outputs quantitative evaluations including scores for article data of the year history from viewers belonging to the organization,
The step of outputting article data constituting the year history on a display so that it can be viewed includes:
The processor includes a viewing object that visualizes article data so that it can be viewed, an object that accepts input operations for comments from the viewer regarding the visualized article data, and one or more input operations for the article data. outputting a GUI including an object that visualizes comments from the viewer;
The step of accepting the posting operation includes:
The processor includes a viewing object that visualizes article data so that it can be viewed, a posting object that accepts the posting operation from the viewer, and comments from other viewers on the article data posted by the viewer's posting operation. A method for creating a year history, the method comprising the step of outputting a GUI including an object for visualizing the chronological history. 2. The chronology production method according to claim 1, wherein the viewer's attributes further include information indicating a division or department of the organization to which the viewer belongs . 3. The chronology production method according to claim 1, wherein the viewer's attributes further include information indicating the viewer's position in the organization . The chronological history includes a plurality of types of chronological history, and each of the plurality of types of chronological history includes an annual history for each number of years since the organization was established, according to any one of claims 1 to 3 . How to create a year history. 5. The chronological history production method according to claim 1 , wherein the chronological history includes a plurality of types of chronological history, and each of the plurality of types of chronological history includes a chronological history of a division or department of the organization. Any one of claims 1 to 5 , wherein the chronology includes a plurality of types of chronology, and the plurality of article data stored in the storage unit includes article data shared between different types of the chronology. The year history production method described in Section 1. 7. The chronology production method according to claim 1, wherein the article data includes document data and image data or audio data including video data related to the document data. The year history has a plurality of layers in which one or more of the article data is arranged in each layer,
The article data is associated with a search tag for searching the article data,
8. The chronological history production method according to claim 1, wherein the tag associated with the article data indicates a layer in which the article data is arranged among the plurality of layers. One or more article data arranged in each of the plurality of hierarchies has an order in which they are displayed on the display,
The tag associated with the article data includes the layer in which the article data is placed among the plurality of layers, and the order of the article data in the order of the one or more article data placed in the layer. The chronology production method according to claim 8 , which shows the following. The step of accepting the editing operation includes :
The processor outputs a GUI including an article object for visualizing the article data posted by the posting operation received via the posting object, and an editing object for accepting an editing operation by the editor. The chronology production method according to any one of claims 1 to 9 , comprising: A chronology production program for realizing the chronology production method according to any one of claims 1 to 10 , when executed by an information processing device. A chronology production device for carrying out the chronology production method according to any one of claims 1 to 10 . comprising a server and a terminal that communicates with the server via a network,
The server is
a storage means for storing a plurality of article data constituting a yearly history of the organization ;
means for transmitting to the terminal screen information that enables viewing of article data constituting the annual history;
means for editing the annual history so as to include posted article data according to information on the editing operation of the annual history received from the terminal;
The terminal is
operating means for accepting user operations on the terminal;
means for displaying a screen based on the screen information received from the server on a display of the terminal ;
The server is
means for determining whether the user has posting authority based on viewer attributes including the length of the user's affiliation with the organization;
further comprising means for collecting and outputting quantitative evaluations including scores for article data of the year history from users belonging to the organization;
The terminal is
means for accepting an article data posting operation from a user determined by the server to have posting authority, via the operating means;
means for transmitting posted article data to the server;
means for receiving an editing operation for the year history from a user who has editing authority via the operation means;
further comprising means for transmitting information on the received editing operation of the year history to the server,
The means for displaying on the display a screen based on screen information that allows viewing of article data constituting the annual history,
A viewing object that visualizes article data so that it can be viewed, an object that accepts input operations for comments from the user on the visualized article data, and comments from one or more of the users input on the article data. has means for outputting a GUI including an object that visualizes the
The means for accepting the posting operation of the article data includes:
It includes a viewing object that visualizes article data so that it can be viewed, a posting object that accepts the posting operation from the user, and an object that visualizes comments from other users on the article data posted by the user's posting operation. A year history production system that has a means to output a GUI .

Images