> On 16 Mar 2021, at 20:27, Natalia Vale Asari <[email protected]> wrote: > > Dear all, > > I have just updated to the latest Bibdesk version (1.8.1), and it seems to > have a different behaviour when generating custom cite keys. > > My cite key format is: > %f{Mnrascitekey}%u1 > where Mnrascitekey is a custom field in my bibtex entries. For example: > > > @article{Aggarwal.2021a, > adsnote = {Provided by the SAO/NASA Astrophysics Data System}, > adsurl = {https://ui.adsabs.harvard.edu/abs/2021arXiv210302581A}, > archiveprefix = {arXiv}, > author = {{Aggarwal}, K M}, > date-added = {2021-03-09 09:56:38 -0300}, > date-modified = {2021-03-09 09:56:40 -0300}, > eid = {arXiv:2103.02581}, > eprint = {2103.02581}, > journal = {arXiv e-prints}, > mnrascitekey = {Aggarwal.2021}, > month = mar, > pages = {arXiv:2103.02581}, > primaryclass = {physics.atom-ph}, > title = {{Electron Impact Excitation of O III: An Assessment}}, > year = 2021,} > > > mnrascitekey = {Aggarwal.2021} > so Bibdesk generates > cite key = Aggarwal.2021a, since there is no other Aggarwal.2021 cite key in > my file. > > > Using the new version of Bibdesk, however, the %u1 format generates a random > letter (albeit the same for a given entry). E.g.: > > @article{Radcliffe.etal.2021i, > adsnote = {Provided by the SAO/NASA Astrophysics Data System}, > adsurl = {https://ui.adsabs.harvard.edu/abs/2021arXiv210308575R}, > archiveprefix = {arXiv}, > author = {{Radcliffe}, J.~F. and {Barthel}, P.~D. and {Thomson}, A.~P. > and {Garrett}, M.~A. and {Beswick}, R.~J. and {Muxlow}, T.~W.~B.}, > date-added = {2021-03-16 09:09:29 -0300}, > date-modified = {2021-03-16 16:18:09 -0300}, > eid = {arXiv:2103.08575}, > eprint = {2103.08575}, > journal = {arXiv e-prints}, > mnrascitekey = {Radcliffe.etal.2021}, > month = mar, > pages = {arXiv:2103.08575}, > primaryclass = {astro-ph.GA}, > title = {{Nowhere to Hide: Radio-faint AGN in the GOODS-N field. II. > Multi-wavelength AGN selection techniques and host galaxy properties}}, > year = 2021, > Bdsk-Url-1 = {https://ui.adsabs.harvard.edu/abs/2021arXiv210308575R}, > Bdsk-Url-2 = > {https://ui.adsabs.harvard.edu/link_gateway/2021arXiv210308575R/EPRINT_HTML}} > > @article{Pilipenko.2013t, > adsnote = {Provided by the SAO/NASA Astrophysics Data System}, > adsurl = {https://ui.adsabs.harvard.edu/abs/2013arXiv1303.5961P}, > archiveprefix = {arXiv}, > author = {{Pilipenko}, Sergey V.}, > date-added = {2021-03-09 09:56:50 -0300}, > date-modified = {2021-03-16 16:19:10 -0300}, > eid = {arXiv:1303.5961}, > eprint = {1303.5961}, > journal = {arXiv e-prints}, > mnrascitekey = {Pilipenko.2013}, > month = mar, > pages = {arXiv:1303.5961}, > primaryclass = {astro-ph.CO}, > title = {{Paper-and-pencil cosmological calculator}}, > year = 2013, > Bdsk-Url-1 = {https://ui.adsabs.harvard.edu/abs/2013arXiv1303.5961P}, > Bdsk-Url-2 = > {https://ui.adsabs.harvard.edu/link_gateway/2013arXiv1303.5961P/EPRINT_HTML}} > > > Has anything changed in the way Bibdesk generates cite keys? > > Thank you! > Natalia >
Yes, this has changed. It now generates unique characters based on the item, so it is more deterministic, and has less chance of depending on the order in which you generate them for different items. Christiaan
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
