> > You can find all duplicate entries easily using the Select Duplicates > or Select Possible Duplicates menu items. The first finds duplicates > based on all standard bibtex fields, while the second finds > duplicates based on the currently selected column (so in your case > that should be Cite Key). > > Also, if you want to import new items without duplicates, it can be > handy to add a (temporary) external file group. The Merge functions > for external groups automatically drop duplicate entries. >
Great. Thanks. >> > >> Secondly, when importing citations from PRL, they have their own >> citekey format. Is there any way to tell BibDesk to impose the auto >> citekey format on imported citations? Likewise, some way to tell >> BibDesk to consolidate all linked files into the autofile location, >> in >> case there are some stray linked files which are elsewhere? >> > > Sure, turn on Cite Key auto-generation in the Cite Key preferences. > Similar for Auto File. Import automatically triggers those. Does that override the cite key that PRL has already imposed? I do have auto-generation turned on, but that only makes a cite key, when one does not exist, as far as I can tell. > > >> Finally, I wrote an rtf template for the preview pane, and wanted the >> DOI to show up as a hyperlink, which was clickable, and would open >> the >> paper in the journal browser. This works if I write an html template, >> but not with an rtf template. The text shows up as a blue underlined >> hyperlink with the link text changed to the correct DOI, but the >> underlying link is not resolved and so the link is broken. >> >> e.g. <span class="url"><a href="http://dx.doi.org/<$fields.Doi/>">< >> $fields.Doi/></a></span> in an html template gives me the correct >> link to the journal, but >> <a href="http://dx.doi.org/<$fields.Doi/>"><$fields.Doi/></a> in an >> rtf template doesn't. >> The link remains http://dx.doi.org/<$fields.Doi>/ rather than >> http://dx.doi.org/10.1103/PhysRevB.51.17151/ >> > > Why would you even expect that to work in RTF? HTML is a different > format from RTF, so if you write HTML in it it's just text. I didn't have any idea how rtf works, clearly I know it is different from html. This is why it is annoying that Pages no longer imports html, because I could easily write the format the way I wanted it in html, add a css file, and it would come out very nicely in Pages '06, but no longer in Pages '08. > For RTF (or other rich text formats) you can use the linkedText > modifier key. However you do need a URL or a URL string. BibDesk has > build-in support to make a URL out of a DOI, if you add Doi as a > Remote URL field. Then you can use $urls.Doi in templates. To get a > link in RTF you then use <$urls.Doi.linkedText/>. OK. Great, I will try that. Thanks again, James ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
