WO2002017276A1

WO2002017276A1 - System and method for providing a curriculum repository

Info

Publication number: WO2002017276A1
Application number: PCT/US2001/025037
Authority: WO
Inventors: William Abrams; Rick Johnson; Todd Watkins; William Chesser
Original assignee: Vital Source Technologies, Inc.
Priority date: 2000-08-22
Filing date: 2001-08-08
Publication date: 2002-02-28
Also published as: AU2001283249A1

Abstract

The system and method of the invention provide for an educational curriculum of an organization to be made available to a user in an accessible manner. The method of the invention starts by obtaining curriculum content (S2). Such curriculum content might be obtained from a professor or from a publisher. Then, the process of the invention digitizes and structures the curriculum content (S4). Then the process of the invention generates a library of curriculum material (S6). The library of curriculum material is the total collection of material held by a facility and offered to educational organizations, i.e., customers. Based on the library of curriculum material, a customer's collection of curriculum materials is generated (S7). The end-user is provided with accessibility to the customer's collection of curriculum materials (S8). The accessibility might be provided in the form of a DVD or via the Internet. The system and method of the invention includes various additional features including validation checks to address copyright concerns, editing features, and permission features, for example.

Description

SYSTEM AND METHOD FOR PROVTOLNG A CURRICULUM REPOSITORY

Copyright Note

A portion of the disclosure of this patent document, including the drawings, contains material which is subject to copyright protection. The copyright owner has no objection to the reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

Background of the Invention

1. Field of the Invention

This invention relates to a system and method for providing an electronic curriculum repository with enhanced accessibility and control over information, and in particular, educational information.

2. Description of the Related Art

In today's educational climate, an increasing number of persons are seeking knowledge and further education regarding a truly diverse and wide variety of subjects. As can be appreciated, education and training takes a wide variety of forms. Education starts at a very young age and extends through high school. Thereafter, persons may attend any of a variety of universities, colleges or technical centers. However, education and training is not limited to these formal environments. Illustratively, many companies, agencies and other entities implement training programs to train people with the skills those people need for their respective jobs. Additionally, after receiving a college education, many persons, in an increasingly greater rate, attend some type of graduate school. Graduate schools may include medical school, law school and business school, as well as a wide variety of other higher educations. Even after such higher educations, for example, persons still attend conferences, seminars and other organized meetings to exchange information and ideas.

Accordingly, education and training are present in our lives from a very young age and might never end for some persons. As described above, this education takes a wide variety of forms. However, one common thread running through this education is the necessity to convey information from persons and materials, who possess the knowledge, to persons wanting the knowledge. The persons providing the knowledge will hereinafter be referred to as "teachers." Further, the persons receiving and wanting the knowledge will hereinafter be referred to as "students." The training environment of a medical student provides insight into the presently used teaching methods. Typically, a medical student starts his or her education with the hope of being enriched by the knowledge he or she seeks. Typically, a medical student may walk into a classroom and, from day one, the lights go out and the shdes start flashing on the screen. The rate at which the slides are shown may average as much as 180 shdes per hour. Nevertheless, the slides pass by in front of the medical student and she is expected to digest this information.

The information used in teaching may come from numerous sources. For example, the shdes shown to the medical students may be the result of years of the professor's collecting. Further, the slides may be one of a kind that the professor obtained from the professor's mentor, who used to be chairman of their department before he retired.

The students correctly perceive those slides as being of tremendous value. However, the students see the shdes one time, and only one time, and then the shdes are gone forever. The students then after class attempt to conjure up the slides either working alone or in groups. The students often unsuccessfully attempt to draw the slides when they are displayed in class. But before the essence of the shde is really captured, the next slide is being displayed. Then, after class the students might approach the professor and humbly request a copy of the slides. However, the slides often represent the career of the professor. As a result, the professor is hesitant to assist in a reproduction of his documents in any form.

The above scenario illustrates one of a variety of situations that prevent the exchange of information and knowledge from a teacher to a student. Accordingly, the scenario results in the students recreating the knowledge to which they were exposed. This recreation might be in the form of notes or crude reproductions of the shdes, or whatever other information was presented in class that day. Accordingly, there is a need to provide a method to exchange knowledge from a teacher to a student that is both beneficial and acceptable to all parties. Alternatively, a situation may be present when the teacher does indeed prepare and provide materials to the students. However, even in this situation there are common problems. For example, a teacher may copy a favorite diagram from a resource book and paste that diagram into their own created materials. The teacher may then surround this copied diagram with the teacher's own text. This, for one, results in potential copyright infringement violations. Further, with the advent of desktop publishing capabilities, the accumulation of these materials is becoming progressively easier. The student accurately perceives this material as coming straight from the professor and, as a result, considers the material of great value. Further, the university, for example, may require the student to purchase the professor's material. Alternatively, the university will recommend that the student buy a series of materials from a particular publisher.

SUMMARY OF THE INVENTION Accordingly, a situation has developed in the academic world, and in other learning environments, in which administrative persons, faculty members and students are discouraged and concerned with regard to the decreasing quality of their study materials. People are discouraged both from the perspective of a teacher, providing the materials, and from the perspective of a student, receiving the materials. For students, the situation is particularly discouraging in that their command of the material, in testing situations as well as other situations, will dictate the success of their careers.

With the rise in technology over the past years, it has been believed by many that technology would step in and solve the problems described above. However, present known technology simply does not address the collection and efficient dissemination of materials necessary to the teaching process.

Accordingly, there is a need for a methodology to effectively collect information from a wide variety of sources and provide this information to students in an efficient manner. Additionally, there is a further need to monitor and control issues regarding distribution of materials, such as copyright issues. In accordance with the system and method of the invention, an entire educational curriculum for an organization is made available to a user in a readily accessible collection. That is, a collection in accordance with the system and method of the invention may be characterized as global to a particular organization, such as a college or corporation, including all curriculum materials that the particular organization utilizes. The system and method of the invention provides navigation of information in the collection in an efficient and effective manner. Accordingly, the user may interact with a certain item of material in the collection as if that certain item were a single textbook or document.

The system and method of the invention utilize media integration in the collection of material. Thus, the content in the collection is not limited to text or pictures, but can contain any material including video or three-dimensional graphics, for example. The system and method of the invention provide non-disparity between the materials in the collection, such materials being collected from a wide variety of sources. Accordingly, this non-disparity promotes multiple contributor participation since all material in the collection is treated the same, irregardless of the contributor, e.g., a publisher, being large or small. The system and method of the invention provide a collection of material using standardized formats. Accordingly, any person or entity may contribute to the collection due to the standardized manner in which the materials in the collection are processed and ultimately presented to the user.

The system and method of the invention provide access to a combination of disparate materials in the collection through one user interface. Even though diverse persons and other entities can participate in contributing to the collection, the user interacts with each item of material in the collection from a single, consistent user interface.

The system and method of the invention maintain the integrity of each individual item of material. Accordingly, copyright status, ownership of the material, and placement of text within its original context is maintained as the disparate materials are utilized by a user, e.g., a student.

The system and method of the invention provide the user with customized views. Although a standard view is always available to the user, the user may also customize their view and is in control of many aspects of user interface environment. Further, a user may view multiple custom views of the same image or figure, for example. However, while the student perceives two views, each of the two views is relying on the same source image.

In accordance with the process of the invention, teaching materials may be characterized as internal materials and external materials. Internal materials include lecture slides, videos created by a university, syllabi, audio materials such as recordings of class lectures, and manuals related to particular subject matter, for example. That is, any materials that are prepared on campus of the university, or in close affiliation with a particular university, may be characterized as internal materials. The internal materials are treated differently than external materials in accordance with the system and method of the invention.

External materials include any material that is not an internal material, which of course includes all material prepared in mass by a publisher, for example. Accordingly, external materials might include books, journals, videos or treatises, for example.

In accordance with one embodiment, the invention might be characterized as including two phases. The first phase includes the accumulation and digitization of material. The second phase includes an assimilation of that digitized material into a workable database.

Accordingly, the first phase of the process in accordance with the invention initially includes digitization of all the materials. Thereafter, the material is "structured." In summary, structuring of the material includes mapping or marking up the document to enhance the accessibility of the document. Further, phase one in accordance with the method of the invention includes addressing all copyright issues associated with the various materials. Then, in phase two, the material is incorporated into a database.

In accordance with one embodiment of the invention, the digitized information is stored in the form of a portable electronic media such as DVDs. The DVDs contain all the information that the student needs for the curriculum of that student. In accordance with one aspect, the student will only have access to the particular courses the student is taking. This access may be afforded in the form of a password to the various curriculum contained on the DVD. Alternatively, the student may have access to any and all information utilized in the entire university's curriculum, for example. Illustratively, prior to the beginning of every semester, the student is provided with their

DVD for that semester. However, it should be appreciated that while this illustrative example uses a DVD, any appropriate electronic media may be utilized. If the student possesses a DVD for a previous semester, that previous DVD might be returned and exchanged for a new DVD.

The universities may mandate the student's use of the DVD curriculum repository system of the invention and include all the costs in the student's annual fees. As a result, the DVDs are a required service. That is, the students agree to accept the service when attending the university, or other training institution. It should be appreciated that the curriculum and materials utilized from one university to another university will differ. As a result, the DVDs distributed at each university will be different from one university to the next university. In accordance with one embodiment of the invention, manuals, textbooks, and all other materials used in the university's curriculum are organized into a digital bookshelf. The digital bookshelf provides an advanced organizer of the curriculum contained in the curriculum repository. In accordance with the system and method of the invention, the various books and various portions, e.g., chapters and sections, within each respective book are separately organized. As a result, a student may use the individual pieces alone or in conjunction with other pieces. Accordingly, every single piece of data whether the piece of data is a heading of a picture, a caption of the heading, or the picture itself, is essentially a file within a larger file. As a result, if a student desires to enlarge a picture, the student has that ability by simply double clicking, or otherwise selecting, the picture, for example. Further, the organization of each document into further individual files allows a student to pick and choose between which materials they choose to use in the preparation of their own personal study materials. BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects of the invention will become apparent from the following descriptions which illustrate exemplary embodiments of the invention when read in conjunction with the accompanying drawings, in which:

Fig. 1 is a flowchart illustrating the process in accordance with an embodiment of the system and method of the invention;

Fig. 2 is a block diagram showing a curriculum repository system in accordance with an embodiment of the invention;

Fig. 3 is a block diagram showing in further detail the operating portion of Fig. 2 in accordance with an embodiment of the invention; Fig. 4 is a block diagram showing in further detail the memory portion of Fig. 2 in accordance with an embodiment of the invention;

Fig. 5 is an exemplary user interface in accordance with an embodiment of the system and method of the invention;

Fig. 6 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 7 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 8 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention; Fig. 9 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 10 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 11 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 12 is a further exemplary user interface showing the table of contents window in accordance with an embodiment of the system and method of the invention; Fig. 13 is a further exemplary user interface showing further aspects of the table of contents window in accordance with an embodiment of the system and method of the invention;

Fig. 14 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention; Fig. 15 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 16 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 17 is a further exemplary user interface showing further aspects of the table of contents window and the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 18 is a further exemplary user interface showing aspects of the table of contents level box in accordance with an embodiment of the system and method of the invention;

Fig. 19 is a further exemplary user interface showing further aspects of the table of contents level box in accordance with an embodiment of the system and method of the invention;

Fig. 20 is a further exemplary user interface showing aspects of the index window in accordance with an embodiment of the system and method of the invention;

Fig. 21 is a further exemplary user interface showing further aspects of the index window in accordance with an embodiment of the system and method of the invention; Fig. 22 is a further exemplary user interface showing aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 23 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 24 is a further exemplary user interface further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 25 is a further exemplary user interface further aspects of the search box in accordance with an embodiment of the system and method of the invention:

Fig. 26 is a further exemplary user interface showing a further user interface in accordance with an embodiment of the system and method of the invention; Fig. 27 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 28 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 29 is a further exemplary user interface showing aspects of an expanded search box in accordance with an embodiment of the system and method of the invention;

Fig. 30 is a further exemplary user interface showing further aspects of the expanded search box in accordance with an embodiment of the system and method of the invention;

Fig. 31 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 32 is a further exemplary user interface showing aspects of the search box including a source drop down selector in accordance with an embodiment of the system and method of the invention;

Fig. 33 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention;

Fig. 34 is a further exemplary user interface showing aspects of a collection window in accordance with an embodiment of the system and method of the invention; Fig. 35 is a further exemplary user interface showing further aspects of the collection window in accordance with an embodiment of the system and method of the invention;

Fig. 36 is a further exemplary user interface showing further aspects of the collection window in accordance with an embodiment of the system and method of the invention;

Fig. 37 is a further exemplary user interface showing further aspects of the collection window in accordance with an embodiment of the system and method of the invention;

Fig. 38 is a further exemplary user interface showing further aspects of the collection window including saving the collection in accordance with an embodiment of the system and method of the invention;

Fig. 39 is a further exemplary user interface showing further aspects of the collection window and the desktop in accordance with an embodiment of the system and method of the invention;

Fig. 40 is a further exemplary user interface showing further aspects of the collection box in accordance with an embodiment of the system and method of the invention;

Fig. 41 is a further exemplary user interface showing further aspects of the collection in accordance with an embodiment of the system and method of the invention;

Fig. 42 is a further exemplary user interface showing further aspects of user interface in accordance with an embodiment of the system and method of the invention; Fig. 43 is a further exemplary user interface showing aspects of searching a collection in accordance with an embodiment of the system and method of the invention:

Fig. 44 is a further exemplary user interface showing further aspects of the search box in accordance with an embodiment of the system and method of the invention; Fig. 45 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 46 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 47 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 48 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention;

Fig. 49 is a further exemplary user interface showing further aspects of the page view window in accordance with an embodiment of the system and method of the invention; Fig. 50 is a flowchart showing the process in accordance with an embodiment of the system and method of the invention;

Fig. 51 is a flowchart showing the "receive material" step of Fig. 50 in further detail in accordance with an embodiment of the system and method of the invention;

Fig. 52 is a flowchart showing the "structure and digitize material" step of Fig. 50 in further detail in accordance with an embodiment of the system and method of the invention;

Fig. 53 is a flowchart showing the "input material into a depository with associated metadata" step of Fig. 50 in accordance with an embodiment of the system and method of the invention;

Fig. 54 is a flowchart showing the "assemble collection within repository for production system step" of Fig. 50 in accordance with an embodiment of the system and method of the invention;

Fig. 55 is a flowchart showing a "create accessible collection" step of Fig. 50 in further detail in accordance with an embodiment of the system and method of the invention;

Fig. 56 is a flowchart showing the "access the collection" step of Fig. 50 in further detail in accordance with an embodiment of the system and method of the invention;

Fig. 57 is a flowchart showing the "generate content for end-user" step of Fig. 56 in further detail in accordance with an embodiment of the system and method of the invention; Fig. 58 is a flowchart showing the "generate content for permissions file" step of Fig. 56 in further detail in accordance with an embodiment of the system and method of the invention;

Fig. 59 is a flowchart showing the "process requests to access content via web pages" step of Fig. 56 in further detail in accordance with an embodiment of the system and method of the invention; and

Fig. 60 is a flowchart showing the "process changes to content" step of Fig. 50 in further detail in accordance with an embodiment of the system and method of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In accordance with the system and method of the invention, an entire educational curriculum for an organization is made available to a user in a readily accessible collection. That is, a collection in accordance with the system and method of the invention may be characterized as global to a particular organization, such as a college or corporation, including all curriculum materials that the particular organization utilizes. Fig. 1 is a flowchart showing the process of the invention. As shown in Fig. 1, the method starts by obtaining curriculum content in step S2. Such curriculum content might be obtained from a professor or from a publisher, for example. Then, the process of the invention digitizes and structures the curriculum content in step S4. This results in curriculum material, i.e., structured curriculum content. Then the process of the invention moves to step 6, as shown in Fig. 1. In step 6, the process generates a library of curriculum material. The library of curriculum material is the total collection of material. Then, the next step S7 in the process is to generate a customer's collection of curriculum materials. The customer's collection of curriculum materials is a subset of the library of curriculum materials. That is, the items that constitute a customer's collection of curriculum materials is actually obtained from the library of curriculum material.

The next step S8 in the process as shown in Fig. 1 is to provide the end-user with accessibility to the customer's collection of curriculum materials. This accessibility might be provided in the form of a DVD or via the Internet, for example.

It should be appreciated that intertwined with the steps as shown in Fig. 1 are a wide variety of features. These features include validation checks, editing features, and permission features, as are described in further detail below. In accordance with one embodiment of the invention, a DVD user is an end user of the curriculum materials. However, according to a different embodiment of the invention, the end user will not always be solely a DVD user. That is, the end user may also have web access to the curriculum repository, for example. In accordance with the system and method of the invention, curriculum material is obtained from various sources including professors and publishers, for example. This obtained material is then digitized. Specifically, the text is rekeyed, or programmatically converted and the graphics may be scanned at the highest available resolution. Then both the text and the graphics are recombined utilizing a "mark-up" language. Illustratively, the text and graphics may be marked-up using Extensible Markup Language (XML).

The curriculum materials are structured in a hierarchical manner. That is, a book includes chapters, chapters include sections, sections include subsections, and so on. Further, it should be appreciated that each chapter, section, subsection and so on may include graphics, such as diagrams or flowcharts, for example. However, in accordance with the system and method of the invention each part of the curriculum material, i.e., each chapter, section, subsection, and graphic, for example, is stored in its own individual file. This allows the system of the invention to individually manipulate each part.

The specific hierarchy, and organization of a particular piece of curriculum material into a given hierarchy, depends on the nature of the material. Illustratively, the curriculum material may be structured into a hierarchy using a programmatic interpretation of the embedded hierarchy, or using a human decision making process. To explain further, a particular book may be available electronically. The book is organized into chapters and sections. Further, the book includes various diagrams dispersed throughout the book. This book may be structured for use in the system of the invention by utilizing a programmatic interpretation. That is, the programmatic interpretation searches through the book and determines the location of all chapter breaks, section breaks, and diagrams. Based on this determination, the system of the invention dissects the book into respective data files that represent each chapter, section and diagram.

However, it should be appreciated that not all obtained materials are so easily structured. For example, a professor may want to include her extensive notes in the curriculum repository. These notes may include hand written materials, typed materials and hand drawn sketches.

Thus, these notes are not so easily structured in accordance with the invention as in the example above, but rather require somewhat more work. First, the notes must be represented in electronic format in any suitable manner. For example, material may be scanned or manually entered. However, the material may not be organized in any particular manner, but rather may be constitute somewhat of a haphazard collection. In this situation, programmatic interpretation cannot be performed since the professor's materials cannot be reliably interpreted. Instead, it may be necessary to use a human decision making process. That is, a person reviews the professor's materials and determines the hierarchical breakdown of the professor's materials.

It should be appreciated that using the system and method of the invention, various software may be used in creating the digitized documents. Such software includes, but is not limited to ADOBE PHOTOSHOP, QUICKTIME, BBEDIT, EPIC, ADEPT, XMETAL, WORD, CUSTOM APPLICATIONS, CANTO CUMULUS, WEBOBJECTS, or ORACLE, for example. Fig. 2 is a block diagram showing an embodiment of a curriculum repository system 1000 in accordance with the system and method of the invention. The curriculum repository system 1000 performs input of various curriculum content, processes these input curriculum content in order to provide structure to the materials in accordance with the invention, and then outputs the structured materials in a suitable form.

The curriculum repository system 1000 includes an operating portion 1100 and a memory portion 1500. The curriculum repository system 1000 also includes an interface portion 1010. The curriculum repository system 1000 receives and outputs data using the interface portion 1010. The interface portion 1010 includes both an input port 1012 and an output port 1014 for receiving and sending data, respectively.

The operating portion 1100 in the curriculum repository system 1000 includes various portions that perform the various operations of the curriculum repository system 1000. Fig. 3 shows in further detail the operating portion 1100. As shown in Fig. 3, the operating portion 1100 includes the document input portion 1110, the structuring portion 1120, the validating portion 1130, the assembly portion 1140, the collection portion 1150, the access portion 1160, the editing portion 1170 and the control portion 1190.

The document input portion 1110 initially inputs and processes curriculum content. Specifically, the document input portion 1110 digitizes the input material. The structuring portion 1120 in the operating portion 1100 structures the curriculum content using a markup language. The validating portion 1130 validates the curriculum material. The assembly portion 1140 assembles the collection of materials in the curriculum repository system 1000. The collection portion 1150 creates customer collections. The access portion 160 provides access to the curriculum materials. The editing portion 1170 performs editorial updates of the curriculum material in the curriculum repository system 1000, as described below.

Additionally, the control portion 1190 controls the operation of the various components and portions in the curriculum repository system 1000. Each of the components of the curriculum repository system 1000 is connected by an interface 1020.

The memory portion 1500 as shown in Fig. 2 stores the various information, including programs and data, necessary for operation of the curriculum repository system 1000. Fig. 4 shows the memory portion 1500 in further detail. As shown in Fig. 4, the memory portion 1500 includes a new input memory 1510, a processed material memory 1520, a library memory 1530, a customer records memory 1540, a backend collections memory 1550 and a system memory 1590.

The new input memory 1510 stores information subsequent to processing by the document input portion 1110. The processed material memory 1520 contains curriculum material data subsequent to processing by the structuring portion 1120. The library memory 1530 stores the curriculum material data generated by the validating portion 1130.

The customer records memory 1540 stores a record hst for each customer, which is associated with the curriculum data stored in the library memory 1530. The backend collection memory 1550 stores data regarding a customer's collection of materials. For example, the backend collections memory 1550 stores curriculum material data for a particular university.

The system memory system memory 1590 stores the various software and other data for operation of the curriculum repository system 1000.

Aspects of the system and method of the invention will hereinafter be described in conjunction with Figs. 2-4. In the process of the invention, materials are initially obtained from a wide variety of sources and may be characterized as "curriculum content. " Curriculum content may include "external materials" from publishers and "internal materials" from professors, for example, as described above. This originally obtained curriculum content is then input into the curriculum repository system 1000 by the document input portion 1110. The document input portion 1110 may include an electronic scanner, a keyboard by which a user manually enters data, or any other suitable input device to input the document in the curriculum content so as to store the curriculum content in digital form. Once the curriculum content is input into the curriculum repository system 1000, the document input portion 1110 stores all the input material in the new input memory 1510.

In further explanation of the operation of the document input portion 1110 and in accordance with one embodiment of the system and method of the invention, the document input portion 1110 validates the integrity of the curriculum content after receiving the curriculum content. This validation might be performed by a human, who then provides input to the document input portion 1110 to designate that the validation is complete. Alternatively, the validation may be automated so as to be performed by the document input portion 1110 without human intervention. The validation of the integrity may check any suitable aspect of the curriculum content. For example, the document input portion 1110 may check the quahty of the document for scanning, that all pages are present, that all referenced figures are present, or any other aspect of the curriculum content.

