3. 
3.4. Database and record structure
Database and record structure | ||||
| Library Master | Procite | EndNote | Reference Manager | Papyrus |
|---|---|---|---|---|
4.1 Files | ||||
| LM: 3 files: dbn.LMD dbn.LMI, dbn.LMS (respectfully: data, indexes, subsets) | Pr: 2 files: dbn.PDT dbn.PDX (respectfully: data and indexes) | En: 1 file: dbn.ENL (+ dbn-Dupl.enl for duplicates+ folder for storing images and charts files)
Modified record types and general preferences are stored for all libraries in the Windows registry: to entirely move libraries to another machine, those changes have to be replicated, see below 4.5. In Macintosh they are stored in: Users -> [your folder] -> Library -> Preferences -> EndNote f folder
|
RM: 2 files dbn.RMD dbn.RMX (respectfully: data and indexes) | Papyrus: 2: db db.IDX (respectfully: data and indexes) |
4.2 Internal database and record structure | ||||
| LM: only vertical: Database -> Record -> Fields -> Subfields (where available: automatic and limited: names, dates) | Pr: only vertical: Database -> Record -> Fields -> Subfields (where available: automatic and limited: names, dates, call numbers) | En: only vertical: Database -> Record -> Fields -> Subfields (names only) | RM: only vertical: Database -> Record -> Fields -> Subfields in names | Papyrus: vertical: Database -> Record -> Fields -> Subfields in names
Relational: record(s) to (record(s); keyword(s) to keyword(s); record(s) to journal titles and keywords |
4.3 Horizontal links: between databases, records, list entries | ||||
| LM: no (but "subsets", and marked records are pointer to records vithout physical duplication) | Pr: no (but "groups", and marked records are pointer to records vithout physical duplication) | En: no | RM: only term synonyms in the 3 indexes (authors, kw, periodicals) : searching for one is searching for all (but "reference index" and marked records are pointer to records vithout physical duplication) | Papyrus: yes, between records; between keywords; various types of links: some built-in, others can be added; Search, Print/Export recognize links for records on the basis of their type; Search recognizes links for keywords on the basis of their type |
4.4 Hierarchical links (es. thesaurus, mother/sons records, text/notecards) | ||||
| LM: no
fields can generate indexes which are exclusive to the generator field, entirely derived from it (i.e. automatically created and updated); cannot be directly edited. Any field data and term list contents (sort of look-up) can be "crossed" in output to replace text: string + abbreviation(s) |
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, 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 field |
RM: no
some fields generate indexes which are not only derived (i.e. automatically created and updated), for they can have independent entries and synonyms and can be directly edited |
Papyrus: yes, between records; between keywords; various types of links: some built-in, others can be added; Search, Print/Export recognize links for records on the basis of their type; Search recognizes links for keywords on the basis of their type and depth
see also dedicated sections: 8 Thesaurus and 14 Term/Entry lists, authority files |
4.5 Ready, predefined record structure | ||||
| LM: yes
they belong to each database.
|
Pr: yes (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 |
En: yes (reference types with other default preferences) they are all automatically shared among different databases on the same computer (stored in the Windows system registry), if you move your database(s) to another machine, you are not automatically carrying the RT modifications and other prefs. with you, but using those active on the new machine, otherwise you must copy the preferences from-to the Windows registry or modify them within the target EndNote db | RM: yes (reference type)
they belong to each database |
Papyrus: yes (reference type)
they belong to each database |
4.6 Input worksheets for different Record types
| ||||
| LM:
1: 50 workforms/RT -with varying fields- for books, articles, thesis, reviews, videos etc.; fields are identified by name: total number is fixed max 65; fields are identified by name; any field has got properties such as : content type (text, number, name, date, call number, literature reference sources); features : repeatable (multiple), required, unique, validate new entry, ignore leading words in searching and sorting, linked to a term table (plus : only tables terms allowed, expand abbreviations if contained), indexed for faster search; fields come with predefined properties but user can change, add, port to other fields; field properties are automatically the same in all RTs (i.e. if subjects field is required, it will so through articles, thesis, computer programs etc.) 2: yes, very deeply 3: yes n, if a field is deleted from RT, or RT is changed to a non-matching type, existing field content is lost;
|
Pr:
1: 39 workforms -with varying fields- for books, articles, e-mail, thesis etc.; fields bear "step" displayed name: total number is fixed max 45; 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 3: yes n, each is a file 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:
1: 30 workforms/reference types -with varying fields- for book, articles, e-sources, ase, bill, thesis etc. (not for journal as a whole serial); fields bear "step" displayed name: total number is fixed max 40; fields are identified by the position they hold in the Generic RT, fixed across all reference types; some fields (names, journal titles, pages, URL, keywords, figure, caption) have peculiarities (internal coding, indexing for fast search, output formatting, sort...) that cannot loose or lend to other fields; but the link between a term list and a field is customizable 2: given the abovementioned constraints, one can add, delete, rename fields; but attributes cannot be changed --apart from : a) link to a term list, b) use or not use indexes during search 3: one can use the six undefined custom fields when a field is deleted from RT (or mismatched), existing content is put to the corresponding Generic RT field; no numeric fields apart from RN for sorting; if fields names are changed in RT, styles are automatically updated, searching and global editing are not affected
|
RM:
1: 35 predefined forms: Reference Types -with varying fields- for books, articles, e-mail, thesis, video, electronic citation etc.; fields bear a label as "step" displayed name: total number is fixed max 37 (of which: 5 user defined + 3 miscellaneous; all user-defined fields are URL and file path compatible); fields are identified by a number which does not imply a fixed position: number is fixed across all the RT; some fields ( names, 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; 2: yes, given the abovementioned constraints, can add, delete, move (by dragging on the RT and fields edit window), rename fields; their attributes cannot be changed 3: no |
Papyrus:
1: 16 predefined forms: Reference Types -with varying fields for books, articles, internet resources, thesis etc.; fields bear a base name which identifies them plus a RT specific name; total number of built-in fields is 59; Any field has got attributes as far as: type (more than 15 types: name, year, number...), quantity (multiple occurrences), indexing (word, phrase ... + n. of chars per indexed word), spell-checking, position within RT and mandatory/optional input 2: modify built-in reference types by adding user-created fields, and changing: name, position, mandatory/optional input of fields; user created RTs are under user's control 3: yes, can create (up to 100) new RTs and (up to 100) new fields [which can be added to built-in RTs] |
4.7 Fields attributes can be changed; can be applied to other fields | ||||
| LM: yes | Pr: no | En: no
the attribute of a field being linked to a term list is customizable insofar as a field can be included in only one list, while a list can include more fields |
RM: no
but can always decide whether input in a given field is mandatory or not |
Papyrus: built-in fields attributes cannot be changed (apart from: no of chars per indexed word; spell-checking and position within RT); attributes for new fields are entirely under user's control until a field is created, then it cannot be altered |
4.8 Multi-value fields
| ||||
| LM: 1: present (output display can recognize also first last and all other occurrences); 2 each entry on a new line (if you select entries from the list, it is up to you not to leave them on the same line) | Pr: 1: Output display recognizes names and kw; automatic indexes recognize only names and kw; sort in subject bibliography recognizes any field, provided occurrences are separated by: slash(es), <CR> Line Feed or semi-colon (;) in author field
2: separators for names and kw and see 1 |
En: names (authors, translators etc.), and kw as far as output is concerned (including subject bibliographies); lists can recognize different separators in every single field (<CR> is always accepted)
2: each occurrence on a new line or properly separated via punctuation |
RM: 1 names, kw , URLs and other external resources; 2 each value is separated by a semi-colon (;) | Papyrus: 1 authors, editors -and their roles, publishers, places, several patents fields, keywords, pictures ... are built-in fields defined as multiple; any newly created field can be multiple and input, indexing, output will recognize this property;
2: each occurrence on a new line |
4.9 Indexed fields for searching | ||||
| LM: all fields content is automatically indexed, out of user's control (apart from one general option : whole or beginning of field is the default searchable string); each character (right/left truncation), word, phrase, is indexed, with user defined stopwords only if in leading position; user can define fields as "indexed" for faster search | Pr: all fields content is automatically indexed, out of user's control; each character (right/left truncation), word, phrase, is indexed, without stopwords, and thus retrievable | En: generally speaking, all fields content is automatically indexed, out of user's control; each character (right/left truncation), word, phrase, is indexed, without stopwords, and thus retrievable.
Special indexes for authors are built-in but but can be excluded from search. Also, one can decide to have, or not, QuickIndexes for kw or full-text; left truncation is not available in the Indexes (Quickindexes increase search speed and db size) |
RM: all fields are indexed for searching purposes: Authors, Dates, Periodical titles, kw, have special -faster- indexes | Papyrus: all fields content is automatically made searchable; many built-in fields are indexed to improve reterieval speed: RN, RefID, names, dates, titles, journals, medium, publishers and places, abstract, comment, kw; indexing for user created fields is under user's control |
4.10 Record number
| ||||
| LM: 1 2 5 6 7 8 9 | Pr: 1 3 (if wanted); 4 5 6 7 8 9 10 (must manually assign) | En: 1; 2; 5 numbers change to avoid duplicates when records are added or copied; 6 as well for output as for sorting the database list; 7; 8
when RN 32,767 has been created (input or import), maximum capacity of db has been reached |
RM: 1 system and 3 user, both: either a) numeric, or b) author-date (more records of same author/same year get alphabetic identifiers); 5 when copied to another database with records bearing same numbers; 6; 7; 8; 10, as 1 b) author-date | Papyrus: 1; 3; 5 (only if copied to another database with records) 6; 7; 8; 9 (must manually enter); 10 as RefID |
