Comments (14)
Bump
from article_templates.
Good question. It will appear on the website with all the metadata/branding volume information, but it's not clear how to have the PDF have the information as well. We'll have to think about that.
from article_templates.
Seems like this is something we can ask Scholastica, @mrshirts , though I would assume they are not going to be processing our PDFs to add anything to them, so they will probably say, "Well, that's your concern."
Assuming they are not helpful, what about:
a) We add something to the LaTeX templates that says "for citation details, visit (url)" and give the URL of the main README.md for their github repo
b) Upon publication we have them update the README.md of their GitHub repo to give citation details
That's not ideal though; better would be to have the citation details in the PDF itself.
What if we made this the last step in the review process? Specifically, once we accept the article, we assign it to an "issue" and give it "page numbers" and then we (or they) can do a PR to a branch of their article which adds these to a header (?) of the article and generates a final PDF for publication. Then we do another PR to remove these so they can make subsequent updates to the article without carrying out volume/page numbers.
from article_templates.
not going to be processing our PDFs to add anything to them
They are not.
I think the "last step in review" is decent. If we set up the template right, we could have a boolean that says whether it is for publication or not, and what the issue/volume number is. Editors could even submit it as a PR themselves.
from article_templates.
I agree with the "last step in review" approach - a few variables and a macro should cover the TeX apart from the changes in the template.
from article_templates.
Is this something you're able to do @dwsideriusNIST ?
from article_templates.
I can write the TeX variables and macros first and just use a placeholder text somewhere in the frontmatter to debug it.
For modifications to the template, we'll need to first decide where/how to put the issue/page/DOI info [I would suggess KISS, replicate something like ACS or AIP] and then probably need help from @liantze or someone with similar skills.
from article_templates.
How about an option like this:
Check the footer of any of the pages.
Question: since there is no print version, are articles assigned an article number (like JCP) or a page identifier. Followup question: if there is an article number, is it part of the DOI? (the class macro could build the DOI from the article number if the relationship is deterministic.)
from article_templates.
Good question about DOI. I will check with CU Libraries about how we will assign them - the decided they would pay the subscription, but we didn't work out how we would do the logistics of assigning.
from article_templates.
I like that look, @dwsideriusNIST .
from article_templates.
Here's a minor update, making the DOI a clickable link.
I'll await an answer from @mrshirts regarding the DOI and article number before submitting a PR. The code is pretty straightforward, so the final modifications will not be difficult.
from article_templates.
I talked to my library contact; CU procurement (as anticipated) is still dragging out the process of the contract with CrossRef, so we still don't know the exact details of DOI numbering. We will have our own root DOI, for the journal, but I don't know how the numbers are generated. I think worst case scenario, we just plug in the number as a PR. That may be part of the editorial process; we (one of the editors) creates a branch with the necessary modifications that they can generate the final PDF.
My imagination is that we are going to be only dealing with 5-10 new papers each month (filtering out a lot at the pre-submission letter level), so this level of work will not be too hard to handle.
from article_templates.
@dwsideriusNIST that looks really elegant and nice. 👍
from article_templates.
@davidlmobley Thanks, the updated code is in PR #56
from article_templates.
Related Issues (20)
- Section / subsection titles intruding into gutter and margins HOT 9
- Number references by order of appearance HOT 4
- Reference standards for bibliography. HOT 26
- Templates producing weird 'fi' characters? HOT 6
- How to include version number in the title of articles HOT 14
- Reference formatting: should pMID's be in the references? HOT 5
- Bolding of Editor names, no author names HOT 2
- Posting DOI's properly in articles and on website HOT 10
- Can we figure out how to make white-spacing easier? HOT 1
- List of things to fix/adjust before issue 1 published (we will ask for people to redo the templates then). HOT 23
- Issue number HOT 9
- Force people to include licensing terms by including it in the template? HOT 32
- Create a way to add translators to the article? HOT 3
- Template had old name for software analyses section HOT 1
- Switch from `natbib` to `biblatex` in `livecoms` document class HOT 12
- Consider using Github's "template repository" mechanism
- Bibliography Modernization HOT 4
- Fix display long URLs in GitHub link HOT 1
- Consider adding line numbers to review versions?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from article_templates.