Method and system for removing content entity object in a hierarchically structured content object stored in a database6611840Abstract A web-based system, method and program product are provided for adding content to a content object stored (e.g., a custom compilation or prepublished work) in a data repository as a group of hierarchically related content entities. Each noncontainer content object is preferably stored as a separate entity in the data repository. Each content entity is also stored as a row in a digital library index class as a collection of attributes and references to related content entities and containers. As the user selects desired objects for inclusion in a content object, the system arranges the objects hierarchically, e.g., into volumes, chapters and sections according to the order specified by the user. The system then creates a file object (e.g., a CBO) defining the content object that contains a list or outline of the container and noncontainer entities selected, their identifiers, order and structure. This file object is stored separately in the data repository. Content is removed from the compilation by removing the container or noncontainer identifier from the list or outline. This is achieved through a user interface by providing a mechanism for enabling a user to select a container or noncontainer (e.g., by title) to be removed. Claims What is claimed is: Description REFERENCE TO A COMPUTER LISTING APPENDIX
Index Class
Attribute ATR
Name Mapping Type Description
SeqID Seq_ID Ext..Alpha [32] Unique sequence
INDEXED identifier for
product entity
EntityType PSF Ext..Alpha [32] Entity type, e.g.,
book, chapter,
section
ParentItem Program Ext..Alpha [16] Unique internal
generated ID of any parent
entity (e.g. For
a section entity,
the parent would
be its chapter
container)
SiblingItem Program Ext..Alpha [16] Unique internal
generated ID of the next
sibling entity (e.g.
For a section
entity, the
siblings would be
other sections of
the same chapter.
ChildItem Program Ext..Alpha [16] Unique internal
generated ID of the first
child entity (e.g.
a chapter entity's
children would be
the sections
it contains.
AuxItem Program Ext..Alpha [16] Reference to first
generated entry in the
auxiliary table for
this entity
ProgramID PE_ID Alpha [4] Identifier of
AC_PE_ID Program to which
the product
belongs
Status Status (SGML) Alpha [1] Indicates if iden-
AC_Status (AC) tity is available
for browse,
search or use
in a CBO
Title Title Alpha [250] Entity title
AC_Title
Subtitle Subtitle Alpha [250] Entity subtitle,
AC_Subtitle if any
ISBN ISBN Alpha [10] Product ISBN
AC_ISBN
CDAOID CDAOID Ext. Alpha [8] Associated
AC_CDAOID component
attribute
YearOfPub Yr_of_Pub Numeric [1] *
AC_Yr_of_Pub
Edition Edition Ext. Alpha [2] *
AC_Edition
Revision Revision Alpha [2] *
AC_Revision
Version Content_Ver Ext. Alpha [8] *
AC_Content.sub.--
Ver
PubMediaType Ext. Alpha [20] Media type, e.g.,
compact disk
ContentType Content_Type Ext. Alpha [8] Content type,
AC_Content.sub.-- e.g., SGML
Type
ContentFilename Filename Ext. Alpha Name of file
AC_Graphic.sub.-- [254] containing the
Filename entity's content
ImageType AC_Image.sub.-- Ext. Alpha [8] Type of image,
Type e.g., TIF.
CharCount SGML_Char.sub.-- Numeric [8] Number of
Cnt non-markup
characters in
content (used to
calculate CBO
price)
AC_ImageCount AC_Image_Cnt Numeric [3] Number of
associated
component
images in content
AvailabilityDate Date_of.sub.-- Ext. Alpha [10] Date entity is
Availability available for use
AC_Date.sub.--
of_Availability
ExpirationDate Date_of.sub.-- Ext. Alpha [10] Date entity is
Expiration no longer
AC_Date.sub.-- available
of_Expiration for use
CreateDate Create_Date Ext. Alpha [14] Date that table
AC_Create.sub.-- entry was created
Date
CreatedBy Created_By Alpha [8] Identifier of user
AC_CreatedBy who created entry
LastModifiedDate Last_Modified.sub.-- Ext. Alpha [14] Last date entry
Date was modified
AC_Last.sub.--
Modified_Date
LastModifiedBy Last_Modified.sub.-- Alpha [8] Identifier of user
By who last modified
AC.sub.-- entry
LastModifiedBy
PageCount PageCount Alpha [6] Actual page count
of content (used
in CBO pricing
formula)
Part Structures & Text Indices This table defines the digital library parts used to store each entity. For a row that represents a product entity, Part 1 contains the SGML content for a product entity. Parts 5-11 are parts containing subsets of that content that can be searched by Text Miner. The Text Index column contains the Text Miner indices for each of these searchable subsets. For a row that represents an entity's associated component, Part 20 contains the actual associated component file. (e.g., images).
Part No. Description Text Index
1 Content None
5 Authored Abstract EABSTRAC
6 Generated Abstract EABSTRAC
7 Index Terms EIXTERMS
8 Key Terms EIXTERMS
9 Entity Structure Part None
10 Teaching Concepts ETEACHCO
11 Concepts Topics ETOPICS
20 Associated Component None
ProductAux Index Class In the present example, the auxiliary index class is used to define additional columns in specified rows of the Product Index class. Specifically, each label in the Keywords column corresponding to the Keyword attribute defines the name of an additional column in the Product Index class The "value" attribute is the attribute type for each of these keywords. Indentations represent nested keywords. The SeqID, ProductItem, ParentItem, SiblingItem and ChildItem attributes specify the rows in the auxiliary Product Index class for storing hierarchical values. In the present example, "Index_Term" is an example of a multi-valued attribute, meaning that there may be more than one index term defined for each program entity. For performance reasons, the values of a multivalued attribute may be stored in separate rows of the Product Index class Thus The "Next ValueItem" attribute identifies the row of the next item in a set of attribute values. Multivalued attributes are structured as linked lists when loaded into digital library 20, and this order is maintained in the auxiliary Product Index class.
Index Class
Attribute
Name Keywords Type Description
SeqID PSF Ext. Alpha [32] Sequence ID of
entity that this
attribute belongs
to
ProductItem Program Ext. Alpha [16] Unique internal
generated ID of the product
index class row
that this attribute
belongs to
ParentItem Program Ext. Alpha [16] Unique internal
generated ID of the
auxiliary product
index class row
that is this
attribute's parent
attribute
SiblingItem Program Ext. Alpha [16] Unique internal
generated ID of the
auxiliary product
index class row
that is this
attribute's next
sibling attribute
ChildItem Program Ext. Alpha [16] Unique internal
generated ID of the
auxiliary product
index class row
that is the first
child attribute for
this attribute
Keyword Pub_Med_Type Alpha [32] Media type (e.g.,
compact disk,
audio tape, paper,
etc.)
AC_Counts AC (Associated
Component)
attribute group
ACFORMID AC type.
NUMBERAC The number for
each AC type.
Index_Term Index term in a
product entity
Key_Term Key term in a
product entity
Contrib_Group This group
Contrib_Role defines properties
Contrib_Title re: one
Contrib.sub.-- contributing
First_Name author of a
Contrib.sub.-- prepublished
Middle_Name book. Since a
Contrib.sub.-- book can have
Last_Name multiple
Contrib_Suffix contributors,
Job_Title more than one
Contrib.sub.-- contrib_group
Affiliation of properties can
Contrib.sub.-- exist for that
Credentials book.
Use_Actuals Switch variable
to determine if
actual or
estimated page
count is to be
used in
calculating price.
Value Value depends on Ext. Alpha [254] Actual value for
specific attribute the keyword
keyword above above
NextValueItem Program Ext. Alpha [16] Unique ID of the
auxiliary product
generated index class row
that is the next
value in a multi-
valued attribute.
Program Entity Group It is sometimes desirable to categorize users and content to facilitate the creation of a compilation. For example, a system user who wishes to compile an album of classical music is not interested in viewing selections from a country music album. Audio content may therefore be categorized according to music type. The user may also be assigned to a particular category, either by default or by personal selection. In a system for creating custom textbooks, subsets are organized according to particular programs or disciplines. For example, prepublished textbooks may be assigned to categories such as Engineering, Mathematics, English, and so on. In the present example, these categories have been defined even more narrowly: Freshman Engineering, Sophomore Engineering, etc. A Program Entity Group is used to define categories or "programs" to which users and prepublished content can be assigned. Program Index Class The Program Index Class definition below defines a Program Index Class or Program Index class that is populated with a row for each user/content category. This index class is used as a quick reference for obtaining attribute information about each program.
Index Class
Attribute Name ATR Mapping Type Description
Program_ID PE_Program_ID Alpha [4] Program iden-
INDEX- tifier, e.g. "FE" is
ED the identifier for
"Freshman
Engineering"
EntityType PSF Ext. Alpha Used when
[32] programs are
nested to define
hierarchical level
of each program
entity
ParentItem Program Ext..Alpha Supporting
generated [16] hierarchical or
"parent"
programs
Title PE_Title Alpha Program Title
[250]
Subtitle PE_Subtitle Alpha Program subtitle,
[250] if any
AvgChrPerImage PE_AC_Avg.sub.-- Numeric Average
Image_Bytes [6] characters per
image for
products within
this program
AvgChrPerSGMLAC PE_AC_Avg.sub.-- Numeric Average
SGML_Bytes [6] characters per
SGML associated
component for
products within
this program
MaxChrPerUPMTier PE_Chars_Per.sub.-- Numeric Maximum
UPM_Tier [6] number of
characters
allowed for a
UPM in this
program
Status PE_Status Alpha [1] Status indicating
whether program
entity is
currently
valid/invalid
CreateDate PE_CreateDate Ext..Alpha Date table
[14] entry created
CreateBy PE_CreateBy Alpha [8] Identifier of user
who created entry
LastModifiedDate PE.sub.-- Ext..Alpha Date entry was
LastModifiedDate [14] last modified
LastModifiedBy PE.sub.-- Alpha [8] Identifier of user
LastModifiedBy who last modified
entry
SiblingItem Program Ext..Alpha Related sibling
generated [16] programs
providing support
for hierarchical
programs.
ChildItem Program Ext..Alpha Related child
generated [16] programs, if any,
providing support
for hierarchical
programs.
AuxItem Program Ext..Alpha Reference to
generated [16] auxiliary table
SeqID PSF Ext. Alpha Unique program
[32] identifier, e.g.,
"FE" for
"Freshman
Engineering"
SeqID PSF Ext. Alpha Unique identifier
[32] (i.e., Sequence
ID) of this row.
ProgramItem Program Ext..Alpha Unique internal
generated [16] ID of row within
auxiliary program
index class that
this attribute
belongs to
ParentItem Program Ext..Alpha Unique internal
generated [16] ID of row within
auxiliary program
index class that
this attribute's
parent attribute
belongs to
SiblingItem Program Ext..Alpha Unique internal
generated [16] ID of row within
auxiliary program
index that this
attribute's next
sibling attribute
belongs to
ChildItem Program Ext..Alpha Unique internal
generated [16] ID of row within
auxiliary program
index that the
first child
attribute for
this attribute
belongs to
Keyword PE_Req_Count Alpha [32] The next
available unique
identifier for a
request
PE_AC_Group This group
defines associated
component
attributes used in
the pricing
formula
PE_AC.sub.-- AC type
FormID
PE_AC.sub.-- Number of
ByteCount "characters" for
that AC type
PE_Price_Group This group
defines more
attributes used in
pricing formula
PE_Country Country
PE_Mone- Monetary unit
tary_Unit
PE_Min.sub.-- Minimum order
Order_Price price
PE_Base.sub.-- Base price added
Cust_Pub.sub.-- to every custom
Price publication
PE_Base.sub.-- Base price added
UPM_Fee when UPM is
included
PE_Incr.sub.-- Additional price
UPM_Fee per UPM pricing
block
PE_Source.sub.-- Price per page for
Price_Per.sub.-- prepublished
Page content included
PE_UPM.sub.-- Number of UPM
Bytes_Per.sub.-- characters in a
Page page
PE_Mini- Minimum
mum_Page.sub.-- number of pages
Limit required in a
custom
publication
PE_Volume.sub.-- Maximum
Page_Limit number of pages
in a volume
Value Value depends on Ext. Alph
specific attribute [254]
keyword above
NextValueItem Program Ext..Alpha Unique internal
Generated [16] ID of row within
auxiliary program
index
representing the
next value of a
multi-valued
attribute.
CustomBookOutline Index Class The CustomBookOutline Index Class defines a relational CBO Index Class that includes a row for each compilation of content created. Each row further includes a reference to a part containing a road map or outline of the compilation of content. The index class is used as a quick reference for obtaining attribute information about a compilation, as well as for locating the corresponding part numbers. Again, the attributes are a matter of design choice.
Index Class
Attribute Name Source Type Description
ProgramID Web application Ext. Alpha Program identifier
[4]
CBOTitle Web application Alpha Custom book title
[120]
ApprovalStatus Program generated Alpha [1] Approval status,
i.e., active,
submitted, ap-
proved, rejected
or printed
UPMCharCount Program generated Alpha [8] Character count
of any user-
provided content
RightsFee Program generated Alpha [8] License fee
SGMLPageEstimate Program generated Alpha [4] Estimated page
count for SGML
content
TotalPageEstimate Program generated Alpha [4] Estimaged total
page count
PriceEstimate Program generated Alpha [8] Estimated price
ISBN Program generated Alpha [10] Unique ISBN
assigned to the
custom book at
submission time.
CreatorID Program generated Alpha [20] Creator's unique
idenfifier
CreatorTS Program generated Alpha [14] Timestamp
representing time
of current edit
LastModifiedTS Program generated Alpha [14] Timestamp
representing time
last modified
CBOTerms Program generated Ext. Alpha Name of file
[32] containing terms
and conditions
that will apply to
custom book?
ActiveCBOPartID Program generated Alpha [3] Part number of
active custom
book
LastUPMPartID Program generated Alpha [3] Part number of
the last user-
provided material
added
Part Structures & Text Indices The part definition describes the parts associated with each compilation. In the present example, three parts are defined: part 1 initially containing the custom book outline, part 2 initially containing a backup copy of the custom book outline for use in undo operations, and parts numbered 50 or higher containing user provided material (UPM). (Note: After undo, part 2 becomes the active CBO, and part 1 is the backup. The attribute value of "ActiveCBOPartID" indicates which is of these is currently the active part.) The first UPM added to a custom book is assigned to part 50, the second UPM added is assigned part 51, and so on. The last UPM part number assigned is stored in the CBO Index class defined above and serves two functions. It is a value that is retrieved and incremented each time new UPM is added. In addition, it serves as an indicator of how many parts the custom book currently contains.
Part No. Description Text Index
1 Part number for Active/Inactive CBO None
2 Part number for Active/Inactive CBO None
50+ Part numbers for user- None
provided content
Request Entity Group Whenever a compilation of content is submitted for publication, the Request Entity Group is used to generate an entry in a Request index class corresponding to the submission request. A unique ISBN is assigned to the CBO once it has been approved for publishing. Attributes are a matter of design choice. In the present example, they describe useful information about the custom book such as its unique identifier, author, approval status, price, etc.
Request Index Class
Index Class
Attribute Name Source Type Description
CBOID Program generated Ext. Alpha Unique CBO
[20] identifier assigned
at submission
time
Userid Program generated Ext. Alpha Author
[20]
ApprovalStatus Program generated Alpha [1] CBO state in
the process
0 - Active
1 - Submitted
2 - Approved
3 - Rejected
4 - Printed
TotalPrice Program generated Numeric Price of custom
[9] book
QtyStudentCopies Web application Numeric Number of
[4] student copies
requested
QtyDeskCopies Web application Numeric Number of desk
[2] copies requested
QtySupplements Web application Numeric Number of books
[2] to be used as
supplements
NeedByDate Web application Ext. Alpha Date needed by
[10]
TermStartDate Web application Ext. Alpha Start date of the
[10] school term for
which this CBO
is created
TermName Web application Ext. Alpha E.g., Spring, Fall
[20]
University Web application Ext. Alpha University name,
[100] e.g., Stanford
University
Department Web application Ext. Alpha Department
[100] name, e.g.,
Electrical
Engineering
ClassName Web application Ext. Alpha Class name, e.g.,
[128] Engineering
Basics
ClassNumber Web application Ext. Alpha Class number
[12]
CourseNumber Web application Ext. Alpha Course number,
[12] e.g., 101
ShipToNameTitle Web application Ext. Alpha *
[12]
ShipToFirstName Web application Ext. Alpha *
[40]
ShipToLastName Web application Ext. Alpha *
[40]
ShipToAddrLine1 Web application Ext. Alpha *
[40]
ShipToAddrLine2 Web application Ext. Alpha *
[40]
ShipToAddrLine3 Web application Ext. Alpha *
[40]
ShipToCity Web application Ext. Alpha *
[40]
ShipToState Web application Ext. Alpha *
[20]
ShipToCountry Web application Ext. Alpha *
[20]
ShipToPostalCode Web application Ext. Alpha *
[20]
PackageISBN Program generated Alpha [10] The ISBN
assigned to the
entire book. This
may be different
from the ISBN's
assigned to
volumes
within the book.
CreateTS Program generated Alpha [14] Time entry
created
RequestID Program generated Ext. Alpha Unique request
[16] identifier
*Self-explanatory
RequestAux Index Class The RequestAux Index Class is used in the present example to add additional columns to designated rows of the Request Index class when a CBO contains more than one volume. More specifically, if greater than one volume exists, the CBO and each volume it contains are each assigned a unique ISBN, and the Volume, VolumeISBN and VolumeID columns are added to the row representing the submission request. The RequestItem, ParentItem, SiblingItem and ChildItem attributes are used to identify the row to which these columns are added.
Index Class
Attribute Name Source Type Description
RequestItem Program Ext. Alpha Unique internal
generated [16] ID of row within
request index
class of entity
that this attribute
belongs to
ParentItem Program Ext. Alpha Unique internal
generated [16] ID of row within
auxiliary request
index class of
entity that is this
attribute's parent
SiblingItem Program generated Ext. Alpha Unique internal
[16] ID of row within
auxiliary request
index class of
entity that is this
attribute's next
sibling (siblings
are ordered)
ChildItem Program generated Ext. Alpha Unique internal
[16] ID of row within
auxiliary request
index class of
entity that is this
attribute's first
child (children
are ordered).
Keyword Volume Alpha [32] The parent
attribute of the
volume
information.
VolumeISBN The child
attribute of
Volume which
stores the ISBN
of the volume.
VolumeID unique internal ID
of row within
request index
class of volume
entity correspond-
ing to this
volume.
Value Program generated Ext. Alpha
[254]
NextValueItem Program generated Ext. Alpha Unique internal
[16] ID of row within
auxiliary request
index
representing the
next value of a
multi valued
attribute.
Login/Registration Database Model The Users Table simply defines a relational table for storing user information. The fourth column represents if this is a primary key field and the fifth column represents if this is a foreign key field.
USERS TABLE
Table Table Table Table Table
Column Column Column Column Column
Name Datatype Null Option is PK is FK
USER_ID VARCHAR2(30) NOT NULL Yes No
DEPT_UD_ID NUMBER(8) NULL No No
UNIV_UD_ID NUMBER(8) NULL No No
DEPART- NUMBER(8) NULL No No
MENT_ID
UNIV_ID NUMBER(8) NULL No No
USERNAME VARCHAR2(30) NOT NULL No No
PASSWORD VARCHAR2(30) NOT NULL No No
TITLE VARCHAR2(100) NULL No No
FIRST_NAME VARCHAR2(30) NULL No No
LAST_NAME VARCHAR2(30) NULL No No
ADDRESS1 VARCHAR2(80) NULL No No
ADDRESS2 VARCHAR2(80) NULL No No
ADDRESS3 VARCHAR2(80) NULL No No
CITY VARCHAR2(50) NULL No No
STATE VARCHAR2(2) NULL No No
ZIP VARCHAR2(10) NULL No No
COUNTRY VARCHAR2(50) NULL No No
PHONE VARCHAR2(15) NULL No No
EMAIL VARCHAR2(80) NOT NULL No No
CHALLENGE VARCHAR2(255) NOT NULL No No
RESPONSE VARCHAR2(255) NOT NULL No No
SECURITY CHAR(1) NOT NULL No No
TIMESTAMP DATE NULL No No
CBO_ID VARCHAR2(64) NULL No No
USER_CBOS Table The USER_CBOS table enables a user to have more than one active CBO at a time.
Table Table Table Table Table
Column Column Column Column Column
Name Datatype Null Option is PK is FK
USER_ID NUMBER(8) NOT NULL Yes No
CBO VARCHAR2(100) NULL No No
TIMESTAMP DATh NULL No No
3. Input Interface An interface 8 is provided to the user for entering information to be stored in digital library 20. Information includes Program categories and prepublished content. The interface can be in a variety of forms, but it must be able to communicate with an OO Api layer 30 which is in the present embodiment comprises a C dll. The interface 8 of the present embodiment is a web based solution consisting of 22, 24, 26 and 28. Alternatively, application code 28 may provide the same function. In the present example, each prepublished content product is input as one SGML file. The hierarchical levels within that SGML file are discernible by their delimiting tag types. Program information is provided as a field identifying the program for each prepublished content product. The program configuration information is defined in PSF/ATR files and loaded into the datastore using the loader 10. 4. Converter Converter 10 receives the SGML files and uses the delimiting tags to separate the product entities and associated components. It also builds a file defining the hierarchical relationships of these entities and components, and extracts relevant product attributes. In the present example, the resulting files include four possible file types: a Product Structure File (PSF), Attribute Files (ATR), Content Component Files and Associated Component Files. Product Structure Files (PSF). For content, the Product Structure File provides a hierarchical outline of the contents in a prepublished product. More specifically, it is a parsable formatted file listing all of the entities making up a content product (e.g., a book container, volume containers, chapter containers and sections, each identified by its sequence identifier). This file is used as a road map (i.e., a list or table of contents) defining the content, order and hierarchical structure of the prepublished product, thereby relating a product's separately stored content entities. It is stored as a part in digital library 20. An example of a PSF file for a content product is shown below:
PRODUCT.C:0130808598.00.00.00
FRONT_AND_BACK_ELEMENT:0130808598.01.01.00
FRONT_AND_BACK_ELEMENT:0130808598.01.02.00
FRONT_AND_BACK_ELEMENT:0130808598.01.03.00
FRONT_AND_BACK_ELEMENT:0130808598.01.04.00
CHAPTER.C:0130808598.02.00.00
FRONT_AND_BACK_ELEMENT:0130808598.02.01.00
SECTION:0130808598.02.02.00
SECTION:0130808598.02.03.00
SECTION:0130808598.02.04.00
SECTION:0130808598.02.05.00
SECTION:0130808598.02.06.00
FRONT_AND_BACK_ELEMENT:0130808598.02.07.00
CHAPTER.C:0130808598.03.00.00
FRONT_AND_BACK_ELEMENT:0130808598.03.01.00
SECTION:0130808598.03.02.00
SECTION:0130808598.03.03.00
SECTION:0130808598.03.04.00
SECTION :0130808598.03.05.00
SECTION:0130808598.03.06.00
FRONT_AND_BACK_ELEMENT:0130808598.03.07.00
CHAPTER.C:0130808598.04.00.00
FRONT_AND_BACK_ELEMENT:0130808598.04.01.00
SECTION:0130808598.04.02.00
SECTION:0130808598.04.03.00
SECTION:0130808598.04.04.00
SECTION:0130808598.04.05.00
FRONT_AND_BACK_ELEMENT:0130808598.04.06.00
CHAPTER.C:0130808598.05.00.00
FRONT#AND_BACK_ELEMENT:0130808598.05.01.00
SECTION:0130808598.05.02.00
SECTION:0130808598.05.03.00
SECTION:0130808598.05.04.00
SECTION:0130808598.05.05.00
SECTION:0130808598.05.06.00
FRONT_AND_BACK_ELEMENT:0130808598.05.07.00
CHAPTER.C:0130808598.06.00.00
FRONT_AND_BACK_ELEMENT:0130808598.06.01.00
SECTION:0130808598.06.02.00
SECTION:0130808598.06.03.00
SECTION:0130808598.06.04.00
SECTION:0130808598.06.05.00
SECTION:0130808598.06.06.00
SECTION:0130808598.06.07.00
SECTION:0130808598.06.08.00
FRONT_AND_BACK_ELEMENT:0130808598.06.09.00
CHAPTER.C:0130808598.07.00.00
FRONT_AND_BACK_ELEMENT:0130808598.07.01.00
SECTION:0130808598.07.02.00
SECTION:0130808598.07.03.00
SECTION:0130808598.07.04.00
SECTION:0130808598.07.05.00
FRONT_AND_BACK_ELEMENT:0130808598.07.06.00
CHAPTER.C:0130808598.08.00.00
FRONT_AND_BACK_ELEMENT:0130808598.08.01.00
SECTION:0130808598.08.02.00
SECTION:0130808598.08.03.00
FRONT_AND_BACK_ELEMENT:0130808598.08.04.00
CHAPTER.C:0130808598.09.00.00
FRONT_AND_BACK_ELEMENT:0130808598.09.01.00
SECTION:0130808598.09.02.00
FRONT_AND_BACK_ELEMENT:0130808598.09.03.00
CHAPTER.C:0130808598.10.00.00
FRONT_AND_BACK#ELEMENT:0130808598.10.01.00
SECTION:0130808598.10.02.00
SECTION:0130808598.10.03.00
FRONT_AND_BACK#ELEMENT:0130808598.10.04.00
CHAPTER.C:0130808598.11.00.00
FRONT_AND_BACK#ELEMENT:0130808598.11.01.00
SECTION:0130808598.11.02.00
SECTION:0130808598.11.03.00
FRONT_AND_BACK_ELEMENT:0130808598.11.04.00
FRONT_AND_BACK_ELEMENT:0130808598.12.01.00
For program categories, the PSF file contains the unique program identifier. As an example, the contents of a PSF file for the "Freshman Engineering" program is shown below: PROGRAM:fe Attribute Files (ATR). Attribute files contain metadata about each program or product entity input. This information must be extracted by converter 10. These files are mapped to the program and product index class defined by the Program and Product index classes (using the ELOADER.INI file described below) and stored in digital library 20. There is one attribute file for each program and for each product entity to be stored. Examples of ATR files are shown below. The first is an ATR file for a "book":
;;
;; PRODUCT.C - ATR file - Created: 29 October 1999 21:55:06
;;
;; Seq_ID: 0130808598.00.00.00
!SKU:0000000014595
!ISBN:0130808598
!Title:Engineering Success
!Contrib_Group
! Contrib_First_Name:Peter
! Contrib_Last_Name:Schiavone
! Contrib_Affiliation:University of Alberta
!PE_ID:FE
!Status:0
!Page_Count:0
!Use_Actuals:1
!Yr_of_Pub:1999
!Edition:01
!Revision:00
!Version:01.00
!Created_By:BARKER
!LastModified_By:BARKER
The ATR for chapter 3 of the preceding book is shown below:
;;
;; CHAPTER.C - ATR file - Created: 29 Oct. 1999 21:55:09
;;
;;Seq_ID: 0130808598.03.00.00
;;
!SKU:0000000014618
!Title:Introduction to Engineering and Engineering Study
!Authored_Abstract:"How much do you know about engineering?
Why did you choose to study engineering?What reasons lead you to
believe that you are ready and equipped to study engineering?
What are the main differences between studying at a university and
studying in high school?What new success skills do you need to succeed
in engineering study?Can you write down 10 answers to each question I
have asked you?Go ahead and try."
!Authored_Abstract:This is often how I begin my lecture to freshman
engineering students enrolled in an introductory engineering class.
After a little thought, most of them realize just how little they know
about
this subject called engineering and (often despite excellent high school
averages) how ill equipped they are to study engineering.
!Authored_Abstract:In this chapter, we address both issues.
First, we ask the following questions:What is engineering?
What do engineers do?Why choose to study engineering?
!Authored_Abstract:The answers to these questions are not only
interesting and informative, but will help keep you motivated along the
long, hard road to an engineering degree.
!Authored_Abstract:In , we address the question, "Are you
prepared and equipped for engineering study?" In doing so, we
examine the study skills required to succeed in the university environment.
For many students, the university is the next logical step after high
school,
the next academic challenge.
Consequently, they expect their freshman year in engineering to be much
like another year of high school-which, of course, it isn`t.
In engineering, such an exception often manifests itself in unacceptably
high first-year attrition rates. We address this issue by focusing on what
you need to do to ensure the best possible start to earning your
engineering degree. Essentially, you must develop the necessary:Work
strategiesStudy strategiesAttitudesCommunication skillsAbility to work
as part of a teamTime management skills
The ATR for section 3.2 of the same book is shown below:
;;
;; SECTION - ATR file - Created: 29 October 1999 21:55:09
;;
;; Seq_ID: 0130808598.03.02.00
;;
!Filename:0130808598.03.02.00.sgm
!CDAOID:AABQHDS0
!Index_Term:engineering
!Index_Term:defined
!Index_Term:engineering, study
!Index_Term:introduction to
!Index_Term:engineering, defined
!Title:What Is Engineering?
!SGML_Char_Cnt:2370
!AC_Counts
ACFORMID:2
NUMBERAC:1
!Associated_Component
! AC_PE_ID:FE
! AC_CDAOID:AABQHDT0
! AC_Title:FIG1
! AC_Image_Type:TIFF
! AC_Graphic_Filename:HiRes.backslash.AABQHDT0.TIF
! AC_Authored_Abstract:None
The ATR file for the "Freshman Engineering" program is shown below:
;;
;Program ID tor Freshman Engineering set to "FE"
!PE_Program_ID:FE
!PE_Title:Freshman Engineering
!PE_Subtitle:
!PE_Req_Count:ESOU002300
;!PE_Related_Material:<value>
!PE_AC_Group
! PE_AC_FormID:1
! PE_AC_ByteCount:2
! PE_AC_FormDesc:Inline Graphic
!PE_AC_Group
! PE_AC_FormID:2
! PE_AC_ByteCount:1000
! PE_AC_FormDesc:Display Graphic
!PE_AC_Group
! PE_AC_FormID:3
! PE_AC_ByteCount:68
! PE_AC_FormDesc:Inline Equation
!PE_AC_Group
! PE_AC_FormID:4
! PE_AC_ByteCount:180
! PE_AC_FormDesc:Display Equation
!PE_AC_Group
! PE_AC_FormID:5
! PE_AC_ByteCount:2000
! PE_AC_FormDesc:SGML
!PE_AC__Avg_Image_Bytes:0
!PE_AC_Avg_SGML_Bytes:0
!PE_Chars_Per_UPM_Tier:2000
!PE_Price_Group
! PE_Country:0
! PE_Monetary_Unit:USD
! PE_Min_Order_Price:1000
! PE_Base_Cust_Pub_Price:1000
! PE_Base_UPM_Fee:0
! PE_Incr_UPM_Fee:10
;JDR add 1/21/99
! PE_Source_Price_Per Page:10
! PE_Minimum_Page_Limit:80
! PE_Volume_Page_Limit:480
! PE_UPM_Bytes_Per Page:1000
!PE_Status:F
!PE_CreateDate:1998-12-07
!PE_CreatedBy:UHANAED
!PE_LastModifiedDate:1999-1-19
!PE_LastModifiedBy:UHANAED
Content Component Files (SGML). Content component files contain the product entities' actual ASCII or binary content that will be stored as parts in digital library 20. In the present example, these files comprise SGML files containing the ASCII text of chapter sections. Associated Component Files. Associated Component (AC) Files contain any non-SGML content associated with the product entities. The content in the associated component files is stored as parts in digital library 20. Both prepublished content and custom book outlines (CBO's), described below, are represented in the described file format. A feature of this format is that content objects such as a prepublished book or CBO are defined by the PSF file. Thus the PSF file may be used to redefine the content, order and structure of the content object without having to access the content itself. This feature proves useful in creating compilations of content, by simplifying the process for adding, moving and deleting content. Composite PSF & ATR Files. Out of the PSF and ATR format comes a third file format that is a composite form of PSF and ATR. For simplicity, this type is also referred to as a PSF+ATR format. One can think of this file as a merge of PSF and ATR files, where attributes from an entity's ATR file have been inserted after that entity in the PSF. For example, it may be desirable to include certain attributes with a PSF file (e.g., author and price). It may be desirable to add certain attributes to the product structure file (e.g., author) when it is stored in the digital library. Accordingly, in the present embodiment, what is stored as "Entity Structure Part" described earlier is actually a composite form of PSF and ATR. For a book or product level entity, this file includes all entities in the book (including the book itself) and their attributes. For a chapter level entity, this file includes all entities in the chapter (including the chapter itself) and their attributes. For a section level entity, this file includes the section entity and its attributes. Attributes are also added to PSF files containing custom compilation outlines created by system users, and Equery result files. In the Equery results files, all of the entities returned are treated flat, namely at the same hierarchical level. An example of a composite file format is shown below:
Top_Entity1: sequence_ID
!Attribute1: value
!Attribute2: value
!Attribute3:
! Subattribute1: value
! Subattribute2: value
!Attribute4: Value4
Sub_Entity1: Sequence_ID
!Attribute1: value
!Attribute2: value
Sub_Sub_Entity1: Sequence_ID
!Attribute1: value
!Attribute2: value
Sub_Entity2: Sequence_ID
!Attribute1: value
!Attribute2: value
An exemplaryentity structure part stored in Digital Library is provided in Appendix A. In the present example, converter 10 is preferably Active System's Attribute Extractor (i.e. AE). Converter 10 creates a load directory for each prepublished content product, identified by that product's ISBN, which contains the product's corresponding Product Structure File (PSF), Attribute Files, Content Component Files and Associated Component Files. It also creates a load directory for each program category, identified by the program identifier and containing the program's corresponding PSF and ATR files. These directories are provided as input to content loader 14. 4. Content Loader Content loader 14 is a software application for loading the program and prepublished content files described above into the digital library 20. It receives the load directories as input from converter 10, then loads this information into digital library according to a content configuration model 12 defined in the ELOADER.INI configuration file (described below). Content loader 14 interfaces with the digital library content server(s) 18 through the OO API layer 16. The content loader 14 has three modes of operation: load, delete and purge. Load. The purpose of this mode of operation is to load or reload the Content Entities, Associated Components and Attributes into the digital library 20. All Content Component Files are stored as binary large objects or BLOBs in the digital library object server 48. All Attribute Files are parsed and the resultant parametric data is stored in the digital library server 44. As previously noted, the input files to the content loader 14 are a Product Structure File (i.e., a sequence-id.psf), an Attribute file for each product entity loaded (i.e., sequenceid.atr), a file for each Content Component (i.e., sequence-id.sgm) and a file for each Associated Component (i.e., sequenceid.cdaOID.gif). The output of the ELoader will be placed into the appropriate index class in the digital library 20 as specified by the configuration model contained in the ELOADER.INI file. Syntax: ELoader--load<sequence-id> Example #1: ELoader--load 012345678 This load command launches loader 14 into load mode. It looks in the load directory identified by an ISBN="012345678" for all of the Attribute Files, Content Components and Associated Components stored therein, and processes these files. Example #2: ELoader 012345678.02.00.00 This load command launches loader 14 into load mode. It looks in the load directory identified by an ISBN="012345678" for all Attribute Files, Content Components, and Associated Components associated with chapter container "012345678.02.00.00", and process these files. Delete. The purpose of this mode of operation is to delete selected Content Entities, Associated Components and Attributes from the Digital Library. The ELoader will delete all content, attributes, and text index entries from digital library 20 for the ISBN/sequence number specified, as well as all child content and attributes associated with that ISBN/sequence number. Syntax: ELoader--delete<sequence-id> Example #1: ELoader--delete 012345678 This command launches loader 14 into delete mode and deletes all content and attributes for the prepublished content product whose ISBN="012345678". Example #2: ELoader--delete 012345678.02.00.00 This command launches loader 14 into delete mode and deletes all entities and attributes for the entity whose sequence number="012345678.02.00.00" as well as all of its children. The rest of the content product remains untouched. Purge. The purpose of this mode of operation is to purge Content Entities, Associated Components and Attributes from the Digital Library after a Load that did not complete successfully. Loader 14 deletes all content, attributes, and text index entries from the digital library 20 even though it is in a partially loaded state. Syntax: ELoader--purge<sequence-id> Example: ELoader--purge 012345678 This command launches loader 14 into purge mode and deletes all content and attributes for the prepublished content product whose ISBN="012345678". 5. Configuration Model Configuration model 12 is embodied in a configuration file called ELOADER.INI, and associated configuration files that it calls. The configuration files contain all of the switches and parameters necessary to customize the operation of loader 14 to the data model defined above. The primary objective of these files is to minimize the need to change loader 14 program source code if the data model is modified. The ELOADER.INI file is organized into several sections with multiple keywords and values in each section. The LOGON and DEBUG sections describe parameters that govern the overall loader operation. The ELOADER section and the Individual Group Sections describe the entity types that have been defined in the exemplary data model (i.e., the Program, Product, CBO and Request entity groups). The Individual Entity Sections describe each entity type that belongs to a given entity group. The ATTRIBUTES section and the Individual Attribute Sections describe the set of attributes that may be loaded for the entities in the data model. The ELOADER.INI file, the data model file, and each of the individual GROUP attribute files are in the same format as an Attribute file as shown in the examples. The GROUP file is in the PSF format. a. Structure LOGON Section. This section specifies the digital library USERID and server names for all operations between content loader 14 and digital library 20.
KEYWORD VALUE MEANING
LIBRARY name The name of the DIGITAL LIBRARY Library
Server to be used.
USERID name The USERID that will be used to logon to
DIGITAL LIBRARY.
PASS- name The PASSWORD of the USERID.
WORD
TEXT name The name of the client instance of the Text Miner
SERVER server.
MAX HITS number The maximum number of hits to be returned by
EQuery (described subsequently)
DEBUG Section. This section specifies internal switch settings that are only used for debugging, testing, and performance analysis.
KEYWORD VALUE MEANING
TRACE 0 No debug trace will be created.
1 Create trace of internal activity for debugging.
This is not a log file.
Log files Section. This section specifies the names of the files to be used for logging and debugging.
KEYWORD VALUE MEANING
LOADER name Filename for Loader log.
TRACE name Filename for debug trace.
ELOADER Section. This section specifies the name of the initialization file containing the full data model with all of its data groups. In other words, it is a pointer to a meta-metadata file.
KEYWORD VALUE MEANING
DATA MODEL Name Filename of a file containing each Group
name and the name of the Group File.
DEFAULT Name Name of the default Group
GROUP
ROOT ENTITY Name String to be concatenated to the unique ISBN
SID of a content object to obtain the root
sequence-id.
CONTENT CLASSES Section. This section specifies the digital library content class for each of the possible file extensions of associated component files.
KEYWORD VALUE MEANING
DEFAULT Name BINARY if the component contains non-human
CONTENT readable data.
CLASS ASCII if the component contains human readable
data.
File Name BINARY if the component contains non-human
extension readable data.
ASCII if the component contains human readable
data.
Groups File. This section lists the names of all hierarchical groups of entities within the data model. All entity instances that belong to the same group will be stored in the same set of digital library index classes. This is a convenient way to manage product-related entities separately from other business-related entities. There may be one or more GROUPS in a Groups File.
KEYWORD VALUE MEANING
GROUP name All instances of entities within this Entity group
will be stored in the same set of digital library
index classes. The Entity types that belong to this
group may be specified via ENTITY keywords in
an Individual Group Section.
Individual Group Attribute Files. Each filename in the group attribute files is the value of one of the GROUP keywords in the Groups File. It identifies the data model entities that will be stored together as a related group and the digital library index class names that will be used to store them. There is one Individual Group Section for each GROUP keyword in the Groups File.
KEYWORD VALUE MEANING
ENTITIES CLASS name The digital library index class name that
will be
used to store all instances of entities that
belong
to this group.
ENTITY ID name The digital library attribute name in the
ENTITIES Index Class for a unique identifier
for
the entity. It is assumed to be unique and
an
index.
ENTITY TYPE name The digital library attribute name in the
ENTITIES Index Class for the digital library
Type ID of the entity.
ENTITY PARENT ID name The digital library attribute name in the
ENTITIES Index Class for the digital library
Item
ID of the parent container of this entity.
ENTITY CHILD ID name The DIGITAL LIBRARY Attribute Name in the
ENTITIES Index Class for the DIGITAL
LIBRARY Item ID of the first child of this
entity.
ENTITY SIBLING ID name The DIGITAL LIBRARY Attribute Name in the
ENTITIES Index Class for the DIGITAL
LIBRARY Item ID of the first sibling of this
entity.
ENTITY AUX ID name The DIGITAL LIBRARY Attribute Name in the
ENTITIES Index Class for the first auxiliary
attribute of this entity.
ENTITY SUBCOMP ID name The DIGITAL LIBRARY Attribute Name in the
ENTITIES Index Class for the first
associated
component of this entity.
ASSOC COMP ATTR name The DIGITAL LIBRARY Attribute Name in the
NAME COMPONENTS Index Class for the DIGITAL
LIBRARY Item ID of the ENTITIES Index Class
item that owns the COMPONENT item.
ASSOC COMP ID name The DIGITAL LIBRARY Attribute Name in the
ATTR NAME COMPONENTS Index Class for the DIGITAL
LIBRARY Item ID of the ENTITIES Index Class
item that owns the COMPONENT item.
ATTRIBUTES CLASS name The DIGITAL LIBRARY Index Class name that
will be used to store all attributes that
are
hierarchical or have multiple instances.
ATTR ENTITY ID name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the DIGITAL
LIBRARY Item ID of the ENTITIES Index Class
item that owns the ATTRIBUTE item.
ATTR PARENT ID name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the DIGITAL
LIBRARY Item ID of the parent container of
this
entity.
ATTR CHILD ID name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the DIGITAL
LIBRARY Item ID of the first child container
of
this entity.
ATTR SIBLING ID name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the DIGITAL
LIBRARY Item ID of the next sibling
container
to this entity.
ATTR NEXT VALUE name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the DIGITAL
LIBRARY Item ID of thc next value of this
entity.
ATTR KEYWORD name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the attribute
containing the Attribute's Keyword.
ATTR VALUE name The DIGITAL LIBRARY Attribute Name in the
ATTRIBUTES Index Class for the attribute
containing the Attribute's Value.
ENTITY name Name of the entity type of the root entity.
ENTITY STRUCTURE Part Specifies the DIGITAL LIBRARY Part Number
PART Number where an internally generated summary of
attribute values for this entity and all of
its
descendants will be stored.
ATTRIBUTE Definitions. Each top-level attribute name that may be present in a Group Attribute file must have keywords defined. Attributes that are part of an attribute hierarchy (i.e. sibling attributes with a parent attribute) are defined by an ATTRIBUTE keyword within the parent's attribute definition.
KEYWORD VALUE MEANING
ATTRI- Defines the beginning of a single attribute. There
BUTE may be one or more ATTRIBUTE definitions in
Group File. Each attribute name that may be
present in an attribute file must have keywords
defined.
Attribute Keywords
KEY-
WORD VALUE MEANING
NAME name The attribute name that will be used to identify
this attribute.
TYPE ENTITY The value of this attribute will be stored as a
Primary attribute in the Entities Index Class of
the appropriate Entity Group.
COMP It uses the DIGITAL LIBRARY attribute
specified by the DIGITAL LIBRARY NAME
keyword. The value of this attribute will be
stored as a Primary attribute in the Components
Index Class of the appropriate Entity Group.
It uses the DIGITAL LIBRARY attribute
specified by the DIGITAL LIBRARY NAME
keyword.
AUX The value of this attribute will be stored as an
Auxiliary attribute along with its keyword.
Depending on its position in the attribute file, it
will also contain the DIGITAL LIBRARY Item
ID of either an Entities Index Class or a
Components Index Class item of the appropriate
Entity Group.
SYS The value of this attribute may not be loaded via
ELoader and it is not explicitly stored in the
Digital Library. The value of this attribute
generated by the DIGITAL LIBRARY query
engine and is available for output by EQuery.
VALUES 1 (default) This attribute may only have one value. The
attribute type may be either PRIM or COMP.
* This attribute may have zero or more values. The
attribute type may only be AUX. The values will
always be retrieved in the same order that they
are stored.
DE- INHERIT If a value is not explicitly specified for this
FAULT attribute, the current value of the same attribute
of the parent entity is used when the entity is
stored (i.e. early binding).
LINK If a value is not explicitly specified for this
attribute, the current value of the same attribute
of the parent entity is used when the entity is
retrieved (i.e. late binding).
NULL If a value is not explicitly specified for this
attribute, the value is assumed to be a NULL
| ||||||