<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">OK, it sounds like you are responsible for archiving some of your data. If they are smallish and fairly static, you could deposit them in a generalist repository like Zenodo or Dryad, which will provide a DOI.<div class=""><br class=""></div><div class="">If you are committed to being the archive, you might enquire with California Digital Library. They can register DOIs with DataCite and they might provide the service for low to no cost since you are supporting the State of California.</div><div class=""><br class=""></div><div class=""><div class="">cheers,</div><div class=""><br class=""></div><div class="">-m. </div><div><br class=""><blockquote type="cite" class=""><div class="">On May 14, 2021, at 12:07 PM, Evan Burgess <<a href="mailto:evan.burgess@airbornesnowobservatories.com" class="">evan.burgess@airbornesnowobservatories.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Mark and Amber,<div class=""><br class=""></div><div class="">Thanks much for these thoughts, this is all very helpful! We are kind of in a weird space as a small for-profit startup built off a NASA JPL research program. We have a few lingering NASA projects that are firmly in the academic space, these data are already or will be going to a DAAC. However, moving forward, most of our data will be entirely separate from those academic/NASA channels. It will be paid for by state or private agencies, with an agreement that the data can be made public. Most companies would probably keep this data private, but as a public benefit corporation we really want the data to benefit all interested parties (of which there are lots including researchers and other non-paying agencies). Our plan has been to manage the data archive ourselves, currently the data is hosted on a public s3 bucket and linked to on our website rather crudely. Our interest for adding a DOI is partially a desire to follow best practice but also so our company can be more better attributed when the data is used.</div><div class=""><br class=""></div><div class="">Thanks, </div><div class="">Evan</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 13, 2021 at 4:04 PM Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" class="">parsonsm.work@icloud.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">Hi Evan,<div class=""><br class=""></div><div class="">Good on you for wanting your data to be referenced properly!</div><div class=""><br class=""></div><div class="">Is ASO the actual archive for the data or are they ulimately archived by NASA or another sponsor? Whoever mints the DOI should recognize that they are taking on a responsibility to maintain that DOI. That doesn’t necessarily mean that they must maintain the data, but they must ensure that the DOI continually links to the current state of the data (whether it has been moved, upgraded, deleted, etc). Once you determine who has that responsibility it will be easier to determine which DOI service to use. I suspect you may be able to tap into a NASA relationship with DataCite.</div><div class=""><br class=""></div><div class=""><div class="">cheers,</div><div class=""><br class=""></div><div class="">-m. </div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On May 13, 2021, at 3:14 PM, Evan Burgess via Esip-preserve <<a href="mailto:esip-preserve@lists.esipfed.org" target="_blank" class="">esip-preserve@lists.esipfed.org</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">Hey All,<div class=""><br class=""></div><div class="">I work for <a href="https://www.airbornesnowobservatories.com/" target="_blank" class="">Airborne Snow Observatories</a>. We release a lot of public geospatial data on snow water resources in California and Colorado. These data consist primarily of gridded geospatial products and pdfs with discussion and analyses of these products. The data is used by both academia and operational water management agencies in real-time and is available on our website.</div><div class=""><br class=""></div><div class="">We are looking into our options for minting DOIs for each of these datasets. We originally looked at DataCite but found it to be prohibitively expensive. I'm curious if anyone has suggestions for DOI minting options that are more cost effective and appropriate for this type of data and use case.</div><div class="">We recently have looked into <a href="https://www.crossref.org/services/content-registration/" target="_blank" class="">Crossref</a>, which seems much cheaper but I'm unsure if disadvantages may be lurking. Any advice on the matter would be greatly appreciated!</div><div class=""><br class=""></div><div class="">Many thanks,</div><div class="">Evan</div></div>
<br class="">_______________________________________________<br class="">Esip-preserve mailing list<br class="">To start a new topic: <a href="mailto:Esip-preserve@lists.esipfed.org" target="_blank" class="">Esip-preserve@lists.esipfed.org</a><br class="">To unsubscribe and manage prefs: <a href="https://lists.esipfed.org/mailman/listinfo/esip-preserve" target="_blank" class="">https://lists.esipfed.org/mailman/listinfo/esip-preserve</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div>
</div></blockquote></div><br class=""></div></body></html>