JPH1040148A - Home page management system and actual information recording medium therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automate the integrated management of various coordinated home page related data to be made open to the public. SOLUTION: A spread sheet type home page management table 11, a constitution management means 13, and an automatic update control means 14 are provided. In the home page management table 11, set values of terms of validity of actual public offering are held by various coordinated home page related data generated so that they are made open to the public through the Internet. The constitution management means 13 checks the matching of the set values of respective terms of validity in the home page management table 11, copies home page related data meeting a predetermined adjustment conditions, and adjust the home page management table 11. An automatic update control means 14 automatically updates home pages to be opened actually to the public according to the adjusted home page management table 11.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a homepage management system and a recording medium for realizing the same, and more particularly to a homepage management system for automating management of a homepage published on the Internet and a recording medium for realizing the same.

[0002]

2. Description of the Related Art In recent years, a world wide computer network called "Internet" has become widely known. Along with this, an information group commonly called a "homepage" is provided on a "server" which is a computer system connected to the Internet,
The number of companies and individuals who want to release various information such as product guides and personal opinions to the whole world is increasing rapidly.
Originally, "homepage" means WW on the Internet
HTML (H) obtained from W (World Wide Web) site
This is the first "page" when an HTML text file described in HyperText Markup Language) is displayed by a predetermined browser, but from now on, the above-mentioned HTML text file and other associated other Now refers to a collection of information such as image files and audio files. Recently, various tools that can easily create such a homepage have been provided, and the amount of information contained in a homepage opened by one company or one individual has been increasing.

By the way, once a home page is created, it becomes obsolete with the passage of date and time, so it is necessary to update the home page little by little. And, in the management work to keep the homepage always up-to-date, in addition to updating the image file or audio file which is the component data of the homepage, updating / adding some pages, etc. Also, various operations such as updating the image file or the audio file correctly while constantly synchronizing are required. However, it is quite troublesome to perform such work on a daily basis while checking the contents of a large number of mutually linked files each time. Therefore, a technique for supporting the homepage management work is required.

[0004] An "electronic file device" described in Japanese Patent Publication No. 6-77237 has been known. The "Electronic File System" automatically detects and deletes unnecessary files based on the registration date and storage period recorded together with the file contents, and applies this to the management of homepages. It is possible to do.

[0005]

However, the prior art mentioned above only mentions the automatic deletion of a file, but does not mention the registration of a new file or the update of an existing file. Furthermore, there is no mention of a process in which a hierarchical structure such as version information / page information / component data described later is considered. That is, in the above-described conventional technology, a series of pages (version information) managed by generations
There is no means to set an individual validity period for each of the pages (page information) and image files included in the page (component data), and check the consistency of those validity periods There has been no means for making automatic adjustments or performing automatic updates including additional registration of new component data. Therefore, there have been the following problems with homepage management.

Basically, a user cannot set an individual validity period for each of version information / page information / component data. Even if the setting can be made manually, the system does not perform a check or a guide display, so that the user must always keep track of all other valid periods that are linked to each other. If one page belongs to multiple versions with different validity periods, or if one component data belongs to multiple pages with different validity periods, it is undeniable to check or adjust the consistency of each validity period. Not easy. Even when the user manually sets an individual validity period for each of the version information / page information / component data, the component data such as a homepage actually published on the Internet and image files therein is set to the validity period. It is not easy to add or replace without doubt based on that.

SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to solve the above-mentioned problems, check and adjust consistency of validity periods individually set for each of version information / page information / component data, and actually publish them. It is an object of the present invention to provide a homepage management system capable of easily updating a homepage, and a recording medium for realizing the same.

[0008]

In order to achieve the above object, a homepage management system according to the present invention stores various homepage related data created for a homepage published on a computer network. In a homepage management system that performs unified management, a homepage management table that holds, for each of the homepage-related data, a set value of an effective period to be actually published as the homepage; Check the consistency of the set value of the period, and if there is homepage related data that violates the predetermined adjustment conditions,
A configuration management unit for duplicating the homepage related data and adjusting the homepage management table; and an automatic update control unit for automatically updating the homepage based on the homepage management table adjusted by the configuration management unit. It is a thing.

