JP2009205211A - Article management method, article management program, and article management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To notify a high order article in a hierarchical structure once that comments on the high order article has been contributed between articles having a hierarchical structure. <P>SOLUTION: In an article management system 4 equipped with a plurality of blog servers 11 to 12, when a blog server 13 receives the contribution request of article data C relevant to an article B from a client 23, a block server 12 which manages article data B acquires URL for article B cooperative acceptance and URL for article A-cooperative acceptance showing the block server 11 which manages article data A associated with the article data B, and stores the URL for article B-cooperative acceptance and the URL for the article A-cooperative acceptance in a storage part, and when receiving article data C from a client 23, the block server refers to the URL for the article B-cooperative acceptance and the URL for the article A-cooperative acceptance stored in the storage part, and transmits the article data C to the block server 12 and the block server 11. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an article management method, an article management program, and an article management system.

  Many websites on the Internet are configured to be easily moved to other sites by attaching URLs (Uniform Resource Indicators) of other sites in the site. In recent years, a service called a blog has rapidly spread. A blog is a type of diary-type website that writes their opinions and memorandums on topics that are not necessarily limited to the web, such as news, sites, personal experiences, specific topics, etc. Many blogs include a system like an electronic bulletin board that allows readers to write comments about articles on the blog, and links from other articles to articles from other articles. A feature called trackback is provided to notify the link source site that a site article has been pasted.

Also, by collecting trackback source comments (child articles) comments and trackbacks, it is possible to efficiently obtain related information from a certain blog article by collecting the trackback source comments / trackbacks, method and apparatus, program, and A storage medium storing a program is disclosed (for example, see Patent Document 1).
JP 2006-331348 A

  Comments posted by such a function can be written irresponsibly because they can be written anonymously, while comments from multiple readers have context over time, creating a community. Also, if a commenter wants to publish a comment posted on another blog as his / her own opinion on his / her blog, the commenter must post to the blog to which he / she is posting and his / her blog by multi-posting. is there. However, multi-posting is not preferable because an article having the same content is posted as a separate article to a plurality of communities (blogs).

  In addition, when a comment contributor posts a comment by using a trackback, his / her blog is linked to the link of the posting destination (link destination). However, since the trackback is a one-way link, only a simple summary of the child article of the link source (in this case, one's own article) or the child article is included only in the parent article (posted article) that is the link destination. Information such as URL is posted. Therefore, the parent article cannot be referred from the child article unless the parent article is referenced and linked in the article of the child article.

  As a method of avoiding such a situation, it is conceivable to link each other by returning the trackback from the parent article receiving the trackback to the child article. However, when a link is pasted by such a method, since the child article is positioned as the same hierarchy as the parent article, it is difficult to follow one thread and it is difficult to establish a community. In addition, by posting a comment on a given article (parent article), a child article for the parent article was created, and further by posting a comment on this child article, a grandchild article was created for the parent article When using a technique such as trackback, a blog server that manages a grandchild article can be notified that a link is pasted to a blog server that manages a child article. Cannot notify the parent article. Therefore, the notification from the grandchild article to the parent article must be performed separately from the notification from the grandchild article to the child article.

  In addition, a system and a tool that hierarchically display a parent-child relationship between articles posted on a personal blog as in Patent Document 1 are provided, but the current situation is on a personal blog where an original article is posted. It is still difficult to develop into a community.

  In view of the above, an object of the present invention is to notify a higher-level article in the hierarchical structure at a time that a comment on a predetermined article has been posted between articles having a hierarchical structure.

  The present invention was created to solve the above-mentioned problem, and the article management method according to claim 1 is an article management system comprising a plurality of article management devices for managing articles posted via a network. When the processing unit of the first article management apparatus receives a posting request for the first article data, which is article data related to a predetermined article, from a client, the article management method of the first article management apparatus The processing unit of the second article management device that manages the second article data, which is data, the identification information of the second article management device and the third article data associated with the second article data Identification information indicating a third article management apparatus that manages the first article management apparatus is transmitted to the first article management apparatus, and the processing unit of the first article management apparatus receives the received identification of the second article management apparatus. Information and 3rd When the identification information of the article management device is stored in the storage unit and the first article data is received from the client, the identification information of the second article management device and the third article stored in the storage unit are stored. A notification that the posting related to the second article data has been made is transmitted to the second article management apparatus and the third article management apparatus with reference to the identification information of the management apparatus. .

  In a situation where a child article (second article) for the third article is generated by posting a comment to the third article, another client sends this child article (second article). By posting a comment on a grandchild article (first article) for a child article (second article) is generated. According to such an invention, the poster of the grandchild article (first article) sends the first article management device that manages the parent article (third article) and the child article (second article). One notification without a separate notification to the managing second article management device that a comment on the parent article (third article) and child article (second article) has been posted. The grandchild article (article C) is sent to the first article management apparatus that manages the parent article (third article) and the second article management apparatus that manages the child article (second article). It becomes possible to notify that it has been posted.

  The article management method according to claim 2 is the article management method according to claim 1, wherein the processing unit of the first article management apparatus that has received the first article data receives the first article received. Is stored in the storage unit in association with the article data related to the first article data, and when a display request for the article data related to the first article data is received from the client, the first data A screen displaying the article data and the article data related to the first article data in association with each other is generated, and the screen is displayed on the client that has requested the display request.

  According to such a configuration, when a hierarchical structure associated with a parent-child relationship between articles occurs, when an article is viewed on the client, both the article at the top of the hierarchy and the article at the bottom are simultaneously displayed on the client. This makes it easier for the user to follow the same thread.

  The article management method according to claim 3 is the article management method according to claim 1 or 2, wherein the processing unit of the first article management apparatus that manages the first article data includes: , Before transmitting the first article data to the second article management apparatus and the third article management apparatus, the second article data and the first article data are sent from the second article management apparatus. Receiving at least one of the article data, generating an edit screen of the article data including the received article data, causing the generated edit screen to be displayed on the client that has requested the display request, and displaying the displayed on the client The article data edited on the editing screen is received as the first article data.

  According to such a configuration, the editing screen including article data allows the user to create a comment article by quoting the body of the article included in the article data. It is possible to easily understand whether the comment is for a part.

  An article management method according to claim 4 is the article management method according to any one of claims 1 to 3, wherein the identification information of the first article management apparatus is stored in the article management apparatus. A fixed link indicating a storage area of the article data to be managed is shown. When the processing unit of the first article management apparatus receives the first article data from a client, the processing unit of the first article management apparatus A first fixed link is generated for the first article data, the generated first fixed link is added to the first article data, and the first article data is stored in the storage unit of the article management apparatus. The second fixed link attached to the article data to be stored and the generated first fixed link are stored in the storage unit in association with each other, and when the article data browsing request is received from the client, the storage Part All the fixed link article data stored to generate a link displayed screen, a screen that the generated and characterized in that display to the client that the viewing request.

  According to such a configuration, when browsing the child article by storing the fixed link indicating the storage area of the parent article data and the fixed link indicating the storage area of the child article data in the storage unit in association with each other. A link from a child article to a parent article can be pasted on the browsing screen.

  The article management method according to claim 5 is the article management method according to any one of claims 1 to 3, wherein the article management system displays a hierarchical structure between articles. And a processing unit of the first article management apparatus notifies the second article management apparatus and the third article management that the posting related to the second article data has been made. When transmitting to the apparatus, related article management apparatus information having identification information indicating the first article management apparatus and identification information indicating the second article management apparatus as a pair of information is sent to the hierarchical structure display apparatus. And when the processing unit of the hierarchical structure display device receives the related article management device information from a plurality of the first article management devices, the identification information indicating the second article management device is used as an upper article. Related information, the first Each piece of related article management device information is stored in a storage unit as identification information indicating a thing management device as information related to a lower article, and when a display request for a hierarchical structure between articles is received from a client, the information is stored in the storage unit On the basis of each of the related article management apparatus information that has been set, the client is caused to display a hierarchical structure display screen that displays information related to the upper article and information related to the lower article.

  According to such a configuration, the hierarchical structure of articles can be displayed in a format that is easy to visually recognize.

  An article management program according to a sixth aspect causes a computer to execute the article management method according to any one of the first to fifth aspects.

  According to such a structure, the program which has the effect of Claims 1-5 can be provided.

  The article management system according to claim 7 is an article management system including a plurality of article management apparatuses that manage articles posted via a network, and the article management system includes at least a first article management apparatus, The first article management apparatus has a second article management apparatus and a third article management apparatus, and the first article management apparatus issues a request for posting first article data, which is article data related to a predetermined article, from a client. When received, the second article management device that manages the second article data that is the data of the predetermined article is associated with the identification information of the second article management device and the second article data. Identification information indicating a third article management device that manages third article data is transmitted to the first article management device, and the first article management device receives the second article management device. The identification information and the identification information of the third article management device are stored in the storage unit, and when the first article data is received from the client, the identification of the second article management device stored in the storage unit The information and the identification information of the third article management device are referred to, and a notification that the posting related to the second article data has been made is transmitted to the second article management device and the third article management device. It is characterized by doing.

  In a situation where a child article (second article) for the third article is generated by posting a comment to the third article, another client sends this child article (second article). By posting a comment on a grandchild article (first article) for a child article (second article) is generated. According to such an invention, the poster of the grandchild article (first article) sends the first article management device that manages the parent article (third article) and the child article (second article). One notification without a separate notification to the managing second article management device that a comment on the parent article (third article) and child article (second article) has been posted. The grandchild article (article C) is sent to the first article management apparatus that manages the parent article (third article) and the second article management apparatus that manages the child article (second article). It becomes possible to notify that it has been posted.

  Moreover, the article management system according to claim 8 is the article management system according to claim 7, wherein the article management system further includes a hierarchical structure display device that displays a hierarchical structure between articles, When the article management apparatus transmits a notification that the posting related to the second article data has been made to the second article management apparatus and the third article management apparatus, Related article management device information having a pair of identification information indicating a management device and identification information indicating the second article management device is transmitted to the hierarchical structure display device, and the hierarchical structure display device includes a plurality of pieces of information. When the related article management device information is received from the first article management device, the identification information indicating the second article management device is used as information related to a higher-level article, and the first article management device is identified. Information subordinate As related information, each of the related article management device information is stored in a storage unit, and when a hierarchical structure display request between articles is received from a client, each of the related article management device information stored in the storage unit Based on the above, a hierarchical structure display screen for displaying information related to the upper article and information related to the lower article is displayed on the client.

  According to such a configuration, the hierarchical structure of articles can be displayed in a format that is easy to visually recognize.

  According to the present invention, it is possible to notify a higher-order article in the hierarchical structure at one time that a comment on a predetermined article has been posted between articles having a hierarchical structure.

  The best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described in detail below with reference to the drawings. In this embodiment, managing articles or article data means storing article data such as a blog transmitted from a client in a storage unit, and if there is a browsing request from another client or the like, the article data in the storage unit is Is displayed on the requesting client.

(System configuration)
FIG. 1 is a diagram illustrating a configuration example of an article management system 4 according to the first embodiment. The article management system 4 includes a plurality of blog servers 1 (article management apparatus: blog server 11 (third article management apparatus), blog server 12 (second article management apparatus), and blog server 13 (first article management apparatus). ), And a plurality of clients 2 (client 21, client 22, client 23,...) Are connected to each other via a network 3. The blog server 1 has a function of managing blogs. The configuration of the blog server 1 will be described later with reference to FIG. The client 2 has a function of sending a blog posting request, blog update information, a blog viewing request, and the like to the blog server 1 and displaying the blog data sent from the blog server 1 on a display unit (not shown).

(Server configuration)
FIG. 2 is a diagram illustrating a configuration example of the blog server 1 according to the first embodiment. The blog server 1 includes a processing unit 100 that processes information, a storage unit 110 that stores information, and a transmission / reception unit 120 that transmits and receives information. The processing unit 100 includes a reception processing unit 101, a transmission processing unit 102, a storage processing unit 103, an acquisition unit 104, an issuing unit 105, and a blog processing unit 106. The reception processing unit 101 has a function of identifying and determining the type of data received by the transmission / reception unit 120. The transmission processing unit 102 has a function of generating data to be transmitted and causing the transmission / reception unit 120 to transmit the data.

  The storage processing unit 103 has a function of storing data in the storage unit 110. The acquisition unit 104 has a function of acquiring data from the storage unit 110. The issuing unit 105 has a function of issuing a permanent link (identification information), a cooperation reception URL (identification information), and the like for each article. The blog processing unit 106 has a function of performing general processing related to a blog such as updating or browsing a blog. The storage unit 110 stores article management data 111 which will be described later.

(Invention outline)
FIG. 3 is a diagram showing an outline of the article management method in the present embodiment. In FIG. 3, the same elements as those in FIG. As illustrated in FIG. 3, for example, it is assumed that an article A that is an original article has been posted on the blog server 11. Assume that an article B, which is a comment on the article A, is posted on the blog server 12. It is assumed that the user using the client 23 has posted the article C, which is a comment on the article B, to the blog server 13.

  In this embodiment, when there is a parent-child relationship between articles as described above, an article A that is an original article is described as “parent article”, and an article B that is a comment on the parent article is described as “child article”. Furthermore, in this embodiment, the article C that is a comment on the article B becomes a “child article” for the article B and a “grandchild article” for the article A. In addition, such a parent-child relationship between articles is expressed as an article having a hierarchical structure. In a general trackback, a notification is sent from the blog server 13 managing the article C, which is a grandchild article, to the blog server 12 managing the article B, which is a direct parent article to the article C. Notification to the blog server 11 managing the article A, which is the parent article, is not performed. In the present embodiment, an object is to perform notification from the blog server 13 to the blog server 11 at the same time as performing notification from the blog server 13 to the blog server 12.

(Article management data)
FIG. 4 is a diagram illustrating a configuration example of article management data in the present embodiment, (a) illustrates a configuration example of article management data, (b) illustrates a configuration example of parent article management data, c) shows a configuration example of the child article management data 307. As shown in FIG. 4A, the article management data 111 includes the own article title 301, the own article text 302, the date and time 303 when the own article was updated, the own article's permanent link 304, and the reception of the cooperation of the own article. It has a URL 305, parent article management data 306 which is data related to a parent article for the own article, and child article management data 307 which is data related to a child article for the own article.

  Here, the permanent link is a URL uniquely assigned to one article, and is a URL that does not change even if the article content is updated. The URL for accepting cooperation has a function of notifying a parent article that a link is pasted in a child article. The URL for cooperative reception also has a function of indicating a destination when the blog server 1 sends a request for acquiring data related to a parent article from the blog server 1 managing the parent article. The own article title 301, the own article text 302, the date and time 303 when the own article was updated, the own article permanent link 304, and the own article cooperation reception URL 305 are described as the own article management data 300.

  Also, as shown in FIG. 4B, the parent article management data 306 stores the parent article permanent link 311 and the parent article cooperation reception URL 312 for each parent article. Further, as shown in FIG. 4C, the child article management data 307 includes a child article permanent link 321, a child article cooperation reception URL 322, and a child article application request from the blog server 1 that manages the child article. The date and time 323 when the child article approval request transmitted from the blog server 1 that manages the child article to the blog server 1 that manages the parent article is received, and the URL 324 for the cooperation reception of the parent article for the target child article. The child article title 325 and the child article text 326 are stored for each child article.

  When there is no parent article for the own article, the parent article management data 306 shown in FIGS. 4A and 4B is blank, and when there is no child article for the own article, FIG. The child article management data 307 shown in (a) and FIG. 4 (c) is blank.

  Further, when a child article and a grandchild article are posted to the own article, the parent article cooperation reception URL 324 for the child article shown in FIG. That is, the URL for receiving the cooperation of the own article) and the URL for receiving the cooperation of the parent article for the grandchild article (that is, the URL for receiving the cooperation of the child article for the own article) are stored. The article management data 111 when the grandchild article is posted will be described later with reference to FIG.

