fred-atherden
commented
4 years ago @Melissa37, are these sec-type values which we need to error on, or are they section titles for DAS which we'll need to fire warnings on?
Title. Use a
element to contain the title (“Data Availability”), and contain the substance of the text within <p>. [[Validator tool result: WARNING: <title> not found, or content not match “Data Availability”]]</p> </blockquote> <p>Or both?</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/Melissa37"><img src="https://avatars.githubusercontent.com/u/6051876?v=4" />Melissa37</a> commented <strong> 4 years ago</strong> </div> <div class="markdown-body"> <p>@FAtherden-eLife The are the These are for the 'sec-type' values Content within '<title>' for DAS are display terms and so JATS4R passes no judgment on them, and it's up to the publisher what they add there.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/fred-atherden"><img src="https://avatars.githubusercontent.com/u/43879983?v=4" />fred-atherden</a> commented <strong> 4 years ago</strong> </div> <div class="markdown-body"> <p>Thanks - I was just confused because, in the recs it does say that the title should be 'Data availability' and says theres a warning for it:</p> <blockquote> <ol start="3"> <li>Title. Use a <code><title></code> element to contain the title (“Data Availability”), and contain the substance of the text within <code><p></code>. [[Validator tool result: WARNING: <code><title></code> not found, or content not match “Data Availability”]]</li> </ol> </blockquote> <p>I'll add include these for the <code>sec-type</code> test.</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/Melissa37"><img src="https://avatars.githubusercontent.com/u/6051876?v=4" />Melissa37</a> commented <strong> 4 years ago</strong> </div> <div class="markdown-body"> <p>@jeffbeckncbi Do you recall why we would insist on a display term at JATS4R? There was a rule but it's been edited out. Should we change the text in the Rec to not pass comment on the content of title?</p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>
@jeffbeckncbi
Rebecca Orris has identified a whole bunch more we can add to the exceptions list: Data availability Data availability statement(s) Data accessibility Data accessibility statement(s) Availability of data and material(s) Data and code availability Code and data availability Data and software availability Software and data availability Availability and data format(s) Availability of data Availability of supporting data Correlates of data availability Data archiving statement(s) Data deposition and access Direct link to deposited data Raw data availability