With newer versions of biblatex (≥2.0) and biber (≥0.9.8) you can define your entries as normal and use the "IDS" field for extra citations keys:
@BOOK{key,
IDS = {key2, key3, ..., keyn},
.
.
}
You can then cite by any of the keys, you can cite by any of them mixed in the same section and and you can use \nocite{*} too - it won't duplicate entries in the bibliography. In fact, the other keys are just aliases to the main key which owns the entry in the .bbl and are redirected to the main key before any label generation etc. happens.
It will also detect if you use a key as a primary key and also an alias elsewhere, in which case it will disable the alias. It also notices duplicate aliases as well as keys now.
lotris defined in your bibliography and you want to useTolkien:1954:LordOfTheRings, try\makeatletter \expandafter\def\csname b@Tolkien:1954:LordOfTheRings\endcsname{\b@lotr} \makeatotherin your document preamble? – Werner Dec 05 '11 at 22:54\cite{\csname b@Tolkien:1954:LordOfTheRings\endcsname}in the main text? – lockstep Dec 06 '11 at 00:06\cite{<stuff>}checks for the existence of\b@<stuff>via a construction. So you should just be able to use\cite{Tolkien:1954:LordOfTheRings}. – Werner Dec 06 '11 at 00:10bibtex; notbiblatex.biblatexdefines things in a much more complicated way it seems. – Werner Dec 06 '11 at 07:28@crossrefdirectly in the .bib-File? I uses this occasionally for fixing typos or convention issues in keys to stay backward compatible. I have not yet tried to use both keys within the same document, so it might be perfectly possible that you end up with two entries. – Daniel Dec 06 '11 at 09:53@crossreftype doesn't exist; using thecrossreffield gives duplicate entries in the bibliography list if both keys are used in the same document. – Caramdir Dec 06 '11 at 19:09