Changes
On April 11, 2022 at 12:10:00 PM UTC,
-
Added the following fields to McMurdo Dry Valleys LTER (MCM) Data Explorer Dashboard
- Database Level with value Project
- FIAR with value No
- Source of Data Policy with value Own
- Region with value Antarctic
- Opening Degree with value Open
- Theme with value Comprehensive
- Host Institute with value Long-term Ecological Research (LTER) Program
- Organizer with value LTER Network
| 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": "USA" | 8 | "value": "USA" | ||
| 9 | }, | 9 | }, | ||
| 10 | { | 10 | { | ||
| 11 | "key": "Data Management ", | 11 | "key": "Data Management ", | ||
| 12 | "value": "In order for the database to function properly, many | 12 | "value": "In order for the database to function properly, many | ||
| 13 | constraints must be put on what type of data can be entered and how | 13 | constraints must be put on what type of data can be entered and how | ||
| 14 | those data are entered. Following the guidelines below will ensure all | 14 | those data are entered. Following the guidelines below will ensure all | ||
| 15 | your data are entered correctly and the website will continue to | 15 | your data are entered correctly and the website will continue to | ||
| 16 | function reliably. Read the submission protocols for your group in | 16 | function reliably. Read the submission protocols for your group in | ||
| 17 | Streams Data Met Data Limno Data Glaciers Data There is a template | 17 | Streams Data Met Data Limno Data Glaciers Data There is a template | ||
| 18 | for each \u2018core data\u2019 table that shows how each file should | 18 | for each \u2018core data\u2019 table that shows how each file should | ||
| 19 | be formatted (column names and column order are both important). Make | 19 | be formatted (column names and column order are both important). Make | ||
| 20 | sure you keep these column headers. If you did not collect data for a | 20 | sure you keep these column headers. If you did not collect data for a | ||
| 21 | certain parameter in the table that season, simply leave it blank. | 21 | certain parameter in the table that season, simply leave it blank. | ||
| 22 | Excel is generally used to work up and format data. When you\u2019re | 22 | Excel is generally used to work up and format data. When you\u2019re | ||
| 23 | done, save your data file in comma-delimited format (.csv). Open it | 23 | done, save your data file in comma-delimited format (.csv). Open it | ||
| 24 | back up and make sure everything still looks ok. Do not use commas in | 24 | back up and make sure everything still looks ok. Do not use commas in | ||
| 25 | any field \u2013 use semicolons instead. This is usually a problem in | 25 | any field \u2013 use semicolons instead. This is usually a problem in | ||
| 26 | the \u2018COMMENTS\u2019 column. We can\u2019t use commas because data | 26 | the \u2018COMMENTS\u2019 column. We can\u2019t use commas because data | ||
| 27 | are output in commadelimited format on the web \u2013 it just makes | 27 | are output in commadelimited format on the web \u2013 it just makes | ||
| 28 | things easier. Missing Data and out-of-range data; inappropriate | 28 | things easier. Missing Data and out-of-range data; inappropriate | ||
| 29 | values in cells. If there are no data for a particular sample, do not | 29 | values in cells. If there are no data for a particular sample, do not | ||
| 30 | write \u201cmissing\u201d or \u201cno data\u201d or \u201cND\u201d in | 30 | write \u201cmissing\u201d or \u201cno data\u201d or \u201cND\u201d in | ||
| 31 | the data column - The database will produce an error if text is | 31 | the data column - The database will produce an error if text is | ||
| 32 | entered into a field expecting digits. Instead, leave that field blank | 32 | entered into a field expecting digits. Instead, leave that field blank | ||
| 33 | and if appropriate, write why it is missing in the | 33 | and if appropriate, write why it is missing in the | ||
| 34 | \u2018Comments\u2019 column. Your group may have existing comment | 34 | \u2018Comments\u2019 column. Your group may have existing comment | ||
| 35 | codes that apply to this situation. Also, some instruments are | 35 | codes that apply to this situation. Also, some instruments are | ||
| 36 | programmed to output a number such as -6999 indicating missing data. | 36 | programmed to output a number such as -6999 indicating missing data. | ||
| 37 | This is also unacceptable to the database \u2013 there may be rules | 37 | This is also unacceptable to the database \u2013 there may be rules | ||
| 38 | for checking the data range that won\u2019t allow extremely high or | 38 | for checking the data range that won\u2019t allow extremely high or | ||
| 39 | extremely low numbers to be input. Do not include any values that you | 39 | extremely low numbers to be input. Do not include any values that you | ||
| 40 | don\u2019t intend for someone using your dataset to actually use | 40 | don\u2019t intend for someone using your dataset to actually use | ||
| 41 | \u2013 delete the value and flag it appropriately in the Comments | 41 | \u2013 delete the value and flag it appropriately in the Comments | ||
| 42 | column. Be careful that your empty data columns don\u2019t include | 42 | column. Be careful that your empty data columns don\u2019t include | ||
| 43 | spaces. This is a text character and will not be accepted by the | 43 | spaces. This is a text character and will not be accepted by the | ||
| 44 | database. In general, consider the type of data that is supposed to go | 44 | database. In general, consider the type of data that is supposed to go | ||
| 45 | in that column and the normal range one would expect. Do not enter | 45 | in that column and the normal range one would expect. Do not enter | ||
| 46 | anything else. Pay special attention to the Date/Time Column The | 46 | anything else. Pay special attention to the Date/Time Column The | ||
| 47 | easiest format to use for the database (and the one we output on the | 47 | easiest format to use for the database (and the one we output on the | ||
| 48 | website) is 'MM/DD/YYYY' for date only, or 'MM/DD/YYYY HH:MM\u2019 for | 48 | website) is 'MM/DD/YYYY' for date only, or 'MM/DD/YYYY HH:MM\u2019 for | ||
| 49 | date and 24 hour time. However, other formats will also work \u2013 | 49 | date and 24 hour time. However, other formats will also work \u2013 | ||
| 50 | contact the data manager to see if your alternate date/time format is | 50 | contact the data manager to see if your alternate date/time format is | ||
| 51 | acceptable before submitting it. MM/DD/YYYY' does not correctly | 51 | acceptable before submitting it. MM/DD/YYYY' does not correctly | ||
| 52 | transfer out of Excel if you use the default - you must define a | 52 | transfer out of Excel if you use the default - you must define a | ||
| 53 | custom format: Highlight the date cells and go to Format -> Cells | 53 | custom format: Highlight the date cells and go to Format -> Cells | ||
| 54 | Under the 'Number' tab, go to 'Custom' at the bottom Under the field | 54 | Under the 'Number' tab, go to 'Custom' at the bottom Under the field | ||
| 55 | that says 'Type:' write 'mm/dd/yyyy' (or \u2018mm/dd/yyyy hh:mm\u2019) | 55 | that says 'Type:' write 'mm/dd/yyyy' (or \u2018mm/dd/yyyy hh:mm\u2019) | ||
| 56 | A way you can check to see if it worked is by opening the file in a | 56 | A way you can check to see if it worked is by opening the file in a | ||
| 57 | text editor (e.g. Notepad in Windows) and checking to see if the year | 57 | text editor (e.g. Notepad in Windows) and checking to see if the year | ||
| 58 | is 4 digits. This is important because even though the default Excel | 58 | is 4 digits. This is important because even though the default Excel | ||
| 59 | date format may display a 4 digit year, it often only saves it as a 2 | 59 | date format may display a 4 digit year, it often only saves it as a 2 | ||
| 60 | digit year. When a 2 digit year is loaded into the database, | 60 | digit year. When a 2 digit year is loaded into the database, | ||
| 61 | \u201c07\u201d will be interpreted as \u201c0007\u201d instead of | 61 | \u201c07\u201d will be interpreted as \u201c0007\u201d instead of | ||
| 62 | \u201c2007.\u201d Another thing to watch \u2013 Dates do not always | 62 | \u201c2007.\u201d Another thing to watch \u2013 Dates do not always | ||
| 63 | transfer correctly between PCs and Macs in Excel files, which is | 63 | transfer correctly between PCs and Macs in Excel files, which is | ||
| 64 | another reason to use comma-delimited (.csv) text files. If your dates | 64 | another reason to use comma-delimited (.csv) text files. If your dates | ||
| 65 | are off by 4 years and 1 day, that is the issue. All fields are | 65 | are off by 4 years and 1 day, that is the issue. All fields are | ||
| 66 | case-sensitive! If there are notes in a template, submission | 66 | case-sensitive! If there are notes in a template, submission | ||
| 67 | instructions, or constraint table that say a certain field must be in | 67 | instructions, or constraint table that say a certain field must be in | ||
| 68 | all-caps, make sure they are or the data will not insert. Try to make | 68 | all-caps, make sure they are or the data will not insert. Try to make | ||
| 69 | your data look like the existing data in the database. Each data | 69 | your data look like the existing data in the database. Each data | ||
| 70 | submission protocol page will have options to download just the column | 70 | submission protocol page will have options to download just the column | ||
| 71 | header or the entire dataset. Download the entire dataset and open it | 71 | header or the entire dataset. Download the entire dataset and open it | ||
| 72 | in Excel and get acquainted with the format \u2013 make your new data | 72 | in Excel and get acquainted with the format \u2013 make your new data | ||
| 73 | format look like the old one. " | 73 | format look like the old one. " | ||
| 74 | }, | 74 | }, | ||
| 75 | { | 75 | { | ||
| 76 | "key": "Data Policy", | 76 | "key": "Data Policy", | ||
| 77 | "value": "MCM LTER data may be used freely with the following | 77 | "value": "MCM LTER data may be used freely with the following | ||
| 78 | restrictions: The Principal Investigator be sent a notice stating | 78 | restrictions: The Principal Investigator be sent a notice stating | ||
| 79 | reasons for acquiring any data and a description of the publication | 79 | reasons for acquiring any data and a description of the publication | ||
| 80 | intentions. The Principal Investigator of the data set be sent a | 80 | intentions. The Principal Investigator of the data set be sent a | ||
| 81 | copy of the report or manuscript prior to submission and be adequately | 81 | copy of the report or manuscript prior to submission and be adequately | ||
| 82 | cited in any resultant publications. A copy of any resultant | 82 | cited in any resultant publications. A copy of any resultant | ||
| 83 | publications should be sent to the McMurdo data manager and principal | 83 | publications should be sent to the McMurdo data manager and principal | ||
| 84 | investigator. The end-user follow the guidelines set forth in the | 84 | investigator. The end-user follow the guidelines set forth in the | ||
| 85 | LTER Network Data Access Policy, Data Access Requirements, and General | 85 | LTER Network Data Access Policy, Data Access Requirements, and General | ||
| 86 | Data Use Agreement here: Definitions \u201cData Set\u201d \u2013 | 86 | Data Use Agreement here: Definitions \u201cData Set\u201d \u2013 | ||
| 87 | Digital data and its metadata derived from any research activity such | 87 | Digital data and its metadata derived from any research activity such | ||
| 88 | as field observations, collections, laboratory analysis, experiments, | 88 | as field observations, collections, laboratory analysis, experiments, | ||
| 89 | or the post-processing of existing data and identified by a unique | 89 | or the post-processing of existing data and identified by a unique | ||
| 90 | identifier issued by a recognized cataloging authority such as a site, | 90 | identifier issued by a recognized cataloging authority such as a site, | ||
| 91 | university, agency, or other organization. \u201cData User\u201d - | 91 | university, agency, or other organization. \u201cData User\u201d - | ||
| 92 | individual to whom access has been granted to this Data Set, including | 92 | individual to whom access has been granted to this Data Set, including | ||
| 93 | his or her immediate collaboration sphere, defined here as the | 93 | his or her immediate collaboration sphere, defined here as the | ||
| 94 | institutions, partners, students and staff with whom the Data User | 94 | institutions, partners, students and staff with whom the Data User | ||
| 95 | collaborates, and with whom access must be granted, in order to | 95 | collaborates, and with whom access must be granted, in order to | ||
| 96 | fulfill the Data User's intended use of the Data Set \u201cData Set | 96 | fulfill the Data User's intended use of the Data Set \u201cData Set | ||
| 97 | Creator\u201d - individual or institution that produced the Data Set | 97 | Creator\u201d - individual or institution that produced the Data Set | ||
| 98 | \u201cData Set Owner\u201d \u2013 individual or institution that holds | 98 | \u201cData Set Owner\u201d \u2013 individual or institution that holds | ||
| 99 | intellectual property rights to the dataset. Note that this may or may | 99 | intellectual property rights to the dataset. Note that this may or may | ||
| 100 | not be defined as a legal copyright. If no other party is designated | 100 | not be defined as a legal copyright. If no other party is designated | ||
| 101 | in the metadata as Data Set Owner, it may be presumed that these | 101 | in the metadata as Data Set Owner, it may be presumed that these | ||
| 102 | rights are held by the Data Set Creator. \u201cData Set | 102 | rights are held by the Data Set Creator. \u201cData Set | ||
| 103 | Distributor\u201d - individual or institution providing access to the | 103 | Distributor\u201d - individual or institution providing access to the | ||
| 104 | Data Sets. \u201cData Set Contact\u201d - party designated in the | 104 | Data Sets. \u201cData Set Contact\u201d - party designated in the | ||
| 105 | accompanying metadata of the Data Set as the primary contact for the | 105 | accompanying metadata of the Data Set as the primary contact for the | ||
| 106 | Data Set. While substantial efforts are made to ensure the accuracy | 106 | Data Set. While substantial efforts are made to ensure the accuracy | ||
| 107 | of data and documentation contained in this Data Set, complete | 107 | of data and documentation contained in this Data Set, complete | ||
| 108 | accuracy of data and metadata cannot be guaranteed. All data and | 108 | accuracy of data and metadata cannot be guaranteed. All data and | ||
| 109 | metadata are made available \"as is\". The Data User holds all parties | 109 | metadata are made available \"as is\". The Data User holds all parties | ||
| 110 | involved in the production or distribution of the Data Set harmless | 110 | involved in the production or distribution of the Data Set harmless | ||
| 111 | for damages resulting from its use or interpretation." | 111 | for damages resulting from its use or interpretation." | ||
| 112 | }, | 112 | }, | ||
| 113 | { | 113 | { | ||
| 114 | "key": "Data Sharing Principle", | 114 | "key": "Data Sharing Principle", | ||
| 115 | "value": "The re-use of scientific data has the potential to | 115 | "value": "The re-use of scientific data has the potential to | ||
| 116 | greatly increase communication, collaboration and synthesis within and | 116 | greatly increase communication, collaboration and synthesis within and | ||
| 117 | among disciplines, and thus is fostered, supported and encouraged. | 117 | among disciplines, and thus is fostered, supported and encouraged. | ||
| 118 | Permission to use this dataset is granted to the Data User free of | 118 | Permission to use this dataset is granted to the Data User free of | ||
| 119 | charge subject to the following terms: Acceptable use. Use of the | 119 | charge subject to the following terms: Acceptable use. Use of the | ||
| 120 | dataset will be restricted to academic, research, educational, | 120 | dataset will be restricted to academic, research, educational, | ||
| 121 | government, recreational, or other not-for-profit professional | 121 | government, recreational, or other not-for-profit professional | ||
| 122 | purposes. The Data User is permitted to produce and distribute derived | 122 | purposes. The Data User is permitted to produce and distribute derived | ||
| 123 | works from this dataset provided that they are released under the same | 123 | works from this dataset provided that they are released under the same | ||
| 124 | license terms as those accompanying this Data Set. Any other uses for | 124 | license terms as those accompanying this Data Set. Any other uses for | ||
| 125 | the Data Set or its derived products will require explicit permission | 125 | the Data Set or its derived products will require explicit permission | ||
| 126 | from the dataset owner. Redistribution. The data are provided for | 126 | from the dataset owner. Redistribution. The data are provided for | ||
| 127 | use by the Data User. The metadata and this license must accompany all | 127 | use by the Data User. The metadata and this license must accompany all | ||
| 128 | copies made and be available to all users of this Data Set. The Data | 128 | copies made and be available to all users of this Data Set. The Data | ||
| 129 | User will not redistribute the original Data Set beyond this | 129 | User will not redistribute the original Data Set beyond this | ||
| 130 | collaboration sphere. Citation. It is considered a matter of | 130 | collaboration sphere. Citation. It is considered a matter of | ||
| 131 | professional ethics to acknowledge the work of other scientists. Thus, | 131 | professional ethics to acknowledge the work of other scientists. Thus, | ||
| 132 | the Data User will properly cite the Data Set in any publications or | 132 | the Data User will properly cite the Data Set in any publications or | ||
| 133 | in the metadata of any derived data products that were produced using | 133 | in the metadata of any derived data products that were produced using | ||
| 134 | the Data Set. Citation should take the following general form: | 134 | the Data Set. Citation should take the following general form: | ||
| 135 | Creator, Year of Data Publication, Title of Dataset, Publisher, | 135 | Creator, Year of Data Publication, Title of Dataset, Publisher, | ||
| 136 | Dataset identifier. For example: McKee, W. 2001. Vascular plant list | 136 | Dataset identifier. For example: McKee, W. 2001. Vascular plant list | ||
| 137 | on the Andrews Experimental Forest and nearby Research Natural Areas: | 137 | on the Andrews Experimental Forest and nearby Research Natural Areas: | ||
| 138 | Long-Term Ecological Research. Corvallis, OR: Forest Science Data | 138 | Long-Term Ecological Research. Corvallis, OR: Forest Science Data | ||
| 139 | Bank: SA002. [Database]. | 139 | Bank: SA002. [Database]. | ||
| 140 | http://www.fsl.orst.edu/lter/data/abstract.cfm?dbcode=SA002. (21 | 140 | http://www.fsl.orst.edu/lter/data/abstract.cfm?dbcode=SA002. (21 | ||
| 141 | October 2004) Acknowledgement. The Data User should acknowledge any | 141 | October 2004) Acknowledgement. The Data User should acknowledge any | ||
| 142 | institutional support or specific funding awards referenced in the | 142 | institutional support or specific funding awards referenced in the | ||
| 143 | metadata accompanying this dataset in any publications where the Data | 143 | metadata accompanying this dataset in any publications where the Data | ||
| 144 | Set contributed significantly to its content. Acknowledgements should | 144 | Set contributed significantly to its content. Acknowledgements should | ||
| 145 | identify the supporting party, the party that received the support, | 145 | identify the supporting party, the party that received the support, | ||
| 146 | and any identifying information such as grant numbers. For example: | 146 | and any identifying information such as grant numbers. For example: | ||
| 147 | Data sets were provided by the Forest Science Data Bank, a partnership | 147 | Data sets were provided by the Forest Science Data Bank, a partnership | ||
| 148 | between the Department of Forest Science, Oregon State University, and | 148 | between the Department of Forest Science, Oregon State University, and | ||
| 149 | the U.S. Forest Service Pacific Northwest Research Station, Corvallis, | 149 | the U.S. Forest Service Pacific Northwest Research Station, Corvallis, | ||
| 150 | Oregon. Significant funding for collection of these data was provided | 150 | Oregon. Significant funding for collection of these data was provided | ||
| 151 | by the National Science Foundation Long-Term Ecological Research | 151 | by the National Science Foundation Long-Term Ecological Research | ||
| 152 | program (NSF Grant numbers BSR-90-11663 and DEB-96-32921). | 152 | program (NSF Grant numbers BSR-90-11663 and DEB-96-32921). | ||
| 153 | Notification. The Data User will notify the Data Set Contact when any | 153 | Notification. The Data User will notify the Data Set Contact when any | ||
| 154 | derivative work or publication based on or derived from the Data Set | 154 | derivative work or publication based on or derived from the Data Set | ||
| 155 | is distributed. The Data User will provide the data contact with two | 155 | is distributed. The Data User will provide the data contact with two | ||
| 156 | reprints of any publications resulting from use of the Data Set and | 156 | reprints of any publications resulting from use of the Data Set and | ||
| 157 | will provide copies, or on-line access to, any derived digital | 157 | will provide copies, or on-line access to, any derived digital | ||
| 158 | products. Notification will include an explanation of how the Data Set | 158 | products. Notification will include an explanation of how the Data Set | ||
| 159 | was used to produce the derived work. Collaboration. The Data Set has | 159 | was used to produce the derived work. Collaboration. The Data Set has | ||
| 160 | been released in the spirit of open scientific collaboration. Data | 160 | been released in the spirit of open scientific collaboration. Data | ||
| 161 | Users are thus strongly encouraged to consider consultation, | 161 | Users are thus strongly encouraged to consider consultation, | ||
| 162 | collaboration and/or co-authorship with the Data Set Creator. By | 162 | collaboration and/or co-authorship with the Data Set Creator. By | ||
| 163 | accepting this Data Set, the Data User agrees to abide by the terms of | 163 | accepting this Data Set, the Data User agrees to abide by the terms of | ||
| 164 | this agreement. The Data Owner shall have the right to terminate this | 164 | this agreement. The Data Owner shall have the right to terminate this | ||
| 165 | agreement immediately by written notice upon the Data User's breach | 165 | agreement immediately by written notice upon the Data User's breach | ||
| 166 | of, or non-compliance with, any of its terms. The Data User may be | 166 | of, or non-compliance with, any of its terms. The Data User may be | ||
| 167 | held responsible for any misuse that is caused or encouraged by the | 167 | held responsible for any misuse that is caused or encouraged by the | ||
| 168 | Data User's failure to abide by the terms of this agreement." | 168 | Data User's failure to abide by the terms of this agreement." | ||
| n | n | 169 | }, | ||
| 170 | { | ||||
| 171 | "key": "Database Level", | ||||
| 172 | "value": "Project" | ||||
| 173 | }, | ||||
| 174 | { | ||||
| 175 | "key": "FIAR", | ||||
| 176 | "value": "No" | ||||
| 177 | }, | ||||
| 178 | { | ||||
| 179 | "key": "Host Institute", | ||||
| 180 | "value": " Long-term Ecological Research (LTER) Program" | ||||
| 181 | }, | ||||
| 182 | { | ||||
| 183 | "key": "Opening Degree", | ||||
| 184 | "value": "Open" | ||||
| 185 | }, | ||||
| 186 | { | ||||
| 187 | "key": "Organizer", | ||||
| 188 | "value": "LTER Network" | ||||
| 189 | }, | ||||
| 190 | { | ||||
| 191 | "key": "Region", | ||||
| 192 | "value": "Antarctic " | ||||
| 193 | }, | ||||
| 194 | { | ||||
| 195 | "key": "Source of Data Policy", | ||||
| 196 | "value": "Own" | ||||
| 197 | }, | ||||
| 198 | { | ||||
| 199 | "key": "Theme", | ||||
| 200 | "value": "Comprehensive" | ||||
| 169 | } | 201 | } | ||
| 170 | ], | 202 | ], | ||
| 171 | "groups": [ | 203 | "groups": [ | ||
| 172 | { | 204 | { | ||
| 173 | "description": "Inventory of Database for Earth Three Poles", | 205 | "description": "Inventory of Database for Earth Three Poles", | ||
| 174 | "display_name": "An Inventory of Database for Earth Three | 206 | "display_name": "An Inventory of Database for Earth Three | ||
| 175 | Poles", | 207 | Poles", | ||
| 176 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | 208 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | ||
| 177 | "image_display_url": | 209 | "image_display_url": | ||
| 178 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | 210 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | ||
| 179 | "name": "inventury-of-database-for-earth-three-poles", | 211 | "name": "inventury-of-database-for-earth-three-poles", | ||
| 180 | "title": "An Inventory of Database for Earth Three Poles" | 212 | "title": "An Inventory of Database for Earth Three Poles" | ||
| 181 | } | 213 | } | ||
| 182 | ], | 214 | ], | ||
| 183 | "id": "d81bbbe8-bec4-4520-9ac1-6d5299667558", | 215 | "id": "d81bbbe8-bec4-4520-9ac1-6d5299667558", | ||
| 184 | "isopen": false, | 216 | "isopen": false, | ||
| 185 | "license_id": "", | 217 | "license_id": "", | ||
| 186 | "license_title": "", | 218 | "license_title": "", | ||
| 187 | "maintainer": "", | 219 | "maintainer": "", | ||
| 188 | "maintainer_email": "", | 220 | "maintainer_email": "", | ||
| 189 | "metadata_created": "2022-04-05T06:44:10.675924", | 221 | "metadata_created": "2022-04-05T06:44:10.675924", | ||
| t | 190 | "metadata_modified": "2022-04-10T09:00:44.600236", | t | 222 | "metadata_modified": "2022-04-11T12:10:00.081145", |
| 191 | "name": "mcmurdo-dry-valleys-lter-mcm-data-explorer-dashboard", | 223 | "name": "mcmurdo-dry-valleys-lter-mcm-data-explorer-dashboard", | ||
| 192 | "notes": "Background The McMurdo Dry Valleys LTER project is an | 224 | "notes": "Background The McMurdo Dry Valleys LTER project is an | ||
| 193 | interdisciplinary study of the aquatic and terrestrial ecosystems in a | 225 | interdisciplinary study of the aquatic and terrestrial ecosystems in a | ||
| 194 | cold desert region of Antarctic . In 1992 this area was selected as a | 226 | cold desert region of Antarctic . In 1992 this area was selected as a | ||
| 195 | study site within the National Science Foundation's Long-term | 227 | study site within the National Science Foundation's Long-term | ||
| 196 | Ecological Research (LTER) Program. Details about the research can be | 228 | Ecological Research (LTER) Program. Details about the research can be | ||
| 197 | reviewed through the original 1992 research proposal to the National | 229 | reviewed through the original 1992 research proposal to the National | ||
| 198 | Science Foundation, or the most recent 2016 proposal, resulting in | 230 | Science Foundation, or the most recent 2016 proposal, resulting in | ||
| 199 | funding for another 6 years.", | 231 | funding for another 6 years.", | ||
| 200 | "num_resources": 1, | 232 | "num_resources": 1, | ||
| 201 | "num_tags": 0, | 233 | "num_tags": 0, | ||
| 202 | "organization": { | 234 | "organization": { | ||
| 203 | "approval_status": "approved", | 235 | "approval_status": "approved", | ||
| 204 | "created": "2020-04-30T11:11:08.802657", | 236 | "created": "2020-04-30T11:11:08.802657", | ||
| 205 | "description": "Aerospace Information Research Institute (AIR) | 237 | "description": "Aerospace Information Research Institute (AIR) | ||
| 206 | under the Chinese Academy of Sciences (CAS) was established in July | 238 | under the Chinese Academy of Sciences (CAS) was established in July | ||
| 207 | 2017, following the approval for consolidation of three CAS | 239 | 2017, following the approval for consolidation of three CAS | ||
| 208 | institutes: the Institute of Electronics (IECAS), the Institute of | 240 | institutes: the Institute of Electronics (IECAS), the Institute of | ||
| 209 | Remote Sensing and Digital Earth (RADI), and the Academy of | 241 | Remote Sensing and Digital Earth (RADI), and the Academy of | ||
| 210 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | 242 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | ||
| 211 | the outcome of CAS efforts towards reformation of its R&D system to | 243 | the outcome of CAS efforts towards reformation of its R&D system to | ||
| 212 | meet future R&D challenges and to better meet the national demands.", | 244 | meet future R&D challenges and to better meet the national demands.", | ||
| 213 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 245 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
| 214 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | 246 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | ||
| 215 | "is_organization": true, | 247 | "is_organization": true, | ||
| 216 | "name": "air", | 248 | "name": "air", | ||
| 217 | "state": "active", | 249 | "state": "active", | ||
| 218 | "title": "Aerospace Information Research Institute, CAS", | 250 | "title": "Aerospace Information Research Institute, CAS", | ||
| 219 | "type": "organization" | 251 | "type": "organization" | ||
| 220 | }, | 252 | }, | ||
| 221 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 253 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
| 222 | "private": false, | 254 | "private": false, | ||
| 223 | "relationships_as_object": [], | 255 | "relationships_as_object": [], | ||
| 224 | "relationships_as_subject": [], | 256 | "relationships_as_subject": [], | ||
| 225 | "resources": [ | 257 | "resources": [ | ||
| 226 | { | 258 | { | ||
| 227 | "cache_last_updated": null, | 259 | "cache_last_updated": null, | ||
| 228 | "cache_url": null, | 260 | "cache_url": null, | ||
| 229 | "created": "2022-04-05T06:45:20.748113", | 261 | "created": "2022-04-05T06:45:20.748113", | ||
| 230 | "datastore_active": false, | 262 | "datastore_active": false, | ||
| 231 | "description": "Background The McMurdo Dry Valleys LTER project | 263 | "description": "Background The McMurdo Dry Valleys LTER project | ||
| 232 | is an interdisciplinary study of the aquatic and terrestrial | 264 | is an interdisciplinary study of the aquatic and terrestrial | ||
| 233 | ecosystems in a cold desert region of Antarctic . In 1992 this area | 265 | ecosystems in a cold desert region of Antarctic . In 1992 this area | ||
| 234 | was selected as a study site within the National Science Foundation's | 266 | was selected as a study site within the National Science Foundation's | ||
| 235 | Long-term Ecological Research (LTER) Program. Details about the | 267 | Long-term Ecological Research (LTER) Program. Details about the | ||
| 236 | research can be reviewed through the original 1992 research proposal | 268 | research can be reviewed through the original 1992 research proposal | ||
| 237 | to the National Science Foundation, or the most recent 2016 proposal, | 269 | to the National Science Foundation, or the most recent 2016 proposal, | ||
| 238 | resulting in funding for another 6 years.\r\n", | 270 | resulting in funding for another 6 years.\r\n", | ||
| 239 | "format": "", | 271 | "format": "", | ||
| 240 | "hash": "", | 272 | "hash": "", | ||
| 241 | "id": "44abed18-c6fe-4d63-9481-45d3a60d97eb", | 273 | "id": "44abed18-c6fe-4d63-9481-45d3a60d97eb", | ||
| 242 | "last_modified": null, | 274 | "last_modified": null, | ||
| 243 | "metadata_modified": "2022-04-05T06:45:20.900804", | 275 | "metadata_modified": "2022-04-05T06:45:20.900804", | ||
| 244 | "mimetype": null, | 276 | "mimetype": null, | ||
| 245 | "mimetype_inner": null, | 277 | "mimetype_inner": null, | ||
| 246 | "name": "data-setMcMurdo Dry Valleys LTER (MCM) Data Explorer | 278 | "name": "data-setMcMurdo Dry Valleys LTER (MCM) Data Explorer | ||
| 247 | Dashboard", | 279 | Dashboard", | ||
| 248 | "package_id": "d81bbbe8-bec4-4520-9ac1-6d5299667558", | 280 | "package_id": "d81bbbe8-bec4-4520-9ac1-6d5299667558", | ||
| 249 | "position": 0, | 281 | "position": 0, | ||
| 250 | "resource_type": null, | 282 | "resource_type": null, | ||
| 251 | "size": null, | 283 | "size": null, | ||
| 252 | "state": "active", | 284 | "state": "active", | ||
| 253 | "url": "https://mcm.lternet.edu/power-search/data-set", | 285 | "url": "https://mcm.lternet.edu/power-search/data-set", | ||
| 254 | "url_type": null | 286 | "url_type": null | ||
| 255 | } | 287 | } | ||
| 256 | ], | 288 | ], | ||
| 257 | "state": "active", | 289 | "state": "active", | ||
| 258 | "tags": [], | 290 | "tags": [], | ||
| 259 | "title": "McMurdo Dry Valleys LTER (MCM) Data Explorer Dashboard", | 291 | "title": "McMurdo Dry Valleys LTER (MCM) Data Explorer Dashboard", | ||
| 260 | "type": "dataset", | 292 | "type": "dataset", | ||
| 261 | "url": "https://mcm.lternet.edu/power-search/data-set", | 293 | "url": "https://mcm.lternet.edu/power-search/data-set", | ||
| 262 | "version": "" | 294 | "version": "" | ||
| 263 | } | 295 | } |
