Difference between revisions of "Basic Concepts"

From Gcube Wiki
Jump to: navigation, search
(→‎Metadata)
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
== Virtual Research Environments and Community Portals ==
+
{|align=right
−
Communities of scientists and research use the gCube middleware and Grid resources to setup Virtual Research Environments (VRE) for Content exchange and collaboration. The gCube empowered VRE provides a framework of applications, services and resources to support the underlying processes of research. The purpose of a VRE is to help researchers in all disciplines by managing the increasingly complex range of tasks involved in carrying out research.
+
||__TOC__
 +
|}
  
−
Portals provide the required tools for content search, browsing, annotation, metadata management and other value added capabilities.
+
[http://www.gcube-system.org gCube] once deployed and installed implements a service that is characterised by some foundational concepts, i.e. Portal, Virtual Research Environment, Workspace and Content (Information Objects, Collections, Annotations and Metadata).
  
−
== Content, Information Objects, and Collections ==
+
== Community Portal ==
−
The Content concept encompasses the data and information that the VRE handles and makes available to its users.It is  an umbrella concept used to aggregate all forms of information objects that a VRE collects, manages, and delivers, including such objects as annotations, and metadata.  
+
This is the "web site" acting as a point of access to the set of Virtual Research Environments operated by a gCube-based Infrastructure.
 +
 
 +
== Virtual Research Environment ==
 +
This is web-based working environment conceived to provide scientists with a collaborative framework enabling them to produce and exchange results with peers around the globe in cost-efficient manner. A VRE not only offers capabilities for accessing cross-disciplinary data and knowledge, it also provides services for exploiting a multiplicity of other disparate tools and computing resources enabling innovative analysis, simulation and domain specific knowledge generation processes.
 +
 
 +
Each VRE has its own offering with respect to available content and capabilities that is tailored to serve the needs of a specific scenario.
 +
 
 +
The set of facilities that might be offered via a VRE are described in the [[Common_Functionality|remainder of this guide]].
 +
 
 +
== Workspace ==
 +
 
 +
A workspace represents a collaborative area in which users can exchange and organize information objects (items) according to their specific needs. Because of this, every user of any Virtual Research Environment is provided with this area. It resembles a classic folder-based file system. For further details, please refer to the [[Workspace|dedicated page]].
 +
 
 +
== Content: Information Objects, Collections, Annotations and Metadata ==
 +
 
 +
The Content concept encompasses the data and information that the VRE handles and makes available to its users.
 +
 
 +
It is  an umbrella concept used to aggregate all forms of information objects that a VRE collects, manages, and delivers, including such objects as annotations, and metadata.  
  
 
Content is composed of a set of information objects organized into collections.
 
Content is composed of a set of information objects organized into collections.
Line 11: Line 29:
 
The notion of Information Object represents the main entity populating the Content of a Virtual Research Environment.
 
The notion of Information Object represents the main entity populating the Content of a Virtual Research Environment.
 
An Information Object can be a complex, multimedia and multi-type object with parts, such as a sound recording associated with a set of slides, a music score, political and economic data associated with interactive simulations, a Ph.D. thesis which includes a representation of a performance, or a simulation experiment and the experimental data set adopted, a data stream representing the pool of data continuously measured by a sensor.
 
An Information Object can be a complex, multimedia and multi-type object with parts, such as a sound recording associated with a set of slides, a music score, political and economic data associated with interactive simulations, a Ph.D. thesis which includes a representation of a performance, or a simulation experiment and the experimental data set adopted, a data stream representing the pool of data continuously measured by a sensor.
 +
 +
gCube supports the management of a number of information objects including [[Time_Series|Time Series Objects]] and [[AquaMaps|AquaMaps Objects]].
  
 
Collections represent the “classic” mechanism to organize Information Objects and to provide focused views of the VRE Content. They are sets of Information Objects aggregated for some management purposes, e.g. behave as a single entity for access rights management. Another typical role assigned to collections is organizing the search space into restricted and/or topic-based sub-sets of it, thus allowing improving the search results.
 
Collections represent the “classic” mechanism to organize Information Objects and to provide focused views of the VRE Content. They are sets of Information Objects aggregated for some management purposes, e.g. behave as a single entity for access rights management. Another typical role assigned to collections is organizing the search space into restricted and/or topic-based sub-sets of it, thus allowing improving the search results.
  
−
Communities exploit any VRE collection through the features offered by the Web Portals.
+
=== Content Annotation ===
−
 
+
−
== Content Annotation ==
+
  
 
As a definition of annotation we could say that it is a written explanation or criticism or illustration that is added to an information object. Informally, annotations are comments or notes made by users in order to expose their ideas about a document.  
 
As a definition of annotation we could say that it is a written explanation or criticism or illustration that is added to an information object. Informally, annotations are comments or notes made by users in order to expose their ideas about a document.  
−
The annotations’ role in a digital library is very important since they promote collaboration between the users of the library. Through annotations, new ideas and concepts can be discussed, something which may help the understanding of an annotated object and the advance of knowledge about it.
+
The annotations’ role in a digital library is very important since they promote collaboration between the users of the library. Through annotations, new ideas and concepts can be discussed, something which may help the understanding of an annotated object and the advance of knowledge about it. For further information, please refer to the [[Common_Functionality#Annotations|dedicated page]].
 +
 
 +
=== Metadata ===
 +
 
 +
Every Information Object is equipped with metadata. The “''classic''” definition of metadata is “''data about other data''”.
 +
 
 +
Metadata are used for '''describing different aspects''' of the data they are associated with, such as the semantics, provenance, constraints, parameters, content, quality, condition, and any other characteristic that is considered important to record. These data can '''be used in different contexts''' and for a diversity of purposes; usually, they are associated with an Information Object as a means for facilitating the effective discovery, retrieval, use and management of the object.
  
−
In gCube a number of different types of annotations are provided. The first distinction has to do with the content of the annotation. So, there are text annotations and associations. By adding a text annotation a user may add a comment or a note about a gCube information object. On the other hand, associations are used in order to create conceptual links between two or more information objects.  
+
The gCube system does not impose any constraint on the metadata it supports, the system is capable to handle any piece of text. Each metadata object contains data described according to '''a specified schema and/or ontology''' in the large (any conceptualisation that defines the terms about a domain). In fact, a metadata object usually manifest in a '''metadata record''', i.e. a number of items of information where each item as well the values assigned to the item might come from one or more controlled vocabularies. An example of metadata schema is [http://dublincore.org/ Dublin Core], i.e. a vocabulary of fifteen properties for use in resource description. An excerpt of a Dublin Core metadata record in XML is as follows
  
−
Annotations can be applied to the whole document or just to a part of it. In the first occasion text annotations or associations are denoted as generic or non-anchored annotations and in the second as anchored ones.
+
...
 +
<dc:creator>Rose Bush</dc:creator>
 +
<dc:title>A Guide to Growing Roses</dc:title>
 +
<dc:description>Describes process for planting and nurturing different kinds of rose bushes.</dc:description>
 +
<dc:date>2001-01-20</dc:date>
 +
...
  
−
Generic annotations should be used when the comment or the association is referred to the whole entity. General comments, notes and additional information about an information object belong to that category.
+
However, multiple metadata schemas/ontologies exist and can be defined, each tailored or specifically designed to satisfy the needs of a well identified community.
  
−
Anchored annotations introduce a more interesting concept of annotating an object. Now, the author is able to bring in information about a specific part/ fragment of an information object. Presumably, this extends the capabilities of users as they may indicate in a visual and descriptive way which part of the information object their comment refer to.
+
Each Information Object might be equipped with an '''arbitrary number of metadata objects''' compliant with a specific schema.
  
−
== Metadata ==
+
[[Category:User's Guide]]
−
The “classic” definition of metadata is “data about data”.
+
−
Metadata are used for describing different aspects of data, such as the semantics, provenance, constraints, parameters, content, quality, condition, and other characteristic. These data can be used in different contexts and for a diversity of purposes; usually, they are associated with an Information Object as a means for facilitating the effective discovery, retrieval, use and management of the object.
+
−
There are a number of schemes for classifying metadata.
+
−
One of them consists in classifying metadata according to the specific role they play:
+
−
; Descriptive metadata : metadata that provide a mechanism for representing attributes describing and identifying an information object, such as its creator, title, publisher, date, format, list of keywords characterising its contents. The term “descriptive” is used here in a consistent, but broader sense than in “descriptive cataloguing”.
+
−
; Administrative metadata : metadata for managing an information object. This category of metadata may include metadata detailing: (i) technical characteristics of the information object, (ii) the history of the operations performed on the information object since its creation/ingest, (iii) means of access, (iv) how the authenticity and integrity of the information object can be verified.
+
−
; Preservation metadata : metadata designed to support the long term accessibility of an information object by providing information about its content, technical attributes, dependencies, management, designated community(ies) and change history. Preservation Metadata have been identified as essential for the long-term management of digital objects. The Reference Model for an Open Archival Information System (OAIS) provides an excellent overview of the role of preservation metadata in the management overtime of digital resources.
+

Latest revision as of 18:53, 11 October 2011

gCube once deployed and installed implements a service that is characterised by some foundational concepts, i.e. Portal, Virtual Research Environment, Workspace and Content (Information Objects, Collections, Annotations and Metadata).

Community Portal

This is the "web site" acting as a point of access to the set of Virtual Research Environments operated by a gCube-based Infrastructure.

Virtual Research Environment

This is web-based working environment conceived to provide scientists with a collaborative framework enabling them to produce and exchange results with peers around the globe in cost-efficient manner. A VRE not only offers capabilities for accessing cross-disciplinary data and knowledge, it also provides services for exploiting a multiplicity of other disparate tools and computing resources enabling innovative analysis, simulation and domain specific knowledge generation processes.

Each VRE has its own offering with respect to available content and capabilities that is tailored to serve the needs of a specific scenario.

The set of facilities that might be offered via a VRE are described in the remainder of this guide.

Workspace

A workspace represents a collaborative area in which users can exchange and organize information objects (items) according to their specific needs. Because of this, every user of any Virtual Research Environment is provided with this area. It resembles a classic folder-based file system. For further details, please refer to the dedicated page.

Content: Information Objects, Collections, Annotations and Metadata

The Content concept encompasses the data and information that the VRE handles and makes available to its users.

It is an umbrella concept used to aggregate all forms of information objects that a VRE collects, manages, and delivers, including such objects as annotations, and metadata.

Content is composed of a set of information objects organized into collections.

The notion of Information Object represents the main entity populating the Content of a Virtual Research Environment. An Information Object can be a complex, multimedia and multi-type object with parts, such as a sound recording associated with a set of slides, a music score, political and economic data associated with interactive simulations, a Ph.D. thesis which includes a representation of a performance, or a simulation experiment and the experimental data set adopted, a data stream representing the pool of data continuously measured by a sensor.

gCube supports the management of a number of information objects including Time Series Objects and AquaMaps Objects.

Collections represent the “classic” mechanism to organize Information Objects and to provide focused views of the VRE Content. They are sets of Information Objects aggregated for some management purposes, e.g. behave as a single entity for access rights management. Another typical role assigned to collections is organizing the search space into restricted and/or topic-based sub-sets of it, thus allowing improving the search results.

Content Annotation

As a definition of annotation we could say that it is a written explanation or criticism or illustration that is added to an information object. Informally, annotations are comments or notes made by users in order to expose their ideas about a document. The annotations’ role in a digital library is very important since they promote collaboration between the users of the library. Through annotations, new ideas and concepts can be discussed, something which may help the understanding of an annotated object and the advance of knowledge about it. For further information, please refer to the dedicated page.

Metadata

Every Information Object is equipped with metadata. The “classic” definition of metadata is “data about other data”.

Metadata are used for describing different aspects of the data they are associated with, such as the semantics, provenance, constraints, parameters, content, quality, condition, and any other characteristic that is considered important to record. These data can be used in different contexts and for a diversity of purposes; usually, they are associated with an Information Object as a means for facilitating the effective discovery, retrieval, use and management of the object.

The gCube system does not impose any constraint on the metadata it supports, the system is capable to handle any piece of text. Each metadata object contains data described according to a specified schema and/or ontology in the large (any conceptualisation that defines the terms about a domain). In fact, a metadata object usually manifest in a metadata record, i.e. a number of items of information where each item as well the values assigned to the item might come from one or more controlled vocabularies. An example of metadata schema is Dublin Core, i.e. a vocabulary of fifteen properties for use in resource description. An excerpt of a Dublin Core metadata record in XML is as follows 

...
<dc:creator>Rose Bush</dc:creator>
<dc:title>A Guide to Growing Roses</dc:title>
<dc:description>Describes process for planting and nurturing different kinds of rose bushes.</dc:description> 
<dc:date>2001-01-20</dc:date>
...

However, multiple metadata schemas/ontologies exist and can be defined, each tailored or specifically designed to satisfy the needs of a well identified community.

Each Information Object might be equipped with an arbitrary number of metadata objects compliant with a specific schema.

Retrieved from "https://wiki.gcube-system.org/index.php?title=Basic_Concepts&oldid=12687"