ufal / clarin-dspace

clarin-dspace digital repository based on DSpace and LINDAT/CLARIN DSpace
http://lindat.cz
BSD 3-Clause "New" or "Revised" License
27 stars 18 forks source link

Current BibTeX hides handle #859

Open TomazErjavec opened 6 years ago

TomazErjavec commented 6 years ago

The current BibTeX export has the handle of the entry in the \url field, which many a \bibliographystyle ignores. This means that, unless the author of a paper is willing to modify the BibTeX by hand, the handle information will not be present in the PDF of the paper. This is bad, as then readers cannot (easily) find the resource, the main ID of the resource is lost, and the authors get less citation and visibility than they could. Furthermore, the name of the resource can be incorrectly capitalised.

The exemplify, I made https://www.overleaf.com/16505840rmymbqmbfyzf where you can check the difference between the exported and "cooked" entry. Note that I have removed double backslashes (cf. #853) by hand from the exported entry.

kosarko commented 6 years ago

The issue is that we cannot influence the style an end user will use for formatting the bibliography. There are styles @misc and urls work with; we should mention those to the user. Also there's @LanguageResource with LREC style; so we might add that.

stranak commented 4 years ago

What we could do, is add some recommendation, like a help message somewhere close to the bibtex citation text. For instance we could explain the problem, as you do here, and say that URL field works, if you use natbib, for instance with plainnat style in Latex.

TomazErjavec commented 4 years ago

add some recommendation, like a help message somewhere close to the bibtex citation text ... and say that URL field works, if you use natbib

The problem here is that people aren't free to choose their BibTeX style, as that is perscribed by the venue.

What I do in my records is add to the BibTeX entry the field note = {\url{http://hdl.handle.net/11356/1329}}. This seems to work just fine with all styles, except that the main .tex file has to use the url package, but that is good practice anyway.

The problem here is that you already use the note for the repository name. I would say that you should use the publisher field for that, or, rather, put the "real" publisher in the publisher field, and just ignore the name of the repository (somewhat bad for our egos, but maybe we can cope:).

So, instead of:

@misc{11356/1329,
 title = {The {CLASSLA}-{StanfordNLP} model for named entity recognition of standard Bulgarian 1.0},
 author = {Ljube{\v s}i{\'c}, Nikola and Osenova, Petya and Simov, Kiril},
 url = {http://hdl.handle.net/11356/1329},
 note = {Slovenian language resource repository {CLARIN}.{SI}},
 copyright = {Creative Commons - Attribution-{ShareAlike} 4.0 International ({CC} {BY}-{SA} 4.0)},
 year = {2020} }

I would suggest:

@misc{11356/1329,
 title = {{The CLASSLA-StanfordNLP model for named entity recognition of standard Bulgarian 1.0}},
 author = {Ljube{\v s}i{\'c}, Nikola and Osenova, Petya and Simov, Kiril},
 publisher = {Jo{\v z}ef Stefan Institute},
 url = {http://hdl.handle.net/11356/1329},
 note = {\url{http://hdl.handle.net/11356/1329}},
 copyright = {{Creative Commons - Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)}},
 year = {2020} }

Note also that I suggest the title is {{...}} rather than having individual words bracketed. In your approach, "CLASSLA-StanfordNLP" will be capitalised correctly, but "Bulgarian" won't.

stranak commented 3 years ago

@TomazErjavec, unfortunately we are still too busy, but if you have tested this and it really works with all the common styles like ACL, APA, etc., it looks like a very useful fix.

Could you guys in Ljubljana try to implement this change and make a pull request? It should not be too hard. I promise we'll look at it then and merge it, hopefuly quickly.

TomazErjavec commented 3 years ago

The only hope here would then be @cyplas, but it could we bee that here is still to busy too?