3. 
3.9. Term/Entry lists
Term/Entry lists |
||||||||
A - Tipology and quantity |
||||||||
| RefWorks (web based) | Procite | EndNote | Reference Manager | |||||
|---|---|---|---|---|---|---|---|---|
 |
 |
 |
 |
|||||
| RW: 3 built-in index lists for authors (i.e. any name field), journal titles, kw-descriptors | Pr: 4 built-in indexes: 5 Field Content Lists: Authors, Titles, Journals, Keywords, RTs; 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 |
||||||||
| RW: no | Pr: not indexes, just term lists | En: yes | RM: no | |||||
C - Can modify the structure of the lists or disactivate them |
||||||||
| RW: no, cannot modify but you can disactivate them | Pr: no cannot modify, but can create more lists ad libitum | En: yes both | RM: no | |||||
D - Lists recognize multi-value (repeatable) fields so that each occurrence becomes a distinct term |
||||||||
| RW: 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 |
||||||||
| RW: no | Pr: no | En: no | RM: no | |||||
F - Lists allow efficient alphabetic scrolling (i.e. incremental searching) |
||||||||
| RW: 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 |
||||||||
| RW: no | 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.) |
||||||||
| RW: 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 |
||||||||
| RW: no never separated; cannot be shared among db also because each user can access only one db; cannot be exported as a file | 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; any can be exported | 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); they can be exported | |||||
J - Relationship between lists' content and fields' content:
|
||||||||
| RW: 1: only derived; 3: authors list is a unique cluster for any 'name' field (author, editor, translator etc.); other lists -descriptors, periodicals, are 1:1 field based in edit (periodicals becomes cluster of two fields -short/full title- only in searching); other titles are scattered | Pr: 1: the four indexes are only derived; 2: other term lists can contain external data; 4: uses cluster for any name and any 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 |
||||||||
| RW: can be directly edited and records content is updated in real time | Pr: 4 indexes require global change, the other term lists can be directly edited, but records content is modified only 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) |
||||||||
| RW: the list it automatically opened at the closest match | 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
|
||||||||
| RW: a) cannot be printed | 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 |
||||||||
| RW: no | 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 |
||||||||
|
RW: yes,
also a short journal titles lookup list is available |
Pr: yes, all of them | En: yes | RM: yes | |||||
P - Lists can be used while searching and browsing |
||||||||
| RW: yes (see Searching) | Pr: yes (see Searching) | En: no (see Searching) | RM: yes (see Searching) | |||||
Q - Lists are useful for formatted output |
||||||||
| RW: no | 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 | |||||
| RefWorks (web based) | Procite | EndNote | Reference Manager | |||||
| |
|
|
|
|||||