With this, for each of the given homepage-related data (version information / page information / component data), after the consistency of the validity period set in the homepage management table is automatically checked,
If there is homepage-related data that conflicts with the adjustment conditions,
The homepage related data is appropriately copied, the homepage management table is adjusted, and the homepage actually published is automatically updated based on the homepage management table.

[0010] Further, the realization information recording medium of the homepage management system of the present invention comprises a first program-related file group for realizing the configuration management means, and a second program-related file group for realizing the automatic update control means. Is recorded.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a homepage management system according to the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram showing a basic configuration of an embodiment of a homepage management system according to the present invention.
11 is a homepage management table, 12 is a homepage related data storage unit, 13 is a configuration management unit, and 14 is an automatic update control unit. In the figure, a homepage management table 11 stores page information defining formal configuration information such as the layout of each page constituting a homepage, and constituent data such as substantial image files and audio files belonging to each page. And version information for grouping a plurality of linked pages and managing generations in a table format. The version information / page information / component data are disclosed on the Internet. The expiration date to be published (the disclosure start date to the disclosure end date) is set individually. The configuration management unit 13, which is a main part of the present embodiment, takes in the set value of the validity period defined for each of the above-described version information / page information / component data from the homepage management table 11, and stores all version information / pages. The set value of each validity period is adjusted in accordance with a predetermined validity period adjustment rule so that the inclusion relation between the information / component data becomes mutually consistent. Then, when the set value of the validity period of any page information or component data deviates from the set value of the version information, the page information or component data having the same content is duplicated, and then each is copied. Reset the validity period according to the relevant version information. The automatic update control unit 14 refers to the homepage management table 11 immediately after the reset of the validity period described above, and fetches the validity period set in each of the version information / page information / component data, Based on these validity periods, automatic registration / update / deletion in the homepage-related data storage unit 12 such as page information and component data actually published on the Internet is performed.

FIG. 2 is a diagram conceptually showing a specific example of a link between homepage-related data to be processed by the homepage management system of FIG. 1. Reference numerals 21 and 22 denote group frames representing versions, respectively. 27 is a group frame representing each page, 231, 232, and 262 are image files, 251 is an audio file, and 261 is a moving image file. In the figure, "Version 1" (reference numeral 21) is "Home" (reference numeral 23), "Page 1" (reference numeral 24), and "Pa".
ge 2 "(reference 25)
“Version 2” (reference numeral 22) is “Home” (reference numeral 26), “Page 2” (reference numeral 25), and “Page 3” (reference numeral 27).
It consists of different types of pages. “Home” (reference 2
“Image 1” (reference numeral 231) and “Image 2” (reference numeral 232) of the image file belong to 3), and “Page 2”
(Reference numeral 25) indicates "Voice 1" (reference numeral 2) of the audio file.
51), and “Page 3” (reference numeral 27) includes “Voice 1” (reference numeral 251) of an audio file and “Im” of an image file.
age 2 ”(reference numeral 262) belongs to“ Home ”(reference numeral 26)
Has a configuration in which “Video 1” (reference numeral 261) of the moving image file belongs. The same contents of “Page 2” (reference numeral 25) are included in both “Version 1” (reference numeral 21) and “Version 2” (reference numeral 22), but “Home” (reference numeral 23). ) And "Home" (reference numeral 26)
About "Version 1" (symbol 21) and "Version
2 ”(reference numeral 22), and“ Image 2 ”belonging to“ Home ”(reference numeral 26) and“ Page 3 ”(reference numeral 27).
(Reference numeral 262) has the same contents, but “Home”
“Image 2” belonging to (reference numeral 23) (reference numeral 262)
It is different from the contents. Also, “Page 2” (code 2
5) and “Vid” belonging to “Page 3” (reference numeral 27).
eo 1 "(reference numeral 261) has the same content.

FIG. 3 and FIG. 4 are views showing an example of a homepage management table which defines a link between homepage-related data to be processed by the homepage management system of FIG. FIG. 4 shows the contents of the homepage management table before adjustment, and FIG. 4 shows the contents of the homepage management table after adjustment by the configuration management unit 13.