The document input portion 1110 also determines whether a backup of the curriculum content is required. If a backup is required, then the document input portion 1110 creates such a backup in any suitable manner. This backup of the curriculum content may be appropriately archived. It should further be appreciated that the system and method of the invention utilizes stored data at various points throughout the process. Accordingly, while not expressly described below, any of such stored data used in the system and method of the invention may be "backed up," as is necessary or desirable. The back-up data might be maintained in an "off-sight" storage facility, for example.

Accordingly, the document input portion 1110 formats and digitizes the curriculum content. Then the document input portion 1110 stores the digitized curriculum content in the new input memory 1510. After the document input portion 1110 inputs and stores the digitized curriculum content in the new input memory 1510, the curriculum content must then be structured by the structuring portion 1120 in accordance with the system and method of the invention.

In accordance with one embodiment, XML is used to structure the curriculum content. Similar to HyperText Markup Language (HTML), XML uses tags to describe elements within a page of text. However, HTML utilizes only predefined tags. On the other hand, XML allows the developer of the page to define the tags. The tags may be utilized to identify virtually any data item. Accordingly, XML allows a marked-up document to function similarly to a database record. In further explanation, XML may be characterized as a series of envelopes containing letters. The envelopes identify the letter within and are equivalent to the XML tags. On the other hand, the letter is equivalent to the text in a marked-up document. The text is identified by the particular XML tags associated with that particular text.

In conjunction with use of XML, a Document Type Definition (DTD) provides the rules under which a document is marked-up using XML. To explain further, the DTD specifies the structure of the XML marked-up document, including the manner in which the content of the document is nested. The DTD utilized to generate the screen shots shown in Figs. 5-49 is shown in Table 1, set forth below. The curriculum content may be marked-up simply by a human decision making process. That is, a human interacts with the structuring portion 1120 to mark up the curriculum content using some logical approach. Alternatively, an automated methodology may be used to mark up the curriculum content. For example, the structuring portion 1120 may mark up the curriculum content based on the detection of certain key words in the curriculum content. After the curriculum content is marked-up using XML, this marked-up material may be characterized as "curriculum material. " Subsequent to the structuring portion 1120 marking up the curriculum content resulting in curriculum material, the processed material is stored in the processed material memory 1520.

The invention herein is described using the markup language XML. However, it should be appreciated that XML is merely one markup language that might be used in the implementation of the invention. Accordingly, any appropriate markup language may be used in the system and method of the invention.

In further explanation of operation of the structuring portion 1120, the structuring portion 1120 may first download the curriculum material from the new input memory 1510. Then, the structuring portion 1120 determines whether the curriculum content is a graphic or simply text. If the curriculum content is a graphic, then the structuring portion 1120 digitizes the graphic if necessary. Thereafter, the structuring portion 1120 tags the graphic to designate where in the marked-up text the graphic is positioned.

If the structuring portion 1120 determines that the curriculum content is not a graphic, i.e., that curriculum content is text, then the structuring portion 1120 structures the text with a suitable markup language, as described above, resulting in structured curriculum material. After the text is marked-up and the graphics are tagged, the structuring portion 1120 performs a validation of the curriculum material, distinct from the validation performed by the validating portion 1130, as described below. For example, the validation process may include the structuring portion 1120 tagging the curriculum material as satisfactorily being digitized and structured.

In accordance with the system and method of the invention, after the curriculum content is marked-up, the resulting curriculum material is not immediately stored in the processed material memory 1520. Rather, in accordance with one embodiment of the system and method of the invention the marked-up curriculum material may be further processed by the structuring portion 1120. Specifically, the structuring portion 1120 may further enhance the curriculum material using a "style template," for example. The style template may be in the form of a small program that works in conjunction with the XML. Specifically, the style template modifies the marked-up XML language with certain fonts or other display characteristics, for example.

Accordingly, use of different style templates allows documents to be displayed differently, even though the same source XML document is utilized.

As a result of processing by the structuring portion 1120, various curriculum materials are stored in the processed material memory 1520. However, the curriculum material must then be further processed by the validating portion 1130 before the curriculum material is placed in the library memory 1530. Specifically, the validating portion 1130 performs a validation check of the curriculum material. This validation check may check any desired aspect of the curriculum material data, which is stored in the processed material memory 1520, including the electronic representation of the data, a check of whether the marked-up curriculum material is legal under the DTD being used, or whether the appearance and content of the curriculum material is acceptable. These validation checks are performed by the validating portion 1130 using an automated process or through interaction with a human decision making process.

Distinct from the above described validation process performed by the validating portion 1130, an edit check may also be performed. This edit check includes going to the actual source of the materials, i.e., a reviewer at the source. Accordingly, the edit check may involve a professor at a university reviewing internal materials, for example. Alternatively, the edit check may involve a pubUsher reviewing the curriculum material, for example. The validating portion 1130 might forward the material to the reviewer at the source using any appropriate method including e-mail. If the reviewer at the source determines that there are deficiencies in the document, then the reviewer at the source may inform the validating portion 1130 of such deficiencies. This may simply involve the reviewer forwarding an edited physical copy of the curriculum material to a person, who then inputs the edits by interacting with the validating portion 1130. This process may be repeated until the reviewer at the source, e.g., a professor, finally approves the curriculum material. Interim edited copies of the curriculum material may be stored in any suitable manner as is necessary or desirable. Once the curriculum material is approved, the validating portion 1130 "commits" the changes to the curriculum material. At this point in the preparation of the curriculum materials, the form and content of the curriculum material are ready to be placed in the library memory 1530. However, further processing is performed by the validating portion 1130. Specifically, it is necessary to determine the copyright status and the licensing status of each item of curriculum material. This information is utilized by the validating portion 1130 to attach appropriate metadata to each item of curriculum material. Metadata may be thought of as data about data. The metadata indicates the status of each item of curriculum material, including copyright and license status. After associating the metadata with the curriculum material, the validating portion 1130 stores the curriculum material in the library memory 1530.

It should be appreciated that all the curriculum material for all the customers, e.g., a university, is stored in the library memory 1530. The curriculum materials stored in the library memory 1530 are then used to generate a backend collection, as described below. That is, a backend collection is generated for each customer. Thus, each backend collection is a subset of the curriculum materials stored in the library memory 1530. However, before forming a backend collection, a records collection is generated by the assembly portion 1140 as described hereinafter.

In accordance with the system and method of the invention, the assembly portion 1140 assembles a "records collection" for a customer. To create a records collection, the assembly portion 1140 first assembles or obtains a list of ah curriculum content hcensed by that particular customer, i.e., curriculum content which the customer wants to license and use. The assembly portion 1140 then checks whether all the hcensed material on the list are in the library memory 1530. The assembly portion 1140 may determine that a curriculum content, which the customer wants to license and use, is not in the library memory 1530. In this situation, the assembly portion 1140 then effects contact with the copyright holder of the desired curriculum content. For example, the assembly portion 1140 may send an e-mail to a person at the "facility" that is developing the curriculum materials. That person may then contact the copyright holder and negotiate a licensee agreement. Once this new curriculum content is supplied from the copyright holder to the facility, the new curriculum content must be processed as described above. It should be appreciated that a customer may desire curriculum content that cannot be obtained for inclusion in the curriculum repository system of the invention. If this is the case, such unobtainable curriculum content must be removed from the customer's hst of desired curriculum content. The assembly portion 1140 may then determine that an item of curriculum material, which the customer wants to license and use, is indeed in the library memory 1530. Once the assembly portion 1140 determines that a particular item of curriculum material is in the library memory 1530, then the assembly portion 1140 adds that item to the "customer's record." That is, once an item of curriculum material is determined to be in the library memory 1530, then the assembly portion 1140 may be said to add that curriculum record to the customer's record. Eventually, the assembly portion 1140 checks all the items on the customer's list to determine if the desired items are in the library memory 1530. Once completed, the customer's record, which includes all available curriculum materials, is stored in the customer records memory 1540. The operation in accordance with the system and method of the invention passes to the collection portion 1150.

In accordance with the system and method of the invention, the collection portion 1150 assembles an accessible backend collection. Initially, the collection portion 1150 receives input identifying which customer is to be processed. Upon receiving this input, the collection portion 1150 then reads the customer's record stored in the customer records memory 1540. As described above, the customer record identifies which curriculum materials in the library memory 1530 to include in that particular customer's backend collection. On an item by item basis, the collection portion 1150 first checks whether each item of curriculum material has undergone an update to its content. This information regarding whether there has or has not been an update may be provided to the collection portion 1150 in any suitable manner. To explain further, the facility may have received notice from a publisher that certain curriculum material has undergone an update. However, the updated version of the curriculum material may not yet be in the library memory 1530. Accordingly, the collection portion 1150 checks this.

If the collection portion 1150 determines that there is an update to an item of curriculum material, the collection portion 1150 then determines whether the update is to be treated as a new document. If the revisions to a particular document are substantial, the updates can be designated as "new." The collection portion 1150 reads this designation. If the updates are not considered new, the processing of that particular curriculum material is taken over by the editing portion 1170, as described below.

Alternatively, if the updates to a particular curriculum material are new, then the processing of that curriculum material returns to the validating portion 1130, as described above. That is, the validating portion 1130 will proceed with a validation process with respect to that particular curriculum material.

If there is no update to the content of a particular curriculum material, then the collection portion 1150 proceeds to add that curriculum material to the accessible backend collection for the customer. In conjunction with adding the curriculum material to the backend collection, the collection portion 1150 verifies the license status of the particular customer vis-a-vis the requested curriculum material. Accordingly, this check performed by the collection portion 1150 further confirms that all license concerns are addressed. The collection portion 1150 then assigns access permissions to the curriculum material in the backend collection. These access permissions allow different persons to access the curriculum material in the backend collection in different ways. The access permissions may vary between different customers. Illustratively, the access permissions may utilize passwords, for example. That is, the collection portion 1150 places a tag on a certain item of curriculum material indicating that a user must enter a certain password to give access to the item of curriculum material. Finally, the collection portion 1150 completes creation of the backend collection by validating the customer access. As described above, the backend collection is a customer's own collection of curriculum material. The backend collection is a subset of the library, stored in the library memory 1530. Accordingly, different customers may well have different backend collections. As described further below, a user may also generate a frontend collection. A frontend collection is essentially a subset of a backend collection. However, it should be appreciated that the frontend collection is not an actual collection of documents. Rather, the frontend collection is simply a collection of pointers to curriculum materials in the backend collection.

In accordance with the system and method of the invention, the curriculum material in a customer's backend collection may be used in a variety of ways. The access portion 1160 operates to provide access to the backend collection stored in the backend collections memory 1550.

Illustratively, the backend collection may be maintained on a DVD. A DVD may be provided to each student, for example. Further, the access portion 1160 in accordance with the system and method of the invention may be disposed on the personal computer of the student, in accordance with one embodiment. The access portion 1160 generates the content of the backend collection for an end user, e.g., a student. Illustratively, the access portion 1160 generates the user interfaces as shown in Figs. 5-49 and as described below. To provide content to an end user, appropriate curriculum materials, i.e., elements, in the backend collection are selected to be accessible for that particular user. Then, a determination is made whether that content is to be delivered to the user on electronic media. If yes, then the access portion 1160, in accordance with an embodiment of the invention generates the media based on the licensed content. The media may be in the form of a DVD, for example. Then, the media is dehvered to the user. Alternatively, the curriculum materials in the backend collection, which are selected for the student, may be placed on a server for access by the end-user.

