Project Overview

1
Project Overview

• Digital library for Course Archival
• ODU, CS department
• Xiaoming Liu

Design
Background
Problem
Technology
Solution
DEMO
Conclusion
2
Background

• Part of ODU Digital Library project.
• Based NCSTRL and bucket.
• The prototype is expected to be finished in this
  semester.

3
Description

• Course Archival problem
• Instructors handout, lecture.
• Students assignment, project.

• Why to keep course archival
• Instructor students future reference..

4
Description

• Current Course archival implementation
• Instructors webpage, FTP site
• Students webpage
• Problem
• Easy to lost
• Can we find the course lectures of CS441 in 1995?
• Without organization
• How can we find all TCP/IP projects done in
  previous years?

5
Solution-Digital Library

• Digital Library
• Definition
• A collection of information that is both
  digitized and organized.
• Strengths
• Support Course archival and search.
• Weaknesses
• Current Digital library is document-oriented,
  that means, all information about one course will
  be scattered into one DL.
• How to integrated these materials?

6
Solution-Bucket

• Bucket
• Definition
• Object-oriented,intelligent agent archival
  entities
• Part of NCSTRL project in ODU.
• Strengths
• Support a collection of all information about
  Course archival.
• Problem
• Course archival items may include complex
  relationship.
• How to express complex login linkage between
  class items?

7
Solution-XML

• Definition
• XML is the Extensible Markup Language, it's a
  metalanguage to let you design your own markup
  language.
• Looks like HTML.
• Strengths
• XML is flexible enough to support complex course
  archival.

Http//www.xml.com
8
Solution-Put it together

• DL
• course search and depository
• Bucket
• storage of information about one course.
• XML
• express the relationship between course items.

9
Design-System flow graph
10
Design-Course model
By Dr S.J.Zeil, http//www.cs.odu.edu/dlibug
11
Design-XML DTD file(part)

• lt!DOCTYPE CLASS
• lt!ELEMENT CLASS (METADATA,Semester)gt
• lt!ELEMENT METADATA (BIB-VERSION,ID,ENTRY,ORGANIZAT
  ION,LANGUAGE,TITLE,AUTHOR,NCSTRLPLUS_ARCHIVALTYPE,
  NCSTRLPLUS_TC,NCSTRLPLUS_SUBJECT,DATE,KEYWORD,ABST
  RACT,PAGES,NCSTRLPLUS_URL)gt
• lt!ELEMENT SEMESTER (METADATA,ASSIGNMENTS,
  HOMEPAGE, LECTURES,HANDOUTS,EMAIL-ARCHIVAL,EXAMgt
• ltELEMENT ASSIGNMENTS (METADATA,ASSIGNMENT,GRADING
  SCRIPTS)gt
• lt!ELEMENT ASSIGNMENT METADATA,DESCRIPTION,FILES,SO
  LUTION,SUBMISSIONS,TESTING)gt
• lt!ELEMENT DESCRIPTION (METADATA,FILES)
• lt!ELEMENT FILES (FILE)gt
• lt!ELEMENT FILE (PCDATA)gtlt!ATTLIST FILE ID
  CDATA REQUIREDgt
• lt!ELEMENT SOLUTION (METADATA,FILES)gt
• lt!ELEMENT SUBMISSIONS (STDUENT)gt
• lt!ELEMENT STUDENT (FILES,GRADE)gt
• lt!ELEMENT GRADE (FILES)gt
• lt!ELEMENT HOMEPAGE (FILES)gt
• lt!ELEMENT LECTURES (CHAPTER)gt
• lt!ELEMENT CHAPTER (FILES)gt
• lt!ELEMENT HANDOUTSSYLLABUS)gtlt!ELEMENT SYLLABUS
  (FILES)gt
• lt!ELEMENT EXAM (MIDTERM, FINAL)gt
• lt!ELEMENT MIDTERM (FILES)gt

12
Technology

• XML parser
• Java XML parser
• Both java and XML provide powerful platform
  independent capacity. Its perfect combination.
• Interface
• JFC Swing
• communication
• Socket and CGI script
• Bucket API
• CGI script

13
DEMO-Author Tool
14
DEMO-View Tool
15
Conclusion

• Although this structure is designated to support
  Course archival. Its flexible enough to support
  other complex document archival.
• See http//www.cs.odu.edu/dlibug in detail.