From: William P. <wil...@ya...> - 2011-05-11 17:09:44
|
On May 11, 2011, at 12:10 PM, Carl Boettiger wrote: > Hi Dryad team, Treebase team, > > Thanks Hilmar, here's an example: > > For instance, this Dryad entry does not point to this treebase entry, Perhaps this is just because it is a recent entry? > The treebase entry in this cahas the Dryad id under a tag I didn't expect: <tb:title.study xmlns:tb="http://treebase.org/terms#">dryad_8661</tb:title.study> > > Meanwhile this Dryad entry does have the treebase identifer, but the treebase entry doesn't have the dryad identifier. > > -Carl Hi Carl, With respect the TreeBASE: <tb:title.study> is not the intended location for a dryad cross-reference -- it happens to be there because the title of the study is pre-populated with "dryad_8661", but the submitter can easily change this. Currently, TreeBASE exposes a DOI like so: <prism:doi xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/">10.1111/j.1469-8137.2011.03677.x</prism:doi> ... but that is for the doi to the publication, so we wouldn't want to use that for Dryad. On the other hand, I'd rather not do a schema change. But we have a field called "URL", which we could pre-populate with "http://dx.doi.org/10.5061/dryad.8661". This field is usually used for publications that don't have a doi, and instead have a particular url -- and it's rarely used. So one kluge (short of a schema change) is to pre-populate the url field with "http://dx.doi.org/10.5061/dryad.8661" and then expose that under the "prism:url" element. What would be a good element to use other than "prism:url" or "prism:doi"? bp |