I do. I've put up a couple of (vastly improved) Endnote-to-Bibtex export styles, available here:
http://people.reed.edu/~ahm/Projects/Citation/Endnote/Styles/ The TempCiteKeys variant is the one that most people should use; it uses the record number of the Endnote database as the cite key, so the resulting output file can be opened as a regular BibTeX file. In addition, the following improvements over the default (and horribly broken) EndNote export have been made: Mapping BibTeX field = Endnote Field (improvement over default below) ---------------------------------------------------------- All types: `ISSN = {`ISSN`},` (or ISBN, where appropriate) `Annote = {`Research Notes`},` `URL = {`URL`},` `EndNoteRefType = {XXX},` (where XXX is the reference type) `Local-URL = {`File Attachments`},` Journal Article -> article `Month = {`Date`},` Book -> book `Editor = {`Series Editor`},` `Number = {`Number of Volumes`},` Thesis -> phdthesis `Address = {`City`},` `Month = {`Date`},` Conference Proceedings -> inproceedings `Organization = {`Series Editor`},` `Edition = {`Edition`},` `Month = {`Date`},` Book Section -> incollection Magazine Article -> article Edited Book -> book `Number = {`Number of Volumes`},` Report -> techreport `Address = {`City`},` Generic -> misc `Howpublished = {`Publisher`},` (instead of Publisher) Eliminate non-used Volume, Number, ISBN Newspaper Article -> article (new) Manuscript -> unpublished (new) Computer Program -> manual (new) Web Page -> misc (new) Unpublished Work -> unpublished (new) -AHM On 2008-04-23, at 9:43 AM, James Howison wrote: > Do we have any users who understand Endnote export templates and how > to edit them? Perhaps you could swing over to this Bug on the Tracker > and test Christian's tweaks to the Endnote bibtex export. The goal, I > think, is to ensure that Endnote never generates citekeys (and then > the import can be opened with temporary citekeys and good ones > generated by BibTex). > > The other alternative is to ensure that Endnote always includes > citekeys, but that has proven hard in the past, since they have to be > unique and of a certain format. > > Its the cases where the default export template generates bibtex with > a mix of entries with and without citekeys that is hard for BibDesk to > handle. > > The background is below or in the Tracker thread. > > Thanks, > James > > Begin forwarded message: > >> From: "SourceForge.net" <[EMAIL PROTECTED]> >> Date: April 22, 2008 4:12:22 PM EDT >> To: [EMAIL PROTECTED] >> Subject: [ bibdesk-Bugs-1948436 ] open with temp citekeys may fail >> when entries have a key >> >> Bugs item #1948436, was opened at 2008-04-22 07:40 >> Message generated for change (Comment added) made by hofman >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=497423&aid=1948436&group_id=61487 >> >> Please note that this message will contain a full copy of the >> comment thread, >> including the initial issue submission, for this request, >> not just the latest update. >> Category: File I/O >> Group: None >> Status: Open >> Resolution: None >> Priority: 2 >> Private: No >> Submitted By: Adam Maxwell (amaxwell) >> Assigned to: Nobody/Anonymous (nobody) >> Summary: open with temp citekeys may fail when entries have a key >> >> Initial Comment: >> This is an excerpt from a user's file, produced by Endnote's BibTeX >> export. Opening with temporary keys assumes that no item has a key, >> but apparently this isn't necessarily so. >> >> As a quick hack, I did a regex find/replace with 's/([EMAIL PROTECTED])[a- >> zA-Z0-9]+,/$1/g' but even that didn't catch all cases, since one of >> the keys had spaces in it. There's probably a more robust way to do >> it, but I'm not even sure it's worthwhile since this has never come >> up before...and it's also difficult to test and catch all cases >> without breaking the current support. >> >> @incollection{ >> Author = {Polin, Linda and Riel, Margaret}, >> Title = {Online Learning Communities}, >> BookTitle = {Designing for Virtual Communities in the Service of >> Learning}, >> Editor = {Barab, Sasha A. and Kling, Rob and Gray, James}, >> Publisher = {Cambridge University Press}, >> Year = {2004} } >> >> @book{ >> pollock1999, >> Author = {Pollock, John L. and Cruz, Joseph}, >> Title = {Contemporary Theories of Knowledge}, >> Publisher = {Roman & Littlefield Publishers}, >> Address = {Lanham, Maryland}, >> Series = {Studies in Epistemology and Cognitive Theory}, >> Keywords = {cogsci >> history}, >> Year = {1999} } >> >> @misc{ >> NSF PR 98-36, >> Author = {NSF}, >> Title = {Science and Engineering Indicators '98 Survey Shows >> Americans' Interest in Science Grows}, >> Publisher = {National Science Foundation}, >> Month = {July 1, 1998}, >> Abstract = {Americans say they are more interested and more aware >> than ever about scientific discoveries, inventions, and new >> technologies. However they still score low on actual understanding >> of basic scientific terms and concepts, such as the definition of >> molecules and DNA, and how frequently the earth revolves around the >> sun.}, >> Keywords = {survey, science, knowledge, attitudes, adult}, >> Year = {1998} } >> >> >> >> ---------------------------------------------------------------------- >> >>> Comment By: Christiaan Hofman (hofman) >> Date: 2008-04-22 23:12 >> >> Message: >> Logged In: YES >> user_id=1162009 >> Originator: NO >> >> Maybe someone with EndNote can test the attched patch ed export >> template? >> I don't even know if it's valid, I just deleted some lines, but the >> format >> is binary. >> File Added: BibTeXExport.ens >> >> ---------------------------------------------------------------------- >> >> Comment By: Adam Maxwell (amaxwell) >> Date: 2008-04-22 22:53 >> >> Message: >> Logged In: YES >> user_id=732757 >> Originator: YES >> >> That's not a bad idea, providing we can find someone who understands >> Endnote export templates :). Maybe link to it on the wiki? Even >> more >> convenient might be to just assign a fake citekey to each entry in >> Endnote...although the user would then have to remember to generate >> new >> keys. >> >> ---------------------------------------------------------------------- >> >> Comment By: James Howison (jameshowison) >> Date: 2008-04-22 22:44 >> >> Message: >> Logged In: YES >> user_id=844653 >> Originator: NO >> >> Actually I meant fix the export on the Endnote side. I think that >> one can >> add new export templates, so BiBDesk could publish a patched version >> of the >> BibTeX export, which always drops the citekeys ... >> >> ---------------------------------------------------------------------- >> >> Comment By: Adam Maxwell (amaxwell) >> Date: 2008-04-22 18:48 >> >> Message: >> Logged In: YES >> user_id=732757 >> Originator: YES >> >> Yeah, I think it does use some field as citekey. There are some >> implementation problems in removing them, though, since the >> Endnote-generated keys may contain almost anything AFAICT (so the >> regex >> would be tricky). >> >> Another problem is that AGRegex find/replace is horrendously slow on >> large >> strings; unfortunately, these Endnote exports tend to be quite >> large, since >> people typically export an entire database, so it can either >> beachball for >> minutes or use up all your address space. We currently do some >> tricky >> scanner/regex combination stuff to work around that. Dropping in >> RegexKitLite might be a better long term solution. >> >> ---------------------------------------------------------------------- >> >> Comment By: James Howison (jameshowison) >> Date: 2008-04-22 17:51 >> >> Message: >> Logged In: YES >> user_id=844653 >> Originator: NO >> >> I haven't used Endnote export for a while, but I seem to recall that >> there >> is an Endnote field which, if present, is used as a citekey. If the >> field >> is absent one gets no citekey. Perhaps the OP sometimes has that >> field >> set? Maybe the best thing to do is to fix the Endnote export so >> that it >> never includes a citekey, whether nor not that field is present. >> >> ---------------------------------------------------------------------- >> >> Comment By: Christiaan Hofman (hofman) >> Date: 2008-04-22 13:13 >> >> Message: >> Logged In: YES >> user_id=1162009 >> Originator: NO >> >> I don't think it's worth it. There will always be edge cases to >> these edge >> cases. Its about something that's broken in the first place, and >> testing >> for broken cases is always less reliable. EndNote really makes a >> mess out >> of it. They should learn what bibtex is. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=497423&aid=1948436&group_id=61487 >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
