JPH05108457A - Hyper text information management device - Google Patents

Abstract

PURPOSE:To provide a hyper text information management device which can easily reuse hyper text information and which can improve the retrieval effi ciency of a reference example. CONSTITUTION:A sample node where hyper text information is recorded is registered in a registration means, and the sample node is designated through a user interface means. A generation means 164 copies the sample node designated through the user interface means, generates a new node, links the new node and the original sample node and generates new hyper text information. A display means 110 displays the content of the new node.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a hypertext information management device for managing information created by nodes and links.

[0002]

2. Description of the Related Art As a conventional hypertext system, "Hypertext: An Introduction and Survey.
Puter, 20, 9, 17-41. Chapel Hill, NC. 1987 ”is known.

For example, the Note Cars System (1985) developed at Palo Alto Research Laboratories of Xerox Co., Ltd.
(Released in March, 2002) treats document editors, graphic editors, graph editors, bitmap editors, etc. that are displayed in windows on the display of personal computers as hypertext nodes (called cards in Note Cars), and We have created an environment in which data such as papers, manuals, teaching materials, etc. can be registered, and such cards can be freely linked by links to form a network and the network can be saved as a file.

The Note Cars link can be placed at any position in all cards as a visualized pointer, or can be saved as an internal attribute of the card without being displayed in the card. Moreover, the user can arbitrarily create a notebook car card or link and register it in the system. In addition, it provides a browse function that visually displays and edits the entire network configuration by filtering by card and link attributes, link direction and depth. Furthermore, it provides a cross-file link mechanism for linking from a card in an independent network in a file unit to a card in a different network. For details on this cross file link mechanism, see "Note.
Cards in a Nutshell.Proceedings of the ACM CHI + GI
Conference pp.45-52) .Toront.1987. ".

Generally, in a hypertext system, information (hypertext information) created by nodes and links includes highly reusable information such as a fixed form. When reusing the highly reusable information, it is necessary to copy the hypertext information. In order to deal with this, some conventional hypertext systems are provided with a copy function in node units or a copy function in hypertext network units.

[0006]

However, although the above-mentioned conventional hypertext system can provide the above-mentioned copy function, copying the information to be reused is as easy as the operation of creating a new node. Since it is not possible, the operability of copying hypertext information was poor.

The hypertext information to be reused is an effective reference case when the desired information is created in the same form. However, in the above-mentioned conventional hypertext system, since it is not possible to efficiently refer to and list reference cases from a form, the operability of searching for reference cases, that is, hypertext information, is poor.

[0008] Therefore, an object of the present invention is to provide a hypertext information management device which can easily reuse hypertext information and improve the reference case retrieval efficiency.

[0009]

In order to achieve the above object, the present invention provides a hypertext information management device for generating and managing hypertext information composed of nodes and links, wherein the hypertext information serving as a template is provided. Registering means for registering a model node that records, user interface means for designating the model node, and transferring the model node designated through the user interface means to create a new node, The new node and the original model node are linked to each other to generate new hypertext information, and display means for displaying the contents of the new node.

[0010]

According to the hypertext information management device of the present invention, the model node in which the hypertext information is recorded is registered in the registration means, and the model node is
Specified via user interface means. The generating means transcribes the template node designated via the user interface means to create a new node, and links the new node and the original template node to generate new hypertext information. To do. Then, the contents of the new node are displayed by the display means.

Therefore, it is possible to easily copy the hypertext information by previously registering the hypertext information to be reused and designating the information by the user interface means.

[0012]

Embodiments of the present invention will be described below with reference to the accompanying drawings.

FIG. 1 is a functional block diagram showing an embodiment of the hypertext information management apparatus according to the present invention.

In FIG. 1, the hypertext information management device is a display device 110 for displaying hypertext.
And a keyboard 120 and a mouse 130 as input devices for inputting various data and commands, and a hypertext file storage unit 1 for storing a hypertext file.
40, a hypertext data management unit 150, and a hypertext system management unit 160.

