Preservation as a Service for Trust (PaaST) [English]
Syndetic Relationships
- NT: access; access data; access service; actor; actual role; archival bond; archival permanent feature; area of activity; assessment; assessment status; association class; attributable class; attributable object; authorized role; benchmark value; binary encoding; capability; class; collection; component description; component permanent feature; content component; content component description; controlling object; data format registry; data profile; data profile attribute definition; digital component; feature; heuristic association; heuristic information; human readable intellectual entity; information management; initial source; inspection; instantiation component; instantiation component description; instantiation object registry; integrity feature; intellectual entity; item; local preservation environment; machine readable intellectual entity; managed record; management set; manifest permanent feature; manifestation; manifestation description; notice of intent to submit; permanent feature; permanent feature expression; preservation action; preservation action data; preservation action report; preservation action set; preservation agreement; preservation assessment; preservation assessment data; preservation assessment report; preservation change; preservation change data; preservation change service; preservation collection; preservation commitment; preservation description; preservation director; preservation environment; preservation intention; preservation item; preservation management data; preservation management document; preservation management information; preservation network; preservation obligation; preservation problem; preservation role; preservation rule; preservation service; preservation service contract; preservation service provider; preservation storage; preservation storage data; preservation storage service; preservation target; preservation target data; preservation target manifestation; preservation target manifestation description; preserved record; preserved record collection; problem handling; problem handling instruction; problem history data; problem report; problem resolution report; producer; record aggregate; record category; record creator; record description; records management data; records management document; rendering; rendering description; reporting; requirement; rule domain; rule result; rule task; ruled action; ruled object; runtime version; runtime version description; service; set; software component; software component description; software registry; storage status; submission; submission document; submission information; submission process; submission processing data; submission processing service; submission set; submission status; submitter; success condition; success criterion; target description; target problem; target state; uniqueness feature; verification; verification data; verification status
- BT: as a service
- RT: document; party; record
- SF: PaaST
InterPARES Definition
n. ~ 1. A project of InterPARES Trust that investigated requirements for preservation of digital information in a manner independent of both the technology used and the assignment or division of responsibilities. – 2. A set of functional and data requirements that specify the actions and information needed for preservation of digital information, while supporting customization for different types of information and different policies, objectives and constraints on preservation.
General Notes
The Open Archival Information System (OAIS) reference model is abstract and lacks sufficient detail for implementation. By contrast, PaaST describes a model and specifications that can be implemented in software.
Citations
- PaaST (0.11) 2016 (†778 p. 3): The Preservation as a Service for Trust (PaaST) project is an initiative of the InterPARES Trust project that directly addresses the challenges of digital preservation in the Cloud. It sets out functional and data requirements that can be included in contracts for preservation with Cloud service providers; however, the potential benefits of using these requirements are not limited to the Cloud. They have been articulated to be applicable across as broad a variety of situations as possible, including · heterogeneity in the types of information objects being preserved; · variety in applicable directives, such as laws, regulations, standards, policies, business rules, and contractual agreements, · including varying conditions of ownership, access, use, and exploitation; · variation in institutional arrangements and relationships between or among the parties involved; · a wide spectrum of circumstances as possible from best practices to worst cases. (†1966)
- PaaST (0.11) 2016 (†778 ): The PaaST requirements have been specifically crafted to enable those responsible for preserving digital information to entrust that information to Cloud service providers. The requirements extend the perception that digital preservation entails the use of different technologies over time and assert that different, independent technologies can be used for digital preservation both simultaneously and sequentially and, most importantly, reliably. (†1970)
- PaaST (0.8) 2016 (†751 ): The Preservation as a Service for Trust (PaaST) project is an initiative in the InterPARES Trust that directly addresses the challenges of digital preservation in the Cloud. It sets out functional and data requirements that can be embodied in contracts for preservation with Cloud service providers; however, the potential benefits of using these requirements are not limited to the Cloud. They have been articulated to be applicable across as broad a variety of situations as possible, including · heterogeneity in the types of information objects being preserved; · variety in applicable directives, such as laws, regulations, standards, policies, business rules, and contractual agreements, · including varying conditions of ownership, access, use, and exploitation; · variation in institutional arrangements and relationships between the parties involved; · across as wide a spectrum as possible from best practices to worst cases. (†1861)
- PaaST (0.8) 2016 (†751 ): The main differences between PaaST and OAIS are (1) the scope of PaaST is limited to digital information; (2) OAIS is predicated on the assumption that preservation will be carried out in a coherent system whereas PaaSt includes the possibility that different requirements for preservation are satisfied by different parties using different technologies; and (3) OAIS intentionally does not provide or constitute a guide to implementation, but PaaST is formulated to facilitate implementation in software. (†1862)
- PaaST (1.0) 2017 (†860 p. 2): The PaaST requirements constitute a supplement to the Open Archival Information System (OAIS) Reference Model. OAIS is a conceptual framework for digital preservation that describes, in a technologically neutral manner, the activities and the information that are necessary for preservation. Effectively, it has defined the universe of discourse for digital preservation in a variety of contexts around the world. As a reference model, OAIS neither specifies a design or an implementation nor prescribes or even recommends any specific technology for preservation. The standard recognizes that implementations might organize functionality differently. PaaST requirements supplement OAIS in that they are intended to be directly implementable in software. Nonetheless, like OAIS, PaaST does not specify what technology should be used. Rather, it defines what the technology must be able to do. (†2421)