(processing)
Next, processing in the article management system 4 according to the first embodiment will be described along FIG. 5 with reference to FIGS. 1 to 4 and FIGS. 6 to 18. Prior to the description of the actual process, the description of the drawings in FIGS. 5 to 18 and the description of the reference numerals will be briefly made, and then the actual process will be described. FIG. 5 is a timing chart showing the flow of processing in the article management system 4 according to the first embodiment. FIGS. 7, 9, 12, 13, and 18 show examples of display screens in the client 2. FIG. 6, FIG. 11 and FIG. 17 are diagrams showing examples of the configuration of article management data in the blog server 11, (a) in FIG. 11 and FIG. 17 shows the configuration of article management data, and (b) Indicates the configuration of child article management data. 6, 11, and 17, reference numerals 300 a to 307 a and 321 a to 326 a correspond to reference numerals 300 to 307 and 321 to 326 in FIG. 4. 8, 10, and 16 are diagrams illustrating configuration examples of article management data in the blog server 12, and (a) in FIGS. 8, 10, and 16 illustrates a configuration of article management data, 8, (b) in FIG. 10, FIG. 16 and FIG. 16 show the structure of the parent article management data, and (c) in FIG. 16 shows the structure of the child article management data. 8, 10, and 16, reference numerals 300 b to 307 b, 311 b, 312 b, and 321 b to 326 b correspond to reference numerals 300 to 307, 311, 31231 to 326 in FIG. 4. 14 and 15 are diagrams showing an example of the configuration of the article management data in the blog server 13. (a) shows the configuration of the article management data, and (b) shows the configuration of the parent article management data. Show. 14 and 15, reference numerals 300c to 307c, 311c, and 312c correspond to reference numerals 300 to 307, 311 and 312 in FIG.

  Here, in the figure explaining the article management data 111, the code with “a” at the end indicates the article management data 111 stored in the blog server 11, and the code with “b” at the end is the blog server 12. Indicates the article management data 111 stored in the blog server 13, and the code accompanied by “c” at the end indicates the article management data 111 stored in the blog server 13. Details of processing in each of the blog servers 11 to 13 will be described later with reference to FIG.

(Posting Article A)
The client 21 transmits article data A (third article data) including a subject (title), text data, and the like regarding the article A to the blog server 11 (S101). The blog server 11 that has received the article data A issues a permanent link (article A permanent link) and a link reception URL (article A link reception URL (identification information indicating the third article management device)) for the article data A. To do.

  Then, as shown in FIG. 6, the blog server 11 stores the subject of the article A in the title 301a in the own article management data 300a of the article management data 111a in the storage unit 110 of the blog server 11, and stores the article A in the body 302a. Store body data. Further, the blog server 11 stores the issued article A permanent link and the article A cooperation reception URL in the permanent link 304a and the cooperation reception URL 305a, and further receives the reception date and time of the article data A (the reception date and time of the article A). Stored in the date and time 303a of the article management data 111a. At this stage, the parent article management data 306a and child article management data 307a related to the article A are blank.