The hypertext data management unit 150 is
Node data management unit 151, link data management unit 15
2. It has a hypertext file management unit 153. The node data management unit 151 manages data and attributes of the node, such as type, title, content, property, and link. The link data management unit 152 manages data and attributes of links such as types, source nodes, and destination nodes. Hypertext file management unit 15
Reference numeral 3 manages, for example, hypertext file copying, repair, version management, compaction, and the like in units of hypertext files.

Hypertext system management unit 160
Is the node type management unit 161 and the link type management unit 1
A node / link type management unit 163 having 62;
The system management unit 166 includes a system parameter management unit 164 and a system history management unit 165.

The node type management unit 161 manages node types such as document (text) nodes, graphic (sketch) nodes, and graph nodes, and the link type management unit 162 manages link types. is there.

The system parameter management unit 164 manages system variables such as initial values such as the display size of the node and the font type, and the system history management unit 165 manages the node of the node displayed on the display screen. It manages the position and editing history.

The hypertext data management unit 15
0 accesses the hypertext file storage unit 140. In the hypertext system management unit 160,
The node / link management unit 163 and the system management unit 166 exchange necessary data with each other, and these management units perform hypertext data management unit 15 as necessary.
Access 0.

Further, the system parameter management unit 164 is
As shown in FIG. 2, it has a node registration function 210, a menu creation function 220, a node copy function 230, an instance creation function 240, and an instance display function 250. Next, each of these functions will be described with reference to FIG.

(1) Description of the node registration function 210. This is a function to register and manage hypertext information that you want to copy and reuse as a form. In this embodiment, in the node for registering hypertext information, a link icon that visualizes a link pointing to a node registered in association with this node (hereinafter referred to as a registered node) is recorded.

In the example shown in FIG. 2, the node 210A having the node registration function has a hierarchical structure of hypertext information 211 represented by nodes and links, hypertext information 212 consisting of only one node, and nodes and links. The hypertext information 213 of the network structure represented by and is registered respectively.
Also, the node 210A includes hypertext information 211.
Link icon 211A that points to a registered node that is a component of the hypertext information 212, link icon 212A that points to a registered node that is a component of the hypertext information 212, and a registered node that is a component of the hypertext information 213. Link icon 213
A and A are recorded and displayed, respectively.

(2) Explanation of the menu creation function 220. It is a function to create a menu for selecting hypertext information to be copied and reused as a form.
The created menu is provided as a registered node selection menu as a user interface for designating a registered template. In this embodiment, in addition to the function of creating a menu (registered node selection menu) 220A for designating a node to be copied from the title of a registered node registered by the node registration function 210, this registered node selection menu 220A is It also has a function to be incorporated in the "menu for creating nodes".

(3) Description of the node copy function 230. This is a function of copying hypertext information corresponding to a desired item selected from a registered node selection menu as a user interface provided by the menu creation function 220. That is, the designated registered node is copied to create a new node (hereinafter referred to as a copy node). In this embodiment, the registered node 21
When another node is referred to by a link from the registered node such as 1 or the registered node 213, Shallow Copy and Deep Cop
y) two copy functions are provided. The former is a function to copy only the referenced node, and the latter is a function to copy the entire hierarchical structure or network structure from the referenced node. The details of these copy functions will be described later.

(4) Description of the instance creation function 240. From the original hypertext information (registered node) to the hypertext information (copy node) created by being copied by the node copy function 230,
A function to create a link of type Instance (hereinafter referred to as the link "Instance"). In other words, the function to manage by linking between the registered node and the copy node.

(5) Instance display function 250 Hypertext information (copy node) copied and created from the original hypertext information (registered node) by the node copy function 230 is linked by the instance creation function 240. Instanc
The function to display the loops in order according to e ”, that is, the function to refer to and list the copy nodes created based on the registered nodes.

In this embodiment, the display means described above is realized by the display device 110. The registration means, the user interface means, and the generation means described above are each realized by the system parameter management unit 164. Specifically, the registration means corresponds to the node registration function, and the user interface means uses the menu creation function. It corresponds to the registered node menu to be created, and the generation means corresponds to the node copy function and the instance link creation function.

