Associating fields with abbreviations

[Galloway]

Is there any way to associate user fields with a journal glossary? I am trying to use a user field for a secondary series title, and would like it to be abbreviated as needed by formatting style. At the moment, it seems only the main series title (in the "journal field") seems to work.

[Jon]

The journal glossary is tied to the journal field (or main series title), it can't be reassigned.

Jon
Sonny Software

[Galloway]

Understood. Perhaps this might be considered in the future? (The ability to associate any abbreviation list with any given field that the user defines; EndNote allows something similar.) It is quite handy for having separate lists and separate fields for series and sub-series, each with defined abbreviations. I realize that sub-series titles are not very common with English language works, but they are quite common in German language publications.

[Jon]

You mean have multiple glossaries (i.e. abbreviation lists), each tied to a different field? It wouldn't be impossible to do, of course, but I imagine it would be kind of klunky. Any field on the main page can have a Term List, but that's not what you're after.

Jon
Sonny Software

[Galloway]

Basically what I am after is having (if possible) one single list (with abbreviations) that I can associate with any field I want (or any number of fields), regardless of which page the field is on. As I said, for books, I have the series title on the main page (which can have abbreviations) but would also like to have the same list (if possible) associated with User 14 (which I am using for the secondary series title), which is on the Additional Fields page. I would like both to be abbreviated (or not) as called for by the style. EndNote does something similar with its "Link Term list" feature; I have the Journal/Series list assigned to three different fields (Journal/Series Title; Tertiary Title [used with Book Chapter references for the Series Title as the Secondary (Journal) title is used for the book title], and a custom user field for the Secondary Series Title).

Ultimately, I would like to be able to generate citations such as:

Orël, Vladimir Èmmanuilovič [Владимир Эммануилович Орёл], and Olg'a Valer'evna Stolbova [Ольга Валерьевна Столбова]. 1995. Hamito-Semitic etymological dictionary: Materials for a reconstruction. Handbuch der Orientalistik 1 (Der Nahe und Mittlere Osten 18), ser. eds. Bertold Spuler and Hartwig Altenmüller. Leiden, New York, and Köln: E. J. Brill.

OR (with change of formatting style):

Orël, V. E., and O. V. Stolbova. 1995. Hamito-Semitic etymological dictionary: Materials for a reconstruction. HdO 1 (NMO 18). Leiden, New York, and Köln: E. J. Brill.

As I said, I am a new user and am trying to migrate from EndNote, so I am learning Bookend's limitations (and strengths) relative to EN.

[Jon]

Are the EndNote Term Lists used for distinguishing between short and full journal names? When I look at the Journal Term List (in EN) I see only the full name. Bookends has Term Lists, too, but they are distinct from the glossary function.

Jon
Sonny Software

[Jon]

Ultimately, I would like to be able to generate citations such as:

Orël, Vladimir Èmmanuilovič [Владимир Эммануилович Орёл], and Olg'a Valer'evna Stolbova [Ольга Валерьевна Столбова]. 1995. Hamito-Semitic etymological dictionary: Materials for a reconstruction. Handbuch der Orientalistik 1 (Der Nahe und Mittlere Osten 18), ser. eds. Bertold Spuler and Hartwig Altenmüller. Leiden, New York, and Köln: E. J. Brill.

OR (with change of formatting style):

Orël, V. E., and O. V. Stolbova. 1995. Hamito-Semitic etymological dictionary: Materials for a reconstruction. HdO 1 (NMO 18). Leiden, New York, and Köln: E. J. Brill.

BTW, the reason we have a journal glossary (and not, say, a book glossary) is because many Journal Article references you cite will belong in the same journals. This makes no sense for books, where you'd have only one entry for that book (for Book Chapters you might have several, but you'd create the chapters by Replicate As Book Chapter or Duplicate, so the solution in the next sentence still works well). You can get the output you want, in a format- and Type-specific manner, by using a user-defined field to hold the short form of the book name. Then in the format, tell Bookends which to use, the full or short form. This shouldn't be much more work than entering the short and long form in a glossary.

Jon
Sonny Software

[Galloway]

BTW, the reason we have a journal glossary (and not, say, a book glossary) is because many Journal Article references you cite will belong in the same journals. This makes no sense for books, where you'd have only one entry for that book (for Book Chapters you might have several, but you'd create the chapters by Replicate As Book Chapter or Duplicate, so the solution in the next sentence still works well). You can get the output you want, in a format- and Type-specific manner, by using a user-defined field to hold the short form of the book name. Then in the format, tell Bookends which to use, the full or short form. This shouldn't be much more work than entering the short and long form in a glossary.

Thanks. I am not sure what to make of this. Several books series titles I know of have well over 100 volumes each. No matter. I've gone back to using EndNotes as I was unable to get Bookends to import properly and I don't have time to verify 5000+ records to work out where Bookends decided to put data. I imagine if I were to start afresh it would be fine, but I am not personally willing to commit that time quite yet.

[Jon]

I was suggesting that if you have two forms of a book name, enter the "second" form in another field (defined by you) and use that field for formats that require the (second) form. With Global Change (Move Field) updating your existing library should be pretty quick.

As for transfer from EN to Bookends, did you export/import as EndNote XML? If so, Bookends maps the EN fields to the corresponding Bookends fields. If you have custom field in EN, of course, the mapping for that can differ (because Bookends doesn't know what those custom field holds). You don't have to work this out yourself, but if you care to pursue it and have an example of a normal field that you think was mapped to the wrong location in Bookends, you can send me that example and I'll take a look (support@sonnysoftware.com).

Jon
Sonny Software