(Posting Article B)
Next, the client 22 to which the display request for the blog (blog A) related to the article A is input via the input unit (not shown) of the client 22 is transferred to the blog server 11 storing the article data A in the storage unit 110. A display request is transmitted (S102). The blog server 11 that has received the blog A display request generates the blog A based on the information stored in the article management data 111a (see FIG. 6) of the storage unit 110, and cooperates with the generated blog A and the article A. A reception URL (URL for article A cooperation reception) is transmitted to the client 22 (S103). At this time, the URL for accepting article A cooperation is transmitted in a format displayed in blog A.

  On the display unit (not shown) of the client 22 that has received the blog A and the article A cooperation reception URL, as shown in FIG. 7, the subject (title), body, and article A cooperation reception URL of the article A are displayed. A blog A display screen 400 is displayed. Next, the posting request screen is displayed on the display unit (not shown) by selecting and inputting a posting request button or the like displayed on the display unit (not shown) of the client 22 via the input unit (not shown) of the client 22. The

  Further, the URL for article A cooperation reception is input into the posting request screen via an input unit (not shown), and further, the selection input of the transmission button displayed on the display unit (not shown) is performed, whereby the client 22 The URL for accepting the article A and the posting screen request displayed on the blog A display screen are transmitted to the blog server 12 managing the blog by the client 22 (S104). The blog server 12 that has received the article A cooperation reception URL and the posting screen request sends an article A related data request including the article A cooperation reception URL to the article A cooperation reception URL, that is, to the blog server 11. The article A is transmitted to the blog server 11 that manages the article A (S105).

  The blog server 11 that has received the article A related data request uses the article management data 111a (see FIG. 6) in the storage unit 110 of the blog server 11 using the article A cooperation reception URL included in the article A related data request as a key. Refer to and extract article A related data. The article A related data includes the subject (title) of article A, the text data of article A, the article A permanent link, the URL for article A cooperation reception, and the like.

  Then, the blog server 11 returns the acquired article A related data to the blog server 12 (S106). The blog server 12 that has received the article A related data receives the permanent link (article A permanent link) of the article A (the parent article for the article B) and the URL for accepting the article A linkage included in the received article A related data as the parent article. The management data 306b (see FIG. 8B) is stored in the parent article permanent link 311b and the parent article cooperation acceptance URL 312b, respectively. The article management data 111b in the storage unit 110 of the blog server 12 at this time is shown in FIG. As shown in FIG. 8A, at this time, the other columns 301b to 305b and 307b are blank. Further, the blog server 12 generates a posting screen 500 (editing screen) as shown in FIG. 9 based on the subject name, body data, and article A permanent link of the article A included in the received article A related data. The posting screen 500 shown in FIG. 9 includes a title display area 501 for displaying the subject (title) of the article A, a text display area 502 for displaying the text of the article A, and a permanent for displaying the permanent link of the article A (parent article). A link display area 503, a posting button 504 for posting, and the like are displayed. The blog server 12 transmits the generated posting screen 500 (see FIG. 9) to the client 22 (S107).

  The client 22 that has received the posting screen 500 (see FIG. 9) displays the posting screen 500 on a display unit (not shown). Then, through an input unit (not shown), the user of the client 22 creates a comment (article B) quoting the text of the article A displayed in the text display area 502 of the posting screen 500. Note that when the article B is created, the text of the article A may not be cited. Further, when the blog server 12 generates the posting screen 500, the text of the article A may not be displayed.

  Then, in order to post the created article B as the blog B, the client 22 transmits the article data B (second article data) to the blog server 12 that manages the blog by the client 22 (S108). The article data B includes the subject (title) of the article B, the body text data, and the URL for article A cooperation reception to indicate that it is a comment for the article A. The blog server 12 that has received the article data B receives a permanent link (article B permanent link) and a link reception URL (article B link reception URL: identification information indicating the second article management device) for the received article data B. Issue.

  Then, the blog server 12 uses the article A cooperation reception URL included in the article data B as a key, and the title and text of the article B in the title 301b in the own article management data 300b (see FIG. 10A) of the storage unit 110. In 302b, the text data of the article B in which the text of the article A is cited is registered. Further, the blog server 12 registers the article B permanent link and the article B cooperation reception URL issued to the permanent link 304b and the cooperation reception URL 305b in the own article management data 300b (see FIG. 10A). Then, the blog server 12 registers the reception date and time of the article data B (the reception date and time of the article B) in the date and time 303b of the own article management data 300b. Comparing FIG. 10 with FIG. 8, data is additionally registered in the title 301b, the body 302b, the permanent link 304b, and the cooperation reception URL 305b of the own article management data 300b.

  Thereafter, the blog server 12 sends an article B application request to the URL for article A cooperation reception, that is, to the blog server 11 (S109). The article B application request is a request for applying to approve the article B as a comment for the article A. The article B application request includes article management data 111b (see FIG. 10) regarding the article B. The blog server 11 that has received the article B application request performs an approval process such as whether to approve the article B as a post comment. Note that the approval process may be performed, for example, when the administrator of the blog on which the article A is posted examines the content of the article B.

  As a result of the approval process, when the article B is approved as a posted comment, the blog server 11 shows the content of the article management data 111b (see FIG. 10) regarding the article B included in the article B application request as shown in FIG. And stored in the corresponding part in the child article management data 307a of the article management data 111a. Specifically, the article B permanent link registered in the permanent link 304a of the own article management data 300b (see FIG. 10A) is stored in the child article permanent link 321a (see FIG. 11B). The URL for article B cooperation reception is stored in the cooperation reception URL 322a of the child article. Then, the article A cooperation reception URL registered in the parent article cooperation reception URL 312b in the parent article management data 306b (see FIG. 10B) is the parent article cooperation reception for the child article in FIG. 11B. It is stored in the URL 324a for use. Furthermore, as shown in FIG. 11, the subject of article B is stored in title 325a, and the text data of article B is stored in text 326a. Furthermore, the blog server 11 stores the reception date / time of the application request in step S109 as the child article application date / time of the article B in the date / time 323a of the child article management data 307a. Then, the blog server 11 transmits the approval result of the article B (article B approval result) to the blog server 12 (S110).

