30 likes | 156 Vues
The CORDEX Data Federation Building System aims to store CORDEX data conforming to metadata conventions, with data nodes like DMI, DKRZ, BADC, and SMHI acting as key providers. It emphasizes data protection through authorization services, with portals offering search functionality, data shopping baskets, user registration, and more. The system facilitates data access and generation of Thredds Metadata, supporting efficient download and openDAP subsetting functionalities.
E N D
Overall systemidea … • Data nodes: • Store CORDEX data • dataconformstometadataconventions • filenaming: C-DRS • NetCDFheaderconventions (CF ..) • ExposeThreddscatalogs • Providedataaccess (http, + ..?..) • Sites actingasdatanodes: • DMI (centralcite) • DKRZ • BADC • SMHI ?,..?.. • Data protection (Authorization ..) • Authorizationservice • MyProxycredentialservice • OpenIDservice • http/cookychaininig • Portal(s): • Data searchfunctionality, • „Data shoppingbasket“ • User registration, help,.. • AAI • Sites runningportals: • DMI ? • IS-ENES / DKRZ ?
.. actions , effort .. Min. datanode: • C-DRS agreement, NetCDF Header conventions, tables… • („C-DRS-checkerlite“ to check conformance .. !?) • C-DRS-libtogenerateconsistentdirectorystructure • Configurationof ESGF datanodeto • GenerateThreddsMetadata • Allowdownload, opendapsubsetting … Min. portal: • ThreddsMetadataharvester + search • Generatedownloadscripts (sec ??)