Building a page of published work from a .bib file

[samclifford]

If we put our publications in a bibtex database we can put the following in an Rmd and knit to md to have it put all bib entries on the one page. Could be an alternative to the current landing page, but would need a custom CSL file to include both a local URL (as current page uses) as well as the URL for the paper/preprint/etc.

---
output: github_document
nocite: '@*'
---

[pearsonca]

two alternatives, both leveraging the github-pages (i.e., jekyll + liquid) framework:

• have a _pubs collection, make a .md file for each pub, and put the bib info in the YAML header. We would then have a publications.md page that uses liquid to display an entry + link for all the items in the _pubs collection. This approach could also standardize what seems to be happening currently with the pub-related pages. Instead of whatever is happening currently, people would just add what they want in the page about that paper to the body of the file, and the pages would be generated from that.
• (could also do this with _ncov, _dengue, _polio etc if we want to divide by topic area, or _draft, _preprint, _published if we want to sort by status - this allows for easier generation of landing pages by topic / status / etc. But: gets dicey if you want to organize things multiple ways)
• have _data/TOPIC1/, _data/TOPIC2/, etc folders, which are just the YAML headers in the previous section. This has the upside of supporting lots of ways of slicing / sorting the data, but doesn't make it easy to also generate a page along with the data.

By using either collections or data, we can use the github pages framework to do the scut work.

[pearsonca]

I do like supporting .bib files though - could write a small tool to inflate a .bib for a particular pub into a start for the files I suggested, or to deflate a target directory to a properly formatted .bib for all the pubs in that directory.

[samclifford]

It seems like there's no real appetite for this.