KR980010836A - Methods and systems for sharing annotations on electronic books and computer program products - Google Patents

Abstract

The present invention allows subsequent book viewers to use annotations or comments on electronic books through the World Wide Web. The first user enters annotation data in the data entry field while viewing the e-book. The data is automatically linked to the appropriate chapter / topic of the e-book and stored on the same server as separate files. When a subsequent user selects an electronic book, annotation data for viewing is likewise provided.

Description

Methods and systems for sharing annotations on electronic books and computer program products

TECHNICAL FIELD The present invention generally relates to computer software, and more particularly, to a method and system for sharing annotations for electronic books through the world wide web.

As a result of the proliferation of computer systems, including LANs and the Internet, individuals as well as organizations have transmitted, stored and used many online electronic documents. In the past few years, the use of the Internet / Intranet as a medium for electronic publishing has increased dramatically. Online documents used by users in both quantitative and diversity terms have increased rapidly. As a result, users can build online documents as books using software products such as IBM's BookManager, and then build these books using bookcases and collections. virtual libraries).

When books are built, they are compressed, indexed for quick retrieval, and stored on a server for remote user access over the Internet / Intranet. If the user wishes to view the book, the appropriate action is taken on the personal user workstation so that the book is called from the server and displayed on the personal workstation. Once an electronic book is displayed on a personal workstation, the user can freely read and exchange information about the material.

Unlike Internet shared documents, individual users can comment on locally stored documents, and other users with access to local storage can view this commentary. For example, if a user reads the text and recognizes an error or something that needs to be updated, the user can create an annotation that can be attached to the document so that others can view it.

However, this is not possible on the Internet. For example, even if the reader of the electronic book finds an error in the electronic book during this procedure, it cannot notify the creator of the document. Similarly, if an electronic book was received from an external source, it would be impossible to add specific information to the book for use by others of the same organization. Also, this is not possible if a group of people wants to collaborate on an electronic document and add annotations so that everyone in the group can see and respond to questions or concerns. Thus, there is a need for a method and system for making annotations of electronic books available through the World Wide Web.

The present invention allows the use of notes or annotations on electronic books through the World Wide Web. The first user enters annotation data for a topic in an electronic book stored remotely on the World Wide Web on his workstation. Comments are automatically linked to book topics. The annotations are then stored on the server side, so that when the electronic book is selected by a subsequent user, the annotations are provided by the World Wide Web so that they can be viewed with the electronic book.

1 illustrates a data processing system that may be used to implement the methods and systems of the present invention.

2 is a diagram of an online e-book topic according to the prior art.

3 shows annotation according to the invention.

4 illustrates creating an annotation panel.

5 shows a list of all annotations associated with a given book.

6 is a flow diagram illustrating the present invention.

7 is a flow diagram illustrating annotations provided for a topic in accordance with the present invention.

8 is a flowchart illustrating a topic transformation according to the present invention.

9 is a flowchart illustrating obtaining annotations on a topic in accordance with the present invention.

10 is a diagram illustrating a book annotation file ID according to the present invention.

11A and 11B are flow diagrams illustrating creating and storing topic annotations in accordance with the present invention.

12 is a flow chart illustrating a list of all topic annotations for a book in accordance with the present invention.

* Explanation of symbols for main parts of the drawings

8: Data Processing System 10: Internet / Intranet

12, 13: personal computer 14: storage device

16: printer / output device 17: mouse

18: mainframe computer 26: system control unit / communication controller

28: gateway server 32: LAN

Referring to FIG. 1, there is shown a data processing system 8 that can be used to implement the present invention. As can be seen in FIG. 1, the data processing system 8 may include a number of networks, such as intranet / internet 10 and local area network (LAN) 32, preferably these The network includes a number of personal computers 12 and 13 respectively. Of course, those skilled in the art will understand that multiple Intelligent Work Stations (IBS) coupled to a host processor may each be used for such a network. As is common in such data processing systems, each personal computer may be coupled to a storage device 14 and / or a printer / output device 16, and may include a mouse ( It may be provided with a pointing device such as 17).

In addition, the data processing system 8 is a plurality of mainframe computers, such as a mainframe computer 18, which is preferably coupled to the intranet / internet 10 using communication links 22. mainframe computer). Mainframe computer 18 may also be coupled to storage device 20, which may serve as a remote storage device for intranet / internet 10. Similarly, the intranet / internet 10 may be a gateway server via a communication link 24 and a sub-system control unit / communications controller 26 via a communication link 34. And (28). The gateway server 28 is preferably an IWS that serves to connect the LAN 32 and the intranet / internet 10.

