1 / 36

The Making of America II Project sunsite.berkeley/moa2 Bernie Hurley

The Making of America II Project http://sunsite.berkeley.edu/moa2 Bernie Hurley Chief Scientist, UC Berkeley Library (bernie@library.berkeley.edu). Today’s Agenda. I. MoA II Project Background II. Planning Phase -- MoA II White Paper

anitra
Download Presentation

The Making of America II Project sunsite.berkeley/moa2 Bernie Hurley

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. The Making of America II Project http://sunsite.berkeley.edu/moa2 Bernie Hurley Chief Scientist, UC Berkeley Library (bernie@library.berkeley.edu)

  2. Today’s Agenda I. MoA II Project Background II. Planning Phase -- MoA II White Paper III. Production Phase -- Progress to Date

  3. I. MoA II Project Background • Standards Setting Project • Continuation of the Encoded Archival Description (EAD) Project • Electronic finding aids for archival materials • MoA II Goal is to Create Community Standards for Digital Library Objects • Including metadata and content • Builds on previous work in the community • Help understand what value metadata adds to scholarly and instructional use of the objects -- and at what cost

  4. MoA II Project Background (Cont.) • Three Phases • The Planning Phase (DLF funded) • Write and review a MoA II White Paper to begin the standards discussion and prepare for the testbed • The Production Phase (NEH Funded) • Create a testbed that will allow the community to experiment with and evaluate different practices for digital archival object discovery, display, navigation and manipulation • Dissemination Phase

  5. II. The MoA II White Paper

  6. II. MoA II White Paper Organization • Part 1: Executive Summary and Project Background • Part 2: The MoA II Model • Part 3: Implementing the MoA II Model • Part 4: Best Practices for Imaging • Appendices • Bibliography, Sample DTD and object encodings, etc.

  7. Part 1: White Paper Executive Summary Goals of the White Paper 1) Start a discussion on creating “community standards” for digital library objects • Review and discussion of this paper is the 1st step 2) Create a MoA II “holistic” model to frame the discussion • Why we need these standards? What do they include? Where do they fit into a larger National DL model? 3) Start an investigation of best practices for the digitization of images 4) Gather information needed for a MoA II testbed

  8. Part 2: The MoA II Model The goal of the MoA II Model is todevelop suites of tools for specific audiences that integrate the discovery, display, navigation and manipulation of standardized objects across distributed repositories.

  9. The MoA II Model: Assumptions 1) A National DL will be made up of many different classes of objects • library, archival, museum, GIS, numeric datasets 2) These objects will populate distributed repositories 3) Scholars and students will require coherent and integrated access to these objects (i.e., distributed repositories are transparent)

  10. Assumptions (Cont.) 4) Therefore, we will need to develop tools that can transparently discover, display, navigate and manipulate DL objects across distributed repositories 5) These tools will require objects be standardized • Note: Having standardized objects may also be helpful to libraries in sharing tool development costs and in the archiving of these objects

  11. MoA II Model and Sub-models The MoA II Model: Goal: Suites of tools for specific audiences that integrate the discovery, display, navigation and manipulation of standardized objects across distributed repositories. • Digital Library Service Model • Digital Object Model • Distributed Systems Architecture Model • Not yet a funded part of the MoA II Project

  12. MoA II -- Digital Library Service Model Services Tools Digital Objects (Digital Object Sub-model)

  13. Service Model (cont.) 1) Services • Suites of Tools that support a particular audience • E.g. K-12 vs. scholarly use of a photograph collection 2) Tools • Client/Server applications that consist of suites of user level behaviors that allow for the discovery, display, navigation and manipulation of standardized digital objects

  14. Service Model (cont.) • User level behaviors (functionality) • Behaviors are what tools do for users • Diary Example: How are you organized (dated entries, accounts, contacts)?; get first/next/previous/last entry 3) Digital Library Objects • Foundation of the Service Model • Need to be standardized so tools can work on them across distributed repositories • Encapsulate content and metadata

  15. Review: Digital Library Service Model Services Tools Digital Objects Content; Metadata; Methods The goal of the MoA II Model is todevelop suites of tools for specific audiences that integrate the discovery, display, navigation and manipulation of standardized objects across distributed repositories.

  16. Workstation Network Union Index -Class Tools -Objects -Class Tools -Objects -Class Tools -Objects Repository Repository Repository MoA II Architecture Model Client/Server, Object Oriented

  17. Web Server Web Browser Java Applet (tool) Applet Internet Workstation IN T E R N E T An Object WEB Implementation ORB Object Repository Object Repository

  18. MoA II Applet/CORBA Implementation 1) Browser: Discovery Applet 2) Browser: Display Applet 1: Object ID 2: Object ID 3: Object ID Display Applet? Repository & Object ID ORB ORB Repository HTTP CORBA Web Server CORBA Repository Layer (server side behaviors) Create HTML page w/display applet DBMS (Content) Union Catalog

  19. Part 3: Implementing the MoA II Model • Select Classes for the MoA II Testbed • Continuos tone photographs, Photo albums, Diaries, Correspondence, Journals, Ledgers • MoA II Digital Library Service Model 1) Services • Audience is scholars 2) Tools • Discover, display and navigate objects in selected classes • Behaviors • General Navigation • Images: Pan , Zoom, Color comparison, etc.,

  20. MoA II Model Implementation (cont.) 3) Digital Library Objects (Model) a) Content • Images, text, encoded text b) Metadata • Descriptive: MARC collection records & finding aids • Structural & Administrative elements defined in detail c) Methods • To be determined by system designer • Create a DTD to Encode (encapsulate) Metadata and Content • Transfer Syntax

  21. Part 4: Best Practices for Imaging • General Recommendations • Scanning, Digital masters & derivatives, Image quality, File formats • Specific Project Recommendations • 24 bit color for color images • 8 bit grayscale for non-color images • Most images should be captured at 600 DPI or greater • Avoid compression • Use TIFF, but record which version

  22. III. Production Phase Progress to Date

  23. MoA II --Progress to Date 1) White Paper 2) The MoA II DTD 3) Digitization Management Software • MS Access Database • MoA II Object Builder 4) Tools: A MoA II Compliant Viewer

  24. 1) MoA II White Paper • Reviewed by the MoA II Participants • Submitted to the Digital Library Federation for publication • Found at http://sunsite.berkeley.edu/moa2 • Use the Postscript version if possible

  25. 2) The MoA II DTD • Version 1.0 is Complete • The DTD, a Tutorial Explaining the DTD and an Example Encoded Document can be found at http://sunsite.berkeley.edu/moa2/ • DTD has 3 Sections • File Inventory • Administrative Metadata Section • Structural Map

  26. 2a) File Inventory <FileGrp VERSDATE='1998-09-01' ADMID='HIREZJPG IPRIGHTS IMGSRC'> <File ID='HRJ1' MIMETYPE='image/jpg' SEQUENCE='1' SIZE='220346' CREATED='1998-09-01' OWNERID='CPR-hi.jpg'> <FLocat LOCTYPE='URL'> http://sunsite.berkeley.edu/~jmcdonou/CPR-hi.jpg</FLocat> </File> </FileGrp>

  27. 2b) Administrative Metadata <AdminMD ID="HIREZJPG"> <FileMgmt> <Image> <Compression>JPEG</Compression> <Dimensions X='1536' Y='1024' /> <BitDepth BITS='16' /> <ColorSpace>RGB</ColorSpace> <CLUT FResident='YES'></CLUT> <Resolution>200 DPI</Resolution> </Image> </FileMgmt>

  28. 2c) Structural Map <StructMap> <div N='1' TYPE='Stereograph' LABEL='Secrettown. 62 miles -- altitude 3,000 feet. Photographer&#39;s number: 47'> <fptr FILEID='HRJ1' MIMETYPE='image/jpeg' /> <fptr FILEID='LRJ1' MIMETYPE='image/jpeg' /> <fptr FILEID='GIF' MIMETYPE='image/gif' /> </div> </StructMap>

  29. 3) Digitization Management Software • Too Difficult to Create MoA II Objects by Hand • Realized That Most Metadata can be Captured During the Digitization Process • Create Digitization Management Software • The MoA II Database • Object definition and data capture • Built on MS Access database • MoA II Object Builder

  30. 3a) MoA II Database • Part 1: Object Definition • Define objects and sub-objects to digitize • Defining the structure • Part 2: Image Management • Define parameters for master and derivatives • Capturing administrative metadata • Generates file names for each image • Part 3: Defaults

  31. 3b) MoA II Object Builder • Program that runs through the MoA II database and creates fully encoded MoA II objects

  32. 4) Tools -- MoA II Compliant Viewer • Java Applet • Used RMI (Remote Method Invocation) to Connect to a Distributed Repository • Series of Method Calls to Retrieve parts of the Object

  33. The END!

More Related