<Insert here a brief introduction to this topic>
<Introduction to the questions asked pertaining to general / pervasive requirements and setting the context of topic-specific requirements. Collation and integration of any pertinent properties and requirements that are consistent across all of the research infrastructures addressed by ENVRIplus requirements gathering.>
<insert here who is responsible for steering and editing this page. But they need to get their go-betweens to agree they have covered the points, e.g. for General requirements>
with help from go betweens and others he co-opts.
<The overview and summary should be written (integrated and distilled) by the topic leader(s), highlighting commonalities and reporting significant variations. It should be refined and agreed by the go-betweens who contributed to this topic. In particular, they should check that critical points have not been missed and that a balance has been attained.>
The following RIs contributed to developing cataloguing requirements
<Delete from the following list any that were not able to contribute on this topic>
<Add an interest inducing sentence or two, to persuade readers to look at the contribution by a particular RI. e.g., What aspect of the summary of requirements, or the special cases, came from this RI. Check with RIs that they feel they are correctly presented.>
ACTRIS: <e.g., This RI ... and therefore has XYZ <Topic> requirements, with a particular empahsis on ...>
Relies on 3 major databases:
Has to comply with WMO Information System to integrate GEOSS.
AnaEE:
implements standards for metadata harmonization:
Relies on following components:
ELIXIR:
Interested in sample description.
Interested in lab equipment cataloguing and activities scheduling.
For paper publication: Web Of Knowledge, Scopus
Standards: GBIF and Darwin-Core
EMSO:
Interested in platform, sensor registry management.
Uses Pangaea, SeaDataNet, Copernicus Marine for data management.
SWE, ISO19XXX standards are used
EPOS:
CERIF as a internal system for every catalogue aspects.
Metadata standards through CKAN and eGMS services (e.g. dublin-core).
Euro-ARGO:
Central system (JCOMMOPS) for platforms, deployment descriptions.
complies with SWE and ISO191XX standards thrgouh seadatanet.
EUROFLEETS2:
complies with SWE and ISO191XX standards thrgouh seadatanet.
ESONET: see EMSO
EUROGOOS:
Coordinates RI above network level, does not coordinate inside networks.
FIXO3: see EMSO
Complies with SWE and ISO19XXX (geonetwork) through AERIS portal.
INSPIRE compliance required
ICOS:
One single integrated Information System provides everything for catalogues
INTERACT:
Tilda component uses CKAN for dataset description
openAIRE is used to publish
INSPIRE compliance required
CKAN is used
ISO191XX, OAI-PMH, DIF and Dublin-Core standard are used
JERICO: see SeaDataNet
LTER:
SEADATANET:
SIOS: