Existing Citations

  • Archiving as a Service (AaaS) (p. 113): Basic requirement that provider of archiving service in cloud environment have to meet is to ensure the confidence of internal and external users in entity of origin and its archival holding. That means that provided service is safe and stable. Provider of services should follow all professional and technical regulations and plans or at least enable long-term preservation practice over entrusted digital objects. Objects intended for long-term preservation should remain accessible by usage of methods such as migration, typed object conversion or other digital preservation methods systematized by Thibodeau,9 ideally performed within provided service. Provider of archiving service should be aware that the service is not reduced to providing mere repository for storing digital documents. Service should encompass proactive archival management of (complex) digital objects, their organizational context and provenance. It should guarantee continued usage of archived objects as authentic and trusted sources of evidence for creator and information for present and potential wider user community. (†2725)
  • community cloud (p. 111): Where the physical infrastructure is implemented, administered, and operated by several organizations in a certain community of consumers from organizations that have shared goals and requirements. (†2722)
  • hybrid cloud (p. 111): The combination of two or more physical cloud infrastructures from different branches of the above listed deployment models that are physically separate but are connected via the means of mutual data and application portability or management hierarchies. (†2724)
  • Infrastructure as a Service (IaaS) (p. 110): Ability to deliver complete virtual datacenters to the user who is then able to configure and deploy virtual machines and other relevant/corresponding virtual components according to their personalized requirements (†2720)
  • Platform as a Service (PaaS) (p. 110): Ability to deliver complete environments (operating systems and required tools) for testing or development of external applications. The user, however, has no control over the configuration settings of the application-hosting environment. (†2719)
  • private cloud (p. 110): Where it is implied that the cloud infrastructure is built and provisioned for private use by a single organization. Private clouds in practice tend to be service-oriented with specific roles and requirements. (†2721)
  • public cloud (p. 111): The cloud infrastructure is intended for “rent” by the public users, as delegated by the provider usually for profit or other means of compensation for the provider. (†2723)
  • Software as a Service (SaaS) (p. 110): Ability to deliver applications from cloud-based physical infrastructure, accessible via various client software tools or devices. The user has no awareness or control of the underlying physical components or software configuration capabilities outside the delivered application. (†2718)