1. Archivists’ Toolkit Preliminaries: Architecture, DB Leslie Myrick NYU

2. Possible Java Architecture JSP Model 2 Architecture –Servlet Controller Handles requests, View selection, instantiates beans –JSPs update the View in the browser –JavaBeans used to represent the object in memory; access DB using JDBC manage the Model –JDBC connection to the data source

3. Similar Use of Servlet/JSP Model in Digital Library Applications Dspace UC Berkeley’s GenX system CDL Preservation Repository

4. JSP Model 2 Cleanest separation of presentation and content –Clear delineation of roles of developers and designers Takes advantage of strengths of servlets and JSPs for serving dynamic content –JSP for presentation layer –Servlets for performing process-intensive tasks Servlet as Controller in charge of request processing, creation of beans or objects used by JSPs to forward request No processing logic in JSPs -- simply responsible for retrieving objects or beans instantiated by servlets

5. JSP Model 2 Architecture

6. JSP Model 1 Bulk of processing performed by JSP –Process requests and draw view Fine for simple applications

7. JSP Model 1 Architecture

8. MySQL vs postgreSQL Both ACID compliant (transaction safe) Both support referential integrity (as of MySQL 4.x) MySQL faster; postgreSQL more robust Finer grained locking in postgreSQL –MultiVersion Currency Control in postgreSQL Want triggers? Views? Inheritance? For now go with postgreSQL MySQL has built-in full-text search capability Ease of installation and maintenance – MySQL hands down.

9. The ACID test Atomicity - All elements of a given transaction take place or none do. Consistency - Each transaction transforms the database from one valid state to another valid state. Isolation - The effects of a transaction are not visible to other transactions in the system until it is complete. Durability - Once a transaction has been committed, it's effects are permanent-- even if the system crashes, or a disk dies.

10. Proposed DB Schema: Archaeology / Genealogy Ultimately based on MOA II model With refinements to NYU’s zeroDB schema for digital object metadata Torqued to describe archival objects and their digital surrogates Same essential hook: pure Aristotelian hierarchy

11. It all comes down to object Pivotal entity is object nesting other objects –objectType can be fonds, collection, component –componentType can be series, file, item, accretion Object hierarchy maintained through: –objectID, parentID, nextSibID

12. Object Table

13. Accession Table

14. Provenance Table

15. Physical Location Tables CREATE TABLE physLoc ( physLocID int(11) NOT NULL auto_increment, physLocLevelID int(11) not NULL default '0', physLocTypeID int(11) NOT NULL default '0', physLoc varchar(128) NOT NULL default '', isPublic tinyint(1) unsigned NOT NULL default '0', PRIMARY KEY (physLocID) ); -- -- Data for table physLocLevel -- INSERT INTO physLocLevel (physLocLevel) VALUES ('repository'); INSERT INTO physLocLevel (physLocLevel) VALUES ('internal location'); INSERT INTO physLocLevel (physLocLevel) VALUES ('physical container'); -- -- Data for table 'physLocType' -- INSERT INTO physLocType (physLocType) VALUES ('accession location'); INSERT INTO physLocType (physLocType) VALUES ('processing location'); INSERT INTO physLocType (physLocType) VALUES ('shelflist location'); INSERT INTO physLocType (physLocType) VALUES ('offsite location');

16. Ingest of Legacy Data from marcxml Student Programmers’ Assignment Probably involve JAXP/DOM Already undertaken conversion of records from Innopac iiirecord dtd to marc21slim schema; tape.mrc to marcxml using marc4J

17. Ingest of Legacy Data from EAD Testbed creation tool XSLT with Java Extensions using Xalan –Get nextID from database –Extensions instantiate and increment DBID, parentID, nextSibID for each component in –Write out to.sql file to dump into DB

18. <xalan:component prefix="counter" elements="init incr" functions="read"> DBID: PARENTID Series: c01- Unittitle: Abstract: Scopecontent:

19. DBID: 3 PARENTID 2 Series: c01-1 Unittitle: Series I: Documentary Material DBID: 4 PARENTID:3 Subseries: c02-1 Unittitle: Subseries A: Subjects DBID:5 PARENTID: 4 Subseries: c03-1 Box: 1 Folder: 1 Unittitle: Advertising Unitdate:undated DBID:6 PARENTID: 4 Subseries: c03-2 Box: 1 Folder: 2-6 Unittitle: Art & Collecting Unitdate: undated

20. INSERT INTO OBJECT (objectID, parentID, nextSibID, hasChildren, componentTypeID) VALUES (3,2,126,1,1); INSERT INTO TITLE (titleID, titleTypeID, title, objectID) VALUES (NULL,1,"Series I: Documentary Material",3) DBID: 3 PARENTID: 2 NEXTSIBID: 126 Series: c01-1 Unittitle: Series I: Documentary Material