-
Notifications
You must be signed in to change notification settings - Fork 4
How to access the article id? #113
Comments
Yes, your understanding is correct, there needs to be an update in Encoda to expose that. I will try to do that today. |
This has been checked against GSDTT. Related to #413 and stencila/thema#113.
I have implemented this in Encoda. Now for an eLife article, the <ul data-itemprop="identifiers">
<li itemscope="" itemtype="http://schema.org/PropertyValue" itemprop="identifier">
<meta itemprop="propertyID"
content="https://registry.identifiers.org/registry/publisher-id"><span
itemprop="name">publisher-id</span><span itemprop="value">50356</span></li>
<li itemscope="" itemtype="http://schema.org/PropertyValue" itemprop="identifier">
<meta itemprop="propertyID" content="https://registry.identifiers.org/registry/doi">
<span itemprop="name">doi</span><span itemprop="value">10.7554/eLife.50356</span></li>
<li itemscope="" itemtype="http://schema.org/PropertyValue" itemprop="identifier">
<meta itemprop="propertyID"
content="https://registry.identifiers.org/registry/elocation-id"><span
itemprop="name">elocation-id</span><span itemprop="value">e50356</span></li>
</ul> I have tested this against https://search.google.com/structured-data/testing-tool/ and it looks good there: Note that the id I shall follow up with a PR that upgrades the version of Encoda (which should be in the process of getting released as I write). |
🎉 This issue has been resolved in version 1.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I need to access the id of an eLife article in order to be able to populate the lists introduced in #111. I think it's represented by the data structure described at https://github.com/stencila/thema/blob/next/src/examples/articleKitchenSink.json#L66(?) which is:
It looks like the
identifiers
block maps toin the generated
selectors.css
, but the individual identifierpublisher-id
doesn't have a selector.Querying the DOM of each example artilce using e.g.
returns
null
in the browser in all cases, suggesting that no identifiers are coming through as yet.Is my understanding correct? Is there something extra I need to do in order to get this data, or does it depend on a change to Encoda to expose it?
The text was updated successfully, but these errors were encountered: