Sonny Software

Apologies for asking too many questions; probably I am taking too much of your time. I am using BE f every day as I am reaching to the end of my dissertation.


So, the issue is: BE makes the Keys unique within the library. Since I have two libraries (one for articles, one for books), and, then I export them for citation, Biber (the tool processing the bibliography) is crying of duplicate keys. isn't there a way of making the keys unique across libraries?



I was thinking a find and replace system (REGEX), for example, which could Suffix the first word of the Title into the Keys; in one of the libraries.
(the problem will be: every time I add a new entry, I need to repeat that find and replace process for the new entries---but, that would be better than having duplicates. Still, a big problem is the Global Change, find and replace doesn't support Regex. Does it?)--other option is to associate the Key generation pattern with individual libraries /may be, you can improve BE to do so for future versions/.

As Bookends is designed there is no way to have unique keys across databases (since they are separate entities and don't know about each other). This is yet another good reason to have one library and use groups and such to maintain logical divisions.

Jon
Sonny Software

I am a bit worried, as the library is growing slowly, it might slow BE down.

Thanks for the superpower tools, the Global Change tools, I am thinking now to do a small trick of inserting a suffix like @ into the Key field of one of the libraries.


Alright!
thanks for the answer

Bookends is very, very fast. It can get a bit slow, but only when you have many thousands of references (30K+). Note that when you get to over 10K references you can improve performance by increasing the internal database cache (preferences).

Jon
Sonny Software

Thanks, I actually have less than 8k references. I might end up unifying them then.