JP4807048B2 - Content creation date management program and method and apparatus - Google Patents

Description

  The present invention relates to the field for generating the creation date of content.

Now that the Internet and intranets have been developed, there are a great number of cases where information required by individuals is searched from the Internet by using a technology such as a search engine. However, many people are confused as to whether the information they have found can be trusted. For example, even if a solution for a software problem is found on the Internet, it is difficult to determine whether the method is still effective. In such a case, it is helpful to determine if there is date information that created the page in the page, but the Web page or content does not necessarily have a creation date or an update date (hereinafter, the creation date includes the update date). It was not described, and there was no way for the user to know the creation date.
JP 2000-155731 A

  The creation date of a page on the Web is a very important factor in determining the reliability of information on the page, but the creation date is not necessarily described in the Web page or content. If the date is not written, the user has no way of determining whether the information on the page is new or old, and the credibility of the information becomes suspicious.

  Also, with existing RSS services (for example, services provided at http://myrss.jp and http://www.hatena.ne.jp), all pages to be monitored are cached, and advertisements and other pages If there is any change, it has a mechanism to report it as difference information. However, this mechanism results in a huge number of pages to be chushed.

  Therefore, the purpose is to present the creation date of the page to the user even if the creation date is not explicitly written in the page to be monitored. A further object of the present invention is to create a DB comprising a set of URL and creation date in the page so that a page to be cached is unnecessary.

The first invention of the present application creates a link table 1 composed of links extracted from Web pages (hereinafter referred to as update pages) designated by a user who summarizes information of update pages and extracted dates, and periodically updates them. A link table creation unit for creating a link table 2 composed of links extracted from pages and extracted dates;
When there is a difference between the link table 1 and the link table 2, a creation date acquisition unit that determines a date of comparison as a creation date;
It has a creation date table creation unit that creates a creation date table including a link destination pointed to by a link table having a difference from the determined creation date.

The second invention of the present application obtains RSS1 obtained by converting RSS to a Web page (hereinafter referred to as update page) designated by a user who summarizes update page information, and periodically obtains RSS2 obtained by converting the update page into RSS. And
When there is a difference between the RSS1 and the RSS2, the creation date acquisition unit that determines the date of comparison as the creation date;
It has a creation date table creation unit that creates a creation date table composed of the determined creation date and the URL indicated by the RSS having a difference.

  The third invention of the present application is characterized in that the update page is a page in which the creation date of the content is not described.

  The fourth invention of the present application further includes a search unit that searches the creation date table for a specified URL and obtains the creation date.

  Even if the content creation date is not explicitly written in the Web page, the content creation date can be obtained.

  Further, even if the content creation date is not explicitly written in the Web page, such a page can be searched using the content creation date as a key.

  In the conventional technology, if there is a creation date in the Web page, that date is adopted as the RSS item publication. If there is no creation date, the accessed date is adopted as the publication. Since the creation date of the content corresponding to the item can be specified, an RSS in which the creation date of the item is guaranteed can be output.

  Further, unlike the existing RSS service, a page to be crushed can be made unnecessary.

  FIG. 1 is a configuration diagram of an embodiment of the present invention. The present invention includes a content creation date management device 1, a Web server 20, and a user terminal 21. The content creation date management device 1 includes a page access unit 2, an RSS generation unit 3, a creation date acquisition unit 4, a creation date table creation unit 5, a search unit 6, an RSS storage unit 7, a creation date table storage unit 8, and a link table creation. Section 13 and a link table storage section 17.

  The page access unit 2 is a processing unit that accesses, via a network, the Web server 20 that manages a Web page having a URL specified by the user when specified by the user or periodically. This Web page is premised on a page that summarizes information of update pages such as the top page of the target site, the “What's New” page, the new arrival information page, and the link of this page points to each content page ( FIG. 1). Hereinafter, this Web page is simply referred to as an update page.

  The RSS conversion unit 3 is a processing unit that converts the update page into RSS to obtain RSS (Really Simple Syndication, Rich Site Summary). The technology for converting the update page into RSS uses an existing technology. The update page is assumed to be a page on which the creation date of content (hereinafter including the creation date and time) is not described, but may be a page on which the creation date is described. For pages where the date of creation of content is not described, specify the portion of the target page to be converted to RSS, such as tag repetition and rules, and use existing technology (for example, Japanese Patent Application No. 2005-053696) to convert it to RSS. Also good.

  The creation date acquisition unit 4 is newly obtained by accessing the update page designated by the user previously and RSS (hereinafter referred to as RSS1) stored in the RSS storage unit 7 and periodically accessing the update page. This is a processing unit that compares RSS (hereinafter referred to as RSS2) and, when there is a difference between RSS1 and RSS2, regarding the RSS item tag that has changed, determines that the date of comparison is “publish”. “Pubdate” is the date when the page is first published on the Web, and is synonymous with the creation date. In addition, a link table (hereinafter referred to as link table 1) that has been previously accessed by the user and specified in the link table storage unit 17 by accessing the update page designated by the user, and a link obtained by periodically accessing the update page. This is a processing unit that compares a table (hereinafter referred to as the link table 2) and determines the date of comparison with the link table that has changed as a publication.

  The creation date table creation unit 5 creates or updates a creation date table including the creation date determined by the creation date acquisition unit 4 and the URL pointed to by the rdf tag in the item tag that has changed, and the creation date table storage unit 8 is a processing unit to be stored. In addition, it is a processing unit that creates or updates a creation date table including the creation date determined by the creation date acquisition unit 4 and the URL indicated by the link table that has changed, and stores the created date table in the creation date table storage unit 8.

  The retrieval unit 6 reads the creation date table from the creation date table storage unit 8 when the user designates the URL of the page for which the user wants to know the creation date from the user terminal 21, searches the designated URL, and creates the creation date. Is a processing unit for obtaining

  The RSS storage unit 7 is a storage unit that stores the RSS created by the RSS conversion unit 3.

  The creation date table storage unit 8 is a storage unit that stores the creation date table created by the creation date table creation unit 5.

  The link table creation unit 13 is a processing unit that extracts all the links from the update page, creates or updates a link table including the extracted links and dates, and stores them in the link table storage unit 17.

  The link table storage unit 17 is a storage unit that stores the link table created by the link storage unit 13.

  Hereinafter, an embodiment of the present invention will be described with reference to a flowchart (FIG. 2).

  First, the page access unit 2 accesses an update page designated by the user (FIG. 3), and the RSS conversion unit 3 obtains RSS (RSS1) (FIG. 4) obtained by converting the update page into RSS and stores it in the RSS storage unit 7. (S1). At this time, the link destination page of the RSS item tag is not saved. FIG. 5 shows a data structure when the RSS of FIG. 4 is stored. When the page of FIG. 3 is converted to RSS, items under “topics” in the middle of FIG. 3 are listed as RSS elements (FIG. 4).

  And the page access part 2 accesses the same update page regularly (for example, every day), and the RSS conversion part 3 converts the update page into RSS and obtains RSS (RSS2) (S2). FIG. 7 shows the RSS when the update page of FIG. 3 is updated as shown in FIG.

Then, the creation date acquisition unit 4 compares RSS1 and RSS2 stored in the RSS storage unit 7 (S3), and if there is a difference between RSS1 and RSS2, the comparison is performed on the item tag that has changed. The date of execution is determined as “pubdate” (S4). FIG. 8 shows the difference between RSS1 and RSS2.
http://www.mhlw.go.jp/bunya/kodomo/topics02/index.html
The creation date is determined as the date of comparison.

  Then, the creation date table creation unit 5 creates or updates a creation date table (FIG. 9) including the determined creation date and the URL pointed to by the changed item tag, and stores it in the creation date table storage unit 8. , RSS2 is copied to RSS1, RSS1 is updated and stored in the RSS storage unit 7 (S5), and the process returns to S2.

  On the other hand, when the URL of the page for which the user wants to know the creation date is sent from the user terminal 21, the retrieval unit 6 reads the creation date table from the creation date table storage unit 8, and searches the creation date table from the URL. To obtain the corresponding creation date and return the creation date to the user.

  Next, an embodiment that does not use RSS will be described.

  First, the page access unit 2 accesses an update page designated by the user, the link table creation unit 13 extracts all links from the update page, and a link table (hereinafter referred to as link table 1) composed of the extracted links and the extracted dates. And stored in the link table storage unit 17.

  The page access unit 2 accesses the same update page periodically (for example, every day), and the link table creation unit 13 creates the link table 2 in the same manner.

  Then, the creation date acquisition unit 4 compares the link table 1 and the link table 2 stored in the link table storage unit 17, and if there is a difference between the link table 1 and the link table 2, there is a change. Regarding the link, the date on which the comparison was made is determined as “pubdate”.

  Then, the creation date table creation unit 5 creates or updates a creation date table composed of the determined creation date and the URL pointed to by the changed link table, stores it in the creation date table storage unit 8, and stores the link table 2. Is copied to the link table 1, the link table 1 is updated and stored in the link table storage unit 17, and the process returns to S2.

  In addition, the following applications using the present invention can be considered.

(1) Application to a search engine A current general Web search engine can have a date when contents are collected, but cannot have a creation date (date uploaded to the net). . According to the present invention, since the creation date of the content can be acquired, it is possible to create an index including the date when creating the search index, and rearrange the search result display options in the order of creation date.

(2) Creation of WEB archive It becomes possible to manage accurately in the order of creation date of contents in a web archive project such as an electronic library.

(3) When using content such as a bulletin board as evidence When monitoring a bulletin board or the like with a popular distribution or the like, specifying a creation date for a bulletin board without a creation date may provide evidence.

(Appendix 1) Computer
A link table 1 composed of links extracted from Web pages (hereinafter simply referred to as update pages) designated by a user who summarizes information of update pages and extracted dates is created, and links extracted from the update pages periodically A link table creation unit for creating a link table 2 composed of the extracted dates;
When there is a difference between the link table 1 and the link table 2, a creation date acquisition unit that determines a date of comparison as a creation date;
A creation date table creation unit that creates a creation date table composed of a link destination pointed to by a link table having a difference from the determined creation date;
Content creation date management program characterized by functioning as
(Appendix 2) Computer
An RSS conversion unit that obtains RSS1 obtained by converting a Web page (hereinafter simply referred to as an update page) designated by a user who summarizes information of update pages into RSS, and periodically obtains RSS2 obtained by converting the update page into RSS,
When there is a difference between the RSS1 and the RSS2, a creation date acquisition unit that determines a date of comparison as a creation date;
A creation date table creation unit that creates a creation date table composed of the determined creation date and the URL pointed to by the RSS having a difference;
Content creation date management program characterized by functioning as
(Supplementary note 3) The content creation date management program according to supplementary note 1 or 2, wherein the update page is a page in which the creation date of the content is not described.
(Supplementary note 4) The content creation date management program according to supplementary note 1, 2 or 3, further comprising a retrieval unit for retrieving the creation date by searching the creation date table for a specified URL.
(Supplementary Note 5) The link table creation unit creates a link table 1 composed of links extracted from a Web page (hereinafter simply referred to as an update page) designated by a user who summarizes information of update pages and extracted dates. Creating a link table 2 consisting of links extracted from the update page and extracted dates;
The creation date acquisition unit, if there is a difference between the link table 1 and the link table 2, determining the date of comparison as the creation date;
A step in which the creation date table creation unit creates a creation date table including a link destination pointed to by a link table having a difference from the determined creation date;
A content creation date management method characterized by comprising:
(Appendix 6)
The RSS conversion unit obtains RSS1 obtained by converting the Web page (hereinafter simply referred to as update page) designated by the user who summarizes the information of the update page into RSS, and periodically obtains RSS2 obtained by converting the update page into RSS;
If the creation date acquisition unit compares the RSS1 and the RSS2 and there is a difference, the step of determining the date of comparison as the creation date;
A step in which a creation date table creation unit creates a creation date table including a URL pointed to by the RSS that has a difference from the determined creation date;
A content creation date management method characterized by comprising:
(Supplementary note 7) The content creation date management method according to supplementary note 5 or 6, wherein the update page is a page in which the creation date of the content is not described.
(Supplementary note 8) The content creation date management method according to supplementary note 5, 6 or 7, further comprising a step in which the search unit searches the creation date table for the specified URL to obtain the creation date.
(Additional remark 9) The link table 1 which consists of the link extracted from the Web page (henceforth an update page) designated by the user who summarizes the information of an update page, and the extracted date is created, and it updates regularly from the update page. A link table creation unit for creating a link table 2 composed of the extracted link and the extracted date;
When there is a difference between the link table 1 and the link table 2, a creation date acquisition unit that determines a date of comparison as a creation date;
A creation date table creation unit that creates a creation date table composed of a link destination pointed to by a link table having a difference from the determined creation date;
Content creation date management device (Appendix 10) characterized in that RSS1 obtained by converting a Web page (hereinafter simply referred to as an update page) designated by a user who summarizes information on update pages into RSS is obtained and periodically updated RSS conversion unit for obtaining RSS2 obtained by converting the page into RSS;
When there is a difference between the RSS1 and the RSS2, the creation date acquisition unit that determines the date of comparison as the creation date;
A creation date table creation unit that creates a creation date table composed of the determined creation date and the URL pointed to by the RSS having a difference;
Content creation date management device (Supplementary Note 11) The content creation date management device according to Supplementary Note 9 or 10, wherein the update page is a page in which the creation date of the content is not described.
(Supplementary note 12) The content creation date management apparatus according to supplementary note 9, 10 or 11, further comprising a search unit that searches the creation date table for a specified URL and obtains the creation date.

Diagram flowchart Web page RSS Data structure when saving RSS Updated web page Updated RSS Updated RSS difference Creation date table

Explanation of symbols

2 page access unit 3 RSS conversion unit 4 creation date acquisition unit 5 creation date table creation unit 6 search unit 7 RSS storage unit 8 creation date table storage unit 13 link table creation unit 17 link table storage unit 20 Web server 20

Claims (4)

Computer
An RSS conversion unit that obtains RSS1 obtained by converting a Web page (hereinafter simply referred to as an update page) designated by a user who summarizes information of update pages into RSS, and periodically obtains RSS2 obtained by converting the update page into RSS,
If there is a difference between the RSS1 and the RSS2, there is a creation date acquisition unit that determines the date of comparison as the creation date for the URL indicated by the link tag in the item tag of the RSS 2 that has changed ,
A creation date table creation unit that creates a creation date table that associates the creation date determined by the creation date acquisition unit with the URL indicated by the link tag in the item tag of RSS 2 that has changed ;
Content creation date management program characterized by functioning as The content creation date management program according to claim 1, further comprising a search unit that searches the creation date table for a specified URL to obtain a creation date. Computer
Obtaining RSS1 obtained by converting the Web page (hereinafter simply referred to as an update page) designated by the user that summarizes the information of the update page into RSS, periodically obtaining RSS2 obtained by converting the update page into RSS,
If there is a difference between the RSS1 and the RSS2, the date of comparison is determined as the creation date for the URL indicated by the link tag in the item tag of the RSS2 that has changed.
Creating a creation date table that associates the creation date determined above with the URL indicated by the link tag in the item tag of RSS 2 that has changed ,
Content creation date management method characterized by the above. An RSS conversion unit that obtains RSS1 obtained by converting a Web page (hereinafter simply referred to as an update page) designated by a user who summarizes information of update pages into RSS, and periodically obtains RSS2 obtained by converting the update page into RSS,
If there is a difference between the RSS1 and the RSS2, there is a creation date acquisition unit that determines the date of comparison as the creation date for the URL indicated by the link tag in the item tag of the RSS 2 that has changed ,
A creation date table creation unit that creates a creation date table that associates the creation date determined by the creation date acquisition unit with the URL indicated by the link tag in the item tag of RSS 2 that has changed ;
A content creation date management device characterized by comprising:

Images