Thank you very much Christiaan. ==Tamer
Sent from my mobile, excuse the brevity and typos. > On May 17, 2023, at 9:37 AM, Christiaan Hofman <[email protected]> wrote: > > I will add a separate preference option to control whether to overwrite > existing cite keys. > > Christiaan > >> On 17 May 2023, at 05:04, M. Tamer Özsu via Bibdesk-users >> <[email protected]> wrote: >> >> Sorry, I missed that question from Christiaan. In my case, I autogenerate >> the cite key, but then want to prefix it with the abbreviation of the name >> of the conference or journal where it appeared. The hacky way I do it is to >> open the .bib file after I autogenerate the cite key and just prepend the >> abbreviation. Then I import them into the master file. Old habit and it >> makes it easier to search for venues. >> >> I suppose I could revise the “add keyword” script to do this all within >> BibDesk - but I don’t know how to refer to the cite key. Hence the hacky >> workflow. >> >> ==Tamer >> >>>> On May 16, 2023, at 10:57 PM, Adam R. Maxwell via Bibdesk-users >>>> <[email protected]> wrote: >>> >>> >>> >>>> On May 16, 2023, at 15:12 , Christiaan Hofman <[email protected]> wrote: >>>> >>>> Just wondering, why would you not want to auto-generate the cite key when >>>> adding? >>> >>> If you have a master .bib file and create smaller ones as needed by >>> project/report/topic/etc, it makes sense that you'd want the same citekeys >>> in both files. At least, I think that was the rationale for not generating >>> a new citekey for an item when copying/dragging (unless it had empty or >>> default citekey)? >>> >>> -- adam >>> > > > > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
