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: Article publication and history dates #833

Open
RPostalli opened this issue Mar 20, 2019 · 2 comments
Open
Labels
Tarefa Tarefa

Comments

@RPostalli
Copy link
Contributor

Relação com estudo: #823

Para versão 1.10 acrescentar o uso de <pub-history> além de <history> descrita na JATS 1.2, mais acréscimo de <event> + <event-desc>.

Exemplo:

<pub-history>
<event>
<date date-type="submitted">
 <day>29</day>
 <month>01</month>
 <year>2001</year>
 </date>
<event-desc>The first version of this work was submitted 
 to Journal A and rejected because "the subject matter 
 is outside the editorial scope of the journal"</event-desc>
</event>
<event>
<date date-type="accepted">
  <day>15</day><month>06</month>
  <year>2017</year>
 </date>
<event-desc>A slightly reworked manuscript of this article was accepted at Journal B</event-desc>
</event>
</pub-history>

JATS recomenda que se pelo menos um data tiver descrição <event-desc>, todas as outras devem estar dentro de pub-history + event.

Best Practice: An may include those things that are usually handled by , such as when the manuscript was received or accepted, but an need not be recorded for any particular date in history. However, the JATS Standing Committee recommends that, within a single XML document, either the or the element be used. In other words, if some of your significant dates need to be described as events, all your dates should be inside in and the any existing elements within made into pub-history/event dates.

Exemplo:

<pub-history>
<event>
<date date-type="submitted">
 <day>29</day>
 <month>01</month>
 <year>2001</year>
 </date>
<event-desc>The first version of this work was submitted 
 to Journal A and rejected because "the subject matter 
 is outside the editorial scope of the journal"</event-desc>
</event>
<event>
<date date-type="accepted">
  <day>15</day><month>06</month>
  <year>2017</year>
 </date>
</event>
</pub-history>

Mais informações. JATS 1.2:

Pub-history: https://jats.nlm.nih.gov/publishing/tag-library/1.2/element/pub-history.html

Event: https://jats.nlm.nih.gov/publishing/tag-library/1.2/element/event.html

Possível uso de @event-type: https://jats.nlm.nih.gov/publishing/tag-library/1.2/attribute/event-type.html

Event-desc: https://jats.nlm.nih.gov/publishing/tag-library/1.2/element/event-desc.html

OBS: Verificar "Journal Article Versions (JAV): Recommendations of the NISO/ALPSP JAV Technical Working Group"

@RPostalli RPostalli added this to the versão 1.10 milestone Mar 20, 2019
@gustavofonseca gustavofonseca added this to Backlog in Atividades Oct 14, 2019
@gustavofonseca gustavofonseca moved this from Backlog to A fazer in Atividades Oct 14, 2019
@robertatakenaka robertatakenaka added the Tarefa Tarefa label Oct 14, 2019
@robertatakenaka robertatakenaka changed the title Estudar recomendações JATS4R: Article publication and history dates Adotar recomendações JATS4R: Article publication and history dates Nov 11, 2019
@gustavofonseca
Copy link
Collaborator

Como mencionei no ticket #873, a recomendação da JATS4R para Article publication and history dates ainda está pendente de ratificação, portanto esta atividade está bloqueada.

@cinthia-vieira
Copy link
Collaborator

A título de exemplo, alguns periódicos já adotam mais de uma data para revisões, como Cerâmica e Psicologia e Sociedade (psicologia-sociedade.zip).

Sei que a discussão sobre a documentação e uso das recomendações está em standby por ora, mas achei interessante anexar esses exemplos aqui :)!

@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

4 participants