-
Notifications
You must be signed in to change notification settings - Fork 5
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
Prepare for Gigascience publication #69
Comments
AffiliationsFormat them for Gigascience like was done in greenelab/connectivity-search-manuscript@46e165b. Ensure affiliations listed multiple times are identical Switch to numbered affiliations, example at greenelab/meta-review@6ac55a9. Underway in #72 Switch reference formatSee the They provide example references here. Some snippets:
Our life will be much easier if as many references as possible use the "Article within a journal by DOI" to reduce citation format polymorphism. FiguresExport to EPS vectors, which are used for the PDF output. Otherwise PDF has low rez rasters that look bad. EPS does not support transparency, therefore some figures may have trouble exporting to EPS. There is a way the transparency can be flattened and replaced with non-transparent vectors, but not sure which applications support doing so. Solution: export to EPS from program creating figure if that works. If that doesn't work, export to PDF/SVG and use another program to convert to EPS. A high resolution raster format will also be helpful (which we likely already have). PNG or TIFF. These will get converted to JPEGs unfortunately. See greenelab/xswap-analysis#28 Add Gigascience required sectionsCheck what these are (depends on article type).
GigaDB reference |
Message from the editor Hongfang Zhang on 2023-12-18:
|
affiliations updated based on what was recently used for Gigascience at https://github.com/greenelab/connectivity-search-manuscript/blob/54317f330b3f7139d0d7f03d4b1187d01017e9d0/content/metadata.yaml refs #69
affiliations updated based on what was recently used for Gigascience at https://github.com/greenelab/connectivity-search-manuscript/blob/54317f330b3f7139d0d7f03d4b1187d01017e9d0/content/metadata.yaml refs #69
affiliations updated based on what was recently used for Gigascience at https://github.com/greenelab/connectivity-search-manuscript/blob/54317f330b3f7139d0d7f03d4b1187d01017e9d0/content/metadata.yaml refs #69
affiliations updated based on what was recently used for Gigascience at https://github.com/greenelab/connectivity-search-manuscript/blob/54317f330b3f7139d0d7f03d4b1187d01017e9d0/content/metadata.yaml refs #69
Okay I think the two remaining things we have to do before submission are:
|
Okay here's what remains:
Wrt to the supplement, there are references that show up in the main the reference list. I expect this to cause problems. So the options I see are:
@zietzm do you have a preference? |
Since I last re-ran the analysis, I can certainly re-export the figures to EPS. I'll get on that today! Regarding the supplement, I'm inclined to just make it a standalone PDF with its own citations. Seems like it would be easiest. |
Okay, we have a supplemental PDF we can use posted at #74 (comment). PDF vector images added in greenelab/xswap-analysis#28. So now the final step is modifying the DOCX, which I build in this job to create artifact The edits that I can think of:
@zietzm do you want to take the lead on this DOCX step? It will mostly be a subtractive process. |
Sure, I can do that! Two quick questions: Do the figures in the DOCX need to be replaced by the PDF figures, or will we include those as separate files? Should I upload the final DOCX to GitHub or just email it? |
I think separate files is okay.
Copying the submission dossier from email: |
ProofEmail to Casey on 2024-01-12:
I downloaded the proof and a view of changes and comments made by the copyeditor I will do a first pass and then notify when done. Note that the Aptara PXE editor can have problems with multiple concurrent sessions, so will close my session when complete and notify. |
Some items I didn't address. @zietzm perhaps you'd like to take it from here?
We will need a mailing address for Casey, the corresponding author.
In the proof, we need a short running title, which gets displayed at the top of each page. I put "An Edge Prior based on Node Degree", but would love more suggestions if anything comes to mind.
This might be fixed by switching Fig 10 to the supplementary figure citation. Have not checked. Hopefully we don't need to do restructuring here.
I believe this is referring to adding figure and table captions in the supplementary PDF and not as a description outside of the supplementary PDF. So this would require updating the supplemental PDF from #74.
I haven't done any of these. You can try to insert these details into the reference menu, but I can never get the formatting right this way, so I've just been replying in a comment to make them do it. Some of the publisher information might be in |
@dhimmel Yes, I'll get to work on those now! Thanks so much for all the help this morning! |
merges #75 from #69 (comment) Co-authored-by: Michael Zietz <michael.zietz@gmail.com>
Great. Fingers crossed this will be the final submission! |
This sounds good to me!
Unfortunately, 7A is referenced before 6. I manually swapped the figures, captions, and manually adjusted the two references to old table 6 and the one reference to old table 7.
Should be addressed in #76. I believe we must merge to have CI produce the PDF?
I think I actually got both of those solved. They are conference papers so I just looked up the official publishers and their locations. |
Awesome. I'm not sure about the process of updating the supplement, perhaps we provide that by email if there is no location in aptara PXE5 to update it. Let me know when you're done with the Aptara edits and then I'll export the diff of our edits and do one final look before submitting it. |
I finished my Aptara edits! Currently shows that the document is open elsewhere, but I don't have it open. Looks like the table caption didn't work properly as that table is HTML instead of markdown... I opened #77 Edit: Here's the updated supplement PDF: |
Proof submittedSubmitted the proof revisions and query responses on PXE5. Thanks @zietzm for the help. Here are the records at time of submission:
|
Thank you @dhimmel! Really appreciate all your help on these edits! |
ProofFrom GigaScience:
Things look good to me, but @zietzm would you like to give it a quick glance and make sure everything looks good to publish (especially the rearranged figure)? You can respond to their email directly with any issues or giving the green light. |
Thanks @dhimmel, will do this now! |
Now published at https://doi.org/10.1093/gigascience/giae001! |
to match rearrangement done at #69 (comment)
to match rearrangement done at #69 (comment)
Good news in email from 2023-11-01:
I'll note some things here that we'll want to do before the final DOCX submission to GigaScience based on what we learned from the connectivity-search-manuscript proofing process.
The text was updated successfully, but these errors were encountered: