Changes
On April 12, 2022 at 12:34:18 PM UTC,
-
Added the following fields to HELCOM Map and Data Service (HELCOM MADS)
- Database Level with value Project
- FIAR with value Yes
- Source of Data Policy with value Own
- Region with value Arctic
- Opening Degree with value Open
- Theme with value Marine
- Host Institute with value HELCOM SCALE project
- Organizer with value Helsinki Commission (HELCOM)
f | 1 | { | f | 1 | { |
2 | "author": "", | 2 | "author": "", | ||
3 | "author_email": "", | 3 | "author_email": "", | ||
4 | "creator_user_id": "2e9fa41b-0394-4070-98d0-205f79d5738b", | 4 | "creator_user_id": "2e9fa41b-0394-4070-98d0-205f79d5738b", | ||
5 | "extras": [ | 5 | "extras": [ | ||
6 | { | 6 | { | ||
7 | "key": "Country", | 7 | "key": "Country", | ||
8 | "value": "International" | 8 | "value": "International" | ||
9 | }, | 9 | }, | ||
10 | { | 10 | { | ||
11 | "key": "Data Management ", | 11 | "key": "Data Management ", | ||
12 | "value": "\"Furthermore, data harvesting systems based on | 12 | "value": "\"Furthermore, data harvesting systems based on | ||
13 | Application Programming Interfaces (APIs) will be developed with the | 13 | Application Programming Interfaces (APIs) will be developed with the | ||
14 | aim to automatically integrate national datasets into a combined and | 14 | aim to automatically integrate national datasets into a combined and | ||
15 | harmonised regional dataset. As a result of the project, harmonised | 15 | harmonised regional dataset. As a result of the project, harmonised | ||
16 | and quality assured pan-Baltic monitoring data that is usable for | 16 | and quality assured pan-Baltic monitoring data that is usable for | ||
17 | research purposes, environmental assessments, sustainable maritime | 17 | research purposes, environmental assessments, sustainable maritime | ||
18 | spatial planning and blue growth will be made accessible. | 18 | spatial planning and blue growth will be made accessible. | ||
19 | Furthermore, Baltic Data Flows will provide tools for creating and | 19 | Furthermore, Baltic Data Flows will provide tools for creating and | ||
20 | disseminating more general data products suitable for communicating | 20 | disseminating more general data products suitable for communicating | ||
21 | status of marine environment to the general public and | 21 | status of marine environment to the general public and | ||
22 | decision-makers.\"" | 22 | decision-makers.\"" | ||
23 | }, | 23 | }, | ||
24 | { | 24 | { | ||
25 | "key": "Data Policy", | 25 | "key": "Data Policy", | ||
26 | "value": "\"More specifically, Baltic Data Flows will: Increase | 26 | "value": "\"More specifically, Baltic Data Flows will: Increase | ||
27 | capacity for national competent authorities for harmonising and | 27 | capacity for national competent authorities for harmonising and | ||
28 | sharing collected environmental monitoring data on the Baltic Sea by | 28 | sharing collected environmental monitoring data on the Baltic Sea by | ||
29 | supporting development of database platforms; Further develop and | 29 | supporting development of database platforms; Further develop and | ||
30 | implement a system for harvesting environmental datasets from national | 30 | implement a system for harvesting environmental datasets from national | ||
31 | sources to regionally harmonised datasets by extending the piloted | 31 | sources to regionally harmonised datasets by extending the piloted | ||
32 | harvested system developed between the project partners ICES and SMHI; | 32 | harvested system developed between the project partners ICES and SMHI; | ||
33 | Provide support to regional harmonisation and create data products | 33 | Provide support to regional harmonisation and create data products | ||
34 | supporting environmental assessments by further defining the data | 34 | supporting environmental assessments by further defining the data | ||
35 | needs and existing reporting formats; Make harmonised datasets | 35 | needs and existing reporting formats; Make harmonised datasets | ||
36 | accessible and discoverable in the European Data Portal (EDP) by using | 36 | accessible and discoverable in the European Data Portal (EDP) by using | ||
37 | DCAT-AP compliant metadata catalogues. Baltic Data Flows will improve | 37 | DCAT-AP compliant metadata catalogues. Baltic Data Flows will improve | ||
38 | the capacity building of the national environmental data hosting | 38 | the capacity building of the national environmental data hosting | ||
39 | organisations and providers of the consortium, in terms of quality | 39 | organisations and providers of the consortium, in terms of quality | ||
40 | control and solutions to make harmonised environmental data available. | 40 | control and solutions to make harmonised environmental data available. | ||
41 | Members of the consortium will build and enhance their ICT | 41 | Members of the consortium will build and enhance their ICT | ||
42 | infrastructure to support better the data sharing process. In doing | 42 | infrastructure to support better the data sharing process. In doing | ||
43 | so, the FAIR principles will be followed (data should be Findable, | 43 | so, the FAIR principles will be followed (data should be Findable, | ||
44 | Accessible, Interoperable and Reusable). Furthermore, data harvesting | 44 | Accessible, Interoperable and Reusable). Furthermore, data harvesting | ||
45 | systems based on Application Programming Interfaces (APIs) will be | 45 | systems based on Application Programming Interfaces (APIs) will be | ||
46 | developed with the aim to automatically integrate national datasets | 46 | developed with the aim to automatically integrate national datasets | ||
47 | into a combined and harmonised regional dataset. As a result of the | 47 | into a combined and harmonised regional dataset. As a result of the | ||
48 | project, harmonised and quality assured pan-Baltic monitoring data | 48 | project, harmonised and quality assured pan-Baltic monitoring data | ||
49 | that is usable for research purposes, environmental assessments, | 49 | that is usable for research purposes, environmental assessments, | ||
50 | sustainable maritime spatial planning and blue growth will be made | 50 | sustainable maritime spatial planning and blue growth will be made | ||
51 | accessible. Furthermore, Baltic Data Flows will provide tools for | 51 | accessible. Furthermore, Baltic Data Flows will provide tools for | ||
52 | creating and disseminating more general data products suitable for | 52 | creating and disseminating more general data products suitable for | ||
53 | communicating status of marine environment to the general public and | 53 | communicating status of marine environment to the general public and | ||
54 | decision-makers.\"" | 54 | decision-makers.\"" | ||
55 | }, | 55 | }, | ||
56 | { | 56 | { | ||
57 | "key": "Data Sharing Principle", | 57 | "key": "Data Sharing Principle", | ||
58 | "value": "\"Make harmonised datasets accessible and discoverable | 58 | "value": "\"Make harmonised datasets accessible and discoverable | ||
59 | in the European Data Portal (EDP) by using DCAT-AP compliant metadata | 59 | in the European Data Portal (EDP) by using DCAT-AP compliant metadata | ||
60 | catalogues. Baltic Data Flows will improve the capacity building of | 60 | catalogues. Baltic Data Flows will improve the capacity building of | ||
61 | the national environmental data hosting organisations and providers of | 61 | the national environmental data hosting organisations and providers of | ||
62 | the consortium, in terms of quality control and solutions to make | 62 | the consortium, in terms of quality control and solutions to make | ||
63 | harmonised environmental data available. Members of the consortium | 63 | harmonised environmental data available. Members of the consortium | ||
64 | will build and enhance their ICT infrastructure to support better the | 64 | will build and enhance their ICT infrastructure to support better the | ||
65 | data sharing process. In doing so, the FAIR principles will be | 65 | data sharing process. In doing so, the FAIR principles will be | ||
66 | followed (data should be Findable, Accessible, Interoperable and | 66 | followed (data should be Findable, Accessible, Interoperable and | ||
67 | Reusable).\"" | 67 | Reusable).\"" | ||
n | n | 68 | }, | ||
69 | { | ||||
70 | "key": "Database Level", | ||||
71 | "value": "Project" | ||||
72 | }, | ||||
73 | { | ||||
74 | "key": "FIAR", | ||||
75 | "value": "Yes" | ||||
76 | }, | ||||
77 | { | ||||
78 | "key": "Host Institute", | ||||
79 | "value": "HELCOM SCALE project" | ||||
80 | }, | ||||
81 | { | ||||
82 | "key": "Opening Degree", | ||||
83 | "value": "Open" | ||||
84 | }, | ||||
85 | { | ||||
86 | "key": "Organizer", | ||||
87 | "value": "Helsinki Commission (HELCOM) " | ||||
88 | }, | ||||
89 | { | ||||
90 | "key": "Region", | ||||
91 | "value": "Arctic" | ||||
92 | }, | ||||
93 | { | ||||
94 | "key": "Source of Data Policy", | ||||
95 | "value": "Own" | ||||
96 | }, | ||||
97 | { | ||||
98 | "key": "Theme", | ||||
99 | "value": "Marine" | ||||
68 | } | 100 | } | ||
69 | ], | 101 | ], | ||
70 | "groups": [ | 102 | "groups": [ | ||
71 | { | 103 | { | ||
72 | "description": "Inventory of Database for Earth Three Poles", | 104 | "description": "Inventory of Database for Earth Three Poles", | ||
73 | "display_name": "An Inventory of Database for Earth Three | 105 | "display_name": "An Inventory of Database for Earth Three | ||
74 | Poles", | 106 | Poles", | ||
75 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | 107 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | ||
76 | "image_display_url": | 108 | "image_display_url": | ||
77 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | 109 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | ||
78 | "name": "inventury-of-database-for-earth-three-poles", | 110 | "name": "inventury-of-database-for-earth-three-poles", | ||
79 | "title": "An Inventory of Database for Earth Three Poles" | 111 | "title": "An Inventory of Database for Earth Three Poles" | ||
80 | } | 112 | } | ||
81 | ], | 113 | ], | ||
82 | "id": "ff87e950-a79d-4947-bc72-83969625717f", | 114 | "id": "ff87e950-a79d-4947-bc72-83969625717f", | ||
83 | "isopen": false, | 115 | "isopen": false, | ||
84 | "license_id": "", | 116 | "license_id": "", | ||
85 | "license_title": "", | 117 | "license_title": "", | ||
86 | "maintainer": "", | 118 | "maintainer": "", | ||
87 | "maintainer_email": "", | 119 | "maintainer_email": "", | ||
88 | "metadata_created": "2022-04-06T06:48:03.016313", | 120 | "metadata_created": "2022-04-06T06:48:03.016313", | ||
t | 89 | "metadata_modified": "2022-04-08T10:00:02.112893", | t | 121 | "metadata_modified": "2022-04-12T12:34:18.199763", |
90 | "name": "helcom-map-and-data-service-helcom-mads", | 122 | "name": "helcom-map-and-data-service-helcom-mads", | ||
91 | "notes": "\"HELCOM Map and Data Service (HELCOM MADS) contains all | 123 | "notes": "\"HELCOM Map and Data Service (HELCOM MADS) contains all | ||
92 | geospatial data relevant for HELCOM work from status assessments to | 124 | geospatial data relevant for HELCOM work from status assessments to | ||
93 | shipping density maps. The HELCOM Map and Data service contains | 125 | shipping density maps. The HELCOM Map and Data service contains | ||
94 | various functionalities for viewing datasets, for example, identify | 126 | various functionalities for viewing datasets, for example, identify | ||
95 | features and attribute table functionalities.\r\n\r\nThe service is | 127 | features and attribute table functionalities.\r\n\r\nThe service is | ||
96 | linked with HELCOM Metadata catalogue to view metadata of each dataset | 128 | linked with HELCOM Metadata catalogue to view metadata of each dataset | ||
97 | and to enable download.\"\r\n", | 129 | and to enable download.\"\r\n", | ||
98 | "num_resources": 1, | 130 | "num_resources": 1, | ||
99 | "num_tags": 0, | 131 | "num_tags": 0, | ||
100 | "organization": { | 132 | "organization": { | ||
101 | "approval_status": "approved", | 133 | "approval_status": "approved", | ||
102 | "created": "2020-04-30T11:11:08.802657", | 134 | "created": "2020-04-30T11:11:08.802657", | ||
103 | "description": "Aerospace Information Research Institute (AIR) | 135 | "description": "Aerospace Information Research Institute (AIR) | ||
104 | under the Chinese Academy of Sciences (CAS) was established in July | 136 | under the Chinese Academy of Sciences (CAS) was established in July | ||
105 | 2017, following the approval for consolidation of three CAS | 137 | 2017, following the approval for consolidation of three CAS | ||
106 | institutes: the Institute of Electronics (IECAS), the Institute of | 138 | institutes: the Institute of Electronics (IECAS), the Institute of | ||
107 | Remote Sensing and Digital Earth (RADI), and the Academy of | 139 | Remote Sensing and Digital Earth (RADI), and the Academy of | ||
108 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | 140 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | ||
109 | the outcome of CAS efforts towards reformation of its R&D system to | 141 | the outcome of CAS efforts towards reformation of its R&D system to | ||
110 | meet future R&D challenges and to better meet the national demands.", | 142 | meet future R&D challenges and to better meet the national demands.", | ||
111 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 143 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
112 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | 144 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | ||
113 | "is_organization": true, | 145 | "is_organization": true, | ||
114 | "name": "air", | 146 | "name": "air", | ||
115 | "state": "active", | 147 | "state": "active", | ||
116 | "title": "Aerospace Information Research Institute, CAS", | 148 | "title": "Aerospace Information Research Institute, CAS", | ||
117 | "type": "organization" | 149 | "type": "organization" | ||
118 | }, | 150 | }, | ||
119 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 151 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
120 | "private": false, | 152 | "private": false, | ||
121 | "relationships_as_object": [], | 153 | "relationships_as_object": [], | ||
122 | "relationships_as_subject": [], | 154 | "relationships_as_subject": [], | ||
123 | "resources": [ | 155 | "resources": [ | ||
124 | { | 156 | { | ||
125 | "cache_last_updated": null, | 157 | "cache_last_updated": null, | ||
126 | "cache_url": null, | 158 | "cache_url": null, | ||
127 | "created": "2022-04-06T06:48:20.163006", | 159 | "created": "2022-04-06T06:48:20.163006", | ||
128 | "datastore_active": false, | 160 | "datastore_active": false, | ||
129 | "description": "\"HELCOM Map and Data Service (HELCOM MADS) | 161 | "description": "\"HELCOM Map and Data Service (HELCOM MADS) | ||
130 | contains all geospatial data relevant for HELCOM work from status | 162 | contains all geospatial data relevant for HELCOM work from status | ||
131 | assessments to shipping density maps. The HELCOM Map and Data service | 163 | assessments to shipping density maps. The HELCOM Map and Data service | ||
132 | contains various functionalities for viewing datasets, for example, | 164 | contains various functionalities for viewing datasets, for example, | ||
133 | identify features and attribute table functionalities.\r\n\r\nThe | 165 | identify features and attribute table functionalities.\r\n\r\nThe | ||
134 | service is linked with HELCOM Metadata catalogue to view metadata of | 166 | service is linked with HELCOM Metadata catalogue to view metadata of | ||
135 | each dataset and to enable download.\"\r\n", | 167 | each dataset and to enable download.\"\r\n", | ||
136 | "format": "HTML", | 168 | "format": "HTML", | ||
137 | "hash": "", | 169 | "hash": "", | ||
138 | "id": "3c41a39e-5f4b-4d73-88de-2e226e6173cf", | 170 | "id": "3c41a39e-5f4b-4d73-88de-2e226e6173cf", | ||
139 | "last_modified": null, | 171 | "last_modified": null, | ||
140 | "metadata_modified": "2022-04-06T06:48:20.348221", | 172 | "metadata_modified": "2022-04-06T06:48:20.348221", | ||
141 | "mimetype": "text/html", | 173 | "mimetype": "text/html", | ||
142 | "mimetype_inner": null, | 174 | "mimetype_inner": null, | ||
143 | "name": "HELCOM Map and Data Service (HELCOM MADS) ", | 175 | "name": "HELCOM Map and Data Service (HELCOM MADS) ", | ||
144 | "package_id": "ff87e950-a79d-4947-bc72-83969625717f", | 176 | "package_id": "ff87e950-a79d-4947-bc72-83969625717f", | ||
145 | "position": 0, | 177 | "position": 0, | ||
146 | "resource_type": null, | 178 | "resource_type": null, | ||
147 | "size": null, | 179 | "size": null, | ||
148 | "state": "active", | 180 | "state": "active", | ||
149 | "url": "https://maps.helcom.fi/website/mapservice/index.html", | 181 | "url": "https://maps.helcom.fi/website/mapservice/index.html", | ||
150 | "url_type": null | 182 | "url_type": null | ||
151 | } | 183 | } | ||
152 | ], | 184 | ], | ||
153 | "state": "active", | 185 | "state": "active", | ||
154 | "tags": [], | 186 | "tags": [], | ||
155 | "title": "HELCOM Map and Data Service (HELCOM MADS)", | 187 | "title": "HELCOM Map and Data Service (HELCOM MADS)", | ||
156 | "type": "dataset", | 188 | "type": "dataset", | ||
157 | "url": "https://maps.helcom.fi/website/mapservice/index.html", | 189 | "url": "https://maps.helcom.fi/website/mapservice/index.html", | ||
158 | "version": "" | 190 | "version": "" | ||
159 | } | 191 | } |