Caution: JavaScript execution is disabled in your browser or for this website. You may not be able to answer all questions in this survey. Please, verify your browser parameters.

dblp survey: BibTeX export for data publications

 

Thank you for helping us.

Only very recently, we started indexing genuine data publications in dblp. You can read about these changes in our latest blog post.

Unlike traditional book or article publications, it is not immediately clear how to export the bibliographic metadata of those records to BibTeX. The goal of this survey is to obtain feedback on our new BibTeX export for data publications.

The results of this survey will not be made publicly available and are only intended for internal use within the dblp team.

This survey should take about 5-10 minutes to complete.

Privacy note

This survey is anonymous.

The record of your survey responses does not contain any identifying information about you, unless a specific survey question explicitly asked for it.

If you used an identifying token to access this survey, please rest assured that this token will not be stored together with your responses. It is managed in a separate database and will only be updated to indicate whether you did (or did not) complete this survey. There is no way of matching identification tokens with survey responses.

It is essential for this survey tool to store cookies with your web browser. The sole purpose of these cookies is to manage the state and flow of this survey. These cookies will be stored separately, and there is no way of linking them with your survey responses.

dblp BibTeX export for data publications
Please help us understand how content you are with our first implementation of the dblp BibTeX export for data publications.
(This question is mandatory)
1
How often are you using dblp's BibTeX export?
(This question is mandatory)
2

In our first implementation of a BibTeX export for data publications, we came up with the data fields shown in the examples below.

Please note that the YYYY-MM-DD string within the note field is intentional and meant to allow you to conveniently enter your concrete access date.

Example export in standard format option:

@misc{DBLP:data/10/HoffmannR18a,
  author       = {Oliver Hoffmann and
                  Florian Reitz},
  title        = {hdblp: historical data of the dblp collection (Version 1)},
  publisher    = {Zenodo},
  year         = {2018},
  month        = apr,
  howpublished = {\url{https://doi.org/10.5281/zenodo.1213051}},
  note         = {Accessed on YYYY-MM-DD.},
  url          = {https://doi.org/10.5281/zenodo.1213051},
  doi          = {10.5281/zenodo.1213051},
  timestamp    = {Mon, 13 Mar 2023 14:31:10 +0100},
  biburl       = {https://dblp.org/rec/data/10/HoffmannR18a.bib},
  bibsource    = {dblp computer science bibliography, https://dblp.org}
}

Example export in condensed format option:

@misc{DBLP:data/10/HoffmannR18a,
  author       = {Oliver Hoffmann and
                  Florian Reitz},
  title        = {hdblp: historical data of the dblp collection (Version 1)},
  publisher    = {Zenodo},
  year         = {2018},
  month        = apr,
  howpublished = {\url{https://doi.org/10.5281/zenodo.1213051}},
  note         = {Accessed on YYYY-MM-DD.}
}

Is at least one of these two export options and their content adequate for the purpose of citing data publications in your next article?

3
Do you encounter any concrete problems with using the BibTeX export as given in Question 2 above? Please let us know!
4

We have decided to use an @misc entry type when exporting BibTeX for data publications. Do you agree with this decision or would you prefer us to use a different BibTeX entry type?

5

BibLaTeX / Biber is a modern reimplementation of BibTeX. BibLaTeX offers, among other advantages, a native @dataset entry type for data publications as well as a @software entry type for software releases. However, BibLaTeX data is not fully compatible with BibTeX data, and is not universally supported by the LaTeX styles of publishers.

You can find more information about BibLaTeX here: https://tex.stackexchange.com/q/25701 (opens in new window)

We could spend time and resources on implementing a BibLaTeX export option alongside the classic BibTeX export. Do you consider this a reasonable investment of our limited resources?

6

Do you know of any standards or best practice guidelines for providing BibTeX records for data publications that you think the dblp BibTeX export options should follow?

Please let us know, and ideally provide a URL linking to a description of the standard/guideline. Thank you very much!

7
Is there anything else you want to let us know with respect to our BibTeX export feature?