(Posting Article C)
Next, a blog A display request is transmitted from the client 23 (S111). Upon receiving the blog A display request, the blog server 11 generates the blog A based on information stored in the article management data 111a (see FIG. 11) in the storage unit 110. Furthermore, the blog server 11 extracts the article A cooperation reception URL and the article B cooperation reception URL from the article management data 111a (see FIG. 11) in the storage unit 110. Then, the blog server 11 transmits the generated blog A, article A cooperation reception URL, and article B cooperation reception URL to the client 22 (S112).

  The client 23 that has received the blog A, the article A cooperation reception URL, and the article B cooperation reception URL displays the blog A on a display unit (not shown). Here, the displayed blog A has an article B display area 610 in which an article B as a child article is displayed in an article A display area 600 in which an article A as a parent article is displayed as shown in FIG. It is displayed. If the client 23 sends a blog B display request to the blog server 12 at the stage of step S111, the blog B as shown in FIG. In the article B display area 700 in FIG. 13, there is an area 710 in which the text of article A is displayed.

  Next, it is assumed that the user of the client 23 posts an article C to an article B that is a child article of the article A. In this case, as described above, the article C is a child article for the article B and a grandchild article for the article A.

  Next, when a selection request such as a posting request button displayed on a display unit (not shown) is input via an input unit of the client 23 (not shown), a posting request screen is displayed on a display unit (not shown). Furthermore, the article B cooperation reception URL, which is the URL for receiving the cooperation of the posting destination article, is input into the posting request screen via the input section (not shown), and the transmission button is selected and displayed on the display section (not shown). By doing so, the URL for accepting the article B and the posting screen request displayed on the blog A display screen are transmitted to the blog server 13 managing the blog by the client 23 (S113).

  The blog server 13 that has received the article B cooperation reception URL and the posting screen request transmits an article B related data request including the article B cooperation reception URL to the blog server 12 indicated by the article B cooperation reception URL. (S114). The blog server 12 that has received the article B related data request uses its own article management data 300b in the storage unit 110 of the blog server 12 with the article B cooperation reception URL included in the article B related data request as a key (FIG. 10A). Article B related data is extracted with reference to FIG. The article B related data includes the subject (title) of article B, the text data of article B, the article B permanent link, the URL for article B cooperation reception, and the like. Further, the blog server 12 extracts all data included in the parent article management data 306b (see FIG. 10B), that is, extracts the article A permanent link and the article A cooperation reception URL, Is added to the article B related data as data related to the parent article.

  Then, the blog server 12 returns the extracted article B related data to the blog server 13 (S115). The blog server 13 that has received the article B related data, as shown in FIG. 14, accepts the permanent link (article B permanent link) of article B (the parent article to article C) included in the received article B related data, and the article B linkage reception. URL, article A permanent link, and article A cooperation reception URL are stored in the corresponding sections 311c and 312c of the parent article management data 306c of the article management data 111c, respectively. Each permanent link and the URL for accepting cooperation are stored in association with each other according to the association in the article management data 111. For example, in FIG. 10, since the article B permanent link and the URL for accepting article B cooperation are associated with each other in the own article management data 300b, the parent article management data 306c in FIG. 14 includes the article B permanent link and the article. The URL for B cooperation reception is stored in association with it.

  Similarly, in FIG. 10, since the article A permanent link and the URL for accepting article A cooperation are associated with each other in the parent article management data 306b, the parent article management data 306c in FIG. Article A cooperation reception URL is stored in association with each other. As shown in FIG. 14, at this time, in the article management data 111c in the blog server 13, only the parent article permanent link 311c and the parent article cooperation reception URL 312c of the parent article management data 306c are registered, and the other fields 301c. ˜305c and 307c are blank. In addition, the blog server 13 generates a posting screen based on the subject name, body data, and article B permanent link of the article B included in the received article B related data. Here, in the generated posting screen, the title of the article B is displayed in the title display area 501 of the posting screen 500 shown in FIG. 9, the body text of the article B is displayed in the body text display area 502, and the permanent link display area 503 is displayed. Will display the article B permanent link. The blog server 13 transmits the generated posting screen to the posting screen requesting client 23 (S116).

  The client 23 that has received the posting screen displays the received posting screen on a display unit (not shown). Through the input unit, the user of the client 23 creates a comment (article C) that quotes the body part of the posting screen. Here, the article C may be created without quoting the text of the article B. Then, in order to post the created article C as the blog C, the client 23 transmits the article data C (first article data) to the blog server 13 that manages the blog by the client 23 (S117). The article data C includes an article B cooperation reception URL for indicating the subject of the article C, the body data of the article C, and a comment on the article B. The blog server 13 that has received the article data C provides a permanent link (article C permanent link) and a link reception URL (article C link reception URL: identification information indicating the first article management device) for the received article data C. Issue.

  Then, the blog server 13 uses the article B cooperation reception URL included in the article data C as a key, and the article C is added to the title 301c in the article management data 300c of the article management data 111c in the storage unit 110 as shown in FIG. The text data of article C is registered in the subject and text 302c. Furthermore, the blog server 13 registers the article C permanent link and the article C cooperation reception URL issued to the permanent link 304c and the cooperation reception URL 305c in the article management data 300c of the article management data 111c. Then, the blog server 13 registers the reception date and time of the article data C (the reception date and time of the article C) in the date and time 303c of the own article management data 300c. When FIG. 15 is compared with FIG. 14, data corresponding to the respective columns 301c to 305c in the own article management data 300c is additionally registered.

  Thereafter, the blog server 13 applies an article C application to the blog server 1 indicated by all the URLs for receiving cooperation in the parent article management data 306c (see FIG. 15B) registered in the URL for receiving cooperation in the parent article 312c. A request is transmitted (S118). In the example shown in FIG. 15, the blog server 13 transmits an article C application request to the blog server 12 and the blog server 11 addressed to the article B cooperation reception URL and the article A cooperation reception URL (S118). The article C application request includes article management data 111c (see FIG. 15) regarding the article C. The blog server 12 and the blog server 11 that have received the article C application request perform an approval process such as whether to approve the article C as a posted comment. Note that the approval process may be performed by, for example, an administrator of a blog posting the article B or the article A examining the contents of the article C.

  As a result of the approval process in the blog server 12, when the article C is approved as a posted comment, the blog server 12 uses the contents of the article management data 111c (see FIG. 15) regarding the article C included in the article C application request as shown in FIG. As shown in FIG. 4, the child article management data 307b is stored in the corresponding part. Specifically, the article C permanent link in the article management data 300c is added to the child article permanent link 321b shown in FIG. 16C, and the article C cooperation reception URL is changed to the child article cooperation reception URL 322b. Added.

  Then, all the cooperation reception URLs registered in the parent article cooperation reception URL 312c in the parent article management data 306c (see FIG. 15B) included in the article C application request, that is, the article A cooperation reception URL and The article B cooperation reception URL is added as a set to the parent article cooperation reception URL 324b for the child article in FIG. Further, the subject of article C is stored in title 325b, and the text data of article C is stored in text 326b. Further, the blog server 12 stores the reception date / time of the application request in step S118 as the child article application date / time of the article C in the date / time 323b of the child article management data 307b. Then, the blog server 12 transmits the approval result of the article C to the blog server 13 (S119). When FIG. 16 is compared with FIG. 10, child article management data 307c related to article C is additionally registered.

  Similarly, when the article C is approved as a posted comment as a result of the approval process in the blog server 11, the blog server 11 uses the content of the article management data 111c (see FIG. 15) regarding the article C included in the article C application request. As shown in FIG. 17, it is additionally stored in the corresponding part of the child article management data 307a. Specifically, the article C permanent link in the own article management data 300c is added to the child article permanent link 321a, and the article C cooperation reception URL is added as a set to the child article cooperation reception URL 322a.

  Then, the article A cooperation reception URL and the article B cooperation reception URL registered in the parent article cooperation reception URL 312c in the parent article management data 306c (see FIG. 15B) included in the article C application request are: Child article management data 307a (FIG. 17B) is added to the URL 324a for receiving cooperation of the parent article for the child article. Further, the title of the article C is stored in the title 325a, and the body data of the article C is stored in the body 326a. Furthermore, the blog server 11 stores the reception date / time of the application request in step S118 as the child article application date / time of the article C in the date / time 323a of the child article management data 307a. Then, the blog server 11 transmits the approval result of the article C to the blog server 13 (S120). When FIG. 17 is compared with FIG. 11, in addition to the information about the article B, the information about the article C is additionally registered in the child article management data 307a.

  Here, looking at the URL 324a for receiving the cooperation of the parent article with respect to the child article in the child article management data 307a of the article management data 111a shown in FIG. 17, in the record corresponding to the article B permanent link, the URL for receiving the article A cooperation. Only registered. This indicates that the article B is a child article of the article A. On the other hand, in the record corresponding to the article C permanent link, the URL for accepting article A cooperation and the URL for accepting article B cooperation are registered. As described above, since the record corresponding to the article B permanent link indicates that the article B is a child article of the article A, it indicates that the article C is a grandchild article of the article A. That is, the article management data 111a has information regarding the hierarchical structure between articles.

  FIG. 18 shows an example of a blog related to the article A sent from the blog server 11 when step S120 is completed. As shown in FIG. 18, an article A display area 800 that is a parent article, an article B display area 810 that is a child article, and an article C display area 820 that is a grandchild article are displayed in the same browser. In FIG. 18, for example, the title of article A, the article B permanent link of the permanent link 321a of the child article shown in FIG. 15, the title of article B, and the article C permanent of the permanent link 321a of the child article shown in FIG. By associating the link with the link, when the user clicks the corresponding title via the input unit, the blog of the corresponding article may be displayed. Similarly, when the blog server 13 displays a blog on the client 2, the blog server 13 displays the article A permanent link and the article B permanent link registered in the permanent link 311c of the parent article in FIG. The blog of article A or article B may be displayed by clicking.

(When there is a parent article of article A)
In the present embodiment, three articles, which are an article A that is a parent article, an article B that is a child article, and an article C that is a grandchild article, are described. May exist. That is, article D → article B → article A → article D → article E →..., There is article D as the parent article of parent article A, and article E,. (Here, “→” indicates that the posting source → the posting destination). In this case, in the step S106, the article D permanent link, the article E permanent link,... Are registered in the parent article permanent link (not shown) in the parent article management data 306a (see FIG. 6) of the blog server 11. . Similarly, an article D cooperation reception URL, an article E cooperation reception URL,... Are further registered in the parent article cooperation reception URL (not shown).

  In the article A related data in step S106, in addition to the article A permanent link and the article A cooperation reception URL, the article D permanent link, the article E permanent link, the article D cooperation reception URL, and the article E cooperation reception URL , ... will be included. Therefore, at the stage of step S107, the permanent link 311b of the parent article in the parent article management data 306b of the blog server 12 (see FIG. 8B) and the link reception URL 312b of the parent article include the article A permanent link and the article A. In addition to the cooperation reception URL, information such as an article D permanent link, an article E permanent link, an article D cooperation reception URL, an article E cooperation reception URL, and so on is further registered.

  Accordingly, in the article B related data in step S115, the article D permanent link, the article E permanent link, the article E permanent link, the article B permanent link, the article B cooperation reception URL, and the article B cooperation reception URL are included. URL for D cooperation reception, URL for article E cooperation reception,. Thus, the article A permanent link, the article B permanent link, the article D permanent link, the parent article permanent link 311c of the parent article management data 306c (see FIG. 15B) of the blog server 13 in the stage of step S118, Article E permanent link,... Is registered, and the URL 312c for accepting cooperation of the parent article includes the URL for accepting the article A cooperation, the URL for accepting the article B cooperation, the URL for accepting the article D cooperation, and for accepting the article E cooperation. URL ... is registered.

  Therefore, in step S118, the blog server 13 uses the article A cooperation reception URL, the article B cooperation reception URL, and the article D registered in the parent article cooperation reception URL 312c of the parent article management data 306c (see FIG. 15). The application request is transmitted to the blog server 1 indicated by the URL for cooperation reception with reference to the URL for cooperation reception, the URL for article E cooperation reception,. As described above, in this embodiment, all articles (article B, article A, article D, article E,...) That are higher than a predetermined article (article C) in the parent-child relationship between articles are managed. A notification that a related article has been posted can be sent to the existing blog server 1 with a single notification.

