3. 
3.3.1. Term/Entry lists
Term/Entry lists |
|||||||||
| Bibus | EndNoteWeb (web based) | RefWorks (web based) | Procite | EndNote | Reference Manager | ||||
|---|---|---|---|---|---|---|---|---|---|
 |
 |
 |
 |
 |
 |
||||
1 - Tipology and quantity |
|||||||||
| Bibus : list (called: Shortcuts) are list of fields content; any number; name is free; only created in batch; you can update and populate them at different stages, each time choosing the same or another field; useful only while inputting data into records; classic Journal list with abbreviations -only useful for output citation styles- is another object | EN: none | 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; any Journals list with up to three abbreviations can also be used for output purpose |
RM: 3 built-in term lists Authors, Journals, Keywords + 1 single optional Phrase list (they do not work the same way for Phrase list is only one, embedded in each db, terms cannot be imported in it or exported from it, no editing available) |
||||
2 - Can create extra |
|||||||||
| Bibus : yes | EN: n.a. | RW: no | Pr: not indexes, just term lists | En: yes | RM: no | ||||
3 - Can modify the structure of the lists or disactivate them |
|||||||||
| Bibus : yes, both | EN: n.a. | 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 | ||||
4 - Lists entries can be linked by cross-references (see, see also, NT/BT, later/earlier etc.) |
|||||||||
| Bibus : no | EN: n.a. | 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 and cataloging by capturing terms | ||||
5 - Relationship between lists' content and fields' content:
|
|||||||||
| Bibus : starting profile is usually 1:1, but when you batch update a list, you may choose a different field at any time: the result will be a cluster (addition) of content coming from different fields | EN: n.a. | RW: 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: uses cluster for names titles and dates | En: cluster structure available, definitely not bound to 1:1 field basis | RM: some cluster fields are available | ||||
6 - Lists can be directly edited or must use global change function |
|||||||||
| Bibus : directly edited, but with no effect on database records | EN: n.a. | 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: records content is automatically modified | ||||
7 - 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) |
|||||||||
| Bibus : no | EN: n.a. | 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 | RM: yes (new are highlighted in colour); autocompletion available | ||||
8 - Lists can be printed/exported |
|||||||||
| Bibus : no | EN: n.a. | RW: no, cannot be printed | Pr: yes all | En: yes all (export as .TXT file and then print the) | RM: yes, all | ||||
9 - Import external data into the lists |
|||||||||
| Bibus : no | EN: n.a. | RW: no | Pr: no 4 indexes, yes the others | En: yes, merge not overwrite |
RM: no
while importing records, non-abbreviated words of journal titles are automatically stored in the Periodical term dictionary |
||||
10 - Lists are useful during input |
|||||||||
| Bibus : yes | EN: n.a. |
RW: yes,
also a short journal titles lookup list is available |
Pr: yes, all of them | En: yes | RM: yes | ||||
11 - Lists can be used while searching and browsing |
|||||||||
| Bibus : no | EN: n.a. | RW: yes (see Searching) | Pr: yes (see Searching) | En: no (see Searching) | RM: yes (see Searching) | ||||
12 - Lists are useful for formatted output |
|||||||||
| Bibus : only dedicated Journa list | EN: n.a. | RW: no | Pr: ALTERNAT.TXT to replace «text» strings; matching entries in Journals list used in citation styles | En: journal lists are designed to replace field content by one out of up to three abbreviations
|
RM: periodical list | ||||
| Bibus | EndNoteWeb (web based) | RefWorks (web based) | Procite | EndNote | Reference Manager | ||||
|
|
|
|
|
|
||||
Keywords: Abbreviations ; Authority files ; Autocompletion ; Go list ; Indexes ; Journal list ; Term lists ; Validation
