Related: #3140

Two questions about the first bullet point?

• why is a new tab preferable over downloading a file? If a user is going to import it into a reference manager (which I'm relatively sure is the usual case), they'll need to download a file: so "new tab" -> "download" vs "download" is an extra step?
• is there / should there be an API endpoint (or content-negotation) for downloading the citation?

This is a request from Gary. Other applications (Google Scholar) provide the .bib in a new tab and this preferable.

To the second point about including more info in the bibtex, these fields aren't showing up when importing citation into latex using standard bibtex setups:

• UNF
• Version
• Publisher

UNF and version number aren't being exported at all.
The repository name is in the publisher field but seems to be ignored.

Exported bibtex from dataset @djbrooke linked to in Harvard Dataverse:

@data{QSZMPD_2017,
author = {King, Gary and Pan, Jennifer and Roberts, Margaret E.},
publisher = {Harvard Dataverse},
title = {Replication data for: How the Chinese Government Fabricates Social Media Posts for Strategic Distraction, not Engaged Argument},
year = {2017},
doi = {10.7910/DVN/QSZMPD},
url = {http://dx.doi.org/10.7910/DVN/QSZMPD}
}

Please also remove the abstract field. it is a nice bit of metadata, but it is never used as part of a citation and just fills up your bibtex file with a lot of extra text.

these tickets should be attached to some planned release with a date. this is an old ticket.

I moved this to the "Ready" column so that we can get this estimated in sprint planning next week. This one fell through the cracks, my fault.

@thegaryking - I'll stop by to learn more about your thoughts on the release planning process.

@thegaryking We have a PR up for review with changes for everything requested except the abstract part. Can you provide a few more details about where you're seeing the abstract show up in BibTeX (or elsewhere)? Thanks!

Abstract ("description") is not part of the BibTex citation, but per Gary's comments above I have removed it from RIS and EndNote XML versions.

On 2cd3a2a; unable to reproduce this behavior (no quotation marks seen in exported bibtex):

@data{FK2/HUBG7P_2018, author = {Finch, Fiona}, publisher = {Root}, title = {Darwin's Finches}, year = {2018}, version = {V1}, doi = {10.5072/FK2/HUBG7P}, url = {https://doi.org/10.5072/FK2/HUBG7P} }

Hi @thegaryking, can you please link me to the citation where you're seeing this behavior? Thanks!

So in the title field for bibtex files, Dataverse needs to turn open quote characters into two back ticks (``) and closed quote characters into two apostrophes ('').

This is because when LaTex sees the regular quote character next to some letters, like "A, it turns that string into a letter with a diaeresis, like Ä. Is that right? (That's what I understand from this stackoverflow question.)

So in the title field for bibtex files, Dataverse needs to turn open quote characters into two back ticks (``) and closed quote characters into two apostrophes ('').

@jggautier created #5424 for the issue above about backticks.