Home . Forum

Bibliography formatting software: an evaluation template

by Francesco Dell'Orso

TABLE OF CONTENTS

  • Legend
  • Web resources
  • 1 Identity card
  • 2 Installation
  • 3 General
  • 4 Structure
  • 5 Input/Edit
  • 6 Import
  • 7 Search
  • 8 Thesaurus
  • 9 Output
  • 10 Formatting language
  • 11 Sort
  • 12 Export
  • 13 Manuscript formatting
  • 14 Term/Entry list
  • 15 Documentation


  • .
    F. Dell'Orso, Bibliography Formatting Software: An Evaluation Template
    Last Update: August, 18, 2000

    4 Database and record structure
    4.1 Files
    Pr: 2 files: dbn.PDT dbn.PDX (respectfully: data and indexes) En: 1 file: dbn.ENL
    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
    Pr: only vertical: Database -> Record -> Fields -> Subfields (where available: automatic and limited: names, dates, quot;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
    Pr: no ("group" is a virtual duplication of -pointer to- records) En: no
    RM: only term synonyms in the 3 indexes: they are equivalent in searching ("reference index" is a virtual duplication of -pointer to- records) 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)
    Pr: no En: 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 Term Lists can be regarded as autonomous (see dedicated section): their content can be imported from external text, updated from records, directly edited. Field data and list contents (sort of look-up) can be "crossed" in output to replace text: secondary title (journal) field + journal list (with up to three abbreviations)
    RM: no 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
    some fields generate indexes which are not only derived, i.e. automatically created and updated, as they can have indipendent entries and synonyms and can be directly edited see also dedicated sections: 8 Thesaurus and 14 Term/Entry lists, authority files
    4.5 Ready, predefined record structure
    Pr: yes (workform), can be shared among different databases En: yes: "reference types", which are automatically shared among different databases (stored in Windows system registry)
    RM: yes (reference type), they belong to each database Papyrus: yes (reference type), they belong to each database
    4.6 Input worksheets
        1. features
        2. can be modified
        3. can create others
    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
    En:
    1: 26 reference types -with varying fields- for book, articles, e-source etc.;

    fields bear "step" displayed name: total number is fixed max 38; fields are identified by the number they bear in the Generic RT which determinates their position: number is fixed across all the reference types (workforms); some fields (names, journal titles, pages, URL, keywords) have peculiarities (internal coding, indexing, output formatting, sort...) that cannot loose or lend to other fields;
    2: yes, given abovementioned constraints, can add, delete, move, rename fields; attributes cannot be changed
    3: yes, up to three
    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;
    no numeric fields apart from RN for sorting; internal pub. date format, Call number for sorting; if fields names are changed in workforms, styles are affected and must be manually fixed, searching and global editing are not
    if a field is deleted from RT, existing record content is put to corresponding Generic RT field renamed;
    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 etc.; fields bear a label as "step" displayed name: total number is fixed max 33 (5 user defined); 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, URL, kw) have, to a different extent, properties (internal coding, indexing, output formatting, sort, searching...) that cannot lose or transfer to other fields;

    2: yes, given the abovementioned constraints, can add, delete, move, 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
    Pr: no En: no
    RM: no Papyrus: built-in fields attributes cannot be changed (apart from: n. 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 Multiples (multi-value) fields
        1. present/absent
       2. specific input rules
    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 as for the output (not kw); no headings sort; lists can recognize different separators in every single field (<CR> always fine)
    2: each occurrence on a new line or properly separated
    RM: 1 names and kw (33 URL); 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
    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: all fields content is automatically indexed, out of user's control (apart form QuickIndexes for kw or full-text); each character (right/left truncation), word, phrase, is indexed, without stopwords, and thus retrievable
    RM: all fields are indexed for searching purposes: Authors, Dates, Periodical titles, kw have special 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
       1. system assigned
       2. reserved, cannot be altered
       3. user assigned
       4. allows duplicate numbers
       5. renumbering
       6. is a sortable field
       7. is a searchable field
       8. can be displayed in printed output
       9. reuse deleted numbers
       10. can be alphanumeric
    Pr: 1 3 (if wanted); 4 5 6 7 8 9 10 (must manually assign) En: 1; 2; 5 (only if copied to another database with records); 6 for output; and database list; 7
    RM: 1; 2 if 1; 3; 5 (only if copied to another database with records); 6; 7; 8; 9 (must manually enter); 10 Papyrus: 1; 3; 5 (only if copied to another database with records)   6; 7; 8; 9 (must manually enter); 10 as RefID


      Previous section   Table of contents   Legend   Following Section   back to Introduction  

    Back to top of page


    F. Dell'Orso, Bibliography Formatting Software: An Evaluation Template
    Last Update: August, 18, 2000

     
     
    | © ESB Forum | a cura di Riccardo Ridi |