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

Adotar recomendações JATS4R: Disclosure of conflicts of interest/competing interests #862

Open
RPostalli opened this issue Oct 2, 2019 · 1 comment
Assignees
Labels
Tarefa Tarefa

Comments

@RPostalli
Copy link
Contributor

Relação com estudo: #823

https://jats4r.org/conflict-of-interest-statements

Se usarmos para SPS 1.10 a JATS 1.2, substituir o tipo de fn "conflict" por "COI-statement"

Motivação: because “conflict” carries a higher potential to be misinterpreted as indicating the existence of a conflict within the paper, rather than just the existence of a COI statement.

Na documentação SPS 1.10 mudar em fn > notas de autor

  • O tipo de fn da tabela de valores;
  • Os exemplos de XML.

OBS: Revisar todos os exemplos da documentação que possam ter fn do tipo conflict.

@RPostalli RPostalli added this to the versão 1.10 milestone Oct 2, 2019
@robertatakenaka robertatakenaka added the Tarefa Tarefa label Oct 14, 2019
@robertatakenaka robertatakenaka changed the title Estudar recomendações JATS4R: Disclosure of conflicts of interest/competing interests Adotar recomendações JATS4R: Disclosure of conflicts of interest/competing interests Nov 11, 2019
@RPostalli RPostalli self-assigned this Nov 21, 2019
RPostalli pushed a commit that referenced this issue Nov 21, 2019
@gustavofonseca gustavofonseca removed this from the versão 1.10 milestone Nov 22, 2019
@gustavofonseca
Copy link
Collaborator

A resolução deste ticket depende do uso da JATS 1.2.

@RPostalli RPostalli added this to the versão 1.10 (2022) milestone Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tarefa Tarefa
Projects
None yet
Development

No branches or pull requests

3 participants