<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Quentin<div class=""><br class=""></div><div class="">In the latest IPT, we have introduced a third type of core which is the Sampling Event core to specifically accommodate this case.</div><div class="">It is still a star schema, and therefore has all the known limitations, but I think it does provide a model to accommodate the specific limitation that you describe.</div><div class=""><br class=""></div><div class="">The sampling event core allows you to describe e.g. the time, place and protocol of the sample (i.e. it is *very* similar to the occurrence fields) but by having it as the core, you can attach the extensions of “occurrences observed / collected” in each sampling event and also things like lists of species present or absent.</div><div class=""><br class=""></div><div class="">We are only just venturing into this new territory and are still working with early adopters to get reference datasets. Would you be keen to work on a pilot of this?</div><div class=""><br class=""></div><div class=""><i class="">For information:</i></div><div class=""><i class="">The DwC-A validator should work, but it’s not been tested in anger with this new format so we might run into some things we need to fix.</i></div><div class=""><i class="">The DwC-A assistant is something that in truth has not be well maintained for years having been developed externally by a contractor, and most likely will not work at all for this. That is not ideal but we haven’t had the resources to maintain it, and it is in very little use. The IPT is the primary tool for publishing along with the BioCASE and TAPIR tools and there are enough hosted IPT installations now that if someone did not wish to run one, a viable host would be offered.</i></div><div class=""><br class=""></div><div class="">I hope this helps clarify things, and we are very willing to help work through issues you may encounter in the sampling event core. </div><div class="">If you wish to simply play around, would you like an account on the demo site? <a href="http://ipt.gbif.org" class="">ipt.gbif.org</a></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Tim</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 11 Nov 2015, at 09:20, Quentin Groom <<a href="mailto:quentin.groom@plantentuinmeise.be" class="">quentin.groom@plantentuinmeise.be</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I'm rather confused how the Darwin Core Star Schema is meant to work for survey data.<div class=""><br class=""></div><div class="">Darwin Core can have one of two Core files, taxon or occurrence. The most appropriate for a survey would seem to be occurrence. So I imagine that in the star schema you could also have a related event file detailing the date and location of each survey and a non-core taxon file detailing the taxa that are observed.</div><div class=""><br class=""></div><div class="">However, this does not seem to be possible. The DWC-A validator (<a href="http://tools.gbif.org/dwca-validator/" class="">http://tools.gbif.org/dwca-validator/</a>), assumes only on core id in the core file so you can't link an occurrence both to a taxon and to an event. This is also true in the Darwin Core Archive Assistant (<a href="http://tools.gbif.org/dwca-assistant/" class="">http://tools.gbif.org/dwca-assistant/</a>). The solution seems to be to put all the information from the taxon core file into the occurrence file, but keep the separate event file linked with the core occurrence id.</div><div class=""><br class=""></div><div class="">Is this correct? It seems rather counter intuitive.</div><div class=""><br class=""></div><div class="">Regards</div><div class="">Quentin<br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Dr. Quentin Groom</div><div class="">(Botany and Information Technology)</div><div class=""><br class=""></div><div class="">Botanic Garden Meise</div><div class="">Domein van Bouchout</div><div class="">B-1860 Meise</div><div class="">Belgium</div><div class=""><br class=""></div><div class="">ORCID: 0000-0002-0596-5376</div><div class=""><br class=""></div><div class="">Landline; +32 (0) 226 009 20 ext. 364</div><div class="">FAX: +32 (0) 226 009 45</div><div class=""><br class=""></div><div class="">E-mail: <a href="mailto:quentin.groom@plantentuinmeise.be" target="_blank" class="">quentin.groom@plantentuinmeise.be</a></div><div class="">Skype name: qgroom</div><div class="">Website: <a href="http://www.botanicgarden.be/" target="_blank" class="">www.botanicgarden.be</a></div><div class=""><br class=""></div></div></div></div></div></div>
</div></div>
_______________________________________________<br class="">IPT mailing list<br class=""><a href="mailto:IPT@lists.gbif.org" class="">IPT@lists.gbif.org</a><br class="">http://lists.gbif.org/mailman/listinfo/ipt<br class=""></div></blockquote></div><br class=""></div></body></html>