Hello, Apologies for digging up this old thread, but I finally am ready to share a Perl script / Applescript combo that I've long been using to replicate the JabRef functionality for journal title abbreviations in Bibdesk. Given a list of abbreviations, its a pretty simple toggle that allows you to change the journal field on a selected number of publications to an abbreviation with periods (ISO version), without periods (Medline version), or to the full title. I also have an applescript that I hook to the "Add file" script hook so that the journal field always has the medline abbreviation to use when auto filing a PDF. Here is a link to the scripts:
http://tuvalu.santafe.edu/~vancleve/?page_id=100 If people find this useful, maybe a link to the scripts can go on the wiki. Best, Jeremy On 12/6/09 6:29 PM, JiHO wrote: > On Mon, Dec 7, 2009 at 01:11, Adam R. Maxwell<[email protected]> wrote: >>> Thanks for the reply. I've tried this but it means that I have to >>> manually change the journal name to the macro for every new entry in >>> my bib file, while 95% of those come from RIS/Bibtex imported in >>> Bibdesk (thanks to the excellent integration with Google Scholar for >>> example). So it just puts the strain of having to maintain something >>> manually on another part of the workflow (and, if I have to choose, >>> I'd rather do one long conversion once in a while that repeated manual >>> edits). Or maybe I am missing something. >> >> How about setting up a script hook that converts the full title to the >> macro value automatically? That would avoid the manual conversion entirely, >> and be less work than what you're doing now. The script could even have an >> alert that says "Missing @string for title foo." > > Thanks for the suggestion. I've never used script hooks before but it > would be a nice application. > >>> Guided by some online advice, I tried to define the >>> abbreviated/full form as @string macros but this does not work because >>> the shortcut of the macro just contain no space. >> >> Do you mean that you tried to use a title with spaces as a macro key? That >> definitely won't work, unfortunately :). > > Yes this is what I tried. Bad online advice ;) > >>> I guess, the real issue comes from Bibtex itself not handling it >>> better, but since this is unlikely to change in the near future >>> (ever?), I figured that Bibdesk might be able to help, the way Jabref >>> did. >> >> It could do something similar, but I think the right way to do this is by >> using BibTeX features, rather than rewriting your entire database all the >> time. > > Well, if I wanted to be picky, I would argue that this looks more like > a band-aid fix using the macro feature of bibtex than a true journal > name toggling "feature". A band-aid that has become standard, but a > band-aid nonetheless. All other software don't have you bother with > this. > > Another more constructive argument is that collaborators finally got > the better of my motivation to use latex and that I'll probably switch > to Pages/Word/Google Docs soon. Fortunately, thanks to CiteInPages, I > don't have to give up BibDesk. And to use BibDesk with CiteInPages, I > need the journal names a single bib database to be the correct ones > (either all abbreviated or all full). > >> Off the top of my head, here are a few of the issues you'd encounter >> adding this to BibDesk. How would you detect and handle errors? You'd have >> to have a UI to manage your full<->abbreviated name mapping, and import >> someone else's map...how would you deal with conflicts? How would you know >> which entries don't have a definition? > > Indeed that requires UI. Probably a new preference pane or a new sheet > within an existing one. You can have a quick look at JabRef to see how > they did it.The UI could be quite close to the one for custom > character conversion: Bibdesk would have an internal list, as > comprehensive as possible and the user would only add its own journals > (and be warned if he tries to enter an existing journal). As for which > entries don't have a definition you could either be lazy and consider > that the user will notice when converting the database, or match the > names against the existing database and pre-fill the custom list with > those that are missing. > >> Practically, how would you handle a case where you're using the same >> database to draft one paper that requires a full title and another that >> requires abbreviated titles? > > I think this would be an edge case: at the limit, one needs the form > appropriate for the journal (abbrv or full) only for the last > compilation, before submission. I wish I often had two papers at this > stage at the same time but this unfortunately proves to be rare ;) > > JiHO > --- > http://maururu.net > > > ------------------------------------------------------------------------------ > Join us December 9, 2009 for the Red Hat Virtual Experience, > a free event focused on virtualization and cloud computing. > Attend in-depth sessions from your desk. Your couch. Anywhere. > http://p.sf.net/sfu/redhat-sfdev2dev > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users -- Jeremy Van Cleve Omidyar Postdoctoral Fellow Santa Fe Institute E-mail: [email protected] Webpage: http://www.santafe.edu/~vancleve/ ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
