Table of Contents

1. Document Type Definition

Save the following as "workflow.dtd"

1.1 Workflow

<!ELEMENT workflow - O ( meta, submission, generated ) >

2. Metadata

2.1 Metadata

Collects all metadata for the ETD.

<!ELEMENT meta - O ( title, author, doctype,
  degree, major, college, university, city, state,
  committee, defenseDate, 
  keywords, copyright, abstract) >

2.2 Title

Title of the ETD

<!ELEMENT title - O ( #PCDATA )* >

2.3 Author

Author's name, split for alphabetizing.

<!ELEMENT author - O ( given, surname, suffix? ) >
<!ELEMENT ( given, surname, suffix) - O ( #PCDATA )* >

2.4 Document Type

"Dissertation," "Thesis," or "Special Report"

<!ELEMENT doctype - O ( #PCDATA )* >

2.5 Degree

"Master of Arts," "Master of Science," "Doctor of Philosophy," etc.

<!ELEMENT degree - O ( #PCDATA )* >

2.6 Major

The name of the student's major.

<!ELEMENT major - O ( #PCDATA )* >

2.7 College

The college in which that major lives.

<!ELEMENT college - O ( #PCDATA )* >

2.8 University

The university that conferred the degree.

<!ELEMENT university - O ( #PCDATA )* >

2.9 Committee

The members of the student's advisory committee. The student may have one chair or two or more co-chairs, followed by many members.

<!ELEMENT committee - O ( ( chair | ( co-chair, co-chair+)), member*) >
<!ELEMENT ( chair | co-chair | member ) - O ( #PCDATA )* >

2.10 Date of Defense

<!ELEMENT defenseDate - O ( #PCDATA )* >

2.11 City, State

<!ELEMENT (city, state) - O ( #PCDATA )* >

2.12 Keywords

The keywords of this ETD.

<!ELEMENT keywords - O ( keyword )* >
<!ELEMENT keyword - O ( #PCDATA )* >

2.13 Copyright

This is the copyright reminder that is authored by the student.

<!ELEMENT copyright - O ( #PCDATA )* >

2.14 Abstract

The Abstract of the ETD. Note the allowable tags below correspond to HTML.

• p - paragraph
• i - italic
• b - bold
• tt - typed text
• sub - subscript
• sup - superscript
• a - hyperlink

<!ELEMENT abstract - - ( p )* >

<!ELEMENT p  - O ( i | b | tt | sub | sup | a | #PCDATA )* >

<!ELEMENT ( i | b | tt | sup | sub ) - - ( #PCDATA )* >

<!ELEMENT a - - ( #PCDATA )* >
<!ATTLIST a 
  href CDATA #IMPLIED
>

3. Submission Tracking Data

3.1 Submission

This collects the information we collect on the submission form. This information helps track the submission.

<!ELEMENT submission - O ( submissionDate, studentEmail, chairEmail, materials) >

3.2 Submission date

Contents are in the form: YYYYMMDD/HHMMSS

<!ELEMENT submissionDate - O ( #PCDATA )* >

3.3 Student's Email

Student's current email address.

<!ELEMENT studentEmail - O ( #PCDATA )* >

3.4 Chair's Email

Chair's current email address.

<!ELEMENT chairEmail - O ( #PCDATA )* >

3.5 ETD Materials

These are the filenames that we collect from the user. The availability of each file depends on the student/committee ETD approval form.

The notify attribute tells the date the graduate school should contact the student to see if the document can be made public (YYYYMMDD).

The size attribute holds the file size (in bytes).

<!ELEMENT materials - O ( filename )* >

<!ELEMENT filename - O ( #PCDATA )* >
<!ATTLIST filename
  availability ( worldwide | university | secure ) worldwide 
  notify CDATA #IMPLIED -- YYYYMMDD --
  size CDATA #IMPLIED -- bytes --
>

4. Generated Data

This data is generated by the submission software during the process of submission.

4.1 Generated

<!ELEMENT generated - O ( callnumber, urn, approvalDate, approvedBy, notified* ) >

4.2 Call Number

The call number of the ETD, as assigned by an automated cataloger. Conforms to the scheme described in ETD Classification.

<!ELEMENT callnumber - O ( #PCDATA )*>

4.3 Universal Resource Name

The global name of the ETD, no matter how it lives in the digital library.

<!ELEMENT urn - O ( #PCDATA )*>

4.4 Approval Date

The date and local time the thesis was approved, in the form: YYYYMMDD/hhmmss

<!ELEMENT approvalDate - O ( #PCDATA )*>

4.5 Approved by

The name of the staff member that approved the ETD.

<!ELEMENT approvedBy - O ( #PCDATA )*>

4.6 Notified

This holds the record that (and when) the graduate school notified the student to attempt to promote the files to public.

<!ELEMENT notified - O ( #PCDATA )* >
<!ATTLIST notified
  date CDATA #IMPLIED
>

5. Example ETD Workflow Record

Save the following as "workflow.rec"

<!DOCTYPE workflow SYSTEM "workflow.dtd" >
<workflow>
<meta>
<title>Use of Metaphor in Shakespeare's Plays and its Potential 
Application in Twenty-first Century Literature
<author>
<given>Albert J.
<surname>Kippleby
<suffix>Jr.
<doctype>Dissertation
<degree>Doctor of Philosophy
<major>Computer Science and Applications
<college>College of Arts and Sciences
<university>Virginia Polytechnic Institute and State University
<city>Blacksburg
<state>Virginia

<committee>
<chair>Prashant Choudhary
<member>Marc Vogel
<member>Wen Wang
<member>Peter Haggerty
<member>Ohm Sornil

<defenseDate>July 16, 1997

<keywords>
  <keyword>Metaphysics
  <keyword>Information Retrieval
  <keyword>Spacecraft

<copyright>Copyright 1997, Albert J. Kippleby

<abstract>

<p>The need for concrete examples increases when technology becomes
difficult to explain.  In documentation for computer systems
especially, we see a wide audience of field experts attempting to
comprehend documentation for computer software and hardware of which
they should only require a cursory understanding.  Additionally, as
the pace of the information age quickens we see document authors
struggle for <i>examplia-concretes</i> with wide applicability, and
consistently rely on excerpts from Shakespearean literature as a
public-domain source for their various explications.

<p>We predict the twenty-first century will be no different.
Actuarial studies show explosion in the information industry such that
four out of five persons will be <i>bona fide</i> electronic document
authors; many of those will have one or more college degrees.  We
prove through computer simulation Machinum Simitatores that authors of
twenty-first century literature will be affected by these examples and
will include metaphor with Shakespearean source into their writing
with increasing frequency.

</abstract>

<submission>
  <submissionDate>19971009
  <studentEmail>ak@vt.edu
  <chairEmail>pc@vt.edu

<materials>
  <filename>etd.pdf
  <filename availability=university notify=19981009 >ch1-3.pdf
  <filename availability=secure notify=19981009 >ch4-6.pdf
  <filename>back.pdf

<generated>
  <callnumber>VTEngElec-PhD-Kippleby-19971009/1997-5001
  <urn>1997-5001
  <approvalDate>19971010
  <approvedBy>Gwen Ewing, Graduate School