Another use of the backend collection in accordance with the system and method of the invention, is the generation of a permissions file. A permissions file is a permanent record for a particular customer. This permanent record documents and preserves the curriculum material, i.e., the backend collection for that particular customer, as well as all the permissions associated with the curriculum material. The permissions might include what students had access to what curriculum material, for example. The appropriate format for the customer file is selected. Then, the permissions file for the specific term or semester is generated. Then, the permissions file is archived on the appropriate media and delivered to the customer. In accordance with a further embodiment of the system and method of the invention, the access portion 1160 may provide the user access to the curriculum materials via a web page. Accordingly, a requestor logs into a web page. Then, the requestor selects the desired content area. Then, a faculty member selects a desired graphic or text. Then, the access portion 1160 forwards the desired graphic or text with permissions and copyright restrictions to the user. In accordance with the system and method of the invention, the editing portion 1170 processes changes to the content of the library memory 1530. When a change, such as an update, is effected, the editing portion 1170 determines whether the content that is to be changed is text or a graphic. If a graphic, for example, the editing portion 1170 gets the latest version of the source graphic from the library memory 1530. Then, the editing portion 1170 determines the location of the graphic in the corresponding XML document. The editing portion 1170 then applies the edits. Alternatively, the editing portion 1170 determines that the curriculum material to be changed is not a graphic, but rather XML marked text. The editing portion 1170 then gets the latest version of the XML text from the library memory 1530. The editing portion 1170 then applies the edits. After applying edits to either a graphic or non-graphic, the editing portion 1170 determines whether the edits are acceptable. If not, then further edits are applied. It should be appreciated that various iterations may be required before all the edits are acceptable. Throughout these iterations, it is of course necessary to store the previously edited document. After all the edits are done, the editing portion 1170 then finalizes the edits, i.e., commits the changes.

Figs. 5-49 illustrate various aspects of operation of the system and method of the invention. In particular, Figs. 5-49 show various user interfaces of the invention. These user interfaces are generated and controlled by the curriculum repository system 1000, shown in Fig. 2. Accordingly, the curriculum repository system 1000 both provides output as shown in Figs. 5-49, as well as processes input as described below.

Fig. 5 shows an exemplary user interface in accordance with the system and method of the invention. As shown in Fig. 5, the user interface includes a desktop 100. The desktop 100 includes a page view window 200. As shown in Fig. 5, the page view window 200 displays a book cover 212. The invention is based on the concept that a structured document can be and should be capable of expression in multiple ways. Accordingly, the pictured view shown in Fig. 5 is designed to function exactly hke the physical book from which the content, discussed below, was derived. Accordingly, as shown in Fig. 5, the page view window 200 displays a book cover 212 to simulate the actual book cover on the physical book. The page view window 200 includes a title bar 220 and a tool bar 230. The title bar 220 shows the title of the particular document displayed in the page view window 200. The tool bar 230 allows the user to perform a variety of operations on a page displayed in the page view window 200. For example, the user may page through the book shown in the page view window 200 by utilizing the toolbar 230. Fig. 6 illustrates an example of a page 210 displayed in the page view window 200 as a result of a user paging through the book 212. Accordingly, the book may be paged through sequentially in a manner that the author and publisher originally intended. As shown in Fig. 6, the page 210 possesses content 211 that one would expect on a typical page. The page 210 includes text 214, a table label 215, a table caption 216, and the table 217 itself.

However, there is a distinction between the page 210 shown in Fig. 6 in the page view window 200 and a traditional physical book. That is, the "picture" of the page shown in Fig. 6 is an expression of a structured XML data file and is not actually a scan or picture of the page 210. Each XML element, such as the table label 215, the table 217 itself, and table caption 216, are actually independently stored as distinct data files. In accordance with the system and method of the invention, these independent data files are then displayed in the page view window 200, shown in Fig. 6, to represent the linear sequence of the content 211. Fig. 7 illustrates a further aspect of the invention. As described above, the page 210 as shown in Fig. 7, for example, is not an image of the actual page in a physical text book, but rather a series of displayed distinct items. As a result, each of the distinct items may be individually manipulated. Illustratively, it is not necessary to expand the entire page 210 in order to view a particular graphic 218, on that page 210, in further detail. Rather, only a particular figure 218 might be expanded as shown in Fig. 8. That is, Fig. 8 shows the figure 218 on the page 210 expanded.

Further, as shown in Fig. 9, the system and method of the invention allow display of multiple graphics 219 such that a user may toggle between the different displayed items. Accordingly, the user is provided substantial flexibility in the manner in which he or she reviews the displayed material. Also, it should appreciated that the browser is not "cloned" in order to show the different items simultaneously. That is, only one application is running, which allows multiple views of the same source image. This is distinct from two appUcations running and showing the same image, i.e., cloning.

Fig. 10 illustrates a further aspect of the invention. As shown in Fig. 10, the displayed page 210 is represented in a standard "style sheet" format in the page view window 200. This format is generated using a standardized set of fonts and page formats. However, in accordance with the system and method of the invention, the user is not limited by a particular display of the content 211. That is, the user can adjust formats, such as preset formats, so as to choose fonts and page formats closer to their liking. Fig. 11 illustrates such a modification of the formatting of the content 211. Accordingly, the system and method of the invention provides a "customized view". This customized view may be created by utilizing the options in the toolbar 230 as shown in Figs. 10 and 11, for example. Fig. 12 shows a desktop 100 that includes a page view window 200, as described above. However, in accordance with the invention, a user may access the source content, e.g., the source XML content, by utilizing a variety of different windows. As shown in Fig. 12 and described above, one such window is the page view window 200. However, Fig. 12 also shows a table of contents window 300. The table of contents window 300 is used to access the same data and information as the page view window 200. That is, it should be appreciated that both the table of contents window 300 and the page view window 200 are an expression of the same data. However, the data in the table of contents window 300 is parsed specifically to show only the hierarchy of the document structure. Accordingly, as shown in Fig. 12, the table of contents window 300 includes a resource document 310, but not the actual content 211 of the page 210. In contrast to the table of contents window 300, the page view window 200 is parsed specifically to show the actual content 211 of pages 210 in a resource document 310.

In accordance with the system and method of the invention, a user may "unnest" items that are displayed in the table of contents window 300. As used herein "unnesting" may be characterized as selection of a particular displayed item to display further content contained within that particular item. Fig. 13 illustrates a further example of the table of contents window 300 showing the resource document 310 unnested. As shown in Fig. 13, the resource document 310 has been unnested to display the resource document chapters 312.

Fig. 14 illustrates further unnesting of the content of the book. As shown in Fig. 14, the resource document chapters 312 are unnested to reveal four resource document chapter sections 314 under the resource document chapter 312. As should be apparent from Figs. 13 and 14, the content as displayed by the table of contents window 300 is arranged in a hierarchical manner.

Fig. 15 illustrates further unnesting. Specifically, the hierarchy is unnested to reveal four additional resource document subsections 316 under the "Normal Heart" resource document section 314, which is in turn under the "The Heart" resource document chapter 312.

Yet again, Fig. 16 illustrates further unnesting of the hierarchy to reveal a table 320 within a resource document subsection 316, i.e., within subhierarchies of a book. In accordance with the system and method of the invention, the DTD utilized by the system of the invention is capable of literally thousands of nested hierarchies. One exemplary DTD is shown in Table 1, set forth below.

Fig. 17 illustrates further aspects of the table of contents window 300 and the page view window 200 in accordance with the system and method of the invention. Specifically, as shown in Fig. 17, the table of contents window 300 displays an item 219, and the page view window 200 displays the same item, which is illustratively a table. However, the table of contents window 300 displays the title of the item 219 only, while the page view window 200 displays the actual content 211 of the item 219. A user utilizes this feature by going to a particular displayed item 219 in the table of contents window 300 and double clicking the unnested item 219 in the table of contents window 300. By double clicking the unnested document, e.g., Table 13-1 as shown in Fig. 17, the page view window 200 is synchronized with the item 219 selected in table of contents window 300. Accordingly, both the table of contents window 300 and the page view window 200 are synchronized to display the same item 219. This affords the advantage of the user being able to display a section of the book, figure or graphic, for example, with ease and speed.

In accordance with an embodiment of the system and method of the invention, Fig. 18 illustrates a user's ability to vary the display of items in the table of contents window 300. Specifically, Fig. 18, illustrates a "table of contents level" box 400. Various check boxes 410 are disposed in the table of contents level box 400. As shown in Fig. 18, the check boxes 410 illustratively designate chapter, section level 1, section level 2, section level 3, section level 4, figure, table and Usting. A user may choose which levels are displayed in the table of contents window 300 by selecting or deselecting the desired levels. Accordingly, if the "table" option in the dialog box 400 was deselected, then the table of contents window 300 would not display any information regarding tables. The table of contents level box 400 may be activated using a variety of suitable techniques such as right clicking a mouse and then choosing the "table of contents level" option.

Fig. 19 further illustrates the selection of the levels using the table of contents level box 400. In the table of contents level box 400 shown in Fig. 19, only the "chapter" and "figure" levels are selected. Accordingly, the user has requested that only the figures and tables, as each relates to each chapter, be shown in the table of contents window 300.

In accordance with a further aspect of the system and method of the invention, Fig. 20 illustrates a manner in which a user may view the contents of a resource document. Fig. 20 shows a page view window 200, similar to those described above. However, Fig. 20 also shows an index window 500 displaying a list of symbols 520. Specifically, the index window 500 displays keyword data in alphabetical order. To explain, each resource document, which is stored in the database, is reviewed for keywords during digitization and structuring of the document. These keywords are chosen to represent as appropriately as possible the content of the resource document. The number of keywords chosen in a resource document may vary depending on the particular nature of the document. A user may select, i.e., unnest, a letter 510, as shown in Fig. 20, in the index window 500. For example, Fig. 21 shows an example of the index window 500 in which the letter 510 "D" has been unnested. As a result, the curriculum repository system 1000 lists all keywords in the resource document or documents that start with "D." Words associated with the keywords are also Usted, to provide additional information.

In accordance with the system and method of the invention, the various documents which may be accessed by the system of the invention contain an enormous amount of information. However, as a result of the hierarchical presentation of the data, the search engine of the invention works very quickly. Fig. 22 shows a search box 600 in accordance with the system and method of the invention.

As shown in Fig. 22, the search box 600 includes a text search box 610, a source drop down selector 620, and a results window 630. The search box 600 also includes a more options button 640, a show context check box 650, a clear button 660, and a search button 670.

The user may choose the particular resource document he or she wishes to search by selecting the desired resource document using the source drop down selector 620. Once the user has chosen the desired resource document 634, as shown in Fig. 22, the user then types the desired search term 612 into the text search box 610, as shown in Fig. 23. Fig. 23 illustrates an example in which the term "diabetes" is inserted in the text search box 610. If the user decides to perform a different search, the user may select the clear button 660. Selection of the clear button 660 clears the text search box 610, such that new text may be typed. When the user is ready to execute the search, the user then selects the search button 670. As a result, the curriculum repository system 1000 executes the search. Specifically, the curriculum repository system 1000 searches for the term within the domain of the resource document 634 selected in the source drop down selector 620, e.g., the resource document "DBSPATH - Cotran" as shown in Fig. 23. Once the search is executed, the curriculum repository system 1000 displays the search results in the results window 630 as shown in Fig. 24. In accordance with one embodiment of the system and method of the invention, the results window 630 displays the search results in the form of a query result item 632. The query result item 632 includes the searched resource document 634 and an occurrence indicator 638. The searched resource document 634 indicates which document was searched. The occurrence indicator 638 indicates the occurrences of the search term 612 in the searched resource document 634. As shown in Fig. 24 the search indicator 638 indicates that the search found several hundred instances of the term "diabetes" in the searched resource document 634. The searched resource document 634 may be selected so as to unnest the searched resource document 634. Once the user unnests the searched resource document 634, the curriculum repository system 1000 generates the content of the search box 600 as shown in Fig. 25.

As shown in Fig. 25, the search box 600 displays the searched resource document 634, as well as the searched resource document chapters 635. In accordance with the invention, the searched resource document chapters 635 are also associated with an occurrence indicator 638. As a result, a user may determine where in the hierarchy of the listed results the searched term 612 exists, as well as how many times the searched term 612 exists. Each searched resource document chapter 635 and its associated occurrence indicator 638 might coUectively be referred to as a query result item 632.

Fig. 26 illustrates further unnesting, similar to that described above with respect to the table of contents window 300. As shown in Fig. 26, the query result items 632 are shown in hierarchical fashion. The occurrence indicator 638 beside each item indicates the number of hits within that item. Accordingly, as shown in Fig. 26, the results window 630 indicates that there are twenty occurrences of the term "diabetes" in the search resource document chapter "The Pancreas." Further, within the chapter "The Pancreas" there is a section pathology. In the section pathology, there are five occurrences of the term "diabetes."

Fig. 27 illustrates further features of the system and method of the invention. As described above, the search box 600 includes a show context checkbox 650. The show context check box 650 allows the user to further unnest the search results to reveal an actual part of a sentence 639 in the particular segment of the resource document. Upon reviewing the search term 612 in the context of the sentence 639, the user may then choose to further review that particular occurrence of the search term 612.

If the user determines that a particular occurrence of the search term 612 warrants further examination, the user may then double chck, or otherwise select, the item in the results window 630. As a result of the user selecting the desired item in the results window 630, the curriculum repository system 1000 then generates that particular document in the page view window 200. Accordingly, the show context checkbox 650 allows the user to unnest the query results to reveal an actual part of the sentence 639 containing the search term 612, before the user reviews the full text representation 651 as displayed in the page view window 200. Accordingly, as further illustrated in Fig. 28, selecting the displayed sentence 639 in the results window 630 will instantly take the user to that resource document page in the page view window 200.

In accordance with the system and method of the invention, the search capabilities are not limited merely to the determination of the occurrence of a search term 612 in a resource document 634. Specifically, the invention allows a user to search based on relationships between terms, e.g., how close one search term 612 is to another term. As shown in Fig. 28, for example, the search box 600 includes a more options button 640. When the user selects the more options button 640 as shown in Fig. 28, the curriculum repository system 1000 generates a modified or expanded search box 600.

Illustratively, Fig. 29 illustrates an expanded search box 600 in accordance with one embodiment of the system and method of the invention. As shown in Fig. 29, the user is requiring that the search term 612 "diabetes" be found only when within 100 words of the term "pancreas." As a result, the number of hits is greatly decreased. In the example as shown in Fig. 29, the number of hits 633 is decreased from hundreds to twenty-three.

Fig. 30 illustrates utilization of an "expand all" command. The expand all command may be effected by clicking on a right pointing arrow, as shown in this exemplary embodiment. Alternatively, macros may be utilized to effect the expand all command. Upon the user selecting the expand all command, the curriculum repository system 1000 generates every relational incidence of diabetes to pancreas to the sentence level. Accordingly, as described above in conjunction with Fig. 28, the user may then make an informed decision whether to actually view the document itself in the page view window 200.

Fig. 31 illustrates further aspects of the invention. As illustrated by Fig. 31, the user can further Umit the search by reducing the number of words between the relevant terms. In the example illustrated by Fig. 31, the user has asked for all occurrences of diabetes within ten terms of pancreas. Accordingly, the result drops from 23 to one term. Further, since the user previously selected the "expand all" command, the results of the search are expanded to the sentence level.

As described above and shown in Fig. 32, the search box 600 includes a source drop down selector 620. The source drop down selector 620 provides a list of aU possible resources that the user may search. Accordingly, the source drop down selector 620 aUows the user to expand their search to include a larger number of resource documents. That is, the user may select the option "all documents" from the source drop down selector 620. When the user selects the "all documents" option, the curriculum repository system 1000 then searches aU the resource documents available and displays the results in the results window 630. As shown in Fig. 32, the four respective resource documents contain 300, 195, 77 and 21 hits respectively. As shown in Fig. 32, each searched resource document 634 is listed as an equal peer. Upon review of the display shown in Fig. 32, the user may select a query result item 632 for further review. Specifically, the user selects a desired query result item 632 and, as a result, unnests the query result item 632. As shown in Fig. 33, two query result items 632 are unnested.

Figs. 34-37 illustrate further aspects of the invention. In the examples shown above in Figs. 5-33, searches were performed on a particular resource document or resource documents. However, the system and method of the invention allow a user to more SpecificaUy select which materials that user desires to search. That is, a user may want to only search particular portion of a first resource document A and only particular portions of a second document B. For example, a user may want to search only those chapters in each resource document that deal specifically with heart disease. In order to aUow this selectivity, the invention allows a user to buUd

"frontend collections." In accordance with one embodiment of the invention, Fig. 34 shows a collection window 700 in the desktop 100. The collection window 700 is utiUzed by a user in conjunction with the table of contents window 300.

As described above, a frontend collection in accordance with the system and method of the invention is essentially a subset of a backend coUection. However, it should be appreciated that the frontend collection is not an actual coUection of documents. Rather, the frontend collection is simply a collection of pointers to curriculum materials in the backend collection.

In further explanation, a user who wishes to create a frontend collection executes an appropriate command, indicating a desire to do so. As a result, an empty collection window 700 appears as shown in Fig. 34. A user may then "drag" a selected item in the table of contents window 300 into the coUection window 700. As shown in Fig. 35, an item 702 "diabetes mellitusis" was selected in the table of contents window 300, dragged, and then dropped into the collection window 700. Fig. 36 shows an example in which a second item 703 was added to the coUection window 700. Fig. 37 Ulustrates a further aspect of the collection window 700. The collection window

700 includes a show book title checkbox 710. If the user selects the show book title checkbox 710, the items in the collection window 700 display the name of the appropriate resource document, e.g., the book title. This allows a user to further monitor the properties of the frontend coUection that the user is creating. It should be appreciated that the user can resequence the materials or can mix materials from different resource documents to generate a completely unique document. It should further be appreciated that the data representing the materials are not actuaUy mixed, but rather the linkages to the data are manipulated to provide the ability to generate the frontend coUections using the collection window 700.

Once a user generates a frontend coUection utilizing the coUection window 700 shown in

Fig. 37, the user may desire to save the frontend collection for any of a wide variety of reasons.

As shown in Fig. 38, a user may prompt a "save box" 800 using a suitable command. The save box 800 is generated on the desktop 100. The save box 800 includes a drop down Ust 810, a directory structure pane 820 and a plurality of buttons 830 for various features. Further, the save box 800 includes a text box 840, in which the user may designate the name of the particular frontend coUection.

Accordingly, the user may choose the directory to which the created frontend coUection is stored using the directory structure pane 820. The name of the stored frontend coUection is then entered using the text box 840. Further, the drop down list 810 allows the user to choose the location of an icon, for example, which represents the stored frontend collection.

Once the frontend coUection is saved, the frontend collection is displayed on the desktop

100 in the form of an icon 850, for example, as shown in Fig. 39. Thereafter, the frontend collection may be opened as a completely separate document, as shown in Fig. 40. As shown in

Fig. 40, the created frontend collection is opened and unnested to reveal all the contents of the created frontend coUection.

Fig. 41 illustrates further aspects of the frontend coUection created using the process as described in conjunction with Figs. 34-40. As shown in Fig. 41, a user selects a particular item 704 of interest. The user then double clicks the item of interest. As a result of this operation, the curriculum repository system 1000 generates the page view in the page view window 200 of the desired item 704. Thereafter, the item 704, a table as shown in the page view window 200, may be expanded for further viewing as shown in Fig. 42.

It should be appreciated that the frontend collection displayed in the coUection window 700, which was created by the user, may be queried for very selective results. That is, the coUection of documents functions as a separate document in every function of the application.

Accordingly, the frontend collection may be searched as shown in Fig. 43. Further, as shown in Fig. 44, the query results may be unnested to the sentence level, as described above. It should be noted that the hierarchy within each selected document is maintained as shown in Fig. 44.

In accordance with the system and method of the invention, the system is not limited to simply text and graphics. That is, video 221 may be embedded into the pages 210, as shown in Fig. 45, just as still photos may be embedded. Additionally, as shown in Fig. 46, a solid object rendering 223 may be utilized as a substitution for multiple view pictures.

Further, as shown in Fig. 47, solid objects 223 may be controlled by the user and can be virtually manipulated by the user. As illustrated by Fig. 48, an object may be turned and zoomed unlike still photos. As further illustrated by Fig. 49, animation 226 may be substituted to demonstrate processes. Such animation is very beneficial in many educational environments.

In accordance with the invention, Figs. 50-60 illustrate various aspects of the process of the invention. Specifically, Fig. 50 is a flowchart showing the process of the invention in accordance with one embodiment. As shown in Fig. 50, the process starts in step SI 00. Then, the process passes to step S200. In step S200, the material is received from any of a wide variety of sources. Then, in step S300, the received material is structured and digitized. Then the process passes to step S400.

In step S400, the material is input into the repository with associated metadata. Then, in step S500, the collection is assembled within the repository for utilization in the production system. Then the process passes to step S600. In step S600, the process determines whether there is an update to the content. If no, then the process passes to step S700. In step S700, the process creates an accessible collection. Then, the process passes to step S800. In step S800, persons access the coUection. Then the process passes to step S900. In step S900, the process determines whether the next term's content is needed, e.g., if a semester has ended and new content is needed. If yes, then the process returns to step S600.

Alternatively, if no in step S900, i.e., the next terms content is not needed, then the process passes to step S950. In step S950, the process ends.

In further explanation of Fig. 50, in step S600, the process may determine that there is an update to the content. Accordingly, if yes in step S600, then the process passes to step SI 000. In step S 1000, the process determines whether the update is to be treated as new. If yes, then the process returns to step S200. If no in step S 1000, i. e. , the update is not treated as new, then the process passes to step SI 100. In step SI 100, the changes to the content are processed. After step SI 100, the process returns to step S400. As described above, in step S400, the process inputs the material into the repository with associated metadata. Fig. 51 is a flowchart showing in further detail the receive material step S200 of Fig. 50.

As shown in Fig. 51, the process starts with step S200. Then, the process passes to step S210. In step S210, the process validates the integrity of the materials. Then, in step S220, the process determines whether a backup is required. If yes, then the process passes to step S230 and step S240. In step S230, the material is backed-up, i.e., a copy is created. In step S240, the process archives the backup. Then, the process passes to step S250.

Alternatively, if the process determines in step S220 that there is not a backup required, then the process also passes to step S250. In step S250, the process formats the material for digitization and structure. Then, the process passes to step S260. In step S260, the process returns to step S300. Fig. 52 is a flowchart showing in further detail the structure and digitize material step

S300 of Fig. 50. As shown in Fig. 52, the process starts with step S300. Then, the process passes to step S310. In step S310, the process uploads the material to the markup facilities.

Then, in step S320, the process determines whether the content is part of a graphic. If yes, then the process passes to step S340. In step S340, the graphic is digitized. Then, the process passes to step S360. In step S360, the graphic is tagged to intersect with the structured content. After step S360, the process passes to step S370.

Alternatively, in step S320, the process may determine that the content is not part of a graphic. If not, then the process passes to step S330. In step S330, the content is structured.

After step S330, the process also passes to step S370. In step S370, the material is validated. Then, the process passes to step S380. In step S380, the process returns to step S400, shown in Fig. 50.

Fig. 53 is a flowchart showing in further detail the "input material into repository with associated metadata" step S400 of Fig. 50. As shown in Fig. 53, the process starts with step S400. Then the process passes to step S405. In step S405, the process validates the materials for input. Accordingly, a determination is made in step S405 whether any further edits are required. Then in step S410, any further edits are applied. Then the process passes to step S420. In step S420, the edits are checked to determine if they are acceptable. For example, the edits might be checked by a professor. If the edits are not acceptable, then the process passes to step S430. In step S430, further edits are applied. After step S430, the process returns to step S420. Alternatively, if yes in step S420, i.e., the edits are acceptable, then the process passes to step S440. In step S440, the changes are committed. Then the process passes to step S450.

In step S450, the copyright status of the material is determined. Then in step S460, the license status of the material is determined. Then, in step S470, the metadata is assigned to the material, designating the copyright and license status. Then in step S480, the library is updated. Then the process passes to step S490. In step S490, the process returns to step S500. Fig. 54 is a flowchart showing in further detail the assemble collection within the repository for production system step S500 of Fig. 50. After step S500 as shown in Fig. 54, the process passes to step S510. In step S510, the list of licensed materials is assembled. Then, in step S520, the process determines whether all the materials are in the system. If no, then the process passes to step S530. In step S530, the copyright holder of the material is contacted. Then, in step S540, a license is negotiated for the inclusion of new materials, which is effected starting with step S200 in Fig. 50. Then the process passes to step S560.

Alternatively, the determination in step S520 may determine that aU the materials are in the system. Accordingly, if yes in step S520, the process passes to step S550. In step S550, the process adds a curriculum material record to a customer record. Then, the process passes to step S560. In step S560, the process returns to step S600 in Fig. 50.

Fig. 55 is a flowchart showing in further detail the create accessible coUection step S700 of Fig. 50. As shown in Fig. 55, the process starts in step S700. Then, the process passes to step S710. In step S710, the hcensed material is verified. Then, in step S720, the customer data is extracted from the production system. Then the process passes to step S730. In step S730, the access permissions are assigned. Then, in step S740, the customer access is validated.

After step S740, the process passes to step S745. In step S745, the process returns to step S750 as shown in Fig. 50. Fig. 56 shows in further detaU the "access the coUection" step of Fig. 50. As shown in

Fig. 56, the process starts in step S800. Then the process passes to step S810. In step S810, the process determines the use of the content. Based on the use determined in step S810, the process passes to one of steps S820, S830 or S840.

In step S820, the process generates content for the end-user. Alternatively, in step S830, the process generates the content for the permissions file. Alternatively, in step S840, the process requests to access the content via web pages, i.e., via the Internet.

After either one of step S820, step S830, or step S840, the process passes to step S850. In step S850, the process returns to step S900.

Fig. 57 is a flowchart showing in further detail the generate content for end-user step S820 of Fig. 56. As shown in Fig. 56, the process starts in step S820. Then, the process passes to step S821.

In step S821, appropriate elements, i.e., the items requested by the customer, are selected from the collection. Then, the process passes to step S822. In step S822, the process determines whether the content is to be dehvered on media. If no, then the process passes to step S823. In step S823, the hcensed content is placed on the server for end-user access. After step S823, the process passes to step S828.

Alternatively, if the content is to be delivered on media in step S822, then the process passes to step S824. In step S824, the media is generated based on the hcensed content. After step S824, the process passes to step S826. In step S826, the media is delivered. Then, the process passes to step S828. Accordingly, after either step S823 or step S826, the process passes to step S828. In step

S828, the process returns to step S850 as shown in Fig. 56.

Fig. 58 is a flowchart illustrating in further detail the generate content for permissions file step S830 of Fig. 56. As shown in Fig. 56, the process starts in step S830. Then, the process passes to step S832. In step S832, the appropriate elements are selected from the collection. Then, in step

S833, the appropriate format for the customer file is selected. Then, the process passes to step S834.

In step S834, the permissions file for the specific term is expressed or generated. Then, the process passes to step S836. In step S836, the permissions file is archived on the appropriate media and delivered.

After step S836, the process passes to step S838. In step S838, the process returns to step S850 as shown in Fig. 56. Fig. 59 is a flowchart showing in further detaU the "process requests to access content via web pages" step S840 on Fig. 56. As shown in Fig. 59, the process starts with step S840. Then, the process passes to step S842. In step S842, a requestor logs into a web page. Then, in step S844 the requestor selects the desired content area. Then the process passes to step S846. In step S846, a faculty member selects a desired graphic/text. Then, in step S846, the desired graphic/text is forwarded with permissions and copyright restrictions.

After step S847, the process passes to step S848. In step S848, the process returns to step S850 as shown in Fig. 56.

Fig. 60 is a flowchart showing in further detail the "process changes to content" step SI 100 of Fig. 50. As shown in Fig. 60, the process starts with step SHOO. Then, the process passes to step S 1120. In step S 1120, the process determines whether the content that is to be changed is a graphic. If yes, then the process passes to step SI 140. In step SI 140, the process gets the last version of the source graphic. Then, in step SI 150, the location of the graphic is determined and referenced. Then the process passes to step SI 160. Alternatively, if no in step SI 120, i.e., the content is not a graphic but rather an XML marked-up document, then the process passes to step SI 130, in which the process gets the latest version of the source XML document. Then the process passes to step SI 160. In step SI 160, the edits are applied. Then the process passes to step S 1170.

In step SI 170, the edits are checked to determine if they are acceptable. For example, the edits might be checked by a professor. If the edits are not acceptable, then the process passes to step SI 175. In step SI 175, further edits are applied. After step SI 175, the process returns to step SI 170. Alternatively, if yes in step SI 170, i.e., the edits are acceptable, then the process passes to step SI 180. In step SI 180, the changes are committed. Then, in step SI 190, the process returns to step S400 in Fig. 50. As described above, the system and method of the invention may utilize a particular DTD in the mark-up of the curriculum content. This DTD is set forth below in Table 1. However it is to be appreciated that the DTD set forth in Table 1 is merely illustrative and not limiting. That is, other DTDs may be utUized in the system and method of the invention. As will be apparent to one of ordinary skill in the art, the DTD in Table 1 utilizes various files from the International Organization for Standardization's ISO standard 8879 (1986); Standard Generalized Markup Language (SGML), which is herein incorporated by reference in its entirety. SGML is an international standard for the description of marked-up electronic text. ξ£

^•uoμdBo jo τapouτ aqj o 'φ no/₀ pappy -

^•rjxed o japouj luaruoo aφ o ϊψBuιo/₀ pappy -

^•pTrøτr jap jo ppoui ruaruoo aφ o% Tj rujo poppy ^_ St?

^■pearr-uuai jo japoru UΘUOO aiμ o} Bmrajqj pappy -

^•UIJ91. o japoui ruaruoo au oj 'UJBUI% pappy -

japoui τuaτuoo aqi o emuijoj pappy -

^•aμμ jo japoui

aqq.01 ϊq:euι<% pappy -

^•rxaιy₀ Ajnua aτμ UTOJJ 'TTΓBUIO^ paAoura-jj - Ov

: jBa e Arai ψvm aiaq . pauTapa-g ' £

ja SUB/uoμsanb JOJ sruauiap B pue b o sa qμ:rre pappy 'Z ^•τuauιaτa sis jdraa a i o amqurre sdeαjreuis pappy T

9I/IΪ/6661

— i> ζ£

<- AHOLSffiiaONVHO ~i>

<-- SNOIIV HCΓISNOO MOisaα -ι>

<-- -i>

<- 666l ^*-q° O ^~i> ζZ

<-- :aιvαMθiLVtraoτvNiorao ~ι>

<- ^~i>

<- sas ja tjreqo πnoads OSI (i ~i>

<- ^'αaain a-a saτnαoiAi -ι>

<- ~i> or

<~ -s nuBra ~j>

<— pur s^ooq oμμuaps jo am nμs aqi luasai a^ ^'aSOcTlQd ~"ϊ>

Ma//0lZ0000r ζTΛ uaxun oα αLd//S9T^SoT^om:l⁰⁹X ^βomog liA//",,

:ιaτμuapι oηqnj puuo

<- αiα iπamnooα satgoιouqoaχ aoinos nμTΛ ^*aτnαθI^ ~i>

<- $dxgppτ 1^:90: IZOI/cO_/υOOZWT A 'pp^uaranoop :pι$ -j> laiavx

L£0SZ/l0SΛ/lDd 9LZLUZQ OΛV Consequently after this change math of any kind may no longer appear in author, affil, date, pubUsher, editor, citation and label.

Also, dformula and dformgrp may no longer appear in keyword, termhead and def.head. 4. Changed the content model of metadata to have editor near author and editor be repeatable.

5. Added the "affil" attribute to editor to link it to the appropriate affiliation.

6. Changed type of pointer in xref to IDREFS .

7. Added title to dformgrp so that it would be in synch with dformula. 8. Changed the content model of cell to allow it to be empty.

9. Changed the type of the attribute of "affil" on author and editor to IDREFS.

10. Reordered the attributes on the cell element.

11. Changed the default to 1 on the attributes column.span and row.span of the cell element. This is consistent with the usual interpretation of the span meaning "this cell spans over X columns and Y rows".

12. Changed the content model of table so that footnotes would appear at the very end.

13._. Added the TIFF notation.

14. Changed the type of the attribute "num" on dformgrp and dformula to CD AT A. 15. Added striked. out value for the type attribute of the emphasis element.

16. Changed the content model of bibliography to make title optional.

17. Removed bibliography and glossary from the document contents model.

2000/02/10 1. Changed the content model of caption to remove label from there.

2. Changed the type of the "pointer" attribute of citation, ref to IDREFS.

3. Changed the type of the "pointer" attribute of footnote.ref to IDREFS.

4. Added the definitions for ISOamsa, ISOamsb, ISOamsc, ISOamsn, ISOamso, ISOamsr, ISObox, ISOcyrl, ISOcyr2, ISOgrk2 and ISOgrk4 with the necessary references to those external entities.

~>

<!- ENTITIES AND NOTATIONS -->

<!NOTATION TIFF PUBLIC

"+//ISBN 0-7923-9432-1 -Graphic Notation//NOTATION Aldus/Microsoft Tagged Interchange File Format//EN'>

<!ENTITY % ISOamsa PUBLIC "ISO 8879-1986//ENTITIES Added Math Symbols: Arrow Relations//EN'

"ISOamsa" >

<!ENTITY % ISOamsb PUBLIC "ISO 8879-1986//ENTITIES Added Math Symbols: Binary Operators//EN' "ISOamsb" >

<!ENTITY % ISOamsc PUBLIC "ISO 8879-1986//ENTITIES Added Math Symbols: Dehmiters//EN'

"ISOamsc" >

<!ENTITY % ISOamsn PUBLIC

"ISO 8879-1986//ENTITIES Added Math Symbols: Negated Relations//EN' "ISOamsn" >

<!ENTITY % ISOamso PUBLIC

"ISO 8879-1986//ENTITIES Added Math Symbols: Ordinary//EN' "ISOamso" >

<!ENTITY % ISOamsr PUBLIC

"ISO 8879-1986//ENTITrES Added Math Symbols: Relations//EN'

"ISOamsr" > <!ENTITY % ISObox PUBLIC

"ISO 8879-1986//ENTITIES Box and Line Drawing/ EN'

"ISObox" >

<!ENTITY % ISOcyrl PUBLIC "ISO 8879-1986//ENTITIES Russian Cyrillic//EN'

"ISOcyrl" >

<!ENTITY % ISOcyr2 PUBLIC "ISO 8879-1986//ENTITIES Non-Russian Cyrillic/ EN' "ISOcyr2" >

<!ENTITY % ISOdia PUBLIC "ISO 8879-1986//ENTITIES Diacritical Marks//EN'

"ISOdia" >

<!ENTITY % ISOgrkl PUBLIC

"ISO 8879-1986/ ENTITIES Greek Letters//EN'

"ISOgrkl" > <!ENTITY % ISOgrk2 PUBLIC

"ISO 8879-1986//ENTITIES Monotoniko Greek//EN'

"ISOgrk2" >

<!ENTITY % ISOgrk3 PUBLIC "ISO 8879-1986//ENTITIES Greek Symbols//EN'

"ISOgrk3" >

<!ENTITY % ISOgrk4 PUBLIC "ISO 8879-1986//ENTITIES Alternative Greek Symbols//EN' "ISOgrk4" >

<!ENTITY % ISOlatl PUBLIC

"ISO 8879-1986//ENTITIES Added Latin 1/ E "

"ISOlatl" >

<!ENTITY % ISOlat2 PUBLIC

"ISO 8879-1986//ENTITIES Added Latin 2//EN"

"ISOlat2" >

<!ENTITY % ISOnum PUBLIC

"ISO 8879-1986//ENTITIES Numeric and Special Graphic//EN'

"ISOnum" >

<!ENTITY % ISOpub PUBLIC

"ISO 8879-1986//ENTITIES Publishing//EN'

"ISOpub" >

<!ENTITY % ISOtech PUBLIC

"ISO 8879-1986//ENTITIES General Technical/ EN"

"ISOtech" >

%ISOamsa;

%ISOamsb;

%ISOamsc;

%ISOamsn;

%ISOamso;

%ISOamsr;

%ISObox;

%ISOcyrl;

%ISOcyr2;

%ISOdia;

%ISOgrkl;

%ISOgrk2;

%ISOgrk3;

%ISOgrk4;

%ISOlatl;

%ISOlat2;

%ISOnum;

%ISOpub;

%ISOtech;

<!ENTITY unknown "[unknown character]" > <!ENTITY Ulegible "[illegible text]" > <!ENTITY handwritten.text "[handwritten text]" >

--> <l~ LNTERNAL PARAMETER ENTITIES ->

^_| ******************************************************** ->

LISTS ->

<!ENTITY % hsts "def.list I list" >

PARAGRAPH-LEVEL STRUCTURES ->

<!~ENTITY % math "formula | dformula | dformgrp" >

<!-- REFERENCE ELEMENTS ->

<!~ENTITY % refs "citatiomref | footnote.ref | xre ' >

<!-- TEXT RENDERING ELEMENTS — >

<! -ENTITY % rend "emphasis | superscript | subscript" >

<!-- ELEMENTS OCCURRING INSIDE TEXT ->

<!~ENTITY % text "%rend; | %refs;" >

<!-- ISO MATH ALPHABET TYPES ->

< ! ~ Indicates which alphabet is used in the element. This may be changed to a notation attribute, where the notation could describe a keyboard mapping. Modify the set as necessary. -> <!ENTITY % a.types "(latin|greek|cyrUlic|hebrew|kanji) 'latin'" >

<!-- TABLE BORDER ENTITIES ->

<!-- NOTE: we could have all border attributes be defined to take the same declared values. XML allows this but SGML doesn't so if there is ever a need to go from XML to SGML, the table attributes would have to be converted.

In each of the following border attributes the declared values are of the form: pp.vw where "pp" is a prefix used so that a tag using aU those border attribute values won't have a name clash. The meaning of "vw" is as follows:

0 no border

1 single border

2 double border

3 triple border dashed dashed border dotted dotted border bold bold border -->

<!ENTITY % table.left.border "left.border (lb.O | lb.l | lb.2 | lb.3 | lb.dashed | lb.dotted | lb.bold)" ->

<!ENTITY % table.rightborder

"rightborder (rb.O | rb.l | rb.2 | rb.3 | rb.dashed | rb.dotted | rb.bold)" >

<!ENTITY % table.top.border

"top. border (tb.O | tb.l | tb.2 | tb.3 | tb.dashed | tb.dotted | tb.bold)" >

<!ENTITY % table.bottom.border

"bottom.border

(bb.O I bb.l I bb.2 | bb.3 | bb.dashed | bb.dotted | bb.bold)" >

<!- TABLE CELL ALIGNMENT ENTITIES ->

<! — The ahgn attribute is for the horizontal alignment: left aligned left center centered right ahgned right justified justified text

The valign attribute is for the vertical alignment: top aligned with the top of the cell vcenter centered bottom aligned with the bottom of the cell — >

<! -ENTITY % table, align "align (left | center | right | justified)" > <! -ENTITY % table.valign

"valign (top | vcenter | bottom)" >

<!-- The shaded attribute is "yes" if the cell is shaded, "no" otherwise. > <! -ENTITY % table. shaded "shaded (yes | no)" >

<!- ENTRY POINT ->

<! — ELEMENT document (title, metadata?, doc.imprint?, chapter*, section*, footnote*) > <l— ******************************************************** >

<!- METADATA ELEMENTS ~>

<!-- METADATA INFORMATION ~>

<!ELEMENT metadata (author*, editor*, affil*, date?, publisher?) >

AUTHOR ->

<!ELEMENT author (#PCDATA I %text;)* > <!ATTLIST author affil IDREFS #ΓMPLΓED >

<!- AUTHOR'S ORGANIZATIONAL

AFFILIATION ->

<!ELEMENT affil (#PCDATA I %text;)* >

<!ATTLIST affil id ΓD ^REQUIRED >

<!-- ALPHANUMERIC DATE -> <!ELEMENT date (#PCDATA I %text;)* >

<!-- PUBLISHER ->

<!ELEMENT pubUsher (#PCDATA I %text; )* >

EDITOR — >

<!ELEMENT editor (#PCDATA I %text;)* >

<!ATTLIST editor affil IDREFS #ΓMPLΓED >

DOCUMENT ΓMPRΓNT ->

<!ELEMENT doc.imprint

(para | table | list)* >

— >

<!-- GENERAL TEXT ELEMENTS -> ->

<!-- SECTION ->

<!ELEMENT section (title, metadata?, (%paras;)*,

(section | chapter)+, glossary?, bibliography*, footnote*)

>

<!-- CHAPTER ->

<!ELEMENT chapter (title, metadata?, keyword*, abstract?, (%paras;)*, level*, glossary?, bibliography*, footnote*) >

<l- LEVEL -> <!ELEMENT level (title, (%paras;)*, level*, glossary?, bibliography*) >

<!-- TITLE — > <!ELEMENT title (#PCDATA | label | %text; | %math;)* >

<!-- GLOSSARY — >

<!ELEMENT glossary (title, (%ρaras;)*) >

<l~ BIBLIOGRAPHY — >

<!ELEMENT bibliography

(title?, (%paras; | bib.list | bibliography)+) >

<!-- BIBLIOGRAPHIC LIST — >

<!ELEMENT bib.list (citation+) >

<!-- CITATION — >

<!ELEMENT citation (#PCDATA | label | %text; )* >

<!ATTLIST citation id ΓD #ΓMPLΓED >

CATEGORIZATION TERM ->

<!ELEMENT keyword (#PCDATA I %text; | formula)* >

<!-- BRIEF SUMMARY OF THE CONTENT ->

<!ELEMENT abstract (title?, (%paras;)+) >

->

<!- ELEMENTS AT THEPARAGRAPHLEVEL -> ->

<!-- LIST -> <!ELEMENT list (title?, item+) >

LIST ITEM ->

<!ELEMENT item (label?, (%paras;)+) >

<l- DEFINITION LIST ->

<!ELEMENT def.list (title?, termhead?, def.head?, def.item+) >

<!- DEFINITION LIST TERM HEADING — >

<!ELEMENT termhead (#PCDATA | %text; | formula)^*1 > <!- DEFINITION LIST DEFINITION HEADING -->

<!ELEMENT def.head (#PCDATA | %text; | formula)* >

<!- DEFINITION LIST ITEM

<!ELEMENT def.item (term, def) >

<!-- DEFINITION LIST TERM — >

<!ELEMENT term (#PCDATA I %text; | %math;)* >

DEFINITION LIST DEFINITION ->

<!ELEMENT def (%paras;)+ >

<!-- PARAGRAPH — >

<!ELEMENT para (#PCDATA I %text; | %lists; | %math;)* >

FIGURE — >

<!ELEMENT figure (title?, metadata?, graphic, textual.rep?, caption?) >

<!ATTLIST figure id ID #ΓMPLΓED >

<!-- CAPTION ->

<!ELEMENT caption (#PCDATA | %text; | %math;)* >

<!-- FORM ->

<!ELEMENT form EMPTY >

<!-- CLINICAL CORRELATION — >

<!ELEMENT clinical, correlation

(title?, (%paras;)+) >

QUESTION/ANSWER SEGMENT — >

<!ELEMENT qa (title?, (q.group | a.group | %paras;)+) >

QUESTION GROUP ->

<!ELEMENT q.group (title?, (q | %paras;)+) >

<!-- QUESTION — >

<!ELEMENT q (label?, (%paras;)+) > <!ATTLIST q answers IDREFS #ΓMPLΓED >

<!- ANSWER GROUP ->

<!ELEMENT a.group (title?, (a | %paras;)+) >

<!- ANSWER ->

<!ELEMENT a (label?, (%paras;)+) >

<!ATTLIST a id ΓD #ΓMPLΓED > _<-₎ ******************************************************** >

<!- TABLE MODEL ~> <-| ******************************************************** >

<!- TABLE ->

<!ELEMENT table (title?, graphic, (tgroup+ | textual.rep), caption?, footnote*) > <!ATTLIST table id ΓD #ΓMPLΓED >

<!- TABLE GROUP ->

<!— Simple tables have only one table group but tables in which the number of columns or stubs change at some point(s) in it must use multiple table groups.

The attribute "ncols" records the number of columns in the table group. The attributes "left, stubs" and "right, stubs" respectively record the number of left and right stubs in the table. The left and right stubs are columns that contain headings for the rows. <!ELEMENT tgroup (header?, body, footer?) >

<!ATTLIST tgroup ncols NMTOKEN #REQUTRED > left, stubs NMTOKEN "0" rightstubs NMTOKEN "0" >

<! ELEMENT header (colspec÷, row+) >

<!ELEMENT body (colspec÷, row+) >

<!ELEMENT footer (colsρec+, row+) > <!-- COLUMN SPECIFICATION ->

<!— A colspec element records attributes that are applicable to a column within the realm of the header, body or footer that contains that column. The values set for a column can be overridden at the cell level if necessary.

The header, body and footer elements should contain as many colspec elements as there are columns in the table. Unfortunately, this cannot be enforced by the DTD. — >

<!ELEMENT colspec EMPTY > <!ATTLIST colspec

%table. align; "left"

%table.valign; "vcenter"

%table.left.border; "lb.0" %table.right.border; "rb.O"

%table.shaded; "no" >

<!- TABLE ROW -> <!— Each row contains as many cell or ocell elements as the number of columns in the table group. — >

<!ELEMENT row (cell | ocell)+ >

<!ATTLIST row

%table.top.border; "tb.O" %table.bottom.border; "bb.O" >

<!- TABLE CELL -->

<!ELEMENT cell (%paras;)* >

<!ATTLIST cell

%table.ahgn; #IMPLIED

%table.valign; #IMPL1ED %table.left.border; #IMPLIED

%table.right.border; #IMPLIED

%table.top.border; #IMPLIED

%table.bottom.border; # MPUED

%table. shaded; #IMPLIED column.span NMTOKEN "1" row.span NMTOKEN "1" >

<!ELEMENT ocell EMPTY >

<!ELEMENT formula (graphic?, textual.rep) >

<!ATTLIST formula id ΓD #ΓMPLΓED alphabet %a.types; > <!-- DISPLAY FORMULA — >

<!ELEMENT dformula (title?, graphic?, textual.rep) >

<!ATTLIST dformula id ID #ΓMPLΓED num CDATA #IMPLIED ahgn (left | center | right) "center" alphabet %a.types; >

<!-- DISPLAY FORMULA GROUP ->

<!ELEMENT dformgrp (title?, (dformula)+) > <!ATTLIST dformgrp id ID #ΓMPLIED num CDATA #1MPL1ED > ahgn (left | center | right) "center" >

<!- ELEMENTS OCCURRING INSIDE TEXT ->

"italics" >

<!ELEMENT superscript

(#PCDATA I %rend;)* > <!ELEMENT subscript (#PCDATA j %rend;)* >

<!-- FOOTNOTE ->

<!ELEMENT footnote (label, (%ρaras;)+) > <!ATTLIST footnote id ΓD #REQUΓRED >

<!- LABEL ->

<!ELEMENT label (#PCDATA | %text;)* >

<!-- REFERENCE ELEMENTS ~>

<!ATTLIST citationref pointer IDREFS #REQUTRED >

<!-- FOOTNOTE REFERENCE ->

<!ELEMENT footnote.ref (#PCDATA | %rend;)* >

<!ATTLIST footnote.ref pointer IDREFS #REQUTRED >

<!ELEMENT xref (#PCDATA | %rend;)* >

<!ATTLIST xref pointer IDREFS #REQUIRED >

<!- MISCELLANEOUS ELEMENTS -->

<!ELEMENT graphic EMPTY >

<!— picfile Defined system entity for the physical graphic file (these are defined with the document) --> <!ATTLIST graphic picfile ENTITY #REQUTRED >

<!ELEMENT textual.rep

(#PCDATA I %rend;)* >

<l— ********** *********TH S Γ F T")TT" ****** ********************* *__'>

As described above, one embodiment of the system of the invention as shown in Figs. 2-4 is in the form of a computer system. As used herein, the term "computer system" is to be understood to include at least a processor operating with a memory. The memory stores at least portions of an executable program code at one time or another. Additionally, the processor executes one or more of the instructions included in that executable program code. As used herein, it wUl be appreciated that the term "executable program code" and term "software" mean substantially the same thing for the purposes of description as used herein. Further, it is to be appreciated that to practice the system and method of the invention, it is not necessary that the processor and/or the memory be physically located in the same place.

That is, it should be appreciated that each of the processor and the memory may be located in geographically distinct locations and connected so as to communicate in a suitable manner. Additionally, it should be appreciated that the processor and/or the memory may be different physical pieces of equipment. Accordingly, it is not necessary that the processor be one piece of equipment in one location and that the memory be another single piece of equipment in another location. That is, it is contemplated that the processor may be two pieces of equipment in two different physical locations. The two pieces of equipment may be connected in any suitable manner. Additionally, the memory may include two or more pieces of memory in two or more physical locations. Further, the memory could include or utilize memory stores from the Internet, Intranet, Extranet LAN or some other source as may be necessary or desired.

As described above, the invention may illustratively be embodied in the form of a computer program or computer operating system. It is to be appreciated that the software that enables the computer operating system to perform the operations described above may be supplied on any of a wide variety of media. Further, it should be appreciated that the implementation and operation of the invention may be in the form of code written in any suitable programming language. It should be appreciated that the software code or programming language that is utilized in a computer system to perform the above described invention may be provided in any of a wide variety of forms. Illustratively, the software may be provided in the form of machine language, assembly code, object code, or an original source code, as weU as other forms of media. Further, the software may be in the form of compressed or encrypted data, for example, of the foregoing types of media.

Additionally, it should be appreciated that the particular medium utilized may take on any of a variety of physical forms. Illustratively, the medium may be in the form of a compact disk, an integrated circuit, a hard diskette, a floppy diskette, a tape, a RAM, a ROM, a remote transmission using a type of communication circuit, as well as any other medium or source of information that may be read by a computer or other operating system.

Accordingly, the software of the method of the invention may be provided in the form of a floppy disk or be transmitted in some form using a direct telephone connection, the Internet, the Intranet, or a satellite transmission, for example. Further, the programming language enabling the method of the invention as described above may be utilized on aU of the foregoing and any other medium by which software or executable program language may be communicated to and utilized by a computer or other operating system. As described herein, the system and method of the invention may utilize an application program, a set of separate apphcation programs, a module of a program, or a portion of a module of a program, for example. As noted above, it should be appreciated that the computer readable language used in the system and method of the invention may be any of a wide variety of programming languages. Further, it is not necessary that a single programming language be utilized in conjunction with operation of the system and method of the invention. Rather, any number of different programming languages may be utilized as is necessary or desirable. As described above, in the system and method of the invention, a variety of user interfaces are utilized. A user interface may be in the form of a dialogue screen as illustrated herein. As used herein, a user interface includes any software, hardware or combination of hardware and software used by a computer system or other operating system that aUows a user to interact with the operating system. A user interface may include any of a touchscreen, keyboard, mouse, voice reader, voice recognizer, dialogue screen, a menu box, a Ust, a checkbox, a toggle switch, a pushbutton or any other object that allows a user to receive information regarding the operation of the program and/or provide the operating system with information. The information provided by the user may be in the form of a command, selection or data, for example. A user interface is utUized by an operating system in the process of running an application program. As should be appreciated, a user interface is typically used for interacting with a user either to convey information or receive information. However, it should be appreciated that in accordance with the system and method of the invention, it is not necessary that a human user actually interact with the user interface generated by the operating system. Rather, it is contemplated that the user interface of the invention interact, i.e., convey and receive information, in communication with another operating system or program, rather than a human user. Illustratively, the other operating system may simulate in whole or in part, the actions of a human user. Further, it is contemplated that the user interfaces utilized in the invention may interact partially with another operating system while also interacting partiaUy with a human user.

It will therefore be readily understood by those persons skUled in the art that the present invention is susceptible to broad utility and apphcation. Many embodiments and adaptations of the present invention other than those herein described, as weU as many variations, modifications and equivalent arrangements, wiU be apparent from or reasonably suggested by the invention in the foregoing description thereof, without departing from the substance or scope of the present invention.

Accordingly, while the present invention has been described herein in detail in relation to its exemplary embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made merely for purposes of providing a full and enabling disclosure of the invention. The foregoing disclosure is not intended or to be construed to hmit the present invention or otherwise exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements, the present invention being hmited only by the claims.

Claims

What is claimed is:

1. A method for providing a curriculum repository comprising the steps of: obtaining various pieces of obtained curriculum content; structuring the obtained curriculum content in a hierarchical manner to generate structured curriculum materials; combining the structured curriculum materials into an electronic data coUection, the electronic data coUection forming a curriculum repository; and selecting items in the curriculum repository to form a customer collection for a customer.

2. The method of claim 1, further including the steps of: determining if the obtained curriculum content is in a digital format before structuring the obtained curriculum material; and if any obtained curriculum content is not in a digital format, then digitizing that piece of obtained curriculum content.

3. The method of claim 1, wherein selecting items in the curriculum repository to form a customer coUection includes determining if a copyrighted item in the curriculum repository is Ucensed by the customer; and if such copyrighted item in the curriculum repository is hcensed by the customer, then including that copyrighted item in the customer coUection; and if such copyrighted item in the curriculum repository is not licensed by the customer, then not including that copyrighted item in the customer coUection.

4. The method of claim 3, wherein if such copyrighted item in the curriculum repository is not hcensed by the customer and not included in the customer coUection, then the method including the step of arranging for the customer to secure a hcense for such copyrighted item in the curriculum repository.

5. The method of claim 1 , wherein selecting items in the curriculum repository to form a customer coUection includes storing a record Ust for each customer, the record Ust identifying items in the curriculum repository used in the customer coUection of the customer.

6. The method of claim 1, wherein selecting items in the curriculum repository to form a customer coUection includes determining if a selected item in the curriculum repository has been updated; and if such item in the curriculum repository has been updated, then including an updated document in the customer coUection.

7. The method of claim 1, wherein obtaining the various pieces of obtained curriculum content includes validating the curriculum content.

8. The method of claim 7, wherein validating the curriculum content includes checking at least one of the quality of print, that aU pages are present and that aU referenced figures are present.

9. The method of claim 1, wherein structuring the obtained curriculum content includes: marking up the curriculum content; and processing the curriculum content using a style template, the style template modifying the marked-up curriculum content.

10. The method of claim 1, wherein selecting items in the curriculum repository to form a customer coUection includes storing the structured curriculum materials on an electronic media; and the method further comprising the step of distributing the electronic media to a user, the user affiliated with the customer.

11. The method of claim 10, wherein the electronic media is a DVD optical disk.

12. The method of claim 10, wherein the electronic media is distributed to a user over the Internet.

13. The method of claim 10, wherein the user accesses the customer collection utilizing a user interface on a personal computer.

14. The method of claim 13, wherein the user interface includes a page view window and a table of contents window; the page view window displays the content of a particular file in the customer collection; and the table of contents window displays a listing of files included in the customer coUection.

15. The method of claim 14, wherein the content of a particular file displayed in the page view window and the Usting of files displayed in the table of contents window utilize the same source file in the customer coUection.

16. The method of claim 14, wherein the user displays the content of a particular file in multiple displays, each of the multiple displays of the content of the particular file utiUzing the same source image in the customer coUection.

17. The method of claim 14, wherein the table of contents window displays the content of the customer collection based on a user's manipulation of a table of contents level selector, the table of contents level selector controlling which portions of the content of the customer collection is displayed.

18. The method of claim 17, wherein the portions of the content of the customer collection include at least one of a chapter, section, figure and table.

19. The method of claim 14, wherein the user interface displays an index window, the index window displays keyword data in alphabetical order.

20. The method of claim 13, further including the step of creating a user front-end collection, the user frontend collection being a subpart of the customer collection.

21. The method of claim 13, wherein the method further includes the step of searching the customer collection for a desired term.

22. The method of claim 3, wherein the customer is a corporation.

23. The method of claim 3 , wherein the customer is a school.

24. The method of claim 3 , wherein the customer is a school and a user is a student at the school.

25. The method of claim 24, wherein the customer collection includes the entire curriculum used by all students at the school, and wherein the student has access to the entire curriculum.

26. The method of claim 1, wherein structuring the obtained curriculum content is performed using a markup language.

27. The method of claim 26, wherein the markup language is Extensible Markup language.

28. A system for providing a curriculum repository, the system comprising: a document input portion that inputs curriculum content; a structuring portion that structures the curriculum content to generate curriculum material; a validating portion that validates the curriculum material, the vahdating portion creating a curriculum material library; an assembly portion that creates a customer records of distinct items, which are available in the curriculum material library, for a particular customer; a coUection portion that forms a customer coUection based on the customer record, the customer coUection portion utilizing items in the curriculum material library; and an access portion that provides a user access to the customer coUection, the user affiliated with the customer.

29. The system of claim 28, wherein the assembly portion determines if a customer possesses a Ucense to an item in the curriculum material library.

30. The system of claim 28, wherein the access portion provides a user access to the customer collection utilizing electronic media.

31. The system of claim 30, wherein the electronic media is a DVD.

32. A system for providing a curriculum repository, the system comprising: means for inputting curriculum content; means for structuring the curriculum content to generate curriculum material; means for validating the curriculum material, the means for vahdating creating a curriculum material library; means for assembling that creates a customer record of distinct items, which are available in the curriculum material library, for a particular customer; means for coUecting that forms a customer coUection based on the customer record, the means for coUecting utilizing items in the curriculum material library; and means for accessing that provides a user access to the customer collection, wherein the user is affiliated with the customer.