(Processing in the blog server)
Next, the processing of the blog server 1 in the first embodiment will be described along FIG. 19 with reference to FIGS. FIG. 19 is a flowchart showing a processing flow of the blog server according to the first embodiment. In FIG. 19, the processes in steps S202 to S204 are processes when the content of the posting is not a child article registration, and the processes in steps S205 to S218 are processes when the child article is registered. . First, the reception processing unit 101 determines whether or not the transmission / reception unit 120 has received a posting screen request together with the cooperation reception URL (S201). If the posting screen request has not been received as a result of step S201 (S201 → No), the reception processing unit 101 determines whether or not article data including an article title, body data, and the like has been received from the client 2 ( S202).

  If the article data has not been received as a result of step S202 (S202 → No), the processing unit 100 advances the processing to step S206. If the article data is received as a result of step S202 (S202 → Yes), since the article data is received without receiving the posting screen request, the processing unit 100 is an article whose article data is not a posted comment. It is determined that the data corresponds to the parent article data, and the issuing unit 105 issues a permanent link and a link reception URL for the received article data (S203).

  Then, the storage processing unit 103 stores the title included in the article data, the body text data, the reception date and time of the article data, the permanent link issued in step S203, and the URL for cooperation reception in the article management data 111 of the storage unit 110. It registers in each column 301-305 of the own article management data 300 (S204). Next, the processing unit 100 returns the process to step S201.

  In step S201, when the posting screen request is received (S201 → Yes), the transmission processing unit 102 includes the posting screen request and the article-related information including the cooperation reception URL received by the blog server 1 indicated by the received cooperation reception URL. A data request is generated, and the generated article-related data request is transmitted to the transmission / reception unit 120 (S205). Next, the reception processing unit 101 determines whether an article-related data request has been received from another blog server 1 (S206). As a result of step S206, when the article related data request is not received (S206 → No), the processing unit 100 proceeds to the process of step S208.

  When an article-related data request is received as a result of step S206 (S206 → Yes), the acquisition unit 104 manages its own article from the article management data 111 in the storage unit 110 using the URL for cooperation reception included in the article-related data as a key. If the title, body data, permanent link, and link reception URL in the data 300 are acquired, and if there is data in the parent article management data 306, all data in the parent article permanent link 311 and the parent article link reception URL 312 (Permanent link and cooperation reception URL) are acquired. Then, the transmission processing unit 102 generates article related data including the title, body data, permanent link, URL for cooperation reception, URL of all parent articles, URL for cooperation reception of parent articles, etc. regarding the acquired own article. Then, the generated article-related data is sent back to the transmission / reception unit 120 toward the blog server 1 that requested the article-related data (S207).

  Next, the reception processing unit 101 determines whether or not article related data has been received from another blog server 1 (S208). If the article-related data has not been received as a result of step S208 (S208 → No), the processing unit 100 advances the processing to step S211. When article related data is received as a result of step S208 (S208 → Yes), the storage processing unit 103 stores all permanent links and all link reception URLs included in the article related data in the article management data 111 of the storage unit 110. Are registered in the parent article permanent link 311 and the parent article cooperation reception URL 312 of the parent article management data 306 (see FIG. 4B) (S209).

  Furthermore, the transmission processing unit 102 generates a posting screen that includes the title of the parent article and the permanent link included in the article-related data, and further includes the body data, thereby quoting the body text of the parent article. A posting screen is transmitted to the client 2 that has transmitted the article-related data request in S205 (S210).

  Next, the reception processing unit 101 determines whether article data has been received from the client 2 (S211). Here, the article data includes the article title, body data, and URL for accepting cooperation of the parent article (posting destination). As a result of step S211, when the article data is not received (S211 → No), the processing unit 100 advances the processing to step S215. As a result of step S211, when the article data is received (S211 → Yes), the processing unit 100 issues a permanent link and a link reception URL for the received article data (S212). Then, the storage processing unit 103 registers the title included in the article data, the body data, the permanent link issued in step S212, the URL for cooperation reception, and the like in the article management data 300 of the article management data 111 (S213).

  At this time, the storage processing unit 103 refers to the parent article cooperation reception URL 312 in the parent article management data 306 registered in step S209, using the parent article cooperation reception URL included in the article data as a key. The titles and body data included in the article data, the reception date and time of the article data, the permanent link issued in step S212, and the URL for cooperative reception are registered in the corresponding fields 301 to 305 of the corresponding article management data 300. Then, the transmission processing unit 102 generates an article application request including the article management data 111 stored in the storage unit 110. Then, the transmission processing unit 102 transmits / receives the article application request generated to the blog server 1 indicated by all the cooperation reception URLs 312 registered in the parent article cooperation reception URL 312 in the parent article management data 306 of the article management data 111. The data is transmitted to the unit 120 (S214).

  Next, the reception processing unit 101 determines whether an article application request has been received from another blog server 1 (S215). As a result of step S215, when the article application request is not received (S215 → No), the processing unit 100 returns to the process of step S201. As a result of step S215, when an article application request is received (S215 → Yes), the processing unit 100 determines whether to approve an article included in the article application request (S216). The approval process may be performed, for example, by a method in which an administrator of a blog published on the blog server 1 examines the content of received article data. When the article is not approved as a result of step S216 (S216 → No), the processing unit 100 proceeds to the process of step S218. That is, the transmission processing unit 102 transmits an article approval result indicating that the article is unapproved to the blog server 1 that is the transmission source of the article application request (S218), and all data included in the article application request determined in step S215. Then, the processing unit 100 returns the process to step S201.

  If the article is approved as a result of step S216 (S216 → Yes), the storage processing unit 103 uses the content of the article management data 111 included in the article application request as the child article management data 307 of the article management data 111 in the storage unit 110. (S217). In step S217, the storage processing unit 103 sets all of the URLs for accepting cooperation stored in the parent article management data 306 in the article management data 111 included in the article application request as a set as the child articles of the child article management data 307. Is stored in the URL 324 for receiving the cooperation of the parent article. Further, the contents of the title 301, the body 302, and the permanent link 304 in the own article management data 300 for which an article application request is being made are stored in the corresponding columns 321 to 323, 325, and 326 of the child article management data 307, respectively. Then, the transmission processing unit 102 transmits the article approval result indicating that the approval is successful to the blog server 1 that is the transmission source of the article approval request (S218), and the processing unit 100 returns the process to step S201.

  In the first embodiment, the article application request transmitted to the blog server 1 that manages the parent article in step S109, step S118 in FIG. 5 and step S214 in FIG. 19 includes the article management data 111. However, the present invention is not limited to this, and a notification that a child article or grandchild article has been posted (that is, an article related to the parent article has been posted) may be transmitted to the blog server 1 that manages the parent article.

  According to the first embodiment, by sending an article application request including the article management data 111 to the blog server 1 that manages the parent article, the notification that the child article or grandchild article has been posted is sent to the parent article. In addition, the blog server 1 managing the parent article can be notified. Thus, the poster of the grandchild article (article C) posts comments on the parent article and the child article to the blog servers 11 and 12 managing the parent article (article A) and the child article (article B). Post the grandchild article (article C) to the blog servers 11 and 12 that manage the parent article (article A) and the child article (article B) with a single notification, without performing notification to the effect This can be notified. In addition, when a hierarchical structure associated with a parent-child relationship between articles occurs, when an article is viewed on the client 2, an article that is higher in the hierarchy and an article that is lower can be displayed on the client 2 at the same time. It becomes easy for the user to follow the same thread. In addition, the user can create a comment article by quoting the body of the article included in the article data by the posting screen including the article data, so it is possible to determine which part of the parent article is the comment when browsing. It can be easily understood.

  Then, by storing the permanent link indicating the parent article data and the permanent link indicating the child article in the storage unit 110 in association with each other, on the browsing screen when browsing the child article, the child article is changed to the parent article. You can put a link. Further, according to the first embodiment, in step S106 in FIG. 5, step S115, and step S207 in FIG. 19, the article relation returned from the blog server 1 that manages the parent article to the blog server 1 that manages the child article. If the user stores the URL for accepting the cooperation of the parent article by including the main body data of the parent article in the data, the user inputs the URL for accepting the cooperation of the parent article to the client 2. The body data of the parent article can be viewed from the blog server 1 managing the blog.

(Second embodiment: hierarchical structure display)
Next, the article management system 4 ′ according to the second embodiment will be described with reference to FIGS. FIG. 20 is a diagram illustrating a configuration example of an article management system according to the second embodiment. In FIG. 20, the same elements as those of FIG. In the second embodiment, each blog server 1 sends the contents of the article management data 111 stored in the storage unit 110 to the electronic bulletin board server (hierarchical structure display device) 5 that shows the information of each article in the thread in a hierarchical structure. Send. The electronic bulletin board server 5 stores the contents of the received article management data 111 in the bulletin board management data of the past part (described later with reference to FIGS. 21 and 22). As will be described later, since the bulletin board management data 911 includes information related to the hierarchical structure between articles, the electronic bulletin board server 5 converts the hierarchical structure between articles to the client 2 based on the stored bulletin board management data. To display.

  20 differs from FIG. 1 in that an electronic bulletin board server 5 is connected to the blog server 1 and the client 2 via the network 3. The electronic bulletin board server 5 manages to display the hierarchical structure of the article data stored in each blog server 1, and when accessed from the client 2, for example, the title related to the article data and the like is related to the parent-child relationship of the article. Accordingly, it has a function of displaying hierarchically.

(Configuration of electronic bulletin board server)
FIG. 21 is a diagram illustrating a configuration example of the electronic bulletin board server according to the second embodiment. The electronic bulletin board server 5 includes a processing unit 900 that processes information, a storage unit 910 that stores information, and a receiving unit 920 that receives information. The processing unit 900 includes a reception processing unit 901, a storage processing unit 902, and an issuing unit 903. The reception processing unit 901 has a function of identifying and determining the type of received data. The storage processing unit 902 has a function of storing data in the storage unit 910. The issuing unit 903 has a function of issuing an electronic bulletin board cooperation reception URL, which is a cooperation reception URL attached to the electronic bulletin board. The storage unit 910 stores bulletin board management data 911. The bulletin board management data 911 will be described later with reference to FIG.

  FIG. 22 is a diagram showing a configuration example of bulletin board management data according to the second embodiment, where (a) shows bulletin board management data, and (b) shows child article management data. As shown in FIG. 22, the bulletin board management data 911 includes an electronic bulletin board cooperation reception URL 912 and child article management data 913. The child article management data 913 includes a child article permanent link 951, a child article cooperation reception URL 952, a child article reception date and time 953, a parent article cooperation reception URL 954 for the child article, a title 955, and a body text 956. is doing. 22 is a child article when the electronic bulletin board is a parent article when the hierarchical structure between articles displayed on the client 2 (see FIG. 20) (hereinafter referred to as an electronic bulletin board) is used. Refers to an article. That is, all articles are child articles when viewed from the electronic bulletin board.

