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

Enable multilanguage articles with translations in <sub-article>s #227

Open
12 tasks
lpanebr opened this issue Dec 10, 2021 · 6 comments
Open
12 tasks

Enable multilanguage articles with translations in <sub-article>s #227

lpanebr opened this issue Dec 10, 2021 · 6 comments

Comments

@lpanebr
Copy link

lpanebr commented Dec 10, 2021

Description

What is the Problem?

Translations in <sub-article> are not processed.

What is the benefit of solving the problem?

Many journals that use the Scielo and PMC JATS style[1,2], and tag multilingual articles with each translation in a <sub-article>[3] would be very happy and LOTs of content would be accessible to a larger audience.

How will we know when the problem has been solved?

The article will be presented with <sub-article> contents properly rendered. PMC and Scielo solve this differently:

  • PMC: Single HTML page and single PDF.
  • Scielo: Individual HTML and PDFs.

Examples:

How could we measure the impact or benefit of the solution?

Adding quick access links to the translations and other content in <sub-article>s and tracking it's usage in any analytics tools.

Documents and Resources

[1] https://www.ncbi.nlm.nih.gov/pmc/pmcdoc/tagging-guidelines/article/dobs.html#dob-multi-lang
[2] https://scielo.readthedocs.io/projects/scielo-publishing-schema/pt_BR/latest/tagset/elemento-sub-article.html?highlight=sub-article
[3] https://jats.nlm.nih.gov/publishing/tag-library/1.3/element/sub-article.html

Tasks

List of any initial tasks, if applicable, that you think might need to be done to progress this issue. e.g...

  • Investigate if there are any open-source search implementations out there.
  • Setup meeting to identify stakeholders.
  • Approving the task.
  • Collecting lots of XML samples. (just ask me)
  • Handling it to the developers for their initial technical evaluation and compilation of thoughts and list of concerns.
  • Evaluation and answering each concern. (just ask me)
  • Getting it done.
  • 🍾

Definition of Done

  • Solution properly handles multiple <sub-article>s for one article with many translations.
  • Solution deployed into a production environment and accessible to users.
  • Solution reviewed and approved by all stakeholders.
  • Solution has been announced to the community.
@gnott
Copy link
Member

gnott commented Dec 15, 2021

Thanks for adding the description here @lpanebr!

@lpanebr
Copy link
Author

lpanebr commented Jun 28, 2022

You're welcome @gnott ! Is this project still active and maintained by elife??

@gnott
Copy link
Member

gnott commented Jul 5, 2022

Hi @lpanebr, the short answer is eLife is still involved (via myself), and primarily only applying security updates rather than adding new features.

@lpanebr
Copy link
Author

lpanebr commented Jul 5, 2022

OK, thank you @gnott for your answer and work. This is such a great project!
It seems it's still in use by eLife so would by lying if I said I'm not curious in the long answer... 😉

The reason for my curiosity is both using it directly and also as the driver for the OJS lensGalley plugin (https://github.com/asmecher/lensGalley).

Thanks again!!

@gnott
Copy link
Member

gnott commented Jul 6, 2022

Very cool! I don't have a full picture of every project which used Lens and uses it now, and I worry about breaking things by accident, unless they are running from their own forks.

A slightly longer answer is due to limited developer time available, and other projects have a higher priority, even the Lens issues described for eLife articles (in a separate internal issues board) are waiting until there's more direction from the planning team.

Next up is to build better automated testing, so it doesn't require manual testing after to a code change.

@lpanebr
Copy link
Author

lpanebr commented Jul 6, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants