compared with
Current by Donal Fellows
on May 27, 2014 15:56.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
| Entity (Scout) | | A domain object that represents something of interest to Automated Watch, for example an entity may represent the JPEG2000 file format. Entities may have Properties. \\ | | D2.3 |
| Execution Environment | | An abstract layer of the Execution Platform which provides a placeholder representing functionality to be fulfilled by a specific technology. The Execution Environment provides the physical infrastructure to perform computation. An example might be the nodes of a Hadoop cluster. \\ | | D2.3 |
| Execution Platform  \\ | EP | An infrastructure that provides the computational resources to enact a Preservation workflow and execute Preservation actions. Abstracted into three layers: the Execution Environment; the Job Execution Service and the Job Submission Service API. \\ | | D2.3 \\
Technology agnostic. Could be Taverna Server, or Hadoop \\ |
| (SCAPE) Experiment Evaluation \\ | | Findings and results, both measurable and non-measurable, of a particular execution of an Experiment, within the Testbed sub-package. \\ | | |
| (SCAPE) Experiment | | {color:#000000}A unit of work that defines an implementation of a User Story, within the Testbed sub-package.  It consists of a dataset, one or more preservation components, a workflow and a processing platform that can be used to evaluate SCAPE technology and provide evidence of scalable processing{color}\\ | | |
| Plan Management API \\ | | {color:#000000}An API to be implemented by Digital Object Repositories that provides HTTP endpoints for the retrieval and management of Preservation Plans.{color} | | |
| Plan Management GUI | | {color:#000000}A graphical user interface application that can be used to view and execute Preservation Plans on a Digital Object Repository that implements the Plan Management API.{color}\\ | | D4.1 |
| Plan Management Service | PMS | Any A service that holds a Preservation Plan and manages its lifecycle. This can be any service that implements the Plan Management API is a Plan Management Service. Note that a PMS may also implement other APIs and be _principally_ known by other names. | | D4.1 |
| Planner | | (in Watch WP domain): An agent with an interest in the change of the state of the world over time. This can be either the planning component or a user client. \\ | | |
| Plato | | A web-based tool that creates a _Preservation Plan_ and provides a user interface for viewing, managing and updating that plan. The plan itself is stored in the _Plan Management Service_ after creation. | | |
| Preservation Plan | | A preservation plan is a live document that defines a series of preservation actions to be taken by a responsible institution due to an identified risk for a set of digital objects or records (called a collection).It is defined by Plato and stored in a Plan Management Service. \\ | | |
| Preservation Action Plan | PAP | A Preservation Action Plan is part of a _Preservation Plan_ --- or a separate document for the purposes of processing --- that describes a set of digital objects, an operation (typically a transformation) to apply to each of them, and a rule that allows the determination of whether the operation on a particular digital object was successful on the basis of characteristics measured on the instantiation of the digital object, what it was transformed into, or the comparison of what it was and what it became. \\
A Preservation Action Plan does _not_ describe how to instantiate the digital object, where to archive successful transformations, or where to report the outcome of applying the PAP. | | |
| Scalable Preservation Environments \\ | SCAPE | {color:#000000}An EU funded project developing scalable services for the planning and execution of institutional preservation strategies on an open source platform that orchestrates semi-automated workflows for large-scale, heterogeneous collections of complex digital objects.{color}\\ | | |
| SCAPE Characterisation Component | | Characterisation components are a family of _SCAPE Components_ (defined to wrap tools produced in WP9) that compute one or more properties of a _single_ instantiated digital object or file. The output ports that produce measures are always annotated with the metric (in the _SCAPE Ontology_) that describes what the component computes. \\ | | |
| SCAPE Component | | SCAPE components are _Taverna Components_, identified by the SCAPE Preservation Components sub-project, that conform to the general SCAPE requirements for having annotation of their behaviour, inputs and outputs. SCAPE components may be stored in the SCAPE Component Catalogue.\\ | | |
| SCAPE Component Catalogue | | A catalogue of Taverna components used when creating and enacting SCAPE workflows. The component catalogue is functionality implemented by myExperiment. | | D7.3 |
| SCAPE Migration Component | | Migration components are a family of _SCAPE Components_ (defined to wrap tools produced in WP10) that apply a transformation to an instantiated digital object or file to produce a new file. The input is annotated with a term (from the _SCAPE Ontology_) that says what sort of digital object/file is accepted, and the output is annotated with a term that says what sort of file is produced. \\ | | |
| SCAPE Ontology | | The SCAPE Ontology is an OWL ontology that formally defines the terms used by computing systems in SCAPE. \\ | | |
| Taverna Components | | Taverna components are _Taverna workflow_ fragments that are stored independently of the workflows that they are used in, and that are semantically annotated with information about what the behaviour of the workflow fragment is. They are logically related to a programming language shared library, though the mechanisms involved differ. \\
Taverna components are stored in a component repository. This can either be a local directory, or a remote service that supports the Taverna Component API (e.g., the _SCAPE Component Catalogue_, implemented by myExperiment). Only components that are stored in a publicly accessible service can be used by a _Taverna workflow_ that has been sent to a system that was not originally used to create it. | | D7.3 |
| Taverna Component Profile | | An XML document that describes the constraints that a Taverna component should adhere to, and the semantic annotations that may be used with that component.\\ | | |
| Taverna Component Repository | | A store of Taverna Components and Taverna component profiles. It is typically expected that the component repository would also be the component catalogue so that the components and their profiles can be found, and it is typically treated as a synonym of a catalogue; myExperiment is both a catalogue and a repository of Taverna components. | | |
| Taverna Command Line Tool \\ | | The Taverna Command Line Tool can execute a Taverna Workflow in a terminal/command prompt, without displaying a Graphical User Interface (GUI) \\ | | |
| Taverna Server | TAVSERV | Taverna Server is a multi-user service that can execute _Taverna workflows_. Clients do not need to understand those workflows in order to execute them. \\ | | |
| Web Content Testbeds | WCT \\ | The Web Content Testbed is one of the Testbeds of the SCAPE project. The Testbeds are represented by memory institutions holding large data sets that are used to test the applicability of tools, workflows, and solutions developed in the SCAPE project. | | |
| Web Snapshot | | The image capture of a web page that is taken when a web page is rendered in a web browser. | | |
| Workflow Repository | | A service that stores workflows, allowing them to be distributed to other people in accordance with the defined access control policies. A workflow repository that holds Taverna workflows is consequently a Taverna workflow repository.\\
MyExperiment is an example of a workflow repository. | | |