Further, in this embodiment, a node for registering a node is defined as a form box (ForBox), a registered node is defined as a form, and a link pointing from the registered node to a copy node is defined as an instance (Instance).

A form box (Form
The data structure of Box) is shown in FIG. This data structure is
Node title 311, hypertext file information 312 to which it belongs, node content (node content) information 313, node property (node attribute) information 314,
The structure of the form box node record 310 is composed of each entry of the link information 315. Further, the entry of the link information 315 indicates the list information of the registered nodes as the actual link information. As this list information, pointers 321 to 324 to forms (registered nodes) are listed in the order of registration of registered nodes.

Next, FIG. 4 shows the relationship between the form box and the registered node selection menu for selecting a form.

In the example shown in FIG. 4, the form box 400 has a registration node 4 as a report creation form.
10 is a registration node 420 as a weekly report form, and a registration node 430 is a 5W1H
Registered nodes 440 as forms are respectively registered, and further link icons 410A, 420A, 4 which represent links pointing to the respective registered nodes.
30A and 440A are recorded and displayed. The title of the registered node (form) is displayed on each link icon.

From the registered node 410, the node 4
Node 411A corresponding to node 11, node 412A corresponding to node 412, node 413A corresponding to node 413, node 414A corresponding to node 414.
However, each of the nodes 415A corresponding to the node 415 is pointed by a link. In this way, the nodes 411A and 412 are associated with the registered node 410.
A hypertext structure is formed by pointing A, node 413A, and node 414A.

The registered node 410 includes nodes 411-4.
A hypertext structure composed of 15 is recorded. From the node 411, the node 411A is changed to the node 4
12 to node 412A, node 413 to node 413A, node 414 to node 414A,
From the node 415, a node 415A is pointed by a link.

Although not shown in FIG. 4, the node 4
Links from 11A to node 412A, from node 412A to node 413A and node 414A, and from node 413A to node 415A, respectively.

From this state, a registered node selection menu 450 is created as shown in FIG. 4 by performing a predetermined operation to execute the menu creation function.

Next, FIG. 5 shows a menu for selecting a registered node incorporated in a normal "node creation menu".

In the example shown in this figure, when the entry of "Form" 500A of the "node creation menu" 500 is selected, the form entry menu 5 including the title of the node to be the form (registered node) is displayed.
10 is called and displayed as a registered node selection menu. When a desired entry in the form entry menu 510 is selected, the content of the node having the corresponding title is copied by the node copy function of the hypertext system management unit 160.

The "node creation menu" 500 is called when a new node is created.
Specifically, it is the following case. (1) When selecting a character string of a predetermined node and creating a new node based on the character string. (2) When creating and adding a new node in the browser node. (3) When creating a new node from the system menu corresponding to the hypertext file.

Next, the shallow copy function and the deep copy function in the node copy function provided by the system parameter management unit 164 will be described.

First, the deep copy process for copying the structure by following the link will be described with reference to the flowchart shown in FIG.

As shown in FIG. 6, when the user selects a desired entry in the registered node menu, the system parameter management unit 164 creates a new node (step 601) and corresponds to the selected entry. The contents of the registered node to be copied are copied to the newly created node (step 602). Next, a link of the instance type is set up from the registered node to the new node (step 603).

Further, a new other node is created corresponding to the other node pointed to by the link from the registered node (step 604), and the contents of the other node corresponding to the registered node are created. The copied new node is copied (step 605).

After that, a link of the type of instance is established from another node corresponding to the registered node to another new node (step 606), and a link from the new node to another new node (new node A link corresponding to the included hypertext information, that is, a link that is not of the instance type) is provided (step 607).

Next, a specific example of deep copy will be described with reference to FIG.

Here, a case where the registered node 410 of the form box 400 shown in FIG. 4 is deep copied will be described.