In FIG. 3, item 31 is a unique target entity name for distinguishing version information / page information / component data from each other, and item 32 is any one of version information / page information / component data. Item 33 is a validity period on the Internet set for each target entity, item 34 is a belonging page indicating all page information to which the corresponding target entity belongs when its type is component data, and item 35 Is the affiliation version that indicates all version information to which the type of the target entity is page information or component data, item 36 is the directory location and file name where the target object is stored, and item 37 is Adjustment of the validity period 33 set for each applicable target entity and belonging version 35 Check flag indicating the presence or absence of sex check, item 38 is a registration flag indicating whether or not to register update homepage based on validity period 33. 3a to 3l are specific table data, respectively.

In the present embodiment, the three-character extension described after the period "." In the target entity name 31 indicates the type of the corresponding file. For example, ".h
“tm” indicates page information, “.snd” indicates an audio file, and “@ 1” immediately before the extension indicates the character described before it. For example, the target entity name “Home@1.htm” in the table data 3i is obtained by updating the file having the same name as the column. This is obtained by updating, and the target entity name 31 “Image2@1.jpg” in the table data 3k
Is the target entity name “Image2.j” in the table data 3c.
pg ”updated, and“ Hom
If "e.htm" is updated, its name will be "Home@2.htm." However, the above description is limited to the case where a file with the same name is saved in another directory, and the updated file is In FIG. 3, the same table data is rewritten. In FIG. 3, the file names corresponding to the target entity names “Home.htm” and “Home@1.htm” are both “Home. htm ", the file corresponding to the target entity name" Home.htm "is located in the directory location" / Ver1 ", the file corresponding to the target entity name" Home@1.htm "is located in the directory location" / Ver2 ", Each is stored.

In the present embodiment, preconditions and adjustment rules for adjusting a homepage management table having an overlapping portion as shown in FIG. 3 are determined as follows.

Prerequisites and Adjustment Rules When attempting to delete certain version information, page information and component data belonging to that version are also subject to deletion. So, before deleting the version information,
The consistency between the validity period set in the version information and the validity period set in the page information and the component data belonging to the version is adjusted.

Preconditions and Adjustment Rules The page information and the file holding the component data belonging to the page are independent of each other. Even if one is deleted, the other remains. Therefore, for the page information and the component data, the consistency of the validity periods set for each is not checked.

Prerequisites and Adjustment Rules In the relationship between version information and page information, or version information and component data, the lower validity period has priority. That is, the release start date of the valid period in the lower page information and the component data is set to a date before the release start date of the valid period in the version information, and the period corresponding to the difference between these different release start dates is Unless any other version information is set as the validity period, the release start date of the validity period in the version information is changed to be earlier in accordance with the release start date of the validity period in the lower page information and the component data. Similarly, a period in which the publication end date of the valid period in the lower page information and the component data is set to a date later than the publication end date of the valid period in the version information, and a period corresponding to the difference between these different publication end dates Is not set as the validity period in any other version information, the release end date of the validity period in the version information is changed down to the lower-level page information and the release end date of the validity period in the component data.

Prerequisites and Adjustment Rules In the above, the release start date of the effective period in the lower page information and the component data is set to a date before the release start date of the effective period in the version information,
In addition, when there is other version information in which a period corresponding to the difference between these different publication start dates is set as a valid period, the valid period is divided. That is, as for the release start date, “the release start date of the validity period in the lower page information and component data” is set as the release start date, and “the release end date of the validity period in the above other versions and the lower page information and the component The first lower-level page information and the component data are generated with the release end date of the release end date of the validity period in the data being the earlier end date, and the “publication start date of the validity period in the version information” is set to The second lower page information and the component data are generated with the release start date and the “disclosure end date of the effective period in the lower page information and component data” as the release end date. In addition, by performing the same processing for the publication end date, the validity period is divided without changing the values of the publication start date and the publication end date set in the initial lower page information and component data. .

For example, the version of the target entity name “Home.htm” (page information) in the table data 3a in FIG. 3 is “Version1.ver”, and the set value of the validity period is “96/96”. 4/14 ”, end date of release“ 96/4/30 ”
It is. On the other hand, the setting value of the validity period of the target entity name “Version1.ver” (version information) in the table data 3g is the release start date “96/4/14” and the release end date “9
6/4/30 ", which is a perfect match, so that the table data 3a can be left as it is and there is no need to change anything.