(processing)
Next, the article management system 4 according to the second embodiment along FIG. 23 while referring to FIGS. 4, 6, 8, 10, 11, 14 to 17, 21, and 22 as appropriate. The flow of processing in 'will be described. FIG. 23 is a timing chart showing the flow of processing in the article management system according to the second embodiment. In FIG. 23, the same processing as in FIG. 5 is denoted by the same step number and description thereof is omitted. The processing of the electronic bulletin board server 5 will be described later with reference to FIG. Furthermore, when referring to the article management data 111 in FIGS. 6, 8, 10, 11, and 14 to 17, the code accompanied by “a” at the end is the article management data stored in the blog server 11. 111, the code with “b” at the end indicates the article management data 111 stored in the blog server 12, and the code with “c” at the end indicates article management data stored in the blog server 13. 111 is shown. The issuing unit 903 of the electronic bulletin board server 5 issues a URL for accepting cooperation on the electronic bulletin board prior to processing.

  When a user who posts the first article (parent article) of a thread wants to display his / her own article (article A) in a bulletin board format, for example, from the electronic bulletin board site, the URL for accepting cooperation of this electronic bulletin board Keep getting. Then, when creating the article A, the user creates the article data A to which the URL of the electronic bulletin board is added together with the subject and body text of the article A. In step S <b> 101, the client 21 used by the user transmits this article data A to the blog server 11. The blog server 11 that has received the article data A issues a permanent link (article A permanent link) and a cooperation reception URL (article A cooperation reception URL) for the article data A, similarly to the processing in the first embodiment. The article management data 300 (see FIG. 4A) of the article management data 111 in the blog server 11 stores the subject name of the article A, the body data, the article A permanent link, the URL for receiving the article A cooperation, and the reception date of the article A. To do.

  At this time, the blog server 11 stores the cooperation reception URL of the electronic bulletin board in the parent article cooperation reception URL 312 in the parent article management data 306 (see FIG. 4B). In other words, the article management data 111 of the blog server 11 at this stage is the URL for receiving cooperation of the electronic bulletin board in the column for receiving cooperation of the parent article (not shown) of the parent article management data 306a of the article management data 111a shown in FIG. Records will be added. At this time, the permanent link field of the parent article (not shown) in the parent article management data 306a (see FIG. 6) of the blog server 11 is the electronic bulletin board site displayed on the display unit (not shown) of the client 2 by the electronic bulletin board server 5. Is stored.

  Thereafter, the blog server 11 transmits the article management data 111 stored in the storage unit 110 of the blog server 11 to the cooperation reception URL of the electronic bulletin board, that is, to the electronic bulletin board server 5 (S301). The electronic bulletin board server 5 that has received the article management data 111 from the blog server 11 uses the contents of the article management data 111 (article management data 111 related to article A) transmitted from the blog server 11 as child article management data of the bulletin board management data 911. 913 is stored. A specific procedure will be described later with reference to FIG.

  As described above, the URL for cooperative reception of the electronic bulletin board is stored in the parent article management data 306 (see FIG. 4B) of the article management data 111 of the blog server 11. As described in the first embodiment, when the blog server 1 generates the article-related data to be returned in step S106, if data exists in the parent article management data 306 (see FIG. 4B), The data of the parent article management data 306 is added to the article related data. Accordingly, the article A related data returned in step S106 includes the URL for cooperation reception of the electronic bulletin board.

  Then, when the procedure described in the first embodiment is performed using the article A related data, the article management data 111 in the blog server 12 at the stage of steps S107 and S302 is shown in FIG. 8B and FIG. In FIG. 5B, the URL for cooperation reception of the electronic bulletin board is additionally registered in the field of the URL 312b for cooperation reception of the parent article in the parent article management data 306b of the article management data 111b, and the URL of the electronic bulletin board site is registered in the permanent link 311b of the parent article. The stored record (row) is added. Note that the URL of the bulletin board site may not be stored. Further, the article management data 111 of the blog server 11 at the stage of step S110 is stored in the column of the URL for accepting cooperation of a parent article (not shown) of the parent article management data 306a of the article management data 111a shown in FIG. It is in a format in which a URL for cooperating reception of a bulletin board is additionally registered, and a record in which the URL of the electronic bulletin board site is stored in a permanent link of a parent article (not shown).

  In step S302, the blog server 12 sends an article B application request including the article management data 111 to the blog server 1 indicated by the URL 312 for cooperative reception of the parent article registered in the parent article management data 306 (FIG. 4 (b)). Related article management device information) is transmitted. As described above, since the URL for cooperation reception of the electronic bulletin board is registered in the parent article management data 306 of the blog server 12, the blog server 12 requests the article B application request to the electronic bulletin board server 5 in step S <b> 302. Send.

  The electronic bulletin board server 5 that has received the article B application request performs the same procedure as the registration of the article management data 111 transmitted in step S301 into the bulletin board management data 911, and the contents of the article management data 111 included in the article B application request. Is added to the bulletin board management data 911 as a new record. That is, the electronic bulletin board server 5 adds the content of the article management data 111 regarding the article B to the child article management data 913 of the bulletin board management data 911. At this time, the URL for accepting cooperation of the electronic bulletin board and the URL for accepting cooperation of the article A are registered in the URL 954 for accepting cooperation of the parent article for the child article corresponding to the article B (see FIG. 22B). It becomes.

  Furthermore, since the URL for cooperation reception of the electronic bulletin board is registered in the parent article management data 306 (see FIG. 4B) of the article management data 111 stored in the blog server 12, the article B in step S115 is registered. The related data includes the URL for cooperation reception of the electronic bulletin board in addition to the content of the article B related data described in the first embodiment. As described in the first embodiment, when the blog server 1 generates article-related data, if data exists in the parent article management data 306, the data of the parent article management data 306 is used as the article-related data. By adding to the data.

  Accordingly, in the article management data 111 of the blog server 13 at the stage of step S116, the cooperation reception URL 312c of the parent article management data 306c of the article management data 111c shown in FIG. A record in which the URL of the electronic bulletin board site is registered is added to the permanent link 311c of the parent article. The article management data 111 after the article data C is transmitted in step S117 and the blog server 13 registers information such as the subject of the article data C and the article C permanent link is the article management data shown in FIG. In this state, the cooperation reception URL 312c of the parent article in the parent article management data 306c of 111c is additionally registered in the cooperation reception URL of the electronic bulletin board and the URL of the electronic bulletin board site in the permanent link 311c of the parent article.

  In step S303, the blog server 13 posts the article including the article management data 111 to the blog server 1 (in this case, the blog servers 11 and 12) indicated by the URL for accepting cooperation of the parent article registered in the parent article management data 306. Send C application request. At this time, as described above, since the URL for cooperative reception of the electronic bulletin board is registered in the parent article management data 306 of the blog server 13, the blog server 13 also sends the article to the electronic bulletin board server 5 in step S 303. Send C application request.

  The electronic bulletin board server 5 that has received the article C application request performs the same procedure as the registration of the article management data 111 transmitted in step S301 in the bulletin board management data 911, and the article management data 111 included in the article C application request. Is added to the bulletin board management data 911. That is, the electronic bulletin board server 5 adds the content of the article management data 111 regarding the article C to the child article management data 913 of the bulletin board management data 911. At this time, the URL for accepting cooperation of the parent article for the child article corresponding to article C is registered with the URL for accepting cooperation of the electronic bulletin board, the URL for accepting article A cooperation, and the URL for accepting article B cooperation. It becomes.

  The article management data 111 in the blog server 12 after receiving the article C application request and finishing the approval request for the article C (step S119) is the parent article management data 306b shown in FIG. A record in which the cooperation reception URL of the electronic bulletin board is registered in the cooperation reception URL 312b and the electronic bulletin board site URL is registered in the permanent link 311b of the parent article is added. Similarly, the article management data 111 in the blog server 11 after receiving the article C application request and finishing the article C approval request (step S120) is the parent article management data 306a shown in FIG. A record in which an electronic bulletin board cooperation reception URL is registered in a parent article cooperation reception URL (not shown) and an electronic bulletin board site URL is registered in a parent article permanent link (not shown) is added.

  Next, a specific example of the bulletin board management data 911 at the time when step S120 in FIG. 23 is completed will be described with reference to FIG. FIG. 24 is a diagram showing a specific example of bulletin board management data according to the second embodiment, where (a) shows bulletin board management data, and (b) shows child article management data. As shown in FIG. 24A, in the field of the electronic bulletin board cooperation reception URL 912 of the bulletin board management data 911, the cooperation reception URL of the electronic bulletin board is registered. Here, a common URL for cooperative reception is registered for all threads. Then, in the child article permanent link 951 of the child article management data 913, in the record of the article A permanent link, the article A cooperation reception URL is registered in the child article cooperation reception URL 952, and the date and time 953 includes the article A. The article management data reception date and time is registered. Furthermore, the URL for cooperation reception of the electronic bulletin board is registered in the URL 954 for cooperation reception of the parent article for the child article. Further, the title 955 registers the subject name of the article A, and the text 956 registers the text data of the article A.

  Similarly, if the permanent link 951 of the child article in the child article management data 913 is the record of the article B permanent link, the article B cooperation reception URL is registered in the child article cooperation reception URL 952, and the date and time 953 contains the article. The article application date and time of B is registered. In addition, in the URL for accepting cooperation of parent articles for child articles 954, the URL for accepting cooperation of electronic bulletin boards and the URL for accepting article A cooperation are registered as a set. The title 955 registers the subject of article B, and the text 956 registers the text data of article B.

  In a record in which the child article permanent link 951 of the child article management data 913 is an article C permanent link, the article C cooperation reception URL is registered in the child article cooperation reception URL 952, and the article 95 The article application date and time of C is registered. In addition, in the URL for accepting cooperation of the parent article for the child article 954, the URL for accepting cooperation of the electronic bulletin board, the URL for accepting the article A cooperation, and the URL for accepting the article B are registered as a set. The title 955 registers the subject of the article C, and the text 956 registers the text data of the article C.

  Here, as indicated by reference numeral 961, the cooperation reception URL of the electronic bulletin board is registered in the parent article cooperation reception URL 954 for the child article A. This indicates that the article A is a child article of the electronic bulletin board, that is, the highest article (parent) article in the hierarchical structure between articles. As indicated by reference numeral 962, the URL for accepting cooperation of the parent article for child article B 954 registers the URL for accepting cooperation of the electronic bulletin board and the URL for accepting article A cooperation. This indicates that the article B is a child article of the article A. As indicated by reference numeral 963, the URL for accepting cooperation of the parent article for child article C 954 is registered with the URL for accepting cooperation of the electronic bulletin board, the URL for accepting article A cooperation, and the URL for accepting article B cooperation. ing.

  Here, for example, in FIG. 24 (b), in the field of reference numeral 963, the URL for cooperation reception of the electronic bulletin board, the URL for article A cooperation reception, and the URL for article B cooperation reception are registered as a set. However, with this information alone, it is unclear whether article C is a child article of article A but a child article of article B, so the processing unit 900 of the bulletin board server 5 refers to the column 962. To do. Then, since information indicating that the article B is a child article of the article A is known from there, the electronic bulletin board server 5 determines that the article C is a child article of the article B and is a grandchild article of the article A. In this way, information related to the hierarchical structure between articles is registered in the bulletin board management data 911. When article C has two parent articles, that is, for example, (article C → article B, and at the same time article C → article A, the permanent link 951 of the child article is the article C permanent. There are two linked records, and the URL for receiving the cooperation of the parent article for the child article in each record is “URL for receiving the cooperation of the electronic bulletin board, URL for receiving the article A cooperation” and “Linking the electronic bulletin board” "Reception URL, Article B Cooperation Reception URL".

(Blog server processing)
Processing in the blog server 1 according to the second embodiment will be described along FIG. 25 with reference to FIG. FIG. 25 is a diagram showing a flow of processing in the blog server according to the second embodiment. In FIG. 25, the same processes as those in FIG. 19 are denoted by the same reference numerals as those in FIG. The article data received in step S202 includes the URL for cooperation reception of the electronic bulletin board entered by the user who created the article data, together with the article title (title) and body text data. Then, after the processing of step S204, the storage processing unit 103 registers the cooperation reception URL of the electronic bulletin board included in the article data in the parent article cooperation reception URL 312 (see FIG. 4B) (S401). At this time, the storage processing unit 903 may register the URL of the electronic bulletin board site in the permanent link 311 of the parent article. At this time, the storage processing unit 103 and the transmission processing unit 102 send the article management data 111 to the cooperation reception URL of the electronic bulletin board in the cooperation reception URL 312 of the parent article in the article management data 111, that is, to the electronic bulletin board server 5. Is transmitted to the transmission / reception unit 120 (S402).

  In step S401, since the URL for receiving cooperation of the electronic bulletin board is registered in the URL 312 for receiving cooperation of the parent article in the article management data 306 of the parent article management data 111, it is received in the step S208. The article-related data includes data of URL 312 for accepting cooperation of a parent article corresponding to a parent article of an article managed by the blog server 1 of the transmission source. This data includes a URL for accepting cooperation on the electronic bulletin board. Then, since the content of the article related data is registered in the parent article management data 306 (see FIG. 4B) of the child article in step S209, all the child articles, grandchild articles,. In the parent article management data 306, the parent article cooperation reception URL 312 field has the electronic bulletin board cooperation reception URL.

  After step S 213, the transmission processing unit 102 transmits all the cooperation reception URLs registered in the parent article cooperation reception URL 312 in the parent article management data 306 (see FIG. 4B) of the article management data 111. Is transmitted to the blog server 1 indicated by Here, as described above, when the parent article is posted, the parent stored in the storage unit 110 of all the blog servers 1 that manage articles related to the article for which the URL for accepting cooperation on the electronic bulletin board is input. Since the cooperation reception URL of the electronic bulletin board is registered in the article cooperation reception URL 312 (see FIG. 4B), the article application request is also transmitted to the electronic bulletin board server 5 (S403).

(Processing of the electronic bulletin board server)
Next, the flow of processing in the electronic bulletin board server 5 according to the second embodiment will be described along FIG. 26 with reference to FIGS. FIG. 26 is a flowchart showing the flow of processing in the electronic bulletin board server according to the second embodiment. First, the reception processing unit 901 of the electronic bulletin board server 5 determines whether an article application request has been received from the blog server 1 (S501). If the article application request has not been received as a result of step S501 (S501 → No), the reception processing unit 901 receives the article management data 111 including the title, the body data, the permanent link, and the link reception URL from the blog server 1. It is determined whether or not (S502). At this time, the article management data 111 includes a URL for cooperative reception of the electronic bulletin board. If the article management data 111 has not been received as a result of step S502 (S502 → No), the processing unit 900 returns the process to step S501.

  When the article management data 111 is received as a result of step S502 (S502 → Yes), the storage processing unit 902 registers the contents of the article management data 111 (see FIG. 4) received in the following procedure in the bulletin board management data 911. (S503). That is, the storage processing unit 902 registers the data of the title 301 and the text 302 in FIG. 4A in the title 955 and the text 956 in FIG. Then, the storage processing unit 902 registers the data of the permanent link 304 and the cooperation reception URL 305 in FIG. 4A in the child article permanent link 951 and the child article cooperation reception URL 952 in FIG. Further, the storage processing unit 902 registers all data in the parent article cooperation reception URL 312 in FIG. 4B in the parent article cooperation reception URL 954 for the child article in FIG. 22B. Here, since only the URL for cooperation reception of the electronic bulletin board is registered in the URL 312 for receiving the cooperation of the parent article in the received article management data 111, the cooperation of the parent article to the child article in FIG. In the reception URL 954, the cooperation reception URL of the electronic bulletin board is registered. Further, the storage processing unit 902 registers the reception date / time of the article management data 111 in the date / time 953.

  As a result of step 501, when the article application request including the article management data 111 of the transmission source blog server 1 is received (S501 → Yes), the storage processing unit 902 includes the article management data included in the article application request. The contents of 111 are registered in the bulletin board management data 911. Specifically, the storage processing unit 902 performs bulletin board management on the data in each column 301, 302, 304, 305 of the own article management data 300 of the article management data 111 included in the article application request in the same procedure as in step S502. The data 911 is additionally registered as a new record in the corresponding fields 951, 952, 955, and 956 of the child article management data 913, and the reception date and time of the article management data 111 is additionally registered in the date and time 953. Further, the storage processing unit 902 sets all the link reception URLs registered in the link reception URL 312 of the parent article management data 306 (see FIG. 4B) of the received article management data 111 as a set. Then, it is registered in the bulletin board management data 911 (S504). Specifically, the storage processing unit 902 registers the parent article cooperation reception URL 954 for the child article of the child article management data 913 (see FIG. 22B).

Next, an example of an electronic bulletin board screen by the electronic bulletin board server 5 according to the second embodiment will be described along FIG. 27 with reference to FIGS. FIG. 27 is a diagram showing an example of an electronic bulletin board screen by the electronic bulletin board server according to the second embodiment. The electronic bulletin board screen (hierarchical image display screen) 1000 shown in FIG. 27 is displayed as a result of a browsing request sent from the client 2 to the electronic bulletin board server 5 after the processing of step S120 in FIG. It is an example of a screen displayed on the section.
As shown in FIG. 27, the electronic bulletin board server 5 uses the electronic bulletin board screen based on the hierarchical structure between articles stored in the URL 954 for cooperative reception of the parent article for the child article in the child article management data 913 in the storage unit 910. In 1000, a hierarchical structure between articles such as article A, article B, and article C (parent-child relationship between articles) is displayed on a display unit (not shown) of the client 2. At this time, the cooperation reception URL saved in the parent article cooperation reception URL 954 for the child article also has a function as an article identifier. That is, when browsing the blog on the client 2, the client 2 acquires the parent article data by following the URL for cooperative reception.

  According to the second embodiment, the hierarchical structure of articles can be displayed in a format that is easy to visually recognize.

  The processing unit 100, the transmission / reception unit 120, and each unit 101 to 106 in the blog server 1 illustrated in FIG. 2, and the processing unit 900, the reception unit 920, and each unit 901 to 903 illustrated in FIG. ) Or a program stored in an HD (Hard Disk) (not shown) is developed in a RAM (Random Access Memory) (not shown) and executed by a CPU (Central Processing Unit) (not shown).

  In this embodiment, the system for managing articles in a blog is targeted. However, the present invention is not limited to this, and any CMS (Contents Management System) may be used. That is, the blog server 1 does not have to be, and may be a server that manages a system using CMS and articles in the CMS. In the present embodiment, the article application request includes the article management data 111. However, the present invention is not limited to this, and the URL for receiving the cooperation of the own article and the URL for receiving the cooperation of the parent article of the own article are paired. As information, you may include an article application request.

