REPORT
Copyright © 2011 ESA and other members
of the SCIDIP-ES Consortium, www.scidip-es.eu
D21.4 Preservation Strategy Toolkit User
Manual
Work package
WP21 Services/Toolkits Development and Adaptation
Task
Author (s)
Brian Ritchie, Shirley Crompton
STFC
Author (s)
Christian Ceprani
ACS
Author (s)
Holger Brocks
ICT
Author (s)
Yannis Marketakis
FORTH
Author (s)
Felix Engel
FTK
Author (s)
Jinsongdi Yu
JU
Author (s)
Luigi Briguglio, Pasquale Andriani
ENG
Authorized by
Reviewer
Name Surname
Company
Doc Id
Dissemination Level
CONFIDENTIAL/PUBLIC
Issue
1.0
Date
11/04/2013
1
SCIDIP-ES EC Grant Agreement n°. 283401
REPORT
Copyright © 2011 ESA and other members
of the SCIDIP-ES Consortium, www.scidip-es.eu
Abstract:
This document represents the User Manual for the Preservation Strategy Toolkit (incorporating the
RepInfo Toolkit) developed in the frame of SCIDIP-ES project. This document contains all useful
information on how to install (if applicable), configure and use the Toolkit.
2
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Document Log
Date
Author
Changes
Version
Status
04/02/2013
Shirley Crompton,
Brian Ritchie, Christian
Ceprani, Holger
Brocks, Yannis
Marketakis, Felix
Engel, Jinsongdi Yu,
Pasquale Andriani and
Luigi Briguglio
First draft for internal
review
0.1
Draft
11/04/2013
Brian Ritchie
Initial draft of PST/RIT 0.2
guide
Draft
4
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
TABLE OF CONTENTS
..................................................... 1
1
INTRODUCTION ........................................................................................................................................................... 7
PURPOSE AND SCOPE ................................................................................................................................................ 7
WHO SHOULD READ THIS DOCUMENT...................................................................................................................... 7
SYSTEM CONTEXT ....................................................................................................................................................... 7
RELEASE NOTES.......................................................................................................................................................... 8
1.1
1.2
1.3
1.4
2
INSTALLATION GUIDE ............................................................................................................................................. 8
2.1 OVERVIEW ..................................................................................................................................................................... 8
2.2 PREREQUISITES ........................................................................................................................................................... 8
2.2.1 SOFTWARE PREREQUISITES .................................................................................................................................................. 9
2.2.2 HARDWARE PREREQUISITES ................................................................................................................................................. 9
2.3 OSS/COTS INSTALLATION ....................................................................................................................................... 9
2.4 PRESERVATION STRATEGY TOOLKIT INSTALLATION ........................................................................................... 9
2.5 UNINSTALLATION ......................................................................................................................................................... 9
3
USING SCIDIP-ES PRESERVATION STRATEGY TOOLKIT....................................................................... 9
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
RUNNING PRESERVATION STRATEGY TOOLKIT .................................................................................................... 9
WORKSPACE................................................................................................................................................................. 9
FIRST PROJECT .......................................................................................................................................................... 10
ONTOLOGY .................................................................................................................................................................. 12
FIRST PNM MODEL ................................................................................................................................................... 13
EDITING PNM OBJECTS ........................................................................................................................................... 16
EDITING RELATIONS .................................................................................................................................................. 17
OBJECTIVES................................................................................................................................................................ 18
DECISIONS ................................................................................................................................................................... 22
RISKS ......................................................................................................................................................................... 24
SOURCE AND EXPORTING MODEL ........................................................................................................................ 25
PNM MODEL EDITOR FEATURES ......................................................................................................................... 26
4
REFERENCE MANUAL ........................................................................................................................................... 34
5
TROUBLESHOOTING COMMON ISSUES ....................................................................................................... 34
ANNEX A. FIGURES AND TABLES.......................................................................................................................... 35
A.1. LIST OF FIGURES ...................................................................................................................................................... 35
A.2. LIST OF TABLES ........................................................................................................................................................ 35
ANNEX B. TERMINOLOGY .......................................................................................................................................... 36
5
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
6
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
1 Introduction
1.1 Purpose and Scope
This document provides an overview of the M18 release of the Preservation Strategy/RepInfo Toolkit
focusing in particular to its installation and usage.
1.2 Who should read this document
Users who may want to understand and operate the Preservation Strategy Toolkit/ RepInfo Toolkit.
1.3 System Context
The Preservation Strategy Toolkit provides core features of the OAIS preservation planning and is
intended to facilitate the crucial tasks of planning, managing and documenting the strategies adopted
for preserving data in an archive. The toolkit uses the Preservation Network Model (PNM), which was
developed within the CASPAR project to represent the output of a preservation analysis conducted for
a digital object to be preserved in a preservation archive or repository.
In an OAIS-compliant archive, there are a number approaches to preserve digital data. Besides using
Representation Information (which includes emulation software), one could migrate (Transform in
OAIS terminology) the data into different formats. The preservation analysis of a digital object enables
identification and assessment of the risks associated with its dependencies on other entities. The
output of this type of analysis underpins the formulation of a suitable preservation strategy to be
adopted by an archive; taking into account the preservation aims, related risk tolerance level,
preservation policies and other requirements. The PNM can be used to articulate the result of
preservation analysis as a network of related objects along with the preservation decisions associated
with the relationships between the objects. An example PNM for the basic preservation of BADC
Mesosphere-Stratosphere-Troposphere (MST) data is given below:
7
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
1.4 Release Notes
The Preservation Strategy and RepInfo Toolkit is designed to support the formulation of preservation strategy
using PNM and the implementation of a chosen preservation solution as a virtual network of Representation
Information objects stored within one or more Representation Information Registries within the Scidip-es einfrastructure.
2 Installation Guide
2.1 Overview
The Preservation Strategy/RepInfo Toolkit is developed as an Eclipse plug-in and the product is
packaged as a self-contained executable application .
2.2 Prerequisites
8
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
2.2.1 Software prerequisites
Software prerequisites respect SCIDIP-ES guidelines and include:

