1 / 7

PAWN: Producer-Archive Workflow Network

PAWN: Producer-Archive Workflow Network. University of Maryland Institute for Advanced Computer Studies Joseph Ja’Ja, Mike Smorul, Mike McGann. What is PAWN?. Software that provides an ingestion framework Distributed and secure ingestion of digital objects into an archive.

arty
Download Presentation

PAWN: Producer-Archive Workflow Network

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. PAWN: Producer-Archive Workflow Network University of MarylandInstitute for Advanced Computer StudiesJoseph Ja’Ja, Mike Smorul, Mike McGann

  2. What is PAWN? • Software that provides an ingestion framework • Distributed and secure ingestion of digital objects into an archive. • Handles the process • From package assembly • To archival storage • Simple interface for end-users • Flexible interface for archive managers • Designed for use in multiple contexts

  3. Distributed Ingestion • Multiple producing sites with different requirements. • Separation of administrative responsibility. • Customizable roles for various parties. • Scalable infrastructure.

  4. Overall Organization • Producers organized into domains, each domain containing a record schedule negotiated with the archive. • Each domain contains a hierarchy of the types of data and record sets (convenient groupings from the record schedule). • An end-user operates within a domain with record sets associated with the account.

  5. Package Workflow Overview • Manager creates Record Sets • Client creates and submits package in accordance with Record Set. • Packages can be reviewed and rejected. • Once approved, packages can be archived • Rejected packages can be held until rectified or deleted for a resubmission • Audit trail tracks all workflow steps

  6. Test Case - SLAC Records

  7. More information • Web site: • http://www.umiacs.umd.edu/research/adapt • Or “I’m feeling lucky” Google keywords: • ADAPT UMIACS

More Related