It is a figure which shows the structural example of the article management system which concerns on 1st Embodiment. It is a figure which shows the structural example of the blog server which concerns on 1st Embodiment. It is a figure which shows the outline of the article management method in this embodiment. It is a figure which shows the structural example of the article management data in this embodiment, (a) shows the structural example of article management data, (b) shows the structural example of parent article management data, (c), The structural example of child article management data is shown. It is a timing chart which shows the flow of processing in the article management system concerning a 1st embodiment. It is a figure which shows the structural example of the article management data in the blog server 11. It is a figure which shows the example of the display screen in a client. It is a figure which shows the structural example of the article management data in the blog server 12, (a) shows the structure of article management data, (b) shows the structure of parent article management data. It is a figure which shows the example of the display screen in a client. It is a figure which shows the structural example of the article management data in the blog server 12, (a) shows the structure of article management data, (b) shows the structure of parent article management data. It is a figure which shows the structural example of the article management data in the blog server 11, (a) shows the structure of article management data, (b) shows the structure of child article management data. It is a figure which shows the example of the display screen in a client. It is a figure which shows the example of the display screen in a client. It is a figure which shows the structural example of the article management data in the blog server 13, (a) shows the structure of article management data, (b) shows the structure of child article management data. It is a figure which shows the structural example of the article management data in the blog server 13, (a) shows the structure of article management data, (b) shows the structure of child article management data. It is a figure which shows the structural example of the article management data in the blog server 12, (a) shows the structure of article management data, (b) shows the structure of parent article management data, (c) is a child article. The structure of management data is shown. It is a figure which shows the structural example of the article management data in the blog server 11, (a) shows the structure of article management data, (b) shows the structure of child article management data. It is a figure which shows the example of the display screen in a client. It is a flowchart which shows the flow of a process of the blog server which concerns on 1st Embodiment. It is a figure which shows the structural example of the article management system which concerns on 2nd Embodiment. It is a figure which shows the structural example of the electronic bulletin board server which concerns on 2nd Embodiment. It is a figure which shows the structural example of the bulletin board management data which concerns on 2nd Embodiment, (a) shows bulletin board management data, (b) shows child article management data. It is a timing chart which shows the flow of processing in the article management system concerning a 2nd embodiment. It is a figure which shows the specific example of the bulletin board management data which concerns on 2nd Embodiment, (a) shows bulletin board management data, (b) shows child article management data. It is a figure which shows the flow of the process in the blog server which concerns on 2nd Embodiment. It is a flowchart which shows the flow of the process in the electronic bulletin board server which concerns on 2nd Embodiment. It is a figure which shows the example of an electronic bulletin board screen by the electronic bulletin board server which concerns on 2nd Embodiment.