For the LAN 32 and the intranet / internet 10, a number of documents or resource objects are stored in the storage device 20 and the mainframe as a resource manager or library service for these stored resources. It can be controlled by the computer 18.

Software program code employing the present invention is typically stored in a memory of a storage device 14 of a stand alone workstation or in a LAN server where a developer can access the code for distribution purposes, This software program code can be on any of a variety of known media for use with data processing systems, such as diskettes or CD-ROMs, and can be accessed via some type of network such as FTP (File Transfer Protocol). The code may be distributed from the memory of the computer system to other computer systems so that users of other computer systems can use the code. Techniques and methods for embedding software code in media and / or for distributing software code are well known and will not be discussed further herein.

The present invention is for use with documents (books) accessible through the World Wide Web (WWW). In this regard, books are stored on a WWW server for user access through a desktop computer. Referring to FIG. 2, a screen 100 is shown that is displayed on a desktop monitor. The user has selected through the WWW an electronic document to retrieve. As shown, an electronic document may be a topic such as Chapter 3.1, titled "The BookManager BookServer Library," for example, from an electronic book entitled "IBM BookManager Bookserver for World Wide Web for OS / 2: Getting Started". ). Topic 102 includes a variety of information that a user can read or select for appropriate action. Even if the user finds some information that requires further explanation, correction, or additional comments, the prior art provides a solution to how all subsequent users of the document can view comments / comments / comments through the WWW. Could not provide.

Referring to FIG. 3, an example of an annotation or annotation that can be added to the topic 102 of FIG. 2 using the present invention is shown. In accordance with the present invention, the annotations or annotations may be stored in a separate file on the WWW server that stores the book, or linked to the appropriate topic to provide the topic and annotation as a single document to the user. In a preferred embodiment, annotations or annotations will be displayed at the end of the current topic.

In FIG. 3, the annotations on topic 102 can be seen. A panel 104 named generally "Notes for: 3.1", denoted by reference numeral 106, indicates that reference is made to topic 102 as shown in FIG. The area, generally identified by reference numeral 108, displays information that the user added to topic 102.

Referring back to FIG. 2, a list of icons is displayed on a toolbar 110 in the screen 100. By selecting an icon of the toolbar 110, the user can perform various functions related to the annotation. For example, by selecting icon 112, the user can create annotations for the topic. By selecting icon 114, all annotations for the currently displayed book can be viewed.

Referring to FIG. 4, the user has selected icon 112 to create an annotation. As can be seen, a data entry field 120 is provided to allow the user to enter certain information that the user wishes to access to the topics and books currently being viewed. As can be seen, the information entered into the data entry field 120 is a topic 102 in an electronic online book named "IBM BookManager BookServer for World Wide Web for OS / 2: Getting Started". Will be related to "3.1 The BookManager BookService Library". By selecting the appropriate button, such as add 122, any information entered into data entry field 120 will be stored as a comment on the appropriate topic. Comments will be stored on the server, which contains the relevant books in separate files. As will be explained in more detail below, by using the appropriate links, annotations will be automatically displayed with the appropriate topic.

Referring to FIG. 5, the user selects icon 114 to display all annotations related to the currently viewed e-book. As shown, topic 3.1 (generally indicated by reference number 130), topic 3.1.4 (generally indicated by reference number 132), and topic "GLOSSARY" (generally indicated by reference number 134). There is a comment on].

Referring to FIG. 6, a high level flow diagram illustrating the present invention is shown. The data process fully described in US patent application Ser. No. 08 / 514,935 is incorporated herein by reference. After commencement of step 200, at block 202 a Dynamic Interchange Translation Agent (DITA) is called. DITA opens the book file at block 204 and then places the book at the requested topic at block 206. At decision block 208, it is determined whether there is an annotation for the opened topic as described in more detail below with reference to FIG. If present, the present invention obtains annotations for this topic at block 210, as will be described in further detail below with reference to FIG. At decision block 212, it is determined whether the annotation was successfully obtained. If the annotation was successfully obtained, the annotation GIF is placed following the topic ID at block 214 and then the active list annotation GIF is placed on the toolbar at block 216. Subsequent to / following block 216, or if it is determined that the annotation was not successfully obtained at decision block 212, or it is determined at annotation block 208 that the annotation does not exist, the present invention proceeds to decision block 218. In this decision block 218, it is determined whether more data is needed by obtaining a text record. If more data is needed, the present invention formats and outputs the text at block 220 and then returns to decision block 218. If not, it is determined at decision block 222 whether the annotation was successfully obtained. If the annotation was successfully obtained, the annotation text is formatted in the table at block 224. At block 226 the formatted annotations for the topic are output. Subsequent to block 226, or if it is determined in block 222 that the annotation was not successfully obtained, the present invention ends at block 228.

