streamline bibtex import

[rschmehl]

I am using hugo academic to build a website for a large team that spans several organisations. The publications of this team are collected in a central bibtex file, which is large. An import with the present version of the academic admin tool still requires considerable manual work per publication:

• copying the generated *.bib file into cite.bib (required to activate the citation button)
• when the bibtex file contains an abstract entry this is included in the generated bib-file, which is generally not what users want that click the cite button.
• adding the projects identifier in the markdown file of the publication to link this publication to specific projects

With this pull request the manual work per publication is reduced to a minimum, regarding the bibtex-file as the single source of information.

• per publication a file cite.bib is generated
• the projects identifiers are auto-generated from corresponding entries in the central bibtex file. These projects entries can include several project identifier strings (without the dashes) separated by white space.
• The entries abstract and projects are removed from the file cite.bib that is generated per publication.

The only remaining work that needs to be done is to copy the PDF of the publications into the generated folders.

[rschmehl]

I am providing the input file, bibliography.bib, and the generated files, index.md and cite.bib.
files.zip

[gcushen]

Thanks for the suggestion.

The main direction for future work on this repo is to support using the main reference managers (e.g. Zotero and Mendeley) to manage almost all options for generating Academic publication pages. So your suggestion is very much aligned with this vision :)

The BibTeX spec does not have an entry named projects, and more importantly, such an entry wouldn't be compatible with the main reference managers like Zotero.

As discussed in other issues, we should use the extra field that is available in Zotero etc. to store key/value mapping for Academic options such as projects. The url entry can be used to store the paper URL.

[rschmehl]

Thanks for the quick reply. A simple fix would be to just swap the projects field with the extra field, passing only the values and let admin import interpret these as projects values for the generated markdown files. But this would work only when there is no other use for the extra field of the bibtex file?

[gcushen]

Closing in favour of #48