First, the user selects "Deep Copy" from the registered node selection menu 450 displayed on the display screen by selecting the entry of "report creation form". Alternatively, when the entry of Deep Copy is selected from the menu 710 for selecting “Shallow Copy”, the system parameter management unit 164
Executes deep copy processing by the following procedure.

(1) Create a new node 720 (contents not copied at this point). This will be the copy node. At this point, nodes 411A-4
15A has not been copied.

(2) The contents of the registration node 410 are copied to the copy node 720. As a result, nodes 721 to 725 corresponding to the contents described in the nodes 411 to 415 are recorded in the copy node 720. At this point, only the copy node 720 has been created.

(3) A link of the instance type is set up from the registration node 410 to the copy node 720.

(4) Corresponding to the nodes 411A to 415A, the nodes 721A to 725A (the contents are not copied at this point) are created. These nodes also become copy nodes. At this time,
From the node 721A to the node 721A in order to reflect the relationship between the nodes 411A to 415A pointed to by the link from the registered node 410 to the copy node.
From node 472A to node 723A and node 72
4A and links from node 7213A to node 725A, respectively (these links are not shown in FIG. 7).

(5) Created copy nodes 721A-7
The contents of the corresponding original nodes (one of the nodes 411A to 415A) are copied to 25A.

In the above (4) and (5), the contents are copied after the copy nodes corresponding to all the original nodes are created. However, the copy node is created for each original node. Then, the contents may be copied.

(6) Copy node 7 from node 411A
21A, node 412A to copy node 722A
, Node 413A to copy node 723A, node 414A to copy node 724A, node 415
A link of type instance is set up from A to the copy node 725A.

(7) A link (not an instance type) is set up from the copy node 720 to the copy nodes 721A to 725A.

That is, from node 721 to copy node 7
21A, from node 722 to copy node 722A,
From the node 723 to the copy node 723A, the node 72
A link of type instance is set up from 4 to the copy node 724A and from the node 725 to the copy node 725A.

Next, the shallow copy processing will be described with reference to the flowchart shown in FIG.

As shown in FIG. 8, when the user selects a desired entry in the registered node menu, the system parameter management unit 164 performs the same processing as steps 601 to 603 of FIG. 6 described in the deep copy processing. Is performed (steps 801 to 803). Finally, a link (not a type of instance) is extended from the new node to all other nodes pointed to by the link from the registered node (step 804). Here, the point that shallow copy differs from deep copy is that you do not copy the other node pointed to by the link from the registered node, but make a reference from the new node to the other node. Is that

Here, a case where the registered node 410 of the form box 400 shown in FIG. 4 is shallowly copied will be described.

First, the user selects "Deep Copy" which is further displayed by selecting the entry of "report creation form" from the registered node selection menu 450 displayed on the display screen. Alternatively, when the shallow copy entry is selected from the menu 910 for selecting “Shallow Copy”, the system parameter management unit 164 executes the deep copy processing in the following procedure.

(1) Create a new node 920 (contents not copied at this point). This will be the copy node.

(2) Contents of registered node 410 (node 4
11) to 415) are copied to the copy node 920. At this point, only the copy node 920 has been created.

(3) A link of the instance type is set up from the registration node 410 to the copy node 920.

(4) In this case, the nodes 411A-41
New nodes corresponding to 15A are not created.

(5) Finally, from node 921 to node 4
11A, a node (922 to node 412A), a node (923 to node 413A), a node (924 to node 414A), and a node (925 to node 415A).

Next, the relationship between the original hypertext information (registered node) and the hypertext information created by copying (copy node) will be described with reference to FIG.

In the example shown in FIG. 10, the form box 1
000 is hypertext information 1 as a form
010 and hypertext information 10 as a form
20 (a hierarchical structure or a network structure represented by nodes and links) is registered. Further, a link icon 1010A pointing to a registered node a that is a component of the hypertext information 1010 and a link icon 1020A pointing to a registered node b that is a component of the hypertext information 1020 are recorded and displayed. There is.