Referring to FIG. 7, there is shown a flow diagram for the steps implemented by the present invention in determining a response to decision block 208 of FIG. At block 240, the topic ID is translated into a sequential topic number (integer), for example 15, as described below in more detail with reference to FIG. At block 242, the integer is converted to hex format (eg, x'F '). At block 244, the hexadecimal format is converted to a character (eg, '00F'). A comment file name is then created from the book name and the conversion character (eg "ABC.00F"). At decision block 248, it is determined whether a file of this name exists in the list of annotations. If it does not exist, a 'does not exist' (DNE) message is returned at block 250. If present, the file is opened at block 252 and a header is read to validate the file. At decision block 254, it is determined whether the annotation file is valid. If valid, a true message is returned at block 256. If it is not valid, an invalid message is returned at block 258.

Referring to FIG. 8, a process for converting the topic ID into the sequential topic numbers of block 240 from FIG. 7 is further described. At block 300, a Softcopy Access Method-code that reads and decodes / the binary book file (SCAM) API is called to specify the location of the current topic. At block 302, the topic is queried for the number following the return of the topic number of block 304.

Referring to FIG. 9, a flow diagram that further illustrates block 210 of FIG. 6 is shown. At decision block 320, it is determined whether there is a comment for this topic. If not present, a false response is returned at block 322. If present, the converted file name (eg, "ABC.00F") is opened at block 324. At decision block 326, it is determined whether the topic integer is zero. If zero, a first head structure is created (list all annotations) at block 328. At block 330, all files for this book (eg, "ABC. *") Are found in the comment list. In block 332, as described in more detail below, the present invention executes procedure C for each valid file except for the corresponding file (.000, ie, the header file). After execution of procedure C, the head structures in block 334 are chained with each other and continue procedure C through block 332. When there are no more files, the present invention ends at block 336.

Returning to decision block 326, if the topic integer is non-zero, procedure C is executed starting at block 340, which generates a topic head structure for a single topic. At block 342, a text record is obtained. At decision block 344, it is determined whether a "Head" record exists. If a head record exists, the text record is parsed at block 346 and the data is placed within the topic head structure at block 348. The present invention then returns to block 342 as described above.

If there is no "head" record at 344, then at 350 the topic information structure is created and chained together. Next, a text record is obtained at block 352. It is then determined in decision block 354 whether the end of the information record has been reached. If not, then block 356 returns to block 352 after the data has been placed in the information structure. If the end of the information record has been reached, then in decision block 358 it is determined whether additional records exist. If there is additional data, the present invention returns to block 350 as described above. If no additional data is present, at block 360 the present invention returns a true message.

Referring to FIG. 10, annotation file IDs for one book are illustrated. As can be seen, the book header file is preferentially set using the book name and the suffix (.000). Then, the annotation file for each topic from 1 to 4095 is set up as shown using the appropriate topic conversion characters for the extension. Thus, annotations can be created for up to 4095 topics in one book (the maximum number of topics that a current book can contain is obviously changeable by design).

Referring to FIGS. 11A and 11B, a flow diagram illustrating the creation and storage of topic notes is shown. At block 400, the end user clicks on the “Create Note” 112 GIF (see FIG. 2) on the toolbar 116 (see FIG. 2). In block 402, a form for entering information such as 1) comment text, 2) user name (optional), and 3) user e-mail, address (optional) is provided. Is provided to the user. In block 404, the user enters information in the form and clicks the ADD push-button. At block 406, book names, topic numbers, and annotation data are collected and stored within the structure. At block 408, the topic ID of the book is converted to an integer topic number as described above with reference to FIG. At block 410, the topic number is converted to hexadecimal and character so that a comment file name (eg, "ABC.00F") is created at block 412. Referring to FIG. 11B, at decision block 414, it is determined whether an annotation file exists. If it does not exist, a new annotation file is created at block 416. Topic head data is written at block 418 and the total annotation count is set to 1 at block 420.

Referring back to decision block 414, if a new annotation file exists, the annotation file is opened for reading / writing in block 422. The topic header is read at block 424 and the total note count is incremented and stored at block 426. Following block 426 and / or block 420, the location at block 428 is stored in the file. In block 430, the present invention points to the end of the file.

In block 432 the annotation data is recorded from the "Info Structure" (eg new annotation information and text attachments) at the end of the file. Then, at block 434 the present invention returns to the full annotation count, and at block 436 the total annotation count (stored earlier) is written into the file. The file is then closed at block 438 and it is determined at decision block 440 whether the file I / O was successful. If successful, a 'true' is returned at block 442. If not successful, a 'false' is returned at block 444.

Referring to FIG. 12, a flow diagram illustrating a procedure for listing all topic annotations for one book is shown. At block 500, the user selects "List All Notes", GIF from the toolbar. At block 502, book names are collected and stored. At block 504, the topic number is set to zero for all topics. Following block 504, as described above with respect to FIG. 9, procedure B (obtain annotations for the topic) is executed. Next, it is determined in decision block 506 whether procedure B was successful. If unsuccessful, at block 508 the present invention ends with an error message. If successful, the structure is read in a loop until the last structure is reached. At block 512, annotation text is formatted and output in the table for each topic in the consolidated page as described above with reference to FIG. The invention then ends at block 514.

Although the present invention has been described with reference to specific embodiments, various changes and modifications may be made by those skilled in the art, and the scope of the present invention should be understood only within the scope of the appended claims.

The present invention allows the use of notes or annotations on electronic books through the World Wide Web. The first user enters annotation data for a topic in an electronic book stored remotely on the World Wide Web on his workstation. Comments are automatically linked to book topics. The annotations are then stored on the server side, so that when the electronic book is selected by a subsequent user, the annotations are provided by the World Wide Web so that they can be viewed with the electronic book.

Claims (9)

A method for allowing a large number of users to share notes about an electronic book through a World Wide Web, the first user comprising: a World Wide Web server; inputting annotation data through their workstation for an electronic book topic remotely stored in a server), ② automatically linking the annotation data to the book topic, ③ the book topic Storing the annotation data to be provided by the world wide web server for subsequent user viewing via subsequent workstations upon selection of the annotation data. The method of claim 1, wherein entering annotation data comprises: opening a control on a toolbar and entering data in a data entry field within the control. How to share the comments on the e-book containing. The method of claim 1, wherein the storing step includes storing the annotation data on the world wide web server that stores the book topic. A system for allowing a plurality of users to share notes about an electronic book via a World Wide Web, the first user comprising: a World Wide Web server; Means for inputting annotation data via their workstation for an electronic book topic remotely stored in a Web server; ② means for automatically connecting the annotation data to the book topic; Means for storing the annotation data including means for storing the annotation data so that upon selection of a book topic the annotation data is provided by the world wide web server for subsequent users to view through subsequent workstations. System for doing so. 5. The apparatus of claim 4, wherein the means for entering annotation data comprises: means for opening a control on a toolbar and means for entering data in a data entry field in the control. A system for sharing annotations on an electronic book comprising a. 5. The system of claim 4, wherein the means for storing comprises means for storing the annotation data on the world wide web server that stores the book topic. A computer program product recorded on a computer readable medium that allows multiple users to share notes about an electronic book via a World Wide Web. program product, comprising: (1) a computer reading that allows a first user to enter annotation data through his workstation for an electronic book topic remotely stored on a World Wide Web server. Computer readable means for automatically coupling the annotation data to the book topic; and the world wide web for subsequent users to view the annotation data through subsequent workstations upon selection of the book topic. A computer comprising computer readable means for storing the annotation data to be provided by a server Program product. 8. The apparatus of claim 7, wherein the computer readable means for entering the annotation data comprises: computer readable means for opening a control on a toolbar and a data entry field in the control. And computer readable means for inputting data into the computer. 8. The computer program product of claim 7, wherein the means for storing comprises computer readable means for storing the annotation data on the world wide web server that stores the book topic. ※ Note: The disclosure is based on the initial application.