Explanation of symbols

111-13 Blog server (article management device)
2, 21-23 Client 3 Network 4 Article management system 5 Electronic bulletin board server (hierarchical structure display device)
100 processing unit (blog server)
101 Reception processing unit (blog server)
102 transmission processing unit 103 storage processing unit (blog server)
104 Acquisition unit 105 Issuing unit (blog server)
106 Blog Processing Unit 110 Storage Unit (Blog Server)
111, 111a-111c Article management data 120 Transmission / reception unit 300, 300a-300c Own article management data 301, 301a-301c Title (article management data)
302, 302a-302c Full text (article management data)
303, 303a to 303c Date and time (article management data)
304, 304a to 304c Permanent link (article management data)
305, 305a to 305c Cooperation acceptance URL (article management data)
306, 306a-306c Parent article management data 307, 307a Child article management data 311, 311b, 311c Permanent link URL of parent article
312, 312 b, 312 c URL for accepting cooperation of parent article
321, 321 a, 321 b Permanent link of child article (article management data)
322, 322a, 322a URL for receiving cooperation of child articles (article management data)
323, 323a, 323b Date and time (article management data)
324, 324a, 324b URL for receiving cooperation of parent article for child article (article management data)
325, 325a, 325b Title (article management data)
326, 326a, 326b Full text (article management data)
400 Blog A display screen 500 Post screen 600 Article A display area 610 Article B display area 700 Article B display area 800 Article A display area 810 Article B display area 820 Article C display area 900 Processing unit (electronic bulletin board server)
901 Reception processing unit 902 Storage processing unit (electronic bulletin board server)
903 Issuer (electronic bulletin board server)
910 Storage unit (electronic bulletin board server)
911 Bulletin board management data 912 URL for accepting cooperation of electronic bulletin boards
913 Child article management data 920 Receiver 951 Child article permanent link (bulletin board management data)
952 URL for child article cooperation reception (bulletin board management data)
953 Date and time (bulletin board management data)
954 URL for parent article cooperation reception for child articles (bulletin board management data)
955 Title (bulletin board management data)
956 Text (Bulletin Board Management Data)
1000 Electronic bulletin board screen

Claims (8)

An article management method for an article management system comprising a plurality of article management devices for managing articles posted via a network,
The processing unit of the first article management apparatus includes:
When a posting request for the first article data, which is article data related to a predetermined article, is received from the client,
A processing unit of a second article management device that manages second article data that is data of the predetermined article;
The identification information of the second article management apparatus and the identification information indicating the third article management apparatus that manages the third article data associated with the second article data are used as the first article management. To the device,
The processing unit of the first article management device includes:
Storing the received identification information of the second article management device and the identification information of the third article management device in the storage unit;
When receiving the first article data from the client,
With reference to the identification information of the second article management device and the identification information of the third article management device stored in the storage unit,
An article management method, comprising: sending a notification that a posting related to the second article data has been made to the second article management apparatus and the third article management apparatus. The processing unit of the first article management apparatus that has received the first article data,
The received first article data is stored in a storage unit in association with article data related to the first article data,
When receiving a display request for article data related to the first article data from the client,
A screen that associates and displays the first article data and article data related to the first article data is generated, and the screen is displayed on a client that has requested the display request. The article management method according to 1. The processing unit of the first article management apparatus that manages the first article data includes:
Before sending the first article data to the second article management device and the third article management device,
Receiving at least one of the second article data and the first article data from the second article management device;
Generating an edit screen of article data including the received article data;
Display the generated edit screen on the client that requested the display request,
The article management method according to claim 1, wherein article data edited on the editing screen displayed on the client is received as first article data. The identification information of the article management device indicates a fixed link indicating a storage area of the article data managed in the article management device,
The processing unit of the first article management device includes:
When receiving the first article data from the client,
A first fixed link is generated for the received first article data, and the generated first fixed link is assigned to the first article data.
The second fixed link attached to the article data related to the first article data stored in the storage unit of the article management apparatus is associated with the generated first fixed link and stored. Remember in the department,
When an article data browsing request is received from a client, a screen that displays all the fixed links of article data stored in the storage unit is displayed, and the generated screen is displayed on the client that requested the browsing. The article management method according to any one of claims 1 to 3, wherein the article management method is characterized. The article management system further includes a hierarchical structure display device that displays a hierarchical structure between articles,
The processing unit of the first article management device includes:
Identification information indicating the first article management device when a notification that the posting related to the second article data has been made is transmitted to the second article management device and the third article management device. And related article management device information having a pair of identification information indicating the second article management device and transmitting to the hierarchical structure display device,
The processing unit of the hierarchical structure display device includes:
When the related article management device information is received from a plurality of the first article management devices, the identification information indicating the second article management device is used as information related to a higher level article, and the first article management device is As the identification information indicating the information related to the lower article, each of the related article management device information is stored in the storage unit,
Upon receiving a display request for a hierarchical structure between articles from the client, information related to the upper article and information related to the lower article are displayed based on each of the related article management device information stored in the storage unit. The article management method according to any one of claims 1 to 3, wherein a hierarchical structure display screen to be displayed is displayed on the client.   An article management program that causes a computer to execute the article management method according to any one of claims 1 to 5. An article management system comprising a plurality of article management devices for managing articles posted via a network,
The article management system includes at least a first article management apparatus, a second article management apparatus, and a third article management apparatus,
The first article management device comprises:
When a posting request for the first article data, which is article data related to a predetermined article, is received from the client,
A second article management device that manages second article data that is data of the predetermined article;
The identification information of the second article management apparatus and the identification information indicating the third article management apparatus that manages the third article data associated with the second article data are used as the first article management. To the device,
The first article management device is
Storing the received identification information of the second article management device and the identification information of the third article management device in the storage unit;
When receiving the first article data from the client,
With reference to the identification information of the second article management device and the identification information of the third article management device stored in the storage unit,
An article management system, wherein a notification that a posting related to the second article data has been made is transmitted to the second article management apparatus and the third article management apparatus. The article management system further includes a hierarchical structure display device that displays a hierarchical structure between articles,
The first article management device includes:
Identification information indicating the first article management device when a notification that the posting related to the second article data has been made is transmitted to the second article management device and the third article management device. And related article management device information having a pair of identification information indicating the second article management device and transmitting to the hierarchical structure display device,
The hierarchical structure display device includes:
When the related article management device information is received from a plurality of the first article management devices, the identification information indicating the second article management device is used as information related to a higher level article, and the first article management device is As the identification information indicating the information related to the lower article, each of the related article management device information is stored in the storage unit,
Upon receiving a display request for a hierarchical structure between articles from the client, information related to the upper article and information related to the lower article are displayed based on each of the related article management device information stored in the storage unit. The article management system according to claim 7, wherein a hierarchical structure display screen is displayed on the client.

Images