Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Related articles #1337

Open
JGilbert-eLife opened this issue Jul 1, 2019 · 0 comments
Open

Related articles #1337

JGilbert-eLife opened this issue Jul 1, 2019 · 0 comments
Assignees
Labels
erudit Érudit Issues feature-request A formal Texture feature specification

Comments

@JGilbert-eLife
Copy link
Collaborator

Description

A related article link is used to connect an article to one or more articles with which it has some sort of relationship. This is used to denote co-submissions, article/commentary pairs and link a correction notice to the corrected article.

User stories

Author

  1. As an author, I want to be able to see if my article is linked to one or more additional articles.

Production staff

  1. As production staff, I want to be able to link two articles so that I can indicate they should be read together.
  2. As production staff, I want to be able to remove a related article link so that I can respond to changes in publication plans or correct errors.
  3. As production staff, I want to be able to see the type of related article link so that I can check this is correct.
  4. As production staff, I want to be able to change the type of link so that I can correct any errors.

But what if . . . ?

Consideration

  • It is assumed that related articles will have a DOI and so the linking uses ext-link-type="doi".
  • One article can be linked to multiple others.
  • It is a PMC requirement to have an @id on the related article link. It serves no internal value or purpose (eLife tried to have different definitions for different relationships but it was very hard to enforce and maintain).
  • There is a suggested usage list of @related-article-type on the JATS documentation: https://jats.nlm.nih.gov/archiving/tag-library/1.2/attribute/related-article-type.html
  • As an example of this, eLife uses for following link types to internally connect different types of article:
    • Research to Research (or Feature to Feature): related-article-type="article-reference"
    • Research to Insight: related-article-type="commentary"
    • Insight to Research: related-article-type="commentary-article"
    • Correction to Research: related-article-type="corrected-article"
  • It cannot be assumed that the related article will be another article from the same journal or the same publisher
  • For eLife, these relationships will need to be connected to the production dashboard so that we can determine the status of linked articles (published, in production, not in production etc).
  • The eLife system of linking articles (within the journal) and integration with the dashboard assumes the data within the system managing the dashboard knows whether the other article is published, is within the production process, or is within the editorial process it can inform production staff of this status as it affects publication of this article - this likely will have no effect on Texture, however.
  • Érudit have suggested using related-article to connect translations to the original article as a possible future use-case for this function.

XML requirements

Example:

<related-article ext-link-type="doi" id="ra1" related-article-type="commentary-article" xlink:href="10.7554/eLife.41770"/>

PKP (and others), may want to use the attribute xlink:title to provide further semantic information. For example:

<related-article related-article-type="companion" vol="2" page="e359"
xlink:title="synopsis" xlink:href="10.1371/journal.pbio.0020359">
<article-title>How to Make a Mother in Five Easy Steps</article-title>
</related-article>

Mock ups

Proposal

@JGilbert-eLife JGilbert-eLife added the feature-request A formal Texture feature specification label Jul 1, 2019
@fabiobatalha fabiobatalha added the erudit Érudit Issues label Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
erudit Érudit Issues feature-request A formal Texture feature specification
Projects
None yet
Development

No branches or pull requests

5 participants