1 / 15

Project Overview

Project Overview. Design. Background. Digital library for Course Archival ODU, CS department Xiaoming Liu. Problem. Technology. Solution. DEMO. Conclusion. Background. Part of ODU Digital Library project. Based NCSTRL+ and bucket.

kemal
Télécharger la présentation

Project Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Overview Design Background Digital library for Course Archival ODU, CS department Xiaoming Liu 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 • Instructor’s handout, lecture. • Student’s assignment, project. • Why to keep course archival • Instructor & student’s future reference..

  4. Description • Current Course archival implementation • Instructor’s webpage, FTP site • Student’s 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) • <!DOCTYPE CLASS [ • <!ELEMENT CLASS (METADATA,Semester*)> • <!ELEMENT METADATA (BIB-VERSION,ID,ENTRY,ORGANIZATION,LANGUAGE,TITLE,AUTHOR,NCSTRLPLUS_ARCHIVALTYPE,NCSTRLPLUS_TC,NCSTRLPLUS_SUBJECT,DATE,KEYWORD,ABSTRACT,PAGES,NCSTRLPLUS_URL)> • <!ELEMENT SEMESTER (METADATA,ASSIGNMENTS, HOMEPAGE, LECTURES,HANDOUTS,EMAIL-ARCHIVAL,EXAM> • <ELEMENT ASSIGNMENTS (METADATA,ASSIGNMENT*,GRADINGSCRIPTS)> • <!ELEMENT ASSIGNMENT METADATA,DESCRIPTION,FILES,SOLUTION,SUBMISSIONS,TESTING)> • <!ELEMENT DESCRIPTION (METADATA,FILES) • <!ELEMENT FILES (FILE*)> • <!ELEMENT FILE (#PCDATA)><!ATTLIST FILE ID CDATA #REQUIRED> • <!ELEMENT SOLUTION (METADATA,FILES)> • <!ELEMENT SUBMISSIONS (STDUENT*)> • <!ELEMENT STUDENT (FILES,GRADE)> • <!ELEMENT GRADE (FILES)> • <!ELEMENT HOMEPAGE (FILES)> • <!ELEMENT LECTURES (CHAPTER*)> • <!ELEMENT CHAPTER (FILES)> • <!ELEMENT HANDOUTSSYLLABUS)><!ELEMENT SYLLABUS (FILES)> • <!ELEMENT EXAM (MIDTERM, FINAL)> • <!ELEMENT MIDTERM (FILES)> • <!ELEMENT FINAL (FILES)>

  12. Technology • XML parser • Java XML parser • Both java and XML provide powerful platform independent capacity. It’s 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. It’s flexible enough to support other complex document archival. • See “http://www.cs.odu.edu/~dlibug” in detail.

More Related