<html><head></head><body><div style="color:#000; background-color:#fff; font-family:lucida console, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1483988507942_74408">Ken and James,</div><div id="yui_3_16_0_ym19_1_1483988507942_75041"><br></div><div id="yui_3_16_0_ym19_1_1483988507942_74691">Thank you for sharing this important issue.</div><div id="yui_3_16_0_ym19_1_1483988507942_74611"><br></div><div id="yui_3_16_0_ym19_1_1483988507942_74488">I am still not certain about the implications of using the LTER Data Portal as the sole archive center of each site's data but two things come to my mind:</div><div id="yui_3_16_0_ym19_1_1483988507942_74632"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_74666">1. I think I misunderstood the EDI members in our last meeting; I was certain that they said that centralization of the LTER data archiving and sharing was eminent.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_74752">2. I think the data archival distribution paradigm has many obvious advantages and even more, our present "centributed" (like we once called in the 90s) data archival model has even more advantages.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_75040"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_75043">I can imagine James' dissapointment when NSF reacted that way but I am very glad that they still favor site's data archival.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_76522"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_76520">In regard to possible conflicts in data policies, that is an inevitable issue that people in the EDI in collaboration with the NCO will have to address and resolve.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_75322"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_75206">EDA<br></div><div id="yui_3_16_0_ym19_1_1483988507942_74233"><span></span></div><div id="yui_3_16_0_ym19_1_1483988507942_74235"> </div><div class="signature" id="yui_3_16_0_ym19_1_1483988507942_74234">Eda C. Melendez Colom<br> Information Manager<br> LTER Program<br> University of Puerto Rico<br> Tel. (787) 764-0000 (1-88225)<br> Fax (787) 772 -1481</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1483988507942_74814"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1483988507942_74820" style="display: block;"> <div style="font-family: lucida console, sans-serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1483988507942_74819"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1483988507942_74818"> <div dir="ltr" id="yui_3_16_0_ym19_1_1483988507942_74817"> <font id="yui_3_16_0_ym19_1_1483988507942_74816" face="Arial" size="2"> <hr id="yui_3_16_0_ym19_1_1483988507942_75207" size="1"> <b><span style="font-weight:bold;">From:</span></b> Ken Ramsey <kramsey@jornada-vmail.nmsu.edu><br> <b><span style="font-weight: bold;">To:</span></b> IM Listsvr <im@lternet.edu>; jlaundre@mbl.edu <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, January 6, 2017 1:05 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [LTER-im] Update on replicating Arctic LTER datasetst to the Arctic Data Center<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1483988507942_74822"><br>Hi Jim,<br clear="none"><br clear="none">This sounds good for the most part. I do not think that the LTER data<br clear="none">policies were intended to exclude Data One or other portals from using<br clear="none">or re-distributing our datasets. I think the exclusion of non-commercial<br clear="none">reuse of research data was meant to keep our data freely available and<br clear="none">that they cannot charge for use of publicly funded datasets.<br clear="none"><br clear="none">Regarding the change to EML, it seems that the simplification of the<br clear="none">use of <funding><para> will lead to issues if the EML specification is<br clear="none">not updated to include the funding agency as EDI will support more than<br clear="none">NSF. I seem to remember that Some LTER sites are not funding by NSF,<br clear="none">although I may be mistaken. What happens if EDI should include agencies<br clear="none">other than NSF in the future?<br clear="none"><br clear="none">Overall, this sounds like a good compromise. How do we update the LTER<br clear="none">data policies for the LTER Network and PASTA/EDI? Would this be an<br clear="none">action item we address at the annual meeting in conjunction with the<br clear="none">LTER EB?<br clear="none"><br clear="none">Ken<br clear="none"><br clear="none"><div class="yqt2272543576" id="yqtfd64225"><br clear="none">>>> James Laundre <<a shape="rect" ymailto="mailto:jlaundre@mbl.edu" href="mailto:jlaundre@mbl.edu">jlaundre@mbl.edu</a>> 2017-01-06 09:46 AM >>><br clear="none"><br clear="none">Replicating Arctic LTER datasets to the Arctic Data Center. <br clear="none"><br clear="none"><br clear="none">As I mentioned in a VTC last Dec one of our PI's final report to NSF<br clear="none">for their Arctic Observing Network (AON) project was being held up<br clear="none">because the data was archived on the LTER Data Portal instead of the new<br clear="none">NSF Arctic Data Center ( <a shape="rect" href="https://arcticdata.io/" target="_blank">https://arcticdata.io </a>). In previous reports<br clear="none">this was considered fine. However this time the comment he received was:<br clear="none"><br clear="none"><br clear="none"><br clear="none">" The NSF-LTER data portal is certainly a national archive, but the<br clear="none">problem is that it has some restrictions on data use. AON data, on the<br clear="none">other hand, is for unrestricted use. .... AON data should be archived on<br clear="none">the Arctic Data center." <br clear="none"><br clear="none">So why can’t the Arctic Data Center pull the data from the LTER Data<br clear="none">Portal? After all they are both Data ONE nodes and it would be messyto<br clear="none">have two different DOIs for the same data. Well after several back and<br clear="none">forth emails, modifications on my end and by Mark and Duane, the Arctic<br clear="none">Data Center was able to replicated metadata and data into the Arctic<br clear="none">Data Center. The main issues that prevented the data from replicating<br clear="none">are listed below: <br clear="none"><br clear="none"><br clear="none">First: The LTER intellectual rights section of the metadata document s<br clear="none">did not meet with NSF Polar Programs policy.<br clear="none"><a shape="rect" href="https://www.nsf.gov/pubs/2016/nsf16055/nsf16055.jsp" target="_blank">https://www.nsf.gov/pubs/2016/nsf16055/nsf16055.jsp </a>. In particular<br clear="none">where the LTER rights policy states: <br clear="none"><br clear="none">“1) Acceptable use . Use of the dataset will be restricted to<br clear="none">academic, research, educational, government, recreational, or other<br clear="none">not-for-profit professional purposes. The Data User is permitted to<br clear="none">produce and distribute derived works from this dataset provided that<br clear="none">they are released under the same license terms as those accompanying<br clear="none">this Data Set. Any other uses for the Data Set or its derived products<br clear="none">will require explicit permission from the dataset owner. <br clear="none"><br clear="none">2 ) Redistribution . The data are provided for use by the Data User.<br clear="none">The metadata and this license must accompany all copies made and be<br clear="none">available to all users of this Data Set. The Data User will not<br clear="none">redistribute the original Data Set beyond this collaboration sphere.”<br clear="none"><br clear="none"><br clear="none">To quote an email; <br clear="none"><br clear="none"><br clear="none">“ These two restrictions make publishing the data in the Arctic Data<br clear="none">Center difficult. The first seems contrary to the policy for AON data in<br clear="none">that they are to be made publicly available (within 6 months of<br clear="none">collection). The second limitation effectively disallows the Arctic Data<br clear="none">Center (and DataONE) from distributing the data. <br clear="none"><br clear="none">In archiving data in the Arctic Data Center, the goal is to make the<br clear="none">data and metadata publicly available and usable without restriction, and<br clear="none">so we’ve been using the Creative Commons Public Domain Dedication<br clear="none">(CC-0) or the Attribution (CC-BY) license for new submissions. ” <br clear="none"><br clear="none">My solution was to modify the license to Attribution (CC-BY) license.<br clear="none">See below for the Intellectual Rights wording used. <br clear="none"><br clear="none">Second (a minor issue): There were differences in how the funding was<br clear="none">entered in the metadata (/eml/dataset/project/funding/para) field. We<br clear="none">had it as a paragraph describing the NSF funding grant number. The<br clear="none">Arctic Data Center just wanted the number as below: <br clear="none"><br clear="none"><br clear="none"><funding> <br clear="none"><para>100000</para> <br clear="none"><para>110000</para> <br clear="none"><para>06000</para> <br clear="none"></funding> <br clear="none"><br clear="none"><br clear="none"><br clear="none">Other issues between the LTER Data Portal and Arctic Data Center were<br clear="none">addressed by Mark and Duane and staff at the Arctic Data Center. <br clear="none"><br clear="none"><br clear="none">I have more datasets that need to be replicated to the Arctic Data<br clear="none">Center. Hopefully before the next reports are due. <br clear="none"><br clear="none"><br clear="none">Jim <br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">---------------------------------------------------------------------------------------------------------------------<br clear="none"><br clear="none">Intellectual Rights <br clear="none"><br clear="none"><br clear="none">This work is licensed under the Creative Commons Attribution 4.0<br clear="none">International License. To view a copy of this license, visit<br clear="none"><a shape="rect" href="http://creativecommons.org/licenses/by/4.0/" target="_blank">http://creativecommons.org/licenses/by/4.0/. </a><br clear="none"><br clear="none"><br clear="none">The re-use of scientific data has the potential to greatly increase<br clear="none">communication, collaboration and synthesis within and among disciplines,<br clear="none">and thus is fostered, supported and encouraged. Permission to use this<br clear="none">dataset is granted to the Data User free of charge subject to the<br clear="none">following terms: <br clear="none"><br clear="none">1. Citation. It is considered a matter of professional ethics to<br clear="none">acknowledge the work of other scientists. Thus, the Data User should<br clear="none">properly cite the Data Set in any publications or in the metadata of any<br clear="none">derived data products that were produced using the Data Set. <br clear="none">2. Acknowledgment. The Data User should acknowledge any institutional<br clear="none">support or specific funding awards referenced in the metadata<br clear="none">accompanying this dataset in any publications where the Data Set<br clear="none">contributed significantly to its content. Acknowledgements should<br clear="none">identify the supporting party, the party that received the support, and<br clear="none">any identifying information such as grant numbers. For example: Data<br clear="none">sets were provided by the Arctic LTER. This material is based upon work<br clear="none">supported by the National Science Foundation under Grants # ... ... and<br clear="none">#.... <br clear="none">3. Notification. The Data User will notify the Data Set Contact when<br clear="none">any derivative work or publication based on or derived from the Data Set<br clear="none">is distributed. The Data User will provide the data contact with two<br clear="none">reprints of any publications resulting from use of the Data Set and will<br clear="none">provide copies, or online access to, any derived digital products.<br clear="none">Notification will include an explanation of how the Data Set was used to<br clear="none">produce the derived work. <br clear="none">4. Collaboration. The Data Set has been released in the spirit of open<br clear="none">scientific collaboration. Data Users are thus strongly encouraged to<br clear="none">consider consultation, collaboration and/or co-authorship with the Data<br clear="none">Set Creator. <br clear="none"><br clear="none"><br clear="none">Disclaimer. While substantial efforts are made to ensure the accuracy<br clear="none">of data and documentation contained in this Data Set, complete accuracy<br clear="none">of data and metadata cannot be guaranteed. All data and metadata are<br clear="none">made available "as is". The Data User holds all parties involved in the<br clear="none">production or distribution of the Data Set harmless for damages<br clear="none">resulting from its use or interpretation. <br clear="none"><br clear="none">-- <br clear="none"><br clear="none">James Laundre <br clear="none">Arctic LTER <br clear="none">Marine Biological Lab <br clear="none">7 MBL St. <br clear="none">Woods Hole, MA 02543 <br clear="none">Phone:508 289 7476 <br clear="none">Email: <a shape="rect" ymailto="mailto:jlaundre@mbl.edu" href="mailto:jlaundre@mbl.edu">jlaundre@mbl.edu</a> <br clear="none">_______________________________________________<br clear="none">Long Term Ecological Research Network<br clear="none">im mailing list<br clear="none"><a shape="rect" ymailto="mailto:im@lternet.edu" href="mailto:im@lternet.edu">im@lternet.edu</a><br clear="none"><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>