On 5 Feb 2008, at 9:12 AM, James Owen wrote: > > > > >>> On Feb 4, 2008, at 4:45 PM, Adam R. Maxwell wrote: >>> >>>> Aren't there more important things to complain about? >>> >>> No, the program is just too d*** good! :-) > > ++ > > Just some little queries..... > > I have been trying to consolidate all my bib files into one big file, > which is going well. However, I run into trouble when I encounter > another reference with the same citekey, probably the same paper, but > possibly with slightly different information, e.g. DOI, or abstract > included. When the citekey flashes up red, it would be nice to click a > button to show the offending alternative citation, so that the > conflict can be resolved. Otherwise, I have to find it manually in the > main database, open it manually and choose one. Also, if I could at > that point discard the new import, rather than have to delete it from > the database, that would also be nice. >
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. > Alternatively, if the citekey could show up red in the main database > view, or with a "duplicate citekey" flag somewhere in the database, > then I could just drag and drop all the citations from one database to > another, then click to find duplicate citekeys, and then go through > and resolve all the conflicts. As it is, I have to do a few at a time. > See my remarks above. Also, if you select a Cite Key column, it becomes easier to spot duplicate cite keys because they will be next to each other. > 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. > 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. 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/>. Christiaan > > James > > > > James Owen > [EMAIL PROTECTED] ------------------------------------------------------------------------- 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