Registered node a (registered node 42 shown in FIG. 4)
(Corresponding to 0 and the registered node 420), the links of the type of instance are respectively linked to the copy nodes a1, a2, a3, a4, and a5.

Further, from the registered node b (corresponding to the registered node 410 shown in FIG. 4), a node c and a node d (node c and node d are the node 4 shown in FIG.
11A and node 412A) (corresponding to the node pointed to by the link from the registered node 410), the node c points to the node e by the link, and the node e points to the node d
Is pointed to. Furthermore, from the registered node b, the copy node b is linked by an instance type link.
1, b2, b3 are indicated respectively. Similarly,
From node c, node d, and node e, a copy node c
1, c2 and c3 are copy nodes d1, d2 and d3,
Copy nodes e1, e2, e3 are pointed to respectively. The copy nodes b1 to b3, the copy nodes c1 to c3, the copy nodes d1 to d3, and the copy node e
Links are also established among the copy nodes 1 to e3 so that the relationships among the registered nodes b, c, d, and e are reflected in the copy nodes.

Here, each copy node has the contents (cases) edited with respect to the contents of the copied registered node, which are different cases.

The contents of the example shown in FIG. 10 are stored in the hypertext data management unit 150 and accessed by the system parameter management unit 164.

With respect to the relationship between the registered node and the copy node, a process shown in FIG. 11 for sequentially displaying (for example, looping) the cases created by copying when the link is not output from the registered node. It will be described with reference to FIG.

As shown in FIG. 11, the user selects the link icon 10 from the link icons displayed in the form box 1000 shown in FIG. 10 displayed on the screen.
10A is selected to select the registered node a registered (step 1101), and then an instruction (menu operation) is made to display the case (step 1102). Then, the system parameter management unit 164 accesses the hypertext data management unit 150 to recognize the relationship between the link icon 1010A, the registered node a, and the copy nodes a1 to a5 as shown in FIG. To a5 are repeatedly displayed on the display screen (step 1103). There are two ways to display the copy node.

One of the methods is as shown in FIG.
In order that all the copy nodes can be displayed on the display screen of the display device 110, the display position of each copy node is shifted and displayed, and the copy nodes are displayed in order as the topmost window. In the example shown in FIG. 13, the copy node a1 is displayed as a window-type copy node Wa1, and similarly, the copy nodes a2 to a5 are also displayed as window-type copy nodes Wa2 to Wa5.
Here, the copy node Wa1 is the topmost window,
Then, the windows of the copy nodes Wa2 to Wa5 are overlapped with each other, but those windows (nodes) are sequentially displayed as the topmost window, so that the user can refer to the case.

Another method is as shown in FIG.
The copy nodes a1 to a5 are displayed one by one on the screen, and the nodes that are not displayed are displayed as icons. Next, a process of sequentially displaying (loop display) the cases created by copying from the original hypertext information (when there are a plurality of nodes) will be described with reference to the flowchart shown in FIG.

As shown in FIG. 15, the user selects the link icon 10 from the link icons displayed in the form box 1000 shown in FIG. 10 displayed on the screen.
20A is selected and the registered node b registered is designated (step 1501).

Then, the hypertext system management section 160 accesses the hypertext data management section 150 and, as shown in FIG.
0A and registered nodes b, nodes c, d, a, copy nodes b1 to b5, copy nodes c1 to c3, copy nodes d1 to d3, and copy nodes e1 to e3, and display the same. A browser window is displayed on the screen, and a structure configured with the registered node b as the root is displayed there (step 1502).

Then, the user selects a desired menu from the menus for instructing "display node" or "display structure" displayed on the screen (step 1503). 164 is
The process corresponding to the selected menu is executed.

That is, when the user selects "display node" in step 1503, the browser window is displayed on the display screen, and the user selects the registered node b in the browser displayed in the browser window. In this case, the copy nodes b1, b2, b3 of the registered node b are repeatedly displayed on the display screen (step 1504). An example of the display state at this time is shown in FIG.
Shown in.

In the example shown in this figure, a browser window 1710 is displayed on the display screen of the display device 110, and a menu 1720 for instructing "display node" or "display structure" is further displayed. .. Also in FIG.
In, the copy nodes b1 to b3 are displayed on the display screen as window type copy nodes Wb1 to Wb3, respectively. At this time, the display position of each copy node is shifted so that each copy node is displayed on the display screen, and the copy nodes are sequentially displayed as the topmost window.

On the other hand, when the user selects "display structure" in step 1503, a browser window is displayed on the display screen and the copy node b of the registered node is displayed.
A menu for selecting any one of 1, b2, and b3 is displayed. Further, for example, when the copy node b1 is selected from the menu, the copy nodes c1, d1, e1 which are the link destination nodes of the copy node b1 are repeatedly displayed on the display screen (step 1506). The display state at this time is shown in FIG.

In the example shown in this figure, a browser window 1710 and menu 1 are displayed on the display screen of the display device 110.
720 is displayed, and copy nodes b1, b2, b3 are further displayed.
A menu 1800 for selecting any of the above is displayed. In FIG. 18, the copy node b1 and the copy node c that is the link destination of the copy node b1.
It is shown that 1, d1, e1 are displayed as window-type copy nodes Wb1, Wc1, Wd1, We1 one by one in that order. Although four copy nodes are displayed in FIG. 18, one copy node is actually displayed sequentially.

Similarly, when the copy node b2 is selected, the copy nodes b2, c2, d2 and e2 are displayed, and when the copy node b3 is selected, the copy nodes b3, c3 and d3 are displayed. , E3 are displayed.

Next, a user interface for reusing hypertext information will be described.

In this embodiment, a user interface including the above-mentioned user interface means is prepared, and the user interface has a form box function. Next, its function will be described.

The form box has a function that allows the user to specify the registered form from the card type menu of the system when a user newly creates a card by registering a card to be copied and reused as a form in the form box. Is provided.

The form box displays the note file (No
te File), there is one corresponding to "F File" in the table of contents card.
ormBox ”titled File Box
x) exists. An example of the form box is shown in FIG.

In the form box 1900, all user cards (cards created by the user) can be registered as forms. Also, a "Form-Box Update" button 191 for adding a submenu that can specify a form to the system menu when a new card is generated
0 is provided.

Here, a card is a unit of information or a unit of function (note cards represent these units as a card), and a note file is
It is a file created by Notecars and is a file for storing and managing cards. A table of contents card is a card used as a table of contents for note files. The card is opened by default when the system opens the note file. A file box is a card for expressing a tree structure.

Since a form box can be easily created, a form can be registered and deleted, and a form can be copied using the user interface having the file box function as described above, these will be described below. To do.

(A) Form Box Creation A form box is created by selecting the "Form-Box Update" button 1910. The button is in the background in the file box by default. "Form-Box Update" button 191
0 can create a form box for a form box or a note file that does not exist. The procedure is shown below.

(1) The user presses the "Form-Box Update" button 1910. (2) The hypertext system management unit 160 displays the file name of the currently opened note file on the menu. (3) The user selects the file name of the note file for which the form box is to be created from the menu. (4) If there is no submenu for designating a form in the card type menu of the system, the hypertext system management unit 160 newly adds the submenu to the card type menu. (5) The hypertext system management unit 160 obtains permission from the user if there is no file box titled "Form Box" in the table of contents card of the note file selected in the above process (3). After that, create a new form box.

(B) Form registration and deletion Since the form box is provided as a file box, the form registration or deletion is registered by inserting the card to be registered in the form box,
It is deleted by removing the card you want to delete from the form box.

(C) Form Copy As shown in FIG. 20, when copying a new form, the form copy is performed by the system card type menu 2
A form entry (Form Entry) menu 2020 corresponding to the form entry (Form Entry) 2010A selected by the user from among the entries of 010 is displayed. From the menu 2020, the title of the card to be copied is displayed. Is done by selecting. When form entry 2010A is selected,
The hypertext system management unit 160 searches the table of contents cards for a file box titled "Form Box" and displays the titles of the cards existing in the file box as a menu. When the menu is selected, the card corresponding to the menu is copied and displayed on the display screen.

