-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use flat folder for JATS output #50
Conversation
@xuanxu I forgot, how are the artifacts copied to the target repository? Would it help if Inara took a target directory as another argument? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tarleb all files in the media
folder are copied to the target repository (also to a media
folder).
It is useful to get all media files from Inara in the media folder to know what to copy.
If we don't want the files to be in a final folder, I think is better to update it in the action pushing to the repo than here.
If I understand it correctly, we need:
Would it be easier to have jats file and images in a separate |
Yeah, I agree I think this would be the ideal solution here (a self-contained folder with everything in related to JATS, but also without any nested folders). |
0becb81
to
6c187e3
Compare
The JATS output file is placed in a folder `paper.jats` together with all media files. A truly flat structure is ensured, i.e., images are in the same folder as the resulting `paper.jats` file, and never in subfolders.
6c187e3
to
595d76a
Compare
I think this should do for now: Instead of a file
|
If that's easier, then we could also make that a |
Just for absolute clarity – the paper (e.g., |
I've prepared a branch in the GH actions to use this changes and keep the paper.jats folder when uploading to the papers repo. I'll merge the changes once this new version of inara is up. |
Yes, the |
Sorry, I'm not entirely clear on these questions:
|
I don't think so (every new commit is automatically re-publishing the Inara Docker image, right?). This is ready.
I'll merge them all at the same time tomorrow morning so I can monitor the actions. |
Thanks @tarleb! |
Hang on, isn't this URL incorrect? (i.e., I think it should be |
@arfon ouch, you are right, the files are in the right place but the URLs for images in the paper all point to |
Argh, my bad. I'll open a new PR in a minute. |
See #53. Do we want to keep the |
Merged! I think |
@arfon can you reaccept this one to regenerate the files? openjournals/joss-reviews#6017 |
Done |
Hey @tarleb, merging #53 seems to have modified the DTD declaration in the generated JATS file, and that makes the validation fail, see the first lines here: |
I've updated the XML validator gem so now we can validate both the Journal Publishing and the Journal Archiving and Interchange tag sets. Still not sure which of them we should use in Inara to generate the paper.jats file. |
This was not intended, sorry. I'll push the fix without PR. Note to self: better not to rush out patches at 2am after the ESC. |
hey @tarleb, I noticed that sometimes there's already a |
I've opened #54 for that. |
Hey both. Can I just check where we landed here? In the joss-papers repo I see a PR that's flattening folders (good), but doesn't seem to be putting the papers into a Also, this most recently-merged PR looks to still be using the old |
Right now, in the
The |
Ah great. So there's nothing to do here? |
Right, I think we're good. |
No description provided.