Changes
On April 5, 2022 at 7:03:42 AM UTC, seanh:
-
No fields were updated. See the metadata diff for more details.
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": "Data Management ", | 7 | "key": "Data Management ", | ||
8 | "value": "\"The collective term \u2018CCAMLR data\u2019 refers | 8 | "value": "\"The collective term \u2018CCAMLR data\u2019 refers | ||
9 | to data which are submitted to the Secretariat by CCAMLR Members to | 9 | to data which are submitted to the Secretariat by CCAMLR Members to | ||
10 | support the policy, scientific and administrative work of the | 10 | support the policy, scientific and administrative work of the | ||
11 | Commission and Scientific Committee and to give effect to Article XX | 11 | Commission and Scientific Committee and to give effect to Article XX | ||
12 | of the Convention. CCAMLR data may also be submitted by | 12 | of the Convention. CCAMLR data may also be submitted by | ||
13 | Non-Contracting Parties participating in CCAMLR activities such as the | 13 | Non-Contracting Parties participating in CCAMLR activities such as the | ||
14 | Catch Documentation Scheme. The CCAMLR Secretariat\u2019s data | 14 | Catch Documentation Scheme. The CCAMLR Secretariat\u2019s data | ||
15 | management systems provide the secure environment in which CCAMLR data | 15 | management systems provide the secure environment in which CCAMLR data | ||
16 | are managed and made available to the CCAMLR community and other users | 16 | are managed and made available to the CCAMLR community and other users | ||
17 | in accordance with the rules for access and use of CCAMLR data | 17 | in accordance with the rules for access and use of CCAMLR data | ||
18 | (https://www.ccamlr.org/en/data/access-and-use-ccamlr-data). These | 18 | (https://www.ccamlr.org/en/data/access-and-use-ccamlr-data). These | ||
19 | data include structured data (data reported in fixed fields within a | 19 | data include structured data (data reported in fixed fields within a | ||
20 | record or file, e.g. an observer logbook) and unstructured information | 20 | record or file, e.g. an observer logbook) and unstructured information | ||
21 | (data or information that are not reported in a traditional row-column | 21 | (data or information that are not reported in a traditional row-column | ||
22 | format, e.g. a document1). The Secretariat\u2019s governance of | 22 | format, e.g. a document1). The Secretariat\u2019s governance of | ||
23 | CCAMLR data aspires to best practice and international standards to | 23 | CCAMLR data aspires to best practice and international standards to | ||
24 | improve the quality and availability of data and information, ensure | 24 | improve the quality and availability of data and information, ensure | ||
25 | the confidentiality and integrity of data and information, promote the | 25 | the confidentiality and integrity of data and information, promote the | ||
26 | integration of data and information, support effective business | 26 | integration of data and information, support effective business | ||
27 | processes and informed decision making through accurate data, and | 27 | processes and informed decision making through accurate data, and | ||
28 | reduce Secretariat costs through efficient management of data and | 28 | reduce Secretariat costs through efficient management of data and | ||
29 | information. As requested by WG-SAM-16, this paper provides | 29 | information. As requested by WG-SAM-16, this paper provides | ||
30 | background, key achievements to date and plans for on-going work | 30 | background, key achievements to date and plans for on-going work | ||
31 | associated with the redevelopment of CCAMLR\u2019s data management | 31 | associated with the redevelopment of CCAMLR\u2019s data management | ||
32 | systems and CCAMLR databases. It updates Members on key tasks | 32 | systems and CCAMLR databases. It updates Members on key tasks | ||
33 | associated with transition to the data warehouse, data extracts and | 33 | associated with transition to the data warehouse, data extracts and | ||
34 | metadata, and the establishment of a data management group, and | 34 | metadata, and the establishment of a data management group, and | ||
35 | outlines the anticipated changes, and associated benefits, for users | 35 | outlines the anticipated changes, and associated benefits, for users | ||
36 | of CCAMLR data. The user community can expect improvements in data | 36 | of CCAMLR data. The user community can expect improvements in data | ||
37 | quality assurance2 (DQA), database documentation and ease of use as | 37 | quality assurance2 (DQA), database documentation and ease of use as | ||
38 | the new system is progressively rolled out, including increased: | 38 | the new system is progressively rolled out, including increased: | ||
39 | Integration across CCAMLR data - Integration provides the benefit of | 39 | Integration across CCAMLR data - Integration provides the benefit of | ||
40 | being able to systematically use data from various data collection | 40 | being able to systematically use data from various data collection | ||
41 | systems to enhance the quality and value of each data source (e.g. | 41 | systems to enhance the quality and value of each data source (e.g. | ||
42 | vessel reported data, observer collected data, vessel monitoring and | 42 | vessel reported data, observer collected data, vessel monitoring and | ||
43 | catch documentation systems), leading to more consistent, reliable and | 43 | catch documentation systems), leading to more consistent, reliable and | ||
44 | timely delivery of data. User-focussed documentation supporting CCAMLR | 44 | timely delivery of data. User-focussed documentation supporting CCAMLR | ||
45 | data systems and CCAMLR data \u2013 CCAMLR data users require a deep | 45 | data systems and CCAMLR data \u2013 CCAMLR data users require a deep | ||
46 | understanding of the structure and meaning of the data being used. | 46 | understanding of the structure and meaning of the data being used. | ||
47 | Gaining a better understanding of CCAMLR data starts with access to | 47 | Gaining a better understanding of CCAMLR data starts with access to | ||
48 | clear documentation of the datasets (entities), and associated data | 48 | clear documentation of the datasets (entities), and associated data | ||
49 | items (attributes) within each dataset, and should include the data | 49 | items (attributes) within each dataset, and should include the data | ||
50 | source(s) and data collection regime(s), and the application of DQA. | 50 | source(s) and data collection regime(s), and the application of DQA. | ||
51 | All uses of the same data item regardless of the source or purpose | 51 | All uses of the same data item regardless of the source or purpose | ||
52 | will use the same name. Assurances regarding CCAMLR data quality - | 52 | will use the same name. Assurances regarding CCAMLR data quality - | ||
53 | Data users require full traceability of data from submission to data | 53 | Data users require full traceability of data from submission to data | ||
54 | delivery. On submission of data, corrections and assumptions must be | 54 | delivery. On submission of data, corrections and assumptions must be | ||
55 | fully auditable. Modern data systems are expected to support | 55 | fully auditable. Modern data systems are expected to support | ||
56 | traceability and reversibility. Automated and manual mark up of data | 56 | traceability and reversibility. Automated and manual mark up of data | ||
57 | (e.g. data corrections), auditable event logs, and the ability to | 57 | (e.g. data corrections), auditable event logs, and the ability to | ||
58 | undo/modify/redo any corrections all become metadata that are securely | 58 | undo/modify/redo any corrections all become metadata that are securely | ||
59 | managed to provide a complete history of the data life cycle. | 59 | managed to provide a complete history of the data life cycle. | ||
60 | Availability of metadata - Data are most valuable when they are | 60 | Availability of metadata - Data are most valuable when they are | ||
61 | accompanied by metadata1 describing where the data came from, if and | 61 | accompanied by metadata1 describing where the data came from, if and | ||
62 | how the data were processed and transformed, how to interpret the data | 62 | how the data were processed and transformed, how to interpret the data | ||
63 | and how DQA was implemented. Metadata facilitates the CCAMLR datasets | 63 | and how DQA was implemented. Metadata facilitates the CCAMLR datasets | ||
64 | to be searchable, discoverable and potentially shareable (under the | 64 | to be searchable, discoverable and potentially shareable (under the | ||
65 | specified data security provisions). Engagement, transparency and | 65 | specified data security provisions). Engagement, transparency and | ||
66 | functionality of data submission - The process of submitting data | 66 | functionality of data submission - The process of submitting data | ||
67 | should be completely transparent and engage with data submitters. Data | 67 | should be completely transparent and engage with data submitters. Data | ||
68 | submission should be supported by standard operating procedures, data | 68 | submission should be supported by standard operating procedures, data | ||
69 | quality feedback, visualisations adding value to the submitted data, | 69 | quality feedback, visualisations adding value to the submitted data, | ||
70 | and training and documentation to ensure best practice and | 70 | and training and documentation to ensure best practice and | ||
71 | productivity gains are realised. Standard tools for the collection and | 71 | productivity gains are realised. Standard tools for the collection and | ||
72 | transmission of data will be explored in particular the evolution of | 72 | transmission of data will be explored in particular the evolution of | ||
73 | e-reporting platforms. Submitted data should be visible to the data | 73 | e-reporting platforms. Submitted data should be visible to the data | ||
74 | provider with appropriate audit controls indicating who provided the | 74 | provider with appropriate audit controls indicating who provided the | ||
75 | data and when a submission was made. Dissemination of CCAMLR data - | 75 | data and when a submission was made. Dissemination of CCAMLR data - | ||
76 | Data access must be convenient and systematic based on strict and | 76 | Data access must be convenient and systematic based on strict and | ||
77 | agreed security protocols. As CCAMLR metadata increase in visibility, | 77 | agreed security protocols. As CCAMLR metadata increase in visibility, | ||
78 | requests for access to secure data will undoubtedly increase. Data | 78 | requests for access to secure data will undoubtedly increase. Data | ||
79 | requests should be supported and facilitated with a rigorous and | 79 | requests should be supported and facilitated with a rigorous and | ||
80 | efficient approval process. Authoritative data (i.e. CCAMLR is the | 80 | efficient approval process. Authoritative data (i.e. CCAMLR is the | ||
81 | issuing authority), in particular CCAMLR management areas, will be | 81 | issuing authority), in particular CCAMLR management areas, will be | ||
82 | accessible as a web service for assimilation by external users an\"" | 82 | accessible as a web service for assimilation by external users an\"" | ||
83 | }, | 83 | }, | ||
84 | { | 84 | { | ||
85 | "key": "Data Policy", | 85 | "key": "Data Policy", | ||
86 | "value": "\"The following Rules for Access and Use of CCAMLR | 86 | "value": "\"The following Rules for Access and Use of CCAMLR | ||
87 | Data were adopted by the Twenty-Second Meeting of the Commission | 87 | Data were adopted by the Twenty-Second Meeting of the Commission | ||
88 | (CCAMLR-XXII, paragraphs 12.1 to 12.6)1: It is recognised that: All | 88 | (CCAMLR-XXII, paragraphs 12.1 to 12.6)1: It is recognised that: All | ||
89 | data submitted to the CCAMLR Secretariat, and maintained by the CCAMLR | 89 | data submitted to the CCAMLR Secretariat, and maintained by the CCAMLR | ||
90 | Data Centre, shall be freely available to Members for analysis and | 90 | Data Centre, shall be freely available to Members for analysis and | ||
91 | preparation of documents for the Commission, Scientific Committee and | 91 | preparation of documents for the Commission, Scientific Committee and | ||
92 | their subsidiary bodies. Such data may be analysed in respect of: | 92 | their subsidiary bodies. Such data may be analysed in respect of: | ||
93 | work specifically outlined and endorsed by the Commission or | 93 | work specifically outlined and endorsed by the Commission or | ||
94 | Scientific Committee; work not specifically endorsed by the | 94 | Scientific Committee; work not specifically endorsed by the | ||
95 | Commission or the Scientific Committee. Inclusion of data, analyses | 95 | Commission or the Scientific Committee. Inclusion of data, analyses | ||
96 | or results from data held in the CCAMLR Data Centre into Working | 96 | or results from data held in the CCAMLR Data Centre into Working | ||
97 | Papers, Background Papers, and any other documents tabled at meetings | 97 | Papers, Background Papers, and any other documents tabled at meetings | ||
98 | of the Commission, Scientific Committee or one of their subsidiary | 98 | of the Commission, Scientific Committee or one of their subsidiary | ||
99 | bodies does not constitute publication and therefore is not a release | 99 | bodies does not constitute publication and therefore is not a release | ||
100 | into the public domain. Inclusion of data held in the CCAMLR Data | 100 | into the public domain. Inclusion of data held in the CCAMLR Data | ||
101 | Centre into the published reports of the Commission, Scientific | 101 | Centre into the published reports of the Commission, Scientific | ||
102 | Committee, Working Groups, CCAMLR Science, the Statistical Bulletin or | 102 | Committee, Working Groups, CCAMLR Science, the Statistical Bulletin or | ||
103 | any other CCAMLR publication constitutes release into the public | 103 | any other CCAMLR publication constitutes release into the public | ||
104 | domain. Inclusion of data held in the CCAMLR Data Centre in any | 104 | domain. Inclusion of data held in the CCAMLR Data Centre in any | ||
105 | publication outside CCAMLR constitutes release into the public domain. | 105 | publication outside CCAMLR constitutes release into the public domain. | ||
106 | Subject to paragraphs (1) to (3), originators/owners of data have the | 106 | Subject to paragraphs (1) to (3), originators/owners of data have the | ||
107 | right to: be consulted (including assignation of authorship) on the | 107 | right to: be consulted (including assignation of authorship) on the | ||
108 | preparation, if necessary including publication, of documents | 108 | preparation, if necessary including publication, of documents | ||
109 | describing analyses and interpretation of their data; approve the | 109 | describing analyses and interpretation of their data; approve the | ||
110 | level of detail revealed in documents using their data; stipulate | 110 | level of detail revealed in documents using their data; stipulate | ||
111 | terms and/or levels of data security if necessary. Accordingly, | 111 | terms and/or levels of data security if necessary. Accordingly, | ||
112 | Requests to the Secretariat for access and/or use of data maintained | 112 | Requests to the Secretariat for access and/or use of data maintained | ||
113 | by the CCAMLR Data Centre by individual Member scientists/officials | 113 | by the CCAMLR Data Centre by individual Member scientists/officials | ||
114 | shall be approved in writing as appropriate by that Member\u2019s | 114 | shall be approved in writing as appropriate by that Member\u2019s | ||
115 | Commission Representative, Scientific Committee image 1 These rules | 115 | Commission Representative, Scientific Committee image 1 These rules | ||
116 | replace those adopted at the Eleventh Meeting of the Commission | 116 | replace those adopted at the Eleventh Meeting of the Commission | ||
117 | (CCAMLR-XI, paragraph 4.35). The current \u2018Rules for Access to CDS | 117 | (CCAMLR-XI, paragraph 4.35). The current \u2018Rules for Access to CDS | ||
118 | Data\u2019 (CCAMLR-XIX, paragraph 5.23) should remain in place | 118 | Data\u2019 (CCAMLR-XIX, paragraph 5.23) should remain in place | ||
119 | alongside the new standard rules until such times as all aspects of | 119 | alongside the new standard rules until such times as all aspects of | ||
120 | CDS data handling are duly taken into account in the new standard | 120 | CDS data handling are duly taken into account in the new standard | ||
121 | rules (CCAMLR-XXII, paragraph 7.22). 133 Access to CCAMLR Data | 121 | rules (CCAMLR-XXII, paragraph 7.22). 133 Access to CCAMLR Data | ||
122 | Representative, or CDS Officer in consultation with the Commission | 122 | Representative, or CDS Officer in consultation with the Commission | ||
123 | Representative. Members are responsible for informing individual | 123 | Representative. Members are responsible for informing individual | ||
124 | scientists or individuals requesting data of the rules governing | 124 | scientists or individuals requesting data of the rules governing | ||
125 | access and use of CCAMLR data and for obtaining agreement to comply | 125 | access and use of CCAMLR data and for obtaining agreement to comply | ||
126 | with such rules. Requests in support of analyses endorsed under | 126 | with such rules. Requests in support of analyses endorsed under | ||
127 | (2)(a) above should include the type of data requested, the degree of | 127 | (2)(a) above should include the type of data requested, the degree of | ||
128 | data aggregation required, the spatial and temporal detail required, | 128 | data aggregation required, the spatial and temporal detail required, | ||
129 | and the anticipated format to be used in presenting results of the | 129 | and the anticipated format to be used in presenting results of the | ||
130 | analyses. For such requests, the Secretariat shall ensure that each | 130 | analyses. For such requests, the Secretariat shall ensure that each | ||
131 | request meets the conditions of the approval granted for the original | 131 | request meets the conditions of the approval granted for the original | ||
132 | endorsement, and, if so, release the data and inform the data | 132 | endorsement, and, if so, release the data and inform the data | ||
133 | owner(s)/originator(s) accordingly. Release of data by the Secretariat | 133 | owner(s)/originator(s) accordingly. Release of data by the Secretariat | ||
134 | to the requestor does not constitute permission to publish or release | 134 | to the requestor does not constitute permission to publish or release | ||
135 | data into the public domain. Such permission remains a matter to be | 135 | data into the public domain. Such permission remains a matter to be | ||
136 | determined between the requestor and the data originator(s). Requests | 136 | determined between the requestor and the data originator(s). Requests | ||
137 | in support of non-endorsed analyses under (2)(b) above should include | 137 | in support of non-endorsed analyses under (2)(b) above should include | ||
138 | the information listed in (8) as well as details of the analytical | 138 | the information listed in (8) as well as details of the analytical | ||
139 | procedures to be used and the opportunity for data | 139 | procedures to be used and the opportunity for data | ||
140 | owner(s)/originator(s) to be involved. For such requests, the | 140 | owner(s)/originator(s) to be involved. For such requests, the | ||
141 | Secretariat shall be satisfied that each request contains the required | 141 | Secretariat shall be satisfied that each request contains the required | ||
142 | information before forwarding it to the data originator(s) for | 142 | information before forwarding it to the data originator(s) for | ||
143 | approval within a specified time period. Once approval has been | 143 | approval within a specified time period. Once approval has been | ||
144 | received the Secretariat shall release the data. Release of data does | 144 | received the Secretariat shall release the data. Release of data does | ||
145 | not constitute permission to publish or for release into the public | 145 | not constitute permission to publish or for release into the public | ||
146 | domain. Such permission remains a matter to be determined between the | 146 | domain. Such permission remains a matter to be determined between the | ||
147 | requestor and the data owner(s)/originator(s). If approval for data | 147 | requestor and the data owner(s)/originator(s). If approval for data | ||
148 | release under (9) is not forthcoming within the specified period, the | 148 | release under (9) is not forthcoming within the specified period, the | ||
149 | Secretariat shall initiate and facilitate consultation between the | 149 | Secretariat shall initiate and facilitate consultation between the | ||
150 | data requestor and data owner(s)/originator(s). The Secretariat shall | 150 | data requestor and data owner(s)/originator(s). The Secretariat shall | ||
151 | not release data without the written approval of the data | 151 | not release data without the written approval of the data | ||
152 | owner(s)/originator(s). Failure to achieve agreement shall be brought | 152 | owner(s)/originator(s). Failure to achieve agreement shall be brought | ||
153 | to the attention of the Scientific Committee and Commission. The | 153 | to the attention of the Scientific Committee and Commission. The | ||
154 | following statement shall be placed on the cover page of all Working | 154 | following statement shall be placed on the cover page of all Working | ||
155 | Papers, Background Papers and any other papers tabled at meetings of | 155 | Papers, Background Papers and any other papers tabled at meetings of | ||
156 | the Commission, Scientific Committee or their subsidiary bodies: | 156 | the Commission, Scientific Committee or their subsidiary bodies: | ||
157 | \u2018This paper is presented for consideration by CCAMLR and may | 157 | \u2018This paper is presented for consideration by CCAMLR and may | ||
158 | contain unpublished data, analyses, and/or conclusions subject to | 158 | contain unpublished data, analyses, and/or conclusions subject to | ||
159 | change. Data in this paper shall not be cited or used for purposes | 159 | change. Data in this paper shall not be cited or used for purposes | ||
160 | other than the work of the CCAMLR Commission, Scientific Committee or | 160 | other than the work of the CCAMLR Commission, Scientific Committee or | ||
161 | their subsidiary bodies without the permission of the originators | 161 | their subsidiary bodies without the permission of the originators | ||
162 | and/or owners of the data.\u2019\"" | 162 | and/or owners of the data.\u2019\"" | ||
163 | }, | 163 | }, | ||
164 | { | 164 | { | ||
165 | "key": "Data Sharing Principle", | 165 | "key": "Data Sharing Principle", | ||
166 | "value": "\"The availability of data maintained on behalf of the | 166 | "value": "\"The availability of data maintained on behalf of the | ||
167 | Commission by the Secretariat is governed by Rules for the Access and | 167 | Commission by the Secretariat is governed by Rules for the Access and | ||
168 | Use of CCAMLR Data. Access and use falls under five general | 168 | Use of CCAMLR Data. Access and use falls under five general | ||
169 | categories: With the exception of STATLANT data (see 2 below), CDS | 169 | categories: With the exception of STATLANT data (see 2 below), CDS | ||
170 | data (see 3 below) and VMS data (see 4 below), all CCAMLR data are | 170 | data (see 3 below) and VMS data (see 4 below), all CCAMLR data are | ||
171 | subject to the Rules for Access and Use of CCAMLR Data (20.18 KB). | 171 | subject to the Rules for Access and Use of CCAMLR Data (20.18 KB). | ||
172 | Under the terms of these rules, data are freely available to Member | 172 | Under the terms of these rules, data are freely available to Member | ||
173 | countries for analysis and preparation of documents for the | 173 | countries for analysis and preparation of documents for the | ||
174 | Commission, Scientific Committee and their subsidiary bodies. STATLANT | 174 | Commission, Scientific Committee and their subsidiary bodies. STATLANT | ||
175 | data are held in the public domain and are freely available. These | 175 | data are held in the public domain and are freely available. These | ||
176 | data are transmitted to FAO and some Regional Bodies, and summary | 176 | data are transmitted to FAO and some Regional Bodies, and summary | ||
177 | statistics are published annually in the CCAMLR Statistical Bulletin | 177 | statistics are published annually in the CCAMLR Statistical Bulletin | ||
178 | (2.2 MB) and other publications such as the FAO Yearbook of Fishery | 178 | (2.2 MB) and other publications such as the FAO Yearbook of Fishery | ||
179 | Statistics. CDS data are subject to the Rules for Access to Catch | 179 | Statistics. CDS data are subject to the Rules for Access to Catch | ||
180 | Documentation Scheme Data (16.01 KB). The release of VMS data is | 180 | Documentation Scheme Data (16.01 KB). The release of VMS data is | ||
181 | subject to the provisions on secure and confidential treatment of | 181 | subject to the provisions on secure and confidential treatment of | ||
182 | electronic reports and messages outlined in Annex B of Conservation | 182 | electronic reports and messages outlined in Annex B of Conservation | ||
183 | Measure 10-04. Copies of data held by other organisations (i.e. | 183 | Measure 10-04. Copies of data held by other organisations (i.e. | ||
184 | non-CCAMLR datasets) are subject to terms specified by each parent | 184 | non-CCAMLR datasets) are subject to terms specified by each parent | ||
185 | organisation. Generally, these terms allow free access and use of the | 185 | organisation. Generally, these terms allow free access and use of the | ||
186 | data. Data requests may be submitted by emailing the Data Centre. | 186 | data. Data requests may be submitted by emailing the Data Centre. | ||
187 | Requests should specify the type of data, spatial and temporal | 187 | Requests should specify the type of data, spatial and temporal | ||
188 | coverage (e.g. areas and seasons) and proposed use of the data. Where | 188 | coverage (e.g. areas and seasons) and proposed use of the data. Where | ||
189 | possible, requests should be endorsed by the national representative | 189 | possible, requests should be endorsed by the national representative | ||
190 | to CCAMLR and the proposed use of the data should make specific | 190 | to CCAMLR and the proposed use of the data should make specific | ||
191 | reference to the work of the Commission or Scientific Committee.\"" | 191 | reference to the work of the Commission or Scientific Committee.\"" | ||
192 | } | 192 | } | ||
193 | ], | 193 | ], | ||
194 | "groups": [], | 194 | "groups": [], | ||
195 | "id": "54ed3816-14a5-409e-bdc5-883c2657d8e3", | 195 | "id": "54ed3816-14a5-409e-bdc5-883c2657d8e3", | ||
196 | "isopen": false, | 196 | "isopen": false, | ||
197 | "license_id": "", | 197 | "license_id": "", | ||
198 | "license_title": "", | 198 | "license_title": "", | ||
199 | "maintainer": "", | 199 | "maintainer": "", | ||
200 | "maintainer_email": "", | 200 | "maintainer_email": "", | ||
201 | "metadata_created": "2022-04-05T07:03:13.185818", | 201 | "metadata_created": "2022-04-05T07:03:13.185818", | ||
n | 202 | "metadata_modified": "2022-04-05T07:03:42.208950", | n | 202 | "metadata_modified": "2022-04-05T07:03:42.385322", |
203 | "name": "ccamlr-gis", | 203 | "name": "ccamlr-gis", | ||
204 | "notes": "The CCAMLR online Geographical Information System (GIS) is | 204 | "notes": "The CCAMLR online Geographical Information System (GIS) is | ||
205 | the result of a collaborative development with the British Antarctic | 205 | the result of a collaborative development with the British Antarctic | ||
206 | Survey in Cambridge, UK. It provides a state-of-the-art repository for | 206 | Survey in Cambridge, UK. It provides a state-of-the-art repository for | ||
207 | managing spatial data for CCAMLR.\r\n", | 207 | managing spatial data for CCAMLR.\r\n", | ||
208 | "num_resources": 1, | 208 | "num_resources": 1, | ||
209 | "num_tags": 0, | 209 | "num_tags": 0, | ||
210 | "organization": { | 210 | "organization": { | ||
211 | "approval_status": "approved", | 211 | "approval_status": "approved", | ||
212 | "created": "2020-04-30T11:11:08.802657", | 212 | "created": "2020-04-30T11:11:08.802657", | ||
213 | "description": "Aerospace Information Research Institute (AIR) | 213 | "description": "Aerospace Information Research Institute (AIR) | ||
214 | under the Chinese Academy of Sciences (CAS) was established in July | 214 | under the Chinese Academy of Sciences (CAS) was established in July | ||
215 | 2017, following the approval for consolidation of three CAS | 215 | 2017, following the approval for consolidation of three CAS | ||
216 | institutes: the Institute of Electronics (IECAS), the Institute of | 216 | institutes: the Institute of Electronics (IECAS), the Institute of | ||
217 | Remote Sensing and Digital Earth (RADI), and the Academy of | 217 | Remote Sensing and Digital Earth (RADI), and the Academy of | ||
218 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | 218 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | ||
219 | the outcome of CAS efforts towards reformation of its R&D system to | 219 | the outcome of CAS efforts towards reformation of its R&D system to | ||
220 | meet future R&D challenges and to better meet the national demands.", | 220 | meet future R&D challenges and to better meet the national demands.", | ||
221 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 221 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
222 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | 222 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | ||
223 | "is_organization": true, | 223 | "is_organization": true, | ||
224 | "name": "air", | 224 | "name": "air", | ||
225 | "state": "active", | 225 | "state": "active", | ||
226 | "title": "Aerospace Information Research Institute, CAS", | 226 | "title": "Aerospace Information Research Institute, CAS", | ||
227 | "type": "organization" | 227 | "type": "organization" | ||
228 | }, | 228 | }, | ||
229 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 229 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
230 | "private": false, | 230 | "private": false, | ||
231 | "relationships_as_object": [], | 231 | "relationships_as_object": [], | ||
232 | "relationships_as_subject": [], | 232 | "relationships_as_subject": [], | ||
233 | "resources": [ | 233 | "resources": [ | ||
234 | { | 234 | { | ||
235 | "cache_last_updated": null, | 235 | "cache_last_updated": null, | ||
236 | "cache_url": null, | 236 | "cache_url": null, | ||
237 | "created": "2022-04-05T07:03:42.216020", | 237 | "created": "2022-04-05T07:03:42.216020", | ||
238 | "datastore_active": false, | 238 | "datastore_active": false, | ||
239 | "description": "The CCAMLR online Geographical Information | 239 | "description": "The CCAMLR online Geographical Information | ||
240 | System (GIS) is the result of a collaborative development with the | 240 | System (GIS) is the result of a collaborative development with the | ||
241 | British Antarctic Survey in Cambridge, UK. It provides a | 241 | British Antarctic Survey in Cambridge, UK. It provides a | ||
242 | state-of-the-art repository for managing spatial data for | 242 | state-of-the-art repository for managing spatial data for | ||
243 | CCAMLR.\r\n", | 243 | CCAMLR.\r\n", | ||
244 | "format": "", | 244 | "format": "", | ||
245 | "hash": "", | 245 | "hash": "", | ||
246 | "id": "daa947b4-4963-49a2-bbb9-8faa9d1efad8", | 246 | "id": "daa947b4-4963-49a2-bbb9-8faa9d1efad8", | ||
247 | "last_modified": null, | 247 | "last_modified": null, | ||
n | 248 | "metadata_modified": "2022-04-05T07:03:42.212328", | n | 248 | "metadata_modified": "2022-04-05T07:03:42.388655", |
249 | "mimetype": null, | 249 | "mimetype": null, | ||
250 | "mimetype_inner": null, | 250 | "mimetype_inner": null, | ||
251 | "name": "CCAMLR GIS", | 251 | "name": "CCAMLR GIS", | ||
252 | "package_id": "54ed3816-14a5-409e-bdc5-883c2657d8e3", | 252 | "package_id": "54ed3816-14a5-409e-bdc5-883c2657d8e3", | ||
253 | "position": 0, | 253 | "position": 0, | ||
254 | "resource_type": null, | 254 | "resource_type": null, | ||
255 | "size": null, | 255 | "size": null, | ||
256 | "state": "active", | 256 | "state": "active", | ||
257 | "url": "https://gis.ccamlr.org/", | 257 | "url": "https://gis.ccamlr.org/", | ||
258 | "url_type": null | 258 | "url_type": null | ||
259 | } | 259 | } | ||
260 | ], | 260 | ], | ||
t | 261 | "state": "draft", | t | 261 | "state": "active", |
262 | "tags": [], | 262 | "tags": [], | ||
263 | "title": "CCAMLR GIS", | 263 | "title": "CCAMLR GIS", | ||
264 | "type": "dataset", | 264 | "type": "dataset", | ||
265 | "url": "https://gis.ccamlr.org/", | 265 | "url": "https://gis.ccamlr.org/", | ||
266 | "version": "" | 266 | "version": "" | ||
267 | } | 267 | } |