1 / 18

PAWN Test III

PAWN Test III. Producer – Archive Workflow Network (PAWN). Distributed and secure ingestion of digital objects into the archive. Use of web/grid technologies – platform independent Ease of integration with data grids or digital libraries. XML Representation of metadata and bitstream

claudinef
Download Presentation

PAWN Test III

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 Test III

  2. Producer – Archive Workflow Network (PAWN) • Distributed and secure ingestion of digital objects into the archive. • Use of web/grid technologies – platform independent • Ease of integration with data grids or digital libraries. • XML Representation of metadata and bitstream • Self describing bitstream submissions • Accountability of transfer and guarantee of data integrity

  3. Distributed Ingestion

  4. Previous workflow • Negotiate Submission Agreement. • Create Submission Information Packet.(SIP) • Submit SIP metadata for approval. • Transfer of SIPs to receiving servers after approval. • Validation of SIP transfer. • Organization of data into collections and transfer into the distributed archive.

  5. Changes • Role of manager is much more significant • Client requirements reduced • No submit, approval, interaction • Multiple domains per management server • Stateless receiving server, manager can review submissions • New model for representing record schedules and file plans

  6. Workflow Overview: Producer • Producer has records that need to be archived. • PAWN presents the producer with the list of record sets the producer is authorized to archive. • Producer selects the relevant record set and selects the list of data to be archived. • PAWN builds package and sends it to the receiving server.

  7. Example: Producer • Works at the Patuxent Wildlife Research Center (domain) • Research scientist for the migratory birds population databases. • Available record sets: • Breeding Bird Census • Breeding Bird Survey • Avian Point Counts • Breeding Bird Atlas Explorer

  8. Example: Record Submission • Submission of the Avian Point Count data published for 2001. (record set) • Presented with the following categories: • Raw Tabular Data • Summarized Tabular Data • FGDC Metadata • Producer selects the relevant files and directories for each category.

  9. Authorities • Categories map to authorities in a record schedule. • Data Layers by USGS (1201-01c) • Raw Tabular Data • Summarized Tabular Data • Documentation (1201-01e) • FGDC Metadata • Producer is not required to know (but can know) the mapping between authorities and categories.

  10. Workflow Overview: Managers • Create record schedules with authorities. • Create accounts for producers authorized to archive. • Create record sets to limit producers to specific archive duties. • Map record set categories to record schedule authorities. • Review packages submitted by producers.

  11. Domains • Logical unit of administration and delegation • Domain contains its own set of: • Producers • Record schedules • Record sets • Managers • Each producer belongs to a domain. • Each manager controls actions within a specific domain.

  12. Overview: Administrators • Create organization hierarchy and domains • Create managers for domains. • Can perform the activities of any manager.

  13. Overview: Account privileges

  14. Components

  15. Overview: Security • Separate realms of security • Archive, each management server • Trust between management server and archive. • Management server issues SAML Assertion to client software that contains: • Domain and identity • Current role (admin, producer, mgr, etc)

  16. Overview: Receiving Server • Mostly disposable, configuration stored on scheduler • Can migrate data between central resource (SRB) and local cache. • Can handle packages from multiple producing sites. • Packages contain authorization information.

  17. Test Collections • NARA Collections • Model current record schedules with focus on producer ingestion • ARL collection • Bush library • Test to see how PAWN works with non-scheduled data sets.

  18. Demo

More Related