10. Term/Entry lists| Citation 9 | RefWorks (web based) | Biblioscape | Bookends | Library Master | Procite | EndNote | Reference Manager | - |
|---|---|---|---|---|---|---|---|---|
 |  |  |  |  |  |  |  | . |
Term/Entry lists | ||||||||
A - Tipology and quantity | ||||||||
| Cit: 4 built-in "indexes" for: authors (translators, editors etc.), journals, publishers and keywords + optional keywords file and two abbreviation tables -journals & publishers-with two entries, full & abbrev. (or viceversa), that can be used only in output styles, if Preferences are set to use abbreviations | RW: 3 built-in index lists for authors (i.e. any name field), journal titles, kw-descriptors | Bscp: Virtually any field (56 available in the standard db structure, but Notes, Abstract, Miscellaneous, and Document never available) can have its own 'lookup list'. Usually (apart from four types of authors) each field generates its own list 1:1. One Term table: accessible from any field. The list is made up of terms, and their possible abbreviations, grouped by category. Abbreviation and category serve as terms filter. Only the term is inserted in the field. Can be imported and exported as tabbed delimited file. One Journal list : each title on a line, three possible values, import/export as tab delimited file. Only useful in output | BK: index lists: authors, editors, keywords, journals/series title + n journal glossaries. Any other field -apart those in the "Drawer" can generate its term list upon user's choice. Journal Glossaries are term lists structured as: "Abbreviation | Short Name | Full Name" |
LM: Index lists are available only when a field is indexed. Virtually any field can be indexed in order to speed search up, and to sort the database; by default some are. Term lists, also Journals, are not indexes, but separate lists that can be used in input and searching. Their structure pattern is: "String | Abbreviation 1 | Abbreviation 2 | Abbreviation 3 | Abbreviation 4" |
Pr: 4 built-in indexes: 4 Field Content Lists: Authors, Titles, Journals, Keywords; other ad libitum term lists; Journal list (whose structure is a three columns table: full form | abbrev. | other) is also used for output purposes; Special list: Alternate text ALTERNAT.TXT: does not have to do with styles, but with printing in general, where text in record fields put between «...» can be replaced by its text equivalent put in an external text file whose structure pattern is: "text {text equivalent} | note"; fixed name, one for db and can be shared with others | En: the 3 basic term lists (authors, journals, keywords) are just a default, they can be deleted, others can be added up to max 31; Journals list also for output purpose | RM: three built-in term lists Authors, Journals, Keywords + 1 single optional Phrase list | |
B - Can create extra | ||||||||
| Cit: no | RW: no | Bscp: yes | BK: yes, both term lists and journal glossaries | LM: yes | Pr: not indexes, just term lists | En: yes | RM: no | . |
C - Can modify their structure or disactivate them | ||||||||
| Cit: no; can decide not to use abbreviation lists | RW: no, but you can disactivate them | Bscp: no | BK: no | LM: can modify length of the key to be indexed | Pr: no, can modify term lists | En: yes both | RM: no | . |
D - Lists recognize multi-value (repeatable) fields so that each occurrence becomes a distinct term | ||||||||
| Cit: yes (see Database and record structure) | RW: yes (see Database and record structure) | Bscp: yes (see Database and record structure) | BK: yes (see Database and record structure) | LM: yes (see Database and record structure) | Pr: yes (see Database and record structure) | En: yes (see Database and record structure) | RM: yes (see Database and record structure) | |
E - Lists can be sorted by user | ||||||||
| Cit: no | RW: no | Bscp: yes, alphabetically A/D and also on related documents counter | BK: yes in A/D mode | LM: no | Pr: no | En: no | RM: no | |
F - Lists allow efficient alphabetic scrolling (i.e. incremental searching) | ||||||||
| Cit: average, depends on keying speed | RW: yes | Bscp: can only move via the mouse | BK: yes | LM: yes | Pr: not particularly, depends on keying speed | En: yes | RM: yes | |
G - List entry can contain its own supplementary data: note, abbreviation, date, compiler, x-refs | ||||||||
| Cit: no but publishers and journals can have abbreviated form -stored in external file- to be used in output | RW: no | Bscp: no, only term Table and Journal List may have other values for each entry, see above Features in general | BK: no, only Journal Glossaries may have up to three forms for each entry | LM: only terms lists can contain up to 4 abbreviations or equivalent terms | Pr: not the 4 indexes; yes journal list(s): abbreviation + note; yes other lists: max 2 additional fields as notes | En: any list defined as "journal list" can have up to 3 abbreviations, and no other data | RM: synonyms terms, which -on their turn- become entries of the list; journal titles list can have up to 3 abbreviations | |
H - Lists entries can be linked by cross-references (see, see also, NT/BT, later/earlier etc.) | ||||||||
| Cit: no | RW: no | Bscp: no | BK: no | LM: no | Pr: no | En: no | RM: Synonyms: each author and kw can have up to 255 synonyms, periodical title up to 3 (output style can use them). Synonyms automatically become physically reciprocal: A with syn. B C, then B with syn. A C etc. They can be used in searching not in editing (unless you work from the Lists towards the refs) | |
I - Lists are physically separated from database | ||||||||
| Cit: "indexes"/look-up lists are never separated; keywords.ini and abbreviation lists -publishers and journals- are external and designed to be shared among different databases | RW: no never separated; cannot be shared among db as each user can access only one db | Bscp: lookup lists are never separated from the db. Term table and Journal name list can be used by other db if copied and kept to different folder | BK: term lists are never separated from db; Journal glossaries can be shared with other db | LM: indexes lists are never separated; Terms tables can be shared among different db | Pr: 4 built-in indexes are embedded, other lists are distinct text files, nevertheless indexes can be accessed -rather than shared- from different databases; other lists can be also shared | En: no, they are all embedded (but you can Copy and Paste an entire list or part of it) | RM: no, they are embedded; apart from the periodical list that can be copied from one database to another ("Term Manager" | Copy periodicals) | |
J - Relationship between lists' content and fields' content:
| ||||||||
| Cit: 1 automatically derived as far as the four "indexes" are concerned; 2 independent as far as keywords, journals and publishers TXT files are concerned; to update the keywords.ini must explicitly save the db index to it; 4 'names' list is a cluster for authors, editors, translators, whilst publishers and journals are 1:1 based | RW: 1: only derived; 3 | Bscp: 1: only derived, as far as the lookup lists are concerned (Refresh if edit an entry); 2: term table and Journal name list can import/export text tab delimited files; 3-4 apart from authors (primary secondary etc.) usually lists are 1:1 field based, non cluster fields | BK: 1: term lists are only derived 2: can host entries not contained in records as long as you do not updeate them to exactly reflect fields content; Journal glossaries are independent and host their own data; 3 each one exclusively belongs to the field that originates it, thus authors and editors are separate files 1:1 relationship | LM: 1: indexes: only derived; 2: terms lists : can contain external data and never reflect field content; 3: yes only 1:1 relationship | Pr: 1: the four indexes are only derived; 2: other term lists can contain external data; 4: uses cluster for any name and title | En: lists derive data from one or more fields (both permanently and on the fly) according to user's preferences; updating can be batch or automatic; any list can have content not derived from records (direct input or import from external source); cluster structure available, definitely not bound to 1:1 field basis | RM: 1: content is derived, but lists can also host entries not already contained in records; 3-4 some cluster fields are available; a "purge" action is available | |
K - Lists can be directly edited or must use global change function | ||||||||
| Cit: look-up lists can be edited only via global change (not field-based); journals and publishers and keywords.ini can be directly edited as TXT files, but records content is still to be modified via global change | RW: can be directly edited and records content is updated in real time | Bscp: via dedicated find/replace function using Regular expressions |
BK: term lists can be edited only via global change; Journal Glossaries can be directly edited, but records content is modified via global change |
LM: indexes can be edited only via global change; tables can be directly edited, but records content is modified via global change | Pr: 4 indexes require global change, the other term lists can be directly edited, but records content is modified via global change | En: yes, they can all be directly edited, but it has no influence on the entries actually contained in the records: must use global change to modify them | RM: yes straightforward global edit from Term manager and records content is automatically modified | |
L - New entries are validated (e.g. compare matching a "go list"; new/old entries, probably a duplicate ...). Autocompletion available (i.e.: matching closest entry already in the list) | ||||||||
| Cit: no validation; autocompletion available | RW: the list it automatically opened at the closest match | Bscp: no | BK: no; autocompletion available | LM: yes, validation is an option (for any type of field) | Pr: no | En: new entries displayed in red; close or identical term is suggested; autocompletion available | RM: yes (new are highlighted); autocompletion available | |
M - Printing lists
| ||||||||
| Cit: a) not the "indexes"; yes abbreviation lists and keywords.ini; b) outside as text file | RW: a) cannot be printed | Bscp: a) yes, use mouse right click on the list and save it as Excel or text file; b) outside as text file and from inside as far as Term and Journal lists are concerned | BK: a) yes, save them as text file and print | LM: a) yes all; b) indexes should be printed via an output Format; terms lists via ad hoc printing command button | Pr: a) yes all; b) from outside only the ALTERNAT list; 2: from inside print indexes: as Subject Bibliography (terms only); any other lists: export and save file | En: a) yes all (export as .TXT file) | RM: a) yes, all the 3 lists; from the inside | |
N - Import external data into the lists | ||||||||
| Cit: no (can insert, copy text into the keywords.ini + abbreviation tables) | RW: no | Bscp: no the lookup lists, yes the Term table and the Journal list | BK: no | LM: not the indexes, yes the terms lists that can be exported, imported, merged with external text files or other term tables of the same database (merge is supposed to warn you that duplicates were present and discarded) | Pr: no 4 indexes, yes the others | En: yes | RM: no
while importing, non abbreviated words of journal titles are automatically stored in the Periodical term dictionary |
|
O - Lists are useful during input | ||||||||
| Cit: yes the four "indexes" work as look-up lists | RW: yes,
also a short journal titles lookup list is available |
Bscp: yes (there are not as many as for searching and this is not customizable) | BK: yes: browse-pick-up terms while editing a record; can swiftly change list: Journal Glossary: abbreviation can be replaced by either short or full name | LM: yes. Any field can use a term/table list. One can force fields to accept data only if already present in a table | Pr: yes, all of them | En: yes | RM: yes | |
P - Lists can be used while searching and browsing | ||||||||
| Cit: (see Searching) | RW: yes (see Searching) | Bscp: yes (see Searching) | BK: yes (see Searching) | LM: yes (see Searching) | Pr: yes (see Searching) | En: yes (see Searching) | RM: yes (see Searching) | |
Q - Lists are useful for formatted output | ||||||||
| Cit: yes, publishers and journals lists work as abbreviation tables across all the styles, if set so | RW: no | Bscp: only Journal list | BK: only Journal Glossaries: can choose short or full form in citation styles | LM: yes the tables. Any style can configure the string to be replaced by specified abbreviation during output; any abbreviation entered in a field can be expanded to the relevant string (the relationship can be the reverse : "Abbreviation | String 1 | String 2 | etc." | Pr: ALTERNAT.TXT to replace «text» strings; matching entries in Journals list used in citation styles | En: journal list are also designed to replace field content by one out of three abbreviations
| RM: periodical list | |
|
| ||||||||
| Citation 9 | RefWorks (web based) | Biblioscape | Bookends | Library Master | Procite | EndNote | Reference Manager | - |
| | | | | | | | . |
