3. 
3.6. Database and record structure
Database and record structure |
||||||||
| RefWorks (web based) | Procite | EndNote | Reference Manager | |||||
|---|---|---|---|---|---|---|---|---|
 |
 |
 |
 |
|||||
A - Database and record organization |
||||||||
| RW: completely hidden (transparent) to the user (SQL tables based) | Pr: only vertical: Database -> Record -> Fields -> Subfields (where available: automatic and limited: names, dates, call numbers) | En: only vertical: Database -> Record -> Fields -> Subfields (available in personal names only: surname, name, suffix) | RM: only vertical: Database -> Record -> Fields -> Subfields only in personal names (surname, the rest of the name) | |||||
B - Horizontal links: between databases, between records, between list entries |
||||||||
| RW: not between databases; folders are virtual sets, pointers to records without physical duplication; not x-refs between list entries, but given the www hypertextual structure you can navigate from one record to another via the list terms (authors, keywords, journal titles etc.) | Pr: no (but "groups", and marked records are pointers to records without physical duplication) |
En: no (but "groups" are pointers to records without physical duplication) |
RM: only term synonyms in the 3 indexes (authors, kw, periodicals) : searching for one synonym is searching for all the connected terms (but "reference indexes" and marked records are pointers to records without physical duplication) | |||||
C - Hierarchical links (es. thesaurus, mother/sons records, text/notecards) |
||||||||
| RW: no |
Pr: no
some fields generate indexes which are entirely derived (automatically created and updated), cannot be directly edited. Field data and list contents (sort of look-up) can be "crossed" in output to replace text: string + alternate.txt; journal field + any journal.lst |
En: no
Term Lists can be regarded as autonomous (see dedicated section): their content can be imported from external text lists, updated from records, derived from different fields, directly edited. Field data and periodical title list can be crossed in output: e.g. secondary journal title (with up to three abbreviations) can replace text entered in records Journal field |
RM: no
some fields generate lists which are not only derived (i.e. automatically created and updated from record contents), for they can have independent entries and synonyms and can be directly edited |
|||||
D - Ready, predefined record structure: features of reference types |
||||||||
| RW: yes. Actually the input workform is only one, containing all the 51 fields and when it is opened, it may include an output style. In this case fields are ticked and grouped by the Accucite feature (accurate citing) to show which ones will be considered and displayed by the output style being used |
Pr: yes according to RT as input workform: individual files that can be shared among different databases (or you might keep them in different folders), if you move the database, you should also copy the workform files.
Fields bear "step" displayed name; fields are identified by a number which determinates their position: number is fixed across all the workforms; some fields (names, titles, dates, pages, URL, keywords, call number) have, to a different extent, properties -such as internal coding, indexing, output formatting, sort, searching...- that cannot lose or transfer to other fields; 2: yes, given abovementioned constraints, can add, delete, move, rename fields; attributes cannot be changed e.g. '5' is either "data file" or "medium designator" or "map type" in 3 different workforms: Data file, Newspaper, Map; if RT "Newspaper" -whereby 5 is "medium designator"- gets changed to "Journal Short form" which lacks
5, then 5 stays there with its content but no name, just number and can be edited;
|
En: yes, according to RT-reference types + other default preferences they are all automatically shared among different databases on the same computer, separately for each PC user.
|
RM: yes, according to RT reference types which belong to each database. fields bear a label as "step" displayed name; fields are identified by a number which does not imply a fixed position: number is fixed across all the RT; some fields (names, journal/periodical titles, dates, pages, link to URL etc., kw) have, to a different extent, properties (internal coding, indexing, output formatting, sort, searching, launch application...) that cannot lose or transfer to other fields | |||||
E - Number of RT record types |
||||||||
| RW: 31 | Pr: 39 | En: 42 (38 + 1 Generic + 3 Unused empty) | RM: max 37 fields allowed (of which: 5 user defined + 3 miscellaneous; all user-defined fields are URL and file path compatible) | |||||
F - Can modify the exisiting record types (apart from changing name) and create extra |
||||||||
| RW: not really, modifications are only related to the output style being used: include/exclude fields and comments that can be added to any field; cannot create extra field, cannot change their names, can use all of them | Pr: yes ( n, each is a file) | En: one can only add, delete, rename fields to a RT within the exisiting family; but attributes cannot be changed --apart from linking a field to a term list ; cannot create extra | RM: can add, delete, move (by dragging on the RT and fields edit window), rename fields within the existing family; their attributes cannot be changed; cannot create extra | |||||
G - Number of fields per record |
||||||||
| RW: 51 (46+5 user defined that can be renamed) + 2 (RefID, RT) + attachments | Pr: 45 | En: max 52: (45 + 7 user definable all of variable length) + 1 record number + 1 record type | RM: 37 (32+5 user defined) | |||||
H - Can create extra fields |
||||||||
| RW: no | Pr: no | En: no | RM: no | |||||
I - Fields attributes can be changed; can be applied to other fields |
||||||||
| RW: no | Pr: no |
En: no
the attribute 'field linked to a term list' is customizable insofar as a field can be included in only one list to be chosen, while a list can include terms from more than one field |
RM: no
but can always decide whether input in a given field is mandatory or not |
|||||
J - Multi-value fields allowed |
||||||||
| RW: several (among which authors, translators, descriptors ...) | Pr: Output display recognizes names and kw; automatic indexes recognize only names and kw (not the titles); sort in subject bibliography recognizes any field, provided separators are present
|
En: yes, always names (authors, translators etc.), and kw in: indexing, sorting the first author, output including subject bibliographies; lists can recognize different separators in every single field (<CR> is always accepted) | RM: names, kw, fields for URLs and other external resources | |||||
K - Record number
|
||||||||
|
RW: system assigned and reserved; it is a sortable and searchable field and it can be displayed in output |
Pr: system assigned or user assigned if wanted; allows for duplicates; renumbering is possible; can be used for sort, search and display; reuse deleted; can be alphanumeric when manually created | En: system assigned; reserved; record numbers change to avoid duplicates when records are added or copied and then renumbered; the same for output and for sorting the database list; it is searchable; can be displayed in output | RM: system assigned and also user controlled, both: either a) numeric, or b) author-date (more records of same author/same year automatically get alphabetic identifiers); renumbered when copied to another database with records bearing same numbers; it is a field that can be used in sorting, searching and display; alphanumeric when author-date | |||||
| RefWorks (web based) | Procite | EndNote | Reference Manager | |||||
| |
|
|
|
|||||