On the other hand, the set value of the effective period of the target entity name "Image1.gif" (image file) of the table data 3b belonging to the same "Version1.ver" is the release start date "96/4/14",
The publication end date is “May 6, 96”, and the publication end date of the validity period in the lower-level component data “Image1.gif” is “May 5, 96
6 ”is set to a date that is later than the release end date of the validity period in the version information“ Version1.ver ”“ 96/4/30. ”Therefore, applying the prerequisites and adjustment rules described above, The setting value of the release end date of the validity period in “Version1.ver” is set to “May 6/96” to match the release end date of the validity period in the lower-level component data “Image1.gif”. “Vers
The validity period of “ion1.ver” is page information “Home.htm”
Does not completely match the validity period in the above, but there is no problem because the change includes the validity period of the lower page information. Similarly, the setting values of the validity period of the target entity name “Image2.jpg” (image file) of the table data 3c are the release start date “96/4/10” and the release end date “96/4/30”, The release start date “96/4/10” of the validity period in the lower-level component data “Image2.jpg” is the version information “Ve
"Rsion1.ver" validity start date "96/4/1
4 ”. Therefore, applying the prerequisites and adjustment rules described above, the release date of the validity period in the version information“ Version1.ver ”is set to“ 96/4/10 The lower-level component data "Image
2.jpg ”to match the effective start date of the validity period.
By the above change, the set value of the version information "Version1.ver" is changed as table data 3g ₀ in FIG. 4 from the table data 3g in Fig.

The target entity name "Voice1.snd" (audio file) in the table data 3d in FIG. 3 is "Version1.v
er ”and“ Version2.ver ”, and their validity period is the release start date“ 96/4/14 ”and release end date“ 96/6/8 ”. End date of release of validity period in element data “Voice1.snd” “96/6
/ 8 ”is set to a date that is later than the end date of publication of the validity period in the version information“ Version1.ver ”“ 96/4/30. ”Therefore, applying the above prerequisites and adjustment rules, Validity period is "96/4/14" to "96/5/6" and "9
6/4/24 ”to“ 96/6/8 ”Specifically, the former“ Voice1.sn ”belonging to the version information“ Version1.ver ”
Set the validity period for “d” from “96/4/14” to “96/5 /
6 "as table data 3d ₁ was changed to the version information at the same time""The latter belong to the" Vo Version2.Ver
Ice1.Snd "table data 3d replicating, additional registration as table data 3d ₂ for the setting value of the effective period" and 96/4/24 "~" 96/6/8 ". Then, add the public of the validity period in the lower component data of "Voice1.snd" of registered table data 3d ₂ end date "96/6 /
8 ”is set to a date that is later than the release end date of the validity period in the version information“ Version2.ver ”“ 5/31/96 ”. Applying the prerequisites and adjustment rules described above, the version information“ The set value of the publication end date of the validity period in “Version2.ver” is set to “96/6/8” to match the publication end date of the validity period in the lower-level component data “Voice1.snd”.

Similarly, the target entity name “Page2.htm” (page information) in the table data 3f in FIG.
It belongs to both version "ion1.ver" and "Version2.ver", and its validity period is set to the release date "96/4/14",
The release end date is “May 28, 96”. That is, the release end date “96/5/28” of the validity period in the lower page information “Page2.htm” is the version information “Version
1.ver ”is set to a date that is later than the end date of the effective period of“ 96/5/6 ”. Therefore, applying the above preconditions and adjustment rules, the effective period is set to“ 9.
6/4/14 ”to“ 96/5/6 ”and“ 96/4/24 ”to“ 96/5/28 ”Specifically, the version information“ Version1.ve
"the set value of the effective period for the" Page2.htm "former belongs to" the r 96/4/14 "~" 96/5/6 "is changed to as table data 3f _1, at the same time the version information" Vers
replicates for Page2.htm "" the latter of belonging to "the ion2.ver the table data 3f as table data 3f ₂ ·
Additional registration and the setting value of the validity period from “96/4/24”
It should be “96/5/28”.