As described above, there are two types of card copying: deep copying and shallow copying. Deep copy is equivalent to the card copy function called from the menu box icon, and copies everything including past history of cards and linked cards. On the other hand, the shallow copy newly creates a card of the same type as the copy target card, and copies only the contents of the card title, the card contents, and the card properties. After copying the card, create a global link called an instance from the original card to the copied card. This is a function for referring to a similar case created by copying the original. The global link allows browsing and traversing of cards copied from the original card.

[0095]

As described above, according to the present invention, hypertext information to be reused is linked to one node and registered and managed, so that it is as easy as the operation of creating a new node. You can copy and generate hypertext information that you want to reuse. That is, the operability of copying can be improved.

Further, when searching for reference cases, the copy node group can be efficiently referred to and listed from the registered node. That is, it is possible to improve the operability of search.

[Brief description of drawings]

FIG. 1 is a functional block diagram showing an embodiment of a hypertext information management device according to the present invention.

FIG. 2 is a diagram for explaining a function for reusing hypertext information in this embodiment.

FIG. 3 is a diagram showing an example of a data structure of a form box in this embodiment.

FIG. 4 is a diagram for explaining the relationship between a form box, a registered node, and a registered node selection menu in the present embodiment.

FIG. 5 is a diagram showing an example in which a registered node selection menu is displayed from the node creation menu in this embodiment.

FIG. 6 Deep Copy (Deep Copy) in this embodiment
) Is a flowchart showing the processing operation of FIG.

FIG. 7 is a diagram for explaining a deep copy processing process according to the present embodiment.

FIG. 8: Shallow copy (Shallow) in this embodiment
3 is a flowchart showing the processing operation of FIG.

FIG. 9 is a diagram for explaining a shallow copy processing process according to the embodiment.

FIG. 10 is a diagram showing a relationship between original hypertext information and hypertext information created by copying in the present embodiment.

FIG. 11 is a flowchart showing a processing operation of displaying a copy node (case) when a link is not output from the registered node according to the present embodiment.

FIG. 12 is a diagram showing a relationship between a form box, a registered node, and a copy node when a link is not output from the registered node in this embodiment.

FIG. 13 is a diagram showing a display example of a copy node (case) when no link is output from the registered node according to the present embodiment.

FIG. 14 is a diagram showing a display example of a copy node (case) when a link is not output from a registered node in this embodiment.

FIG. 15 is a flowchart showing a processing operation of displaying a copy node group (case) created by copying from original hypertext information in the present embodiment.

FIG. 16 is a diagram showing a relationship between a form box, a registered node, and a copy node group when a link is output from the registered node in this embodiment.

FIG. 17 is a diagram showing a display example of a copy node group (case) when a link is output from a registered node in this embodiment.

FIG. 18 is a view showing a display example of a copy node group (case) when a link is output from a registered node in this embodiment.

FIG. 19 is a diagram for explaining a form box according to the present embodiment.

FIG. 20 is a diagram showing a display example of a form entry menu in the present embodiment.

[Explanation of symbols]

110 ... Display device, 120 ... Keyboard, 130 ... Mouse, 140 ... Hypertext file storage device, 15
0 ... Hypertext data management unit, 151 ... Node data management unit, 152 ... Link data management unit, 153 ... Hypertext file management unit, 160 ... Hypertext system management unit, 161 ... Node type management unit, 1
62 ... Link type management unit, 163 ... Node / link type management unit, 164 ... System parameter management unit, 16
5 ... System history management unit, 166 ... System management unit.

Claims (1)

[Claims] 1. A hypertext information management device for generating and managing hypertext information composed of nodes and links, and a registration means for registering a model node recording the hypertext information as a model, and the model node. User interface means for designating a new node by posting the template node specified via the user interface means, and linking the new node with the original template node. A hypertext information management device comprising: a generation unit that generates new hypertext information; and a display unit that displays the contents of the new node.