Java Runtime Environment 1.6 or higher
2.2.2 Hardware prerequisites
None.
2.3 OSS/COTS Installation
None.
2.4 Preservation Strategy Toolkit Installation
Unzip the archive file pst.zip to create a folder hierarchy; the PST folder includes an executable file
‘Preservation Strategy Toolkit.exe’ that launches the combined Toolkit.
2.5 Uninstallation
The PST can be removed by deleting the folder hierarchy obtained from the archive file. User project
files are stored in a ‘workspace’ folder that is specified by the user on startup; the contents of this
folder (or folders, if multiple workspaces were created) can also be deleted, if the user does not plan
to use them again in future.
3 Using SCIDIP-ES Preservation Strategy Toolkit
This section gives a brief tutorial on how to use the PST.
3.1 Running Preservation Strategy Toolkit
After unzipping the archive simple run the executable file called 'Preservation Strategy Toolkit' in the
directory in which PST was unzipped.
3.2 Workspace
9
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
After launching the application, a pop-up dialog prompts user for a workspace location. The workspace
is a folder where all projects are stored, so that everything is one place. This dialog appears every time
on PST launching and it is possible to use multiple workspaces.
It is recommended not to edit files inside workspace directory manually and only use Preservation
Strategy Toolkit to change data in it.
3.3 First Project
A preservation project may be created in several ways:

in main menu by clicking on file -> new -> Preservation Project
10
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science

by clicking on the first toolbar's icon just above file menu and selecting Preservation Project

using the right mouse click context menu on the Project Explorer view which is on the left side
of the application.
The New Project dialog appears. Set a name for a project and specify the Serializer Provider and
ontology which will be used for the new project. The tool supports of use of custom ontology that
extends the base PNM ontology. For the M18 implementation, user should use the provided default
ontology file.
11
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
After clicking on finish button you will notice that your project was added to the Project Explorer view
on the left side of the application.
Note: the RepInfo perspective requires a separate ontology file.
3.4 Ontology
Double click on the Ontology in the Project Explorer to open the Ontology Viewer.
It is not allowed to change anything in the ontology, but the editor provides a useful view to inspect
the ontology.
12
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
There are six tabs on the bottom of the view:





Objectives - shows attributes which are automatically set for every new objective created in the
project. In the default ontology there are six attributes and in most of them are only keys
predefined. The 'preservationFunction' drop down list shows a list of predefined preservation
function.
Risks - shows attributes which are automatically set for every new risk created in the project.
Decisions - shows attributes which are automatically set for every new decision created in the
project.
PNMs - shows list of default properties which are automatically added to every new PNM
object..
Dependencies or Relations - shows list of dependencies which may be used while creating
relations between PNM objects. The default Ontology restricts the relationships permitted
between different types of PNM objects.
3.5 First PNM Model
Create a new PNM model using one of three same ways available for creating a project.
In the dialog which appears type 'main' as the model name. The project should be automatically
selected; if not use the 'Choose project' button and select 'sample project'.
After creating a new model, the PNM model editor should open in the centre of the Preservation
Strategy Toolkit. If not, than you can open it by double-clicking on the model listed in the Project
Explorer.
13
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
The centre panel of the application should look like this:
The PNM model editor is a graphical editor which is a drawing canvas in which you design your
preservation network model graph. You can add new PNM objects by dragging it from a view on the
right from the editor. Drag two Digital Data Objects and place them in the model.
14
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
You can move objects by dragging them on the canvas. If you drag an object outside the canvas, the
canvas will automatically expand. You can also use the small arrow in the right bottom corner to
change the canvas size. To remove a PNM object just use right mouse click context menu and press
'Delete object' or use Main Menu -> Edit -> Delete selected PNM.
Create a relation between these objects. Move the mouse over one object and click on the arrow icon
which is on the top left corner of the object. Next move the mouse over the second object (this will
show a dotted line rooted on the first object) and click. A ‘Choose Dependency’ dialog appears and
asks you to choose a dependency type to use in this relationship.
Choose one of the dependencies and click the OK button.
15
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Removing relations is similar to removing PNM objects, you can use Main Menu -> Edit or right mouse
click context menu.
If there are unsaved changes in the object, a * is displayed next to the editor name on the dialog box
title. You can save changes by pressing CTRL + S hot key, or by clicking the Save button in the toolbar
(fourth from the left), or using main menu -> File -> Save menu item.
3.6 Editing PNM objects
Click on the bottom PNM object in the canvas. It should be marked as selected with a dotted border
around it; and the PNM Properties Editor on the right side of the application should be filled with
information about the selected object.
16
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
You can use the PNM Properties Editor to edit PNM data. Try changing name of the object to 'Source';
the name used in the canvas should be updated automatically.
Clicking on the 'Change type' button will pop up the type chooser dialog with all DigitalDataObj
subtypes specified in the ontology file.
There are two tabs in the view:


Properties - shows all properties which are specified for this object. The default Ontology
currently specifies one property 'seeAlso'.
You can add new property as a simple key and value pair and clicking on 'addnew attribute'
button below. It is permissible to delete user-defined properties, so that there is a 'delete'
button on the right of every property which is not pre-defined in the default ontology.
Risks - shows the list of all risks associated with this PNM object. We will get back to this tab
later.
3.7 Editing relations
Click on the arrow between two PNM objects in the canvas. You should have noticed that the tab in
the properties editor has changed from the PNM Properties Editor to the Relation Editor.
17
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
You can change previously-set dependency of the relation by clicking 'Change' button near
dependency name.
There are also two tabs here:


Objective - shows information about objectives set for this relation,
Decision - shows information about decisions set for this relation.
We will cover both those tabs later.
3.8 Objectives
Objectives are stored in multiple containers called Objective Sets. Create a new set using the same
method you used while creating new project.
The Objective Set editor should open:
18
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
On the top there are fields for basic set attributes: name, title, description and namespace. Namespace
will be used for every objective in this set.
On the bottom there is a list of all objectives in this set. The three buttons on the right are used to
manage objectives:



New - creates a new objective in this set and open the Objective Editor,
Delete - deletes the selected objectives,
Edit - opens the Objective Editor for the selected objectives.
19
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Create new objective (you can also use File -> New -> Objective or right mouse click context menu) and
name it 'objective a'.
Recall that there are predefined values for preservationFunction specified in the ontology; they are
listed in the combo box.
The panel on the bottom is used to add new attributes for this objective only.
Add 'objective b' to the 'first' set and create new set 'second' with two other objectives in it.
Open the 'main' PNM model and click on a relation between two objects. This brings up the relation
Editor populated with relation information.
20
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Go to the 'Objective' tab and click the 'Set' button.
21
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
The 'Choose objective' dialog appears with the list of all objectives groups in sets. Choose one of them
and click the OK button. If you want you can create new objectives using the 'Create new objective'
button.
The tab in the Relation Editor should now be filled with the objective data, its name and all attributes
in the table below. You can use three buttons here:



Set - set a different objective to use in this relation,
Clear - removes the objective from this relation (it does not remove objective from the
Objective Set),
Edit objective - open the Objective Editor.
The same options are available in the:


