1. Extracting and Ingesting DDI Metadata and Digital Objects from a Data Archive into the iRODS extension of the NARA TPAP Using the OAI-PMH J. Ward, A. de Torcy, M. Chua & J. Crabtree IASSIST 2010 Ithaca, N.Y.

2. Oldest Institute or Center at UNC-CH Founded 1924 Mission: Teaching, research, & service for social sciences Cross-disciplinary focus

3.  Rules-Based policy enforcement  iRODS grid based technology  OAI-PMH harvesting from Odum Dataverse Network

4.  Ingest Odum collections into iRODS  Break apart Odum preservation policies  Code these policies into series of iRODS rules

5. *From http://unc.renci.org/wordpress/wp-content/uploads/2009/05/irods-slide41.jpg

6. *From http://unc.renci.org/wordpress/wp-content/uploads/2009/05/nara-grid22.jpg

7. *From http://unc.renci.org/wordpress/wp-content/uploads/2009/05/irods-slide5.jpg

8. *From http://wiki.cetis.ac.uk/images/9/9d/OAI-PMH_overview.png

9. *From http://developers.sun.com/learning/javaoneonline/2007/pdf/TS- 4656.pdf

10. Global Identifier hdl:1902.29/H-864009 handle Study Title Harris 1986 Disabled Americans - Employment Survey, Study no. 864009 … Harris 1986 Disabled Americans - Employment Survey, Study no. 864009 hdl:1902.29/H- 864009 …

11. Level 1 Dataflow of extraction and ingest process

12. iRODS Rule ==== parseDDI.ir ==== Format DDI and extract metadata|| msiXsltApply(*xsltObjPath, *ddiObjPath, *BUF)##(XSLT transformation) msiDataObjCreate(*xmlObjPath,null,*DEST_FD)##(Create XML file) msiDataObjWrite(*DEST_FD,*BUF,*Written)##(Write XML file) msiDataObjClose(*DEST_FD,*junk)##(Close XML file) msiLoadMetadataFromXml(*ddiObjPath, *xmlObjPath)|nop(Load into iCAT) Input parameters *ddiObjPath=$1% Example: /odum/home/rods/1902.29/H-339/ddi.xml *xmlObjPath=$2% Example: /odum/home/rods/1902.29/H-339/AVUs.xml *xsltObjPath=/odum/home/rods/prototype/formatDDI.xsl Output parameters ruleExecOut *From https://www.irods.org/index.php/iRODS_Videos

13.  Step 1 = define policy areas  Step 2 = create policy declaration statements for each policy area; state the requirements for operation, not technical specifics  Step 3 = each entity in a policy statement is defined in language descriptions: humans and machine-readable references  Step 4 = deontic statements: logical statements define actors, actions, and constraints that enforce a policy statement.  Step 5 = Write iRODS rules for each statement Wolfe, Robert. 2007. PLEDGE policy list. MIT Libraries. http://pledge.mit.edu/images/1/13/PLEDGEPolicies20070927.pdf

14.  Organization, Environment, and Legal Policies  Defined dataset succession plan  Defined access policies  Log access for accountability  Reference TRAC criteria  Community and Usability Policies  Require a deposit agreement  Process and Procedure Policies  Defined iCAT to DDI discovery crosswalk  Store dataset’s DDI metadata as object  Defined persistent identifiers  Defined UNF’s and Checksums  Provide reporting of preservation network  Technology and Infrastructure Policies  Defined number of replication copies  Defined geographic location for the copies  Provide authentication policy  Provide versioning  Provide control for deletion/replacement  Defined replica validation frequency via UNF’s and Checksums

15. Video Demo http://ils.unc.edu/~wardj/share/eScience2009/2009-11-16-IEEE_demo.swf

16. Acknowledgements This work is funded by the NSF grant OCI-0848296 and is a collaboration with NARA on the development of the "NARA Transcontinental Persistent Archive Prototype". The initial work on this project was funded by the NARA supplement to NSF SCI 0438741, “Cyberinfrastructure; from Vision to Reality” – Transcontinental Persistent Archive Prototype (TPAP) (2005-2008).

17. Questions?