PAWN:Main: Difference between revisions
From Adapt
No edit summary |
No edit summary |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
PAWN | PAWN is a mature software platform that is extremely flexible in implementing centralized and distributed ingestion and processing workflows. It is built on an infrastructure-independent scalable, secure, and reliable architecture. | ||
PAWN was designed to handle the ingest process from producer-archive agreement through final publishing of objects in long term repository. To support this part of an objects lifecycle, PAWN provides the following functionality: | |||
* Organization of all possible data types into easy to use templates used to create packages | |||
* A mechanism for collecting item level approval and reject marks as well as a way of specifying which marks are required. | |||
* A mechanism to allow users to have customizable roles rather than locking users into predefined roles. | |||
* Allow automated and manual process chains to be defined and executed on data in PAWN. In addition, allow these chains to be customized depending on record set and template requirements. | |||
* Through domains, different producer-archive agreements may be specified and operate independently on the same software infrastructure. | |||
*Demonstrations | |||
**[[Pawn:Public Demonstration|Public Demonstration]] | |||
**[[Pawn:NARA Demonstration|NARA Demonstration]] | |||
**[[Pawn:NDIIPP Demonstration|NDIIPP Demonstration]] | |||
*[[Pawn:FAQ|PAWN FAQ]] | |||
*[[Pawn:User Documentation|User Documentation]] | |||
*[[Pawn:Development Documentation|Development Documentation]] | |||
'''Case Studies''' | |||
* [[Pawn:ICDL Book Builder|ICDL Book Builder]] |
Latest revision as of 19:55, 12 September 2008
PAWN is a mature software platform that is extremely flexible in implementing centralized and distributed ingestion and processing workflows. It is built on an infrastructure-independent scalable, secure, and reliable architecture.
PAWN was designed to handle the ingest process from producer-archive agreement through final publishing of objects in long term repository. To support this part of an objects lifecycle, PAWN provides the following functionality:
- Organization of all possible data types into easy to use templates used to create packages
- A mechanism for collecting item level approval and reject marks as well as a way of specifying which marks are required.
- A mechanism to allow users to have customizable roles rather than locking users into predefined roles.
- Allow automated and manual process chains to be defined and executed on data in PAWN. In addition, allow these chains to be customized depending on record set and template requirements.
- Through domains, different producer-archive agreements may be specified and operate independently on the same software infrastructure.
- Demonstrations
- PAWN FAQ
- User Documentation
- Development Documentation
Case Studies