Comments (12)
I'm not a biblatex expert myself but I opened a PR that demonstrates the basic steps this would involve
#85
I haven't yet spent much time trying to adapt the biblatex style to the livecoms one since this involves quite a bit of work.
Does it need to be fully reproduced?
There are a number of existing styles one could choose from (more on the biblatex contrib).
The PR uses the standard numeric-comp
style with one modification (displaying DOIs as valid hyperlinks).
It also contains a commented-out stab a displaying author names like in the current livecoms format (although that still needs more work).
Helpful material for further style adaptation:
from article_templates.
Thanks for this (and your other issues, which I or one of us will hopefully revisit soon -- all great points). On this one, would you be willing to submit a PR to change? I think we're amenable to switch. I haven't worked with biblatex much myself yet, but your point about web site and other citations sounds like a great reason to switch.
from article_templates.
@davidlmobley
Since I'm already using biblatex for the atomistic.software article, it would would be great to get some feedback on how closely the citation style needs to be reproduced, see comparison in
from article_templates.
Sorry for the delay; this has been in my tasks but I'm oversubscribed. I don't think the style needs to be exactly reproduced. cc @dwsideriusNIST and @mrshirts in case they have input. Let me see also if anyone else wants to provide feedback.
from article_templates.
sorry, missed this issue. I can't get to this for at least two weeks. One concern I have is how biblatex
will deal with the requirement of electronic links (DOI, pMID, etc.) and using just one. For some history, take a look at closed issues #53 and #62
from article_templates.
Hey Dan, just added the ASAP version for the atomistic.software article at https://github.com/ltalirz/livecoms-atomistic-software/blob/master/releases/LiveCoMS_Article_ASAP_V1.pdf
Perhaps have a look whether you notice anything that needs to be improved in the bibliography layout.
In this particular case there doesn't seem to be an issue with identifier precedence (but there isn't really much diversity besides DOIs and URLs).
from article_templates.
@ltalirz I'll fork your paper and inspect the difference between natbib and biblatex!
from article_templates.
@ltalirz would you create a branch of your paper with the atomistic.software.bl.bib
file included so that I run a comparison with natbib?
from article_templates.
@ltalirz would you create a branch of your paper with the
atomistic.software.bl.bib
file included so that I run a comparison with natbib?
Done! https://github.com/ltalirz/livecoms-atomistic-software/tree/natbib-comparison
from article_templates.
Following the editorial decision, I'll be reverting the bibliography of the atomistic.software article back to bibtex/natbib.
In order to serve as (part of the) motivation for the transition to biber/biblatex, below I'll document the issues encountered in this process when using the bibtex export of the zotero reference manager (and comparing it to the biber
export):
- handling of preprints: missing publisher
- handling of wikipedia articles: no URL and no visited date. To some degree this could be considered a question of taste; displaying the the URL is clearly more friendly to readers who want to view the article though.
Using @article
for bibtex
Using @inreference
(=item from a reference work) for biber
- handling of web sites: link text is missing link color & is non-breaking
- handling of software on github: no link to the repository
@dwsideriusNIST Any suggestions on how to work around these issues in bibtex for the time being?
from article_templates.
@ltalirz I'll attempt substitutions to solve these differences and then make a PR into your natbib-comparison branch
from article_templates.
Thanks a lot for the quick reply @dwsideriusNIST !
In the meanwhile I've fixed the issue with the URLs by modifying the settings of the zotero bibtex exporter (I believe the livecoms template expects them in the url
field, not in the howpublished
field).
P.S. One thing I came across (just for reference): zotero added type = {GitHub Guide}
to one of the entries, which caused the livecoms template to crash with You can't pop an empty literal stack for ...
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
- Formatting at time of publication (DOI, volume, etc.)? HOT 14
- 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
- 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.