Difference between revisions of "GCube Object Metadata"

From Gcube Wiki
Jump to: navigation, search
m (Created page with '{| align="right" ||__TOC__ |} This page is intended to provide its users with a detailed list of metadata-related conventions and policies governing the production of metadata as…')
 
 
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:TO BE REVISED]]
 +
 
{| align="right"
 
{| align="right"
 
||__TOC__
 
||__TOC__
Line 4: Line 6:
 
This page is intended to provide its users with a detailed list of metadata-related conventions and policies governing the production of metadata associated with these objects.  
 
This page is intended to provide its users with a detailed list of metadata-related conventions and policies governing the production of metadata associated with these objects.  
  
−
Metadata can be produced according to diverse metadata formats / schema. Thus for each Object type, in the following it is reported  
+
Metadata can be produced according to diverse metadata formats / schema. Thus for each Object type, in the following it is reported a brief description of the metadata associated with it in diverse schema.
 +
 
 +
== Global Policies ==
 +
 
 +
This section contains policies that applies to the gCube objects independently from their typologies.
 +
 
 +
=== Attribution Policies ===
 +
 
 +
Every object produced via gCube / iMarine should be annotated with the following sentence: "...". 
 +
 
 +
=== Data Provenance Policies ===
 +
 
 +
Every time a gCube object is produced by relying on pre-existing data, it should be annotated with a provenance record listing the exploited data and their provider according to well known statements -- if available. Available statements are reported below:
 +
* <add here the OBIS statement>;
 +
 
 +
In addition to that, the provenance record might include the list of processes used to produce the gCube object. Available statements are reported below:
 +
* <add here the statistical service statement>;
 +
* <add here the AquaMaps "service" statement>;
 +
 
 +
== AquaMaps Objects ==
 +
 
 +
These objects ...
 +
 
 +
=== Conceptual schema ===
 +
 
 +
* who produces the object, who publishes the object;
 +
* how the object has been produced;
 +
* what the object is about;
 +
* disseminate all the manifestations of the object;
 +
 
 +
=== ISO 19115 Metadata ===
 +
 
 +
MD_Metadata section
 +
* '''hierarchyLevel''': dataset
 +
* '''language''': English
 +
* '''Contacts''': three roles are envisaged, i.e. author, publisher and resourceProvider;
 +
** '''author''': the end user that has created the object;
 +
** '''publisher''': the iMarine Consortium;
 +
*** individualName: iMarine Consortium;
 +
*** organisationName: iMarine.eu;
 +
*** positionName: N/A;
 +
*** contactInfo.onlineResource.linkage: info@i-marine.eu | support@imarine.research-infrastructures.eu;
 +
** '''resourceProvider''': the iMarine Consortium; ...
 +
 
 +
MD_DataIdentification section
 +
* '''title''': <species name> Species Distribution Map
 +
* '''abstract''':
 +
*: This <species name> Species Distribution Map has been produced by the AquaMaps methodology <cite>.
 +
*: In particular, it has been produced by relying on the iMarine (www.i-marine.eu) facilities supporting Species Distribution Maps production implementing this methodology. This map has been produced by using <report here details on the dataset and algorithm>.
 +
* '''credits''':
 +
*: This layer has been produced by iMarine (www.i-marine.eu). iMarine (283644) is funded by the European Commission under Framework Programme 7
 +
* '''purpose''':
 +
*: The aim of this <species name> Species Distribution Map is to provide its users with a model-based map displaying a prediction of species distributions based on occurrence records.
 +
* '''descriptiveKeywords.keyword''': AquaMaps; Species Distribution Map; <species name>;
 +
* '''topicCatergory''': biota;
 +
* '''language''': English
 +
* '''extent''': ...
 +
 
 +
MD_Constraints section
 +
* '''useLimitation''':
 +
* '''accessConstraints''': ???
 +
* '''useConstraints''': ???
 +
 
 +
MD_Distribution section: list ALL the web-based protocols for accessing this map including WCS, WFS, WMS;
 +
 
 +
DQ_DataQuality section
 +
* scope: dataset
 +
* lineage.statement:
 +
*: This map was obtained by the iMarine (www.i-marine.eu) facilities supporting Species Distribution Maps production. 
 +
Original input data had been obtained ...
 +
Original methodology had been developed by ...
 +
 
 +
== Tree Objects ==
 +
 
 +
A number of objects are exposed via Tree objects, i.e. objects managed by the gCube [[Tree-Based_Access | Tree-based Access]] facilities.
 +
 
 +
=== OAI-PMH Tree Objects ===
 +
These objects stem from:
 +
* the harvesting of resources from a data provider by relying on the OAI-PMH protocol
 +
* the representation of the harvested resources via Tree objects. 
 +
 
 +
A detailed description of these objects is available at [[OAITMPlugin#Tree_model | this page]].
  
−
== AquaMaps Objects ==  
+
=== Species Data Discovery Tree Objects ===
 +
These objects stem from:
 +
* the materialisation of data objects that can be retrieved via the Species Product Discovery service
 +
* the representation of the materialised objects via Tree objects. 
  
−
== OAI-PMH Tree Objects ==
+
A detailed description of these objects is available at [[SpeciesTMPlugin | this page]].  
−
These objects stem from the harvesting of resources from a data provider by relying on the OAI-PMH protocol.  
+
  
−
A detailed description of these objects is available at the [[OAITMPlugin#Tree_model | following page]].  
+
=== FishFinder Tree Objects ===
 +
These objects stem from:
 +
* the materialisation of data objects that can be retrieved via the '''FAO Fish Finder''' service
 +
* the representation of the materialised objects via Tree objects.
  
−
== Species Data Discovery Tree Objects ==
+
A detailed description of these objects is available at [[FishFinderTMPlugin | this page]].
  
 
== Time Series Objects ==
 
== Time Series Objects ==
 +
These objects ...

Latest revision as of 19:48, 14 July 2016


This page is intended to provide its users with a detailed list of metadata-related conventions and policies governing the production of metadata associated with these objects.

Metadata can be produced according to diverse metadata formats / schema. Thus for each Object type, in the following it is reported a brief description of the metadata associated with it in diverse schema.

Global Policies

This section contains policies that applies to the gCube objects independently from their typologies.

Attribution Policies

Every object produced via gCube / iMarine should be annotated with the following sentence: "...".

Data Provenance Policies

Every time a gCube object is produced by relying on pre-existing data, it should be annotated with a provenance record listing the exploited data and their provider according to well known statements -- if available. Available statements are reported below:

  • <add here the OBIS statement>;

In addition to that, the provenance record might include the list of processes used to produce the gCube object. Available statements are reported below:

  • <add here the statistical service statement>;
  • <add here the AquaMaps "service" statement>;

AquaMaps Objects

These objects ...

Conceptual schema

  • who produces the object, who publishes the object;
  • how the object has been produced;
  • what the object is about;
  • disseminate all the manifestations of the object;

ISO 19115 Metadata

MD_Metadata section

  • hierarchyLevel: dataset
  • language: English
  • Contacts: three roles are envisaged, i.e. author, publisher and resourceProvider;
    • author: the end user that has created the object;
    • publisher: the iMarine Consortium;
      • individualName: iMarine Consortium;
      • organisationName: iMarine.eu;
      • positionName: N/A;
      • contactInfo.onlineResource.linkage: info@i-marine.eu | support@imarine.research-infrastructures.eu;
    • resourceProvider: the iMarine Consortium; ...

MD_DataIdentification section

  • title: <species name> Species Distribution Map
  • abstract:
    This <species name> Species Distribution Map has been produced by the AquaMaps methodology .
    In particular, it has been produced by relying on the iMarine (www.i-marine.eu) facilities supporting Species Distribution Maps production implementing this methodology. This map has been produced by using <report here details on the dataset and algorithm>.
  • credits:
    This layer has been produced by iMarine (www.i-marine.eu). iMarine (283644) is funded by the European Commission under Framework Programme 7
  • purpose:
    The aim of this <species name> Species Distribution Map is to provide its users with a model-based map displaying a prediction of species distributions based on occurrence records.
  • descriptiveKeywords.keyword: AquaMaps; Species Distribution Map; <species name>;
  • topicCatergory: biota;
  • language: English
  • extent: ...

MD_Constraints section

  • useLimitation:
  • accessConstraints: ???
  • useConstraints: ???

MD_Distribution section: list ALL the web-based protocols for accessing this map including WCS, WFS, WMS;

DQ_DataQuality section

  • scope: dataset
  • lineage.statement:
    This map was obtained by the iMarine (www.i-marine.eu) facilities supporting Species Distribution Maps production.

Original input data had been obtained ... Original methodology had been developed by ...

Tree Objects

A number of objects are exposed via Tree objects, i.e. objects managed by the gCube Tree-based Access facilities.

OAI-PMH Tree Objects

These objects stem from:

  • the harvesting of resources from a data provider by relying on the OAI-PMH protocol
  • the representation of the harvested resources via Tree objects.

A detailed description of these objects is available at this page.

Species Data Discovery Tree Objects

These objects stem from:

  • the materialisation of data objects that can be retrieved via the Species Product Discovery service
  • the representation of the materialised objects via Tree objects.

A detailed description of these objects is available at this page.

FishFinder Tree Objects

These objects stem from:

  • the materialisation of data objects that can be retrieved via the FAO Fish Finder service
  • the representation of the materialised objects via Tree objects.

A detailed description of these objects is available at this page.

Time Series Objects

These objects ...

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