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

Foreseen change of JATS XMLs for IOP (Chinese Physics C), on June 3rd 2024 #321

Open
agentilb opened this issue Apr 4, 2024 · 2 comments
Assignees

Comments

@agentilb
Copy link
Collaborator

agentilb commented Apr 4, 2024

Hi,

Here is the description of the change, as received from the publisher:

I am writing to inform you of a forthcoming change to the XML format that you receive from IOPP. We are upgrading our content from the current JATS Journal Publishing 1.1 format to JATS Journal Publishing 1.3 format.

This upgrade will be implemented on the 3rd June 2024 and from that date all IOPP content will be supplied in the new 1.3 format. It is important to note that we will not be able to support the previous JATS 1.1 format from this point. No further changes to the content, its delivery method or delivery frequency are due to take place at this time.

Screenshot 2024-04-04 at 14 08 13 Screenshot 2024-04-04 at 14 08 27

The only change that you will see, initially, is that there will be a different DOCTYPE declaration on the files and a new value of the article/@dtd-version attribute. No other aspects of the XML files will change in June. In the longer term, we want to make use of some of the features of JATS 1.3 that are not in JATS 1.1, and this will involve some changes in the XML, but it won’t happen immediately.

Here is directory that contains the new structure of XMLs:
https://cernbox.cern.ch/s/abaxOriMmXP7Ls0

As far as I understand, there is no major change foreseen in June

@ErnestaP ErnestaP self-assigned this Jun 25, 2024
@ErnestaP
Copy link

This change does not influence harvesting and parsing :) @agentilb, can I close this issue?

@pamfilos
Copy link

let leave it here as reminder, we can close when we have updates from their side, or we move to crossref

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

3 participants