To support adding clinical trials data to Crossref deposits, the data must be parsed from the article XML. They are specified in <related-object> tags present in the <article-meta> tag, sometimes inside the <abstract> but maybe not.
Since some other <related-object> tags may be present in the article-meta, it only looks for tags that have a @source-id-type attribute.
The data structure returned is a list of OrderedDict() containing key value data. This will later be used to populate objects and end up in Crossref and PubMed deposits.
Coverage increased (+0.0008%) to 99.711% when pulling 0148a0e0580d4fb4ada910a91177c128f3d13fe7 on clinical-trials into 3f5f796d105e25ec08b1edfdd93594404ed1e0eb on develop.
Re issue https://github.com/elifesciences/elife-crossref-feed/issues/146
To support adding clinical trials data to Crossref deposits, the data must be parsed from the article XML. They are specified in
<related-object>
tags present in the<article-meta>
tag, sometimes inside the<abstract>
but maybe not.Since some other
<related-object>
tags may be present in the article-meta, it only looks for tags that have a@source-id-type
attribute.The data structure returned is a list of
OrderedDict()
containing key value data. This will later be used to populate objects and end up in Crossref and PubMed deposits.