Main Menu in Edit menu (Set Objective, Delete Objective, Edit Objective, creating new
objective is included in Set Objective),
Right click context menu after clicking on the relation,

Toolbar
3.9 Decisions
Decisions are defined in a similar manner to objectives. The main difference is that decisions do not
have multiple decision sets, there is only one set for the entire preservation project. While creating a
new decision using a wizard you will only be asked for the project in which the decision should be
created.
Try creating a decision named 'decision 1' using one of the three methods as before.
22
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Open the Decisions editor by double clicking on 'Decisions' in project explorer:
Add a second decision named 'decision 2' using the 'New' button. A new unnamed decision will be
added to the list; double click on it or select and press the 'Edit' button to open the Decision Editor and
set its name to ‘decision 2’:
23
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
The Decision Editor is similar to the Objective editor, but the predefined values are different and taken
from the Ontology. You can of course add your own attributes using 'add new attribute' button.
Open the 'main' PNM model editor, click on a relation and change the properties tab to 'Decision'. It
should be blank, as 'Objective' tab was initially.
Use one of the following four ways to set a decision for this relation:



Click on the 'Set' button in the tab and choose a decision from the pop up dialog. You can
create a new decision by pressing 'create new objective' in the dialog;
Use Main Menu -> Edit -> Set decision and choose an existing decision or create a new one,
Use the right click context menu on the relation,

Click on the toolbar icon:
Afterwards, the 'Decision' tab should be filled with the decision information: its name and list of
attributes. There are two buttons, which work the same as in the Objective tab:


Clear – removes the decision from the relation (does not remove decision from the project),
Edit decision - opens the editor for the decision.
All set, clear, edit options are also available in the toolbar, main menu and right mouse click context
menu.
3.10 Risks
Risks are stored in one set for the entire project. Risk Set Editor and Risk Editor look and behave in the
same way as for decisions. Create new risks named 'risk 1' and 'risk 2' in the same way you created
new decisions.
Open the 'main' PNM model editor and click on one of the PNM objects in the model. The PNM
Properties Editor should appear on the right side of the Preservation Strategy Toolkit. Change the tab
to 'Risks'.
24
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
This will show a list of all risks set for this PNM. You can add new risks in several ways:




Clicking on the 'Add' button and choosing a risk from the list shown in the popup dialog. There
is a 'Create new risk' button which allows you to create a new risk and automatically add it to
the selected PNM object;
Clicking on the Main Menu -> Edit -> Add risk and selecting a risk. There is also an option to
create new risk and automatically add it to the PNM object;
Using the right click context menu after clicking on the PNM object in the model. The menu
looks the same as in the Main Menu;
Clicking on the toolbar icon
Afterwards, the 'Risks' tab should be refreshed and filled with all selected risks. There are two more
buttons in the tab:


Delete - deletes selected risks from the PNM object only unmaps the association between the
Risk and PNM objects (it does not delete the actual risk objects from the project),
Edit - opens editors for every selected risk.
All add, delete, edit options are also available in toolbar, main menu and right mouse click context
menu.
3.11 Source and exporting model
You can view the source of each editor by selecting source tab on the bottom of the editor.
25
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
It is possible to export a PNM model to one file which will include all necessary data in it. If there are
any objectives, risks or decisions used in a model they will be in the exported file. To perform export
use Main Menu -> File -> Export and select PNM Model.
Click on the 'Choose pnm model' button to select the PNM model you want to export and use 'Choose
file' to specify the location of the file to perform export. You can change the serializer provider, but this
an advanced option so should be left with default value. Press the 'Finish' button and the export will
be performed.
3.12 PNM Model editor features
The PNM Model editor enables users to save an image file of the model. To perform this use Main
Menu -> File -> Save as image option or user toolbar icon



. Three image formats are supported:
jpg
png
bmp
PNM Models may grow very large and difficult to edit. The zooming feature can be used to focus on
part of a large model. You can change zoom by using Main Menu -> View -> Zoom options, right mouse
26
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
click context menu on the blank space in the editor or toolbar icons
. You can also maximize
editor view by pressing CTRL + M; restoring the zoom level is performed with the same key action.
3.13 Working with Solutions
A PNM Model can contain Alternative nodes; the interpretation is that the parent or source PNM
object may be preserved by preserving one or more of the children (and any network on which they
depend). The Solutions interface is a mechanism that allows users to “mark” parts of a model as
Included, Excluded or Undecided. Once created, Solutions can be saved, and reloaded later.
Suppose we have the following PNM:
Normally, we would begin by saying that we want to Include the topmost or primary object in the
PNM. To do this, we select the object, and then choose “include this node and its subgraph” either
from the toolbar Solutions menu or from the right-click context menu.
27
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
When we do this, the PST marks as Included (by drawing a ring around the edge) all objects on which
the chosen object definitely depends. However, where there is an Alternative node, all objects under it
are now marked as Undecided (with a ‘?’ in the background). We could save the Solution like this, or
we could decide to include one of the alternatives. To do this, select the top object of the alternative,
and choose “include this node and its subgraph” as before.
28
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Again, all objects on which this second object definitely depends are marked as Included. Note that the
other alternative is now marked as Excluded (with a red cross). The PST does this because, as we have
chosen one alternative, the others are not mandatory. We can still decide to include some or all of the
alternatives as well: simply select the topmost object and ask to include it.
29
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Here, we have asked to include Linux, and refined the alternatives under Windows to include XP and
Win7, but not Vista.
3.13.1 Inspecting the Cost of a Solution
The PST currently provides a basc cost mechanism that aggregates the total cost valule in the chosen
solution path. Each PNM object has a numerical ‘cost’ attribute. The ‘Calculate cost of this solution’
action on the toolbar Solutions menu displays a dialog showing the total cost of (all the nodes in) the
current Solution. To compare the costs of two Solutions, you could construct the first Solution (and
perhaps save it as Solution1, say), display and make a note of its total cost; then change it (or clear the
whole Solution and create a new one), and display its cost.
30
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
We save the current solution as Linux-XP-Win7; then show its cost:
31
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Next, we add Vista to the current solution, and calculate the cost again:
32
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
If we decide this is too much, we can reload the Vista-free solution that we saved earlier.
In the M30 release, PST will offer an abstraction layer and permits user to plugin their own specific
Cost and/or Risk computation modules..
3.14 The RepInfo Toolkit
In preference to developing the RepInfo Toolkit as a separate tool, we have decided to add support for
RepInfoNetworks (RINs) to the PST’s preservation project model. This enables us to use the same
graphical editor for PNMs and for RINs, and should simplify the process of generating an initial RIN
from a PNM (or from a particular Solution for a PNM).
At present, the treatment of RINs is very similar to PNMs. The ‘RIN models’ node in the Project
Explorer is similar to ‘PNM models’, but lists RINs. New RINs can be created similarly to PNMs, etc. RINs
are opened in a RIN editor, which looks similar to the PNM Editor.
33
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
A key difference between PNM and RIN models is that they are based on different ontologies (though
some aspects are the same; for example, both contain Composite and Alternate objects). When the
PST is started, it asks for separate ontology files for the two kinds of network.
The M18 releasesupports the graphical construction of RINs in the same manner illustrated above for
the creation of PNMs. Once the Scidip-es Framework library - which mediates and controls the
communication between a RepInfo Registry and its clients - becomes available, PST/RIT should be able
to interact with the RepInfo Registry and offers further functionalities. For example, permits the tool
to select and extract fragments ofRIN, to allow users to modify them and store the changes or to
upload new objects to the Registry for sharing with other Registry users. APA, who is developing the
Framework, plans to release the Framework before M24.
4 Reference Manual
5 Troubleshooting Common Issues
Put here a troubleshooting guide with a clear list of common problems and possible causes and
solutions.
34
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Annex A.
A.1.
Figures and Tables
List of Figures
No table of figures entries found.
A.2.
List of Tables
Non è stata trovata alcuna voce dell'indice delle figure.
35
SCIDIP-ES EC Grant Agreement n°. 283401
SCIDIP-ES
SCIence Data Infrastructure for Preservation – Earth Science
Annex B.
Terminology
ACRONYM
AIP
ARK
CDMI
DOI
ES
GIS
KB
OS
OWL
PI
PNM
PURL
RDF
RepInfo
SNIA
SWKM
VM
WP
XAM
XML
DESCRIPTION
Archival Information Package
Archival Resource Key
Cloud Management Interface
Digital Object Identifier
Earth Science
Gap Identification Service
Knowledge Base
Orchestration Service
Web Ontology Language
Persistent Identifier
Preservation Network Model
Persistent Uniform Resource Locator
Resource Description Framework
Representation Information
Storage Networking Industry Association
Semantic Web Knowledge Middleware
Virtual Machine
Work Package
eXtensible Access Method
eXtensible Mark-up Language
36
SCIDIP-ES EC Grant Agreement n°. 283401