As described above, when the consistency check and adjustment of the validity period of the target entity registered in the homepage management table are completed, the "completed" check is set in the corresponding check flag 37.

FIG. 5 is a diagram showing an example of the flow of processing by the configuration management means in FIG. 1. The processing for checking and adjusting the validity period of each target entity in the homepage management table described specifically It is a summary of the flow. In the figure, the configuration management unit 13 first refers to the homepage management table 11 stored in the homepage-related data storage unit 12 and checks the check flag 37 for an unchecked target entity for which the “completed” check is not set. The table data is extracted (step 401). Then, referring to the belonging version 35 of the target entity (step 402), it is determined whether the set value of the validity period in the target entity deviates from the set value of the validity period in any version information (step 403). ). If the set value of the validity period in the target entity is also included in the set value of the validity period in any version information (step 403 = No), immediately go to step 4
Jump to 08. In addition, the set value of the release start date of the validity period in the target entity is a date before the set value of the release start date of the validity period in any version information, or the release date of the release period of the validity period in the target entity If the set value is a date later than the set value of the publication end date of the validity period in any of the version information (step 403 = Yes), it is determined whether or not the target entity belongs to a plurality of versions (step 403). Step 40
4).

If it is determined in step 404 that the target entity belongs to only one version (step 40)
At 4 = No), the set value of the validity period in the version information is changed according to the preconditions and adjustment rules described above (step 405), and the process jumps to step 408. If it is determined that the target entity belongs to a plurality of versions (step 404 = Yes), the validity period of the target entity is divided for each version according to the above-described preconditions and adjustment rules, and the same. Duplicate and additionally register the target entity (step 40
6) Further, since the validity period of the target entity currently being checked has been changed by the division, whether the set value of the validity period in the changed target entity deviates from the set value of the validity period in any version information. Then, the process jumps to step 405. In the last step 405, "completed" check is set to the check flag 37 in the table data of the target entity in the homepage management table 11.

The processing of steps 401 to 408 described above is repeated for all target entities registered in the homepage management table 11, including target entities newly divided and additionally registered in step 406. In addition,
The prerequisites and adjustment rules for validity period consistency check and adjustment are not limited to the above-mentioned, and other preconditions and adjustment rules may be applied. For example, in the prerequisites and adjustment rules described above, the lower validity period was prioritized, but instead, the higher validity period was prioritized, and the lower page information and component elements were changed. If data may be registered before the version information, it may be changed so that it does not check whether the release start date of the lower validity period is earlier than the release start date of the validity period of the corresponding version Good. Further, the user may be asked for confirmation when adjusting or changing the validity period of the version.

FIG. 6 is a diagram showing an example of the flow of processing by the automatic update control means in FIG. First, in FIG.
With reference to the homepage management table 11 in the inside (step 501), it is determined whether or not there is a target entity whose validity period has not been checked for all registered target entities for which the “completed” check is not set in the check flag 37. If there is at least one valid entity whose validity period has not been checked (step 502 = Yes), the configuration management unit 13 is activated, and the validity period consistency check and adjustment processing shown in FIG. 5 are performed. Is performed (step 503), and the process proceeds to step 504. If there is no target entity whose validity period has not been checked (step 502 = No), the process immediately jumps to step 504. In step 504, the setting value of the registration flag 38 of the target entity in the homepage management table 11 is referred to, and if "completed" is set (step 504 = Yes), the processing jumps to the homepage deletion processing in step 511 and thereafter. I do.
On the other hand, if “completed” is not set (step 50
4 = No), in order to determine whether or not the target entity should be registered on the homepage, it is determined whether or not the release start date of the validity period in the corresponding table data has passed the current date (step 505), and the current date is not yet determined. Is not reached (step 505 = No), the process ends without doing anything.

If the current date has reached the disclosure start date (step 505 = Yes), it is determined whether or not a higher version to which the target entity belongs has already been registered (step 506). If the higher version is not registered (step 506 = No), a version directory dedicated to the version is created on the server (step 507), and the version information of the corresponding higher version in the homepage management table 11 is stored. After setting “completed” in the registration flag 38 (step 508), the file storing the page information and the component data which are the target entities to be disclosed is registered in the version directory (step 509), and "Completed" is set in the registration flag 38 of the table data corresponding to the entity (step 510), and the home page is updated. If a higher version has already been registered (step 506 = Yes), step 507 is executed.
Skip steps 509 and 5
Execute 10 to update the homepage.

