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

Compile online packages according to the new Open Issue structure for delivering individual articles that are part of an issue. #166

Closed
eliselavy opened this issue Dec 12, 2022 · 9 comments
Assignees

Comments

@eliselavy
Copy link
Collaborator

eliselavy commented Dec 12, 2022

all necessary information for you to prepare the online packages according to the new Open Issue structure for delivering individual articles that are part of an issue.

In the volume tag, the attribute content-type="open-issue" needs to be included.
Example: 32

Attached, you can find the unreleased XML guidelines which contain information on Open Issues. The above is detailed at anker #volume-open-issues (heading Open Issues), the other important section is #folder-structure-open-issue-articles (heading Open Issue Articles), which explains the folder structure.

What may be interesting is the fact that apparently, an issue.xml is not mandatory:
“To capture their appearance within the issue ToC a separate Issue-XML shall be delivered along with the article.“
This means that you should only have to supply article packages, if the order in which articles appear is not that important. It may then be difficult to sort an editorial that is published last in the first place of the ToC, though.

Another difference I saw is that an additional “oi” must be contained in the filename of the ZIP file: {journal-code-online}{article-id}oi{timestamp}.zip. Also, the package name is different to what you last supplied, because it is technically an article package.

Additionally, the folder that contains the article PDF and the article XML has an “.open-issue” at the end. Also, it is on the first level of the package.

@eliselavy
Copy link
Collaborator Author

@eliselavy
Copy link
Collaborator Author

@eliselavy eliselavy reopened this Dec 14, 2022
@eliselavy
Copy link
Collaborator Author

An example package has been generated based on a JDH's article example.

jdh_jdh-2021-1003_oi_2023-02-02--19-03-40.zip

Take care about:

  • naming of the zip
  • naming the main directory

@eliselavy
Copy link
Collaborator Author

Take into account this package:

The difference is the folder structure. The issue folder needs to be on the first level.

jdh_jdh-2021-1003_oi_2023-02-03--10-56-40.zip

@eliselavy
Copy link
Collaborator Author

@eliselavy
Copy link
Collaborator Author

In developemnt- still not test made with DG
Will be for the issue 3 in place
issue 2 need to be integrated manually. result will be 26/05/2023

@eliselavy
Copy link
Collaborator Author

By delivering packages for:

Regarding the package you sent: It looks great, but the folder structure / ZIP naming is not in line with our requirements. Please find attached a version I adjusted manually. If you compare it with your package, the differences become clear, I believe, but let me know in case you want me to describe them again.

@eliselavy
Copy link
Collaborator Author

To test now with issue 3 with 5 articles

@eliselavy
Copy link
Collaborator Author

see #240

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

1 participant