Thanks to everyone for their insights, comments, and suggestions in reply to my query. I, too, would think that a journal (or publishing house) that didn't want a particular kind of information (e.g., url) in a bibliographic reference (e.g., for a research article) would design the *.bst file to it ignored all such unwanted fields. The new APS Rev-TeX-4.1.bst file does not do this. Out of curiosity, I've tried *.bst files from other journals in my field (physics) and from a couple of book publishers (including one for which I have under contract a long book that will have a lot of references); I have yet to find one that excludes all fields except the ones that the publisher wants to appear in the printed bibliography. This seems grossly ineffective, but I'm certainly no expert on writing *.bst files (!). It seems a real shame that it's not possible (or, I gather, practical) to implement some straightforward such capability in JabRef, some sort of filters that the user could use to tell JabRef what fields to export into the *.bll field. Otherwise, JabRef seems very well designed, is a joy to work with, and has cut the amount of time and hassle in generating citation lists by an enormous amount. Anyway, thanks again--- michael
-----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, January 08, 2015 2:32 AM To: [email protected] Subject: Jabref-users Digest, Vol 99, Issue 1 Send Jabref-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/jabref-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Jabref-users digest..." Today's Topics: 1. Data lost (!) in entry type customization (Greg?rio Miranda) 2. Re: Data lost (!) in entry type customization (Greg?rio Miranda) 3. Re: Data lost (!) in entry type customization (Oliver Kopp) 4. control which fields JabRef exports to a bbl file (Michael A. Morrison) 5. Re: control which fields JabRef exports to a bbl file (Peter Rockett) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Jan 2015 13:46:10 -0200 From: Greg?rio Miranda <[email protected]> Subject: [Jabref-users] Data lost (!) in entry type customization To: [email protected] Message-ID: <cah5shshknx0khgz-hkak9r_uhr-itb5kkbszvz1yv1m1gw7...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi guys, I have spent some time last week dealing with the #1243 bug concerning the entry type customization. Although I was getting tired to customize them again and again (and again) I was OK with the 2.10 version. (A workaround is provide here, but I still didn't test it). http://sourceforge.net/p/jabref/bugs/1243/#b06b But I just found something that I have to share with you. I'm pretty sure that JabRef just erase the editor field in at least one inbook entry. I mean, it's more than an annoying and inoffensive bug, it's a real chance to finish my dissertation with serious reference errors. I'm worried now about continuing to use JabRef 2.10 for my reference management. Should I migrate to a previous version? There's some steps that I can avoid in order to avoid losing data? I'm thinking about customizating the minimal as posible the next entrys, but there's something more that I have to have in mind? Regards, Greg?rio Miranda -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Tue, 6 Jan 2015 22:39:03 -0200 From: Greg?rio Miranda <[email protected]> Subject: Re: [Jabref-users] Data lost (!) in entry type customization To: [email protected] Message-ID: <CAH5sHSEd75=juasf1gkhydv57rnpjnojxv0fo0blvplfwv+...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, An upgrade: actually I found that this issue is only peripheral related to entry type customization since I have, by default, three editor fields in my InBook entries. I did some experimentation with them and, sincerely, it's all f*cked up. Some conclusion comes up, though: I'm consistently losing data in these fields/entries. I'm having the sames malfunctions described in this e-mail <https://sourceforge.net/p/jabref/mailman/message/28389638/>(from 2011) but couldn't find the problem related between known bugs. Please, let me know if I'm losing something and if there's a workaround (run JabRef as su was not effective). And sorry for the amateur english. Regards, Greg?rio Miranda 2015-01-05 13:46 GMT-02:00 Greg?rio Miranda <[email protected]>: > Hi guys, > > I have spent some time last week dealing with the #1243 bug concerning > the entry type customization. Although I was getting tired to > customize them again and again (and again) I was OK with the 2.10 > version. (A workaround is provide here, but I still didn't test it). > http://sourceforge.net/p/jabref/bugs/1243/#b06b > > But I just found something that I have to share with you. I'm pretty > sure that JabRef just erase the editor field in at least one inbook > entry. I mean, it's more than an annoying and inoffensive bug, it's a > real chance to finish my dissertation with serious reference errors. > > I'm worried now about continuing to use JabRef 2.10 for my reference > management. Should I migrate to a previous version? There's some steps > that I can avoid in order to avoid losing data? I'm thinking about > customizating the minimal as posible the next entrys, but there's > something more that I have to have in mind? > > Regards, > Greg?rio Miranda > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 3 Date: Wed, 7 Jan 2015 12:54:12 +0100 From: Oliver Kopp <[email protected]> Subject: Re: [Jabref-users] Data lost (!) in entry type customization To: "[email protected]" <[email protected]> Message-ID: <CAA55TJpjADeC==gANqJh=f2s2_oq365ic0vgoogdcf7vqrw...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Dear Greg?rio , 2015-01-07 1:39 GMT+01:00 Greg?rio Miranda <[email protected]>: > An upgrade: actually I found that this issue is only peripheral > related to entry type customization since I have, by default, three > editor fields in my InBook entries. [...] > I'm having the sames malfunctions described in this e-mail (from 2011) > but couldn't find the problem related between known bugs. In that email, Morten wrote that there is no support for multiple fields. Do I understand you correctly that you are trying to have an entry with multiple fields with the same key? I never worked with that and I think, it is not supported by JabRef. Is that legal in BibTeX? editor = {a}, editor = {b}, editor = {c} I think, one has to write editor = {a and b and c}. Cheers, Oliver ------------------------------ Message: 4 Date: Wed, 7 Jan 2015 16:00:22 -0600 From: "Michael A. Morrison" <[email protected]> Subject: [Jabref-users] control which fields JabRef exports to a bbl file To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi, I'm relatively new to JabRef and am unclear about how to control which of the fields in a given entry will actually be exported to the BibTeX in the *.bbl file created by JabRef. For example, downloading citations from most journal cites directly into JabRef automatically fills in the url field (and often the Doi field) in the General tab in the entry editor. When I run BibTeX with a standard bst file (e.g., the one for the American Physical Society), the resulting LaTeX bibliography contains the url even though the APS does not want it included in the bibliography environment I submit to the journal. The obvious way to solve the problem is to edit, by hand, every entry in the bibliography environment before I submit the paper. This seems extremely inefficient. Another obvious solution would be to edit every entry in JabRef and remove the information in the url (and other unwanted fields, such as Doi) before I run BibTeX to generate the bibliography I will then paste into the LaTeX file I'll submit to the journal. This seems an unsatisfactory solution, not only because it would be very tedious with a long bibliography (e.g., for a review article) but also because I would like to keep that information for future use in other circumstances. Is there a way, within JabRef, to tell control which fields to include in the BibTeX it generates and which to leave out? (I thought the Entry Export editor was the answer, but studying the information I could find on line suggests that it's not.) Thanks very much. --- michael Michael Morrison University of Oklahoma -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 5 Date: Thu, 08 Jan 2015 08:31:43 +0000 From: Peter Rockett <[email protected]> Subject: Re: [Jabref-users] control which fields JabRef exports to a bbl file To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="windows-1252" On 07/01/15 22:00, Michael A. Morrison wrote: > control which fields JabRef exports to a bbl file > > Hi, > > I?mrelativelynew to JabRef and am unclear about how to control which > of the fieldsin a given entrywillactuallybe exported to the BibTeX in > the *.bbl file created by JabRef. For example, downloading citations > from most journal cites directly into JabRefautomaticallyfills in the > url field(and often the Doi field)in the General tab in the entry > editor. When I run BibTeX with a standard bst file (e.g., the onefor > the American Physical Society), the resulting LaTeX bibliography > contains the url even though the APS does not want it included in the > bibliography environmentI submit to the journal. The obvious way to > solvethe problem is to edit, by hand, every entry in thebibliography > environment before I submit the paper. This seems extremely > inefficient. Another obvious solution would be to editevery entry in > JabRefand remove theinformationin the url(and other unwanted fields, > such as Doi) before I run BibTeX to generate the bibliography I will > then paste into the LaTeX file I?ll submit to the journal. This > seemsanunsatisfactory solution, not onlybecauseit would be very > tedious with a long bibliography (e.g., for a review article) but also > because I would like to keep that information for future use in other > circumstances. Is there a way, within JabRef, to tellcontrolwhich > fields to include in the BibTeX it generates and which to leave out? > (I thought the Entry Export editor was the answer, but studying the > information I could find on line suggests that it?s not.) Thanks very > much.--- michael > > Michael Morrison > > Michael If you get an answer to this I (and I, suspect, many others) will be delighted! But having looked at this before at length, I think the consensus is that this is a deficiency of the bst file you are using, and not JabRef. I routinely create a paper-specific bib file so I can do things like deleting unwanted fields that the (often publisher-supplied!) bst file insists on including. One other option, which has just occurred to me and hence haven't tried, is to run sed (or a similar stream editor) on the bbl file to comment out "\newblock URL \url{" fields. If you use an IDE like TexStudio, I think it should be possible to automate this using the Macros facility? Peter -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ---------------------------------------------------------------------------- -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ------------------------------ _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users End of Jabref-users Digest, Vol 99, Issue 1 ******************************************* ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users