If it is determined in step 504 that "registered" is set in the registration flag 38 of the target entity (step 5)
04 = Yes), it is determined whether or not the current date has passed the publication end date of the validity period in the corresponding table data (step 511). If it has not passed (step 511 = No), nothing is done. The process ends without executing. On the other hand, if the current date has passed the release end date (step 5
11 = Yes), the target entity is deleted from the corresponding version directory on the server (step 51).
Along with 2), the entry of the target entity is deleted from the homepage management table 11 (step 513), and the homepage is updated.

The processing of steps 501 to 513 is
This is repeated for all target entities registered in the homepage management table 11 to complete the update registration of the homepage. Here, the registration flag 38 indicates “completed”.
Is set as a part of the homepage currently open on the Internet, the corresponding table data in the homepage management table 11 cannot be changed.

The first program-related file group for realizing the configuration management means 13 and the second program-related file group for realizing the automatic update control means 14 include, for example, a floppy disk and a CD-ROM. It shall be provided in a form stored as realization information on a recording medium.

[0035]

As described above in detail, according to the homepage management system of the present invention, each of the given homepage-related data (version information / page information / component data) is set in the homepage management table. After the consistency of the validity period is automatically checked, if there is any homepage-related data that violates the adjustment conditions, the homepage-related data is appropriately duplicated and the homepage management table is adjusted. The actually published homepage is automatically updated. Therefore, it is possible to automate the work related to the update of the homepage without requiring the user to know all the validity periods set in the respective homepage-related data that are linked to each other, and to prevent the occurrence of an artificial work error. It is possible to prevent and improve the reliability and to manage the homepage more easily and efficiently than before. Then, it is not necessary to be conscious of the formal configuration information of the homepage, and it is possible to concentrate solely on creating or updating various types of component data corresponding to the actual content of the homepage. It is possible to improve the quality and to improve the efficiency of the creation or update work process. In addition, by actively applying the above-mentioned effects, browsing the homepage by updating it more frequently and more frequently while maintaining the quality of the homepage released to external third parties higher than before Since it is possible to always make the impact received by a third party fresh, the degree of expectation and recognition of the third party with respect to the homepage and its sender can be dramatically increased.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a basic configuration of an embodiment of a homepage management system according to the present invention.

FIG. 2 is a diagram conceptually showing a specific example of a link between homepage-related data to be processed by the homepage management system of FIG. 1;

FIG. 3 is a diagram showing an example of a homepage management table defining a link between homepage-related data to be processed by the homepage management system of FIG. 1;

FIG. 4 is a diagram showing an example of a homepage management table defining a link between homepage-related data to be processed by the homepage management system of FIG. 1;

FIG. 5 is a diagram illustrating an example of a processing flow by a configuration management unit in FIG. 1;

FIG. 6 is a diagram showing an example of the flow of processing by the automatic update control means in FIG.

[Explanation of symbols]

 11 homepage management table 12 homepage related data storage unit 13 configuration management unit 14 automatic update control unit 21, 22 version information 23 to 27 page information 231, 232, 262 image file 251 audio file 261 video file

Claims (2)

[Claims] 1. A homepage management system for integrally managing various linked homepage-related data created for a homepage to be published on a computer network, wherein a validity period to be actually published as the homepage is provided. A homepage management table that holds the set value of each homepage-related data, and a homepage that checks the consistency of the set value of the validity period for each of the homepage-related data in the homepage management table, and that violates a predetermined adjustment condition. When there is related data, a configuration management means for duplicating the homepage related data and adjusting the homepage management table; and automatically updating the homepage based on the homepage management table adjusted by the configuration management means. A homepage management system characterized by providing automatic update control means. 2. The apparatus according to claim 1, wherein a first program-related file group for realizing the configuration management means and a second program-related file group for realizing the automatic update control means are recorded. Realization information recording medium of homepage management system.