Regenerate citekeys on new computer #2209
-
Hi! For the first time since I started to use Zotero, I'm on a new computer. I've synced my library using Zotero's sync service, but I run into problem with BBT's citekeys. To my understanding, the citekeys generated by BBT on my old computer can't be synced to the new. So what I'm trying to is using the same template for my citekeys (auth.lower + year). This results in citekeys like thoresson2022, and when there are many citekeys for the same year and author, thoresson2022a etc. But when generated on my new computer, the extra letter creating unique citekeys isn't added to the same source. So what is thoresson2022a on my old computer and my new one are two different articles by Thoresson, both published in 2022. Is this expected when regenerating citekeys on the news computer? Any suggestion on how to bring my old citekeys to the new one? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Two ways to get them to the new computer:
Those are unfortunately the only ways to get what you want. The behavior you see is indeed expected, but only because I know how BBT works in detail, I don't think anyone would expect this behavior. I have tried to get around this with ways of smuggling data across during sync, but none of them ended well; I have once had to abandon a Zotero account because of how thoroughly I screwed the account up, which is why I'm |
Beta Was this translation helpful? Give feedback.
Two ways to get them to the new computer:
The keys can be synced up, but you have to pin them all. That will sync over cleanly. In an upcoming release of Zotero (don't know when though), zotero items get a real citekey field, and then nothing else needs to be done.
If the old computer is fully synced up, you could just copy your Zotero profile (which includes the databases) to the new computer, and everything will be as it was. No need to pin in this case.
Those are unfortunately the only ways to get what you want. The behavior you see is indeed expected, but only because I know how BBT works in detail, I don't think anyone would expect this behavior. I have tried to get around this…