Comments (7)
I like the idea of a custom CSL style. We should emphasize what we think is important and not be beholden to tradition.
I generally agree with your points above. Alternative viewpoints on the following:
Just having a year for the date is too imprecise.
True, but we can't always reliably get more precise information. Metadata for some older manuscripts includes placeholder days and months in some cases (e.g. January 1 of the year). For some URLs, I doubt our ability to automatically retrieve accurate date stamps.
Authorship information is important, but often takes up too much of a reference.
This may be reader-dependent. I personally remember more past literature based on authors and dates than titles. Author X 2011
may mean something to me even though This is the title of my important paper
does not.
I don't see a need to print the URL. As a reader, I find it easier to search for the title than to type in a URL in most cases.
from rootstock.
I noticed in the meta review manuscript that some of the reference whitespace was missing when CSL fields were absent. See references 19 and 21 for examples in this version of the pdf.
Is that controlled by or fixable in the CSL file? It may only affect references that do not have a date.
Edit: It may be the lack of authors that is the problem, not the lack of date.
from rootstock.
Is that controlled by or fixable in the CSL file? It may only affect references that do not have a date.
Yeah this bugged me too when I was created the revised CSL. I played around a bunch and couldn't find a solution that would always perform appropriate newlines. I can look into a solution. We may have to print "No date", "Date missing", or "In press" as a workaround. Is that acceptable?
In general, when there's no date or other missing metadata, it's because the CSL is incomplete. So generally you should manually override this metadata. But yes, I agree that even with incompete metadata we should provide an aesthetic display.
from rootstock.
"In press" seems journal-specific, and not a good match for some of the resources we may link to. "No date" sounds better to me. Or can we use " " as the default?
Coming up with a placeholder for missing authors is even harder. It's not that content has "No authors", but rather that we don't know the specific author(s) to attribute sometimes.
from rootstock.
In the future, we may update the CSL to list book editors when there are no book authors. See greenelab/meta-review#74
from rootstock.
Another CSL suggestion from #132 (comment) is to add a default value when there is no author:
See meta-review for an example reference without an author. The title and venue are concatenated without whitespace.
The possible solution in #132 (comment) requires further testing.
from rootstock.
I think we did a good first pass at making an optimal CSL style for modern scholarly publishing. So will close this issue.
There are still some spacing issues which were exposed by looking at all metadata combinations in manubot/manubot#110.
from rootstock.
Related Issues (20)
- Review Commons / Template Compatibility HOT 1
- Deploy built DOCX to Github pages HOT 4
- load_bibliography: error reading 'content/manual-references.json' HOT 6
- no output saved in a forked manuscript HOT 4
- Editing Demo Manuboat HOT 1
- deployment timeout HOT 6
- Issues with local build command HOT 1
- Upgrade manubot to fix pubmed API calls. HOT 6
- Images are not shown in Word (docx) HOT 13
- Contributor Roles Taxonomy HOT 3
- AI workflow cannot create PR HOT 3
- best practice for integrating pandas-generated tables into manubot docs HOT 5
- Error: The process '/usr/share/miniconda3/condabin/conda' failed with exit code 1 HOT 5
- more elegant use of GitHub-set env variables HOT 10
- Change the name of the generated output pdf and .docx files HOT 4
- Convert repository to GitHub Template HOT 4
- Run failed: pages build and deployment HOT 1
- setup failing HOT 2
- docx fails to open HOT 4
- AppVeyor CI builds fail due to spellcheck dependencies HOT 3
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 rootstock.