|
|  |
3.7. Searching
Searching |
1 Different levels and approaches:
|
| RefWorks (web based): 1 easy; 2 menu driven; 3; 4 not really but 'advanced' is window-like with four available field choices and Boolean operators; 5 |
| Biblioscape:1. easy and expert; 2; 3; 4; 5.
Many different approaches for Bibliographic Database (i.e. References Module) Notes and Tasks Modules have got their own search methods (see below). Browsing the database in the brief record list: one record per line, as many field-columns as desired (7 by default, can add more); sort on top of column bar, descending sort only if secondary index available: can customize) Lookup search on 56 fields: select a field, entries (sortable) in term list show number of related documents (sortable) and point to them; Dynamic blue folder: one or more SQL (13 operators) query statements are permanently stored in a folder to form one SQL query: each statement is single field based; statements ar connected via boolean and, or, but it follows its own criteria: you write something like (A or B) and (C or D), it changes in A or B or (C and D) ... Quick search saved queries: field and the seeked value (no boolean operators) Indexed search it includes 3 submodules (+ 2 sub-sub), none can be saved as query expression: Fast (no boolean, no field selection); Smart pseudo-natural language queries or SQL (abbreviated or full), up to this extent: select bib.*, folder.*, fld_bib.* from bib, folder, fld_bib where (folder.Folder<>'Boronic Acid') and (fld_bib.Folder_ID=Folder.Folder_ID) and (bib.Ref_ID=fld_bib.Ref_ID). Here you can use the full power of SQL; Indexed: can use jolly characters (? *), boolean, soundex, near, parentheses: (A or B) and (C or D) it is possible here, but cannot save query expressions and the function is not assisted; Indexed is the only non-SQL searching mode within Biblioscape, it indexes every word in any record, no field delimited Advanced SQL query builder, statements are connected only by boolean AND, can be saved BiblioSQL: SQL queries tool, not driven: must be familiar with SQL; queries can be saved; Find: sequential search on any or one selected field Navigation through links established by users among bib. references, and references and Notes; also an automatic ring navigation through authors, keywords, journal titles: e.g. click on an author name and it will show all record in the database containing the same name Searching a Biblioscape database on the Internet via www interfacesee Internet and Other features
Tasks Module:
|
| Bookends: 1 easy + expert,
a) by means of one preformatted window with templates for : only one field selection plus record type, scope (database, retrieved records), mode (any text, whole words, right truncation); boolean operators; up to 10 query terms;
2, 4 : SQL/Regex (regular expressions) structured (on unindexed fields + indexed "any-field") |
| Library Master: 1 easy "jump to a record": type a string for an indexed field, on the short record list display; expert: assisted command driven (see 2);
2 command driven, assisted by buttons for fields and their contents, (not for operators apart from "="); syntax control; 3 (from indexed fields); 4; 5 Short Record List browsing is default window, database dependent: one record per line, can choose any field to display in columns. Quick Find/Jump to record: enter string based upon indexed fields. Sort on any displayed field by clicking the column field bar |
| Procite: 1 easy browsing indexes + direct "Quick Find" by typing string; expert: assisted command driven (see 2); 2 command driven, assisted by buttons but syntax errors are possible; 3; 4; 5
Short Record List browsing is default window, database dependent: one record per line, can choose any field to display in up to six columns. Quick Find: enter string based upon sort key. Sort on any displayed field by clicking the column field bar |
| EndNote: 1 one "query by example" template, with syntax control; 2: command driven only for Z39.50 searching, see below; 4 (very limited); 5. -- Mac ed. can also use Spotlight search
Short Record List browsing is default window, common to all databases: one record per line; can handle up to eight (8) columns and use any field to display. Quickly move to record by directly entering a string belonging to first sort field key (no special windows is displayed). Sort (A/D) on any displayed field by clicking the column field bar. Cannot use term lists here to point to records. Cannot toggle between short list and search result: one or the other. Can show preview of one highlighted record |
| Reference Manager: 1 Usually only expert; easy "Quick retrieval" available in Term Manager; 2: command driven, assisted by buttons; 3: no, lists are available only to pick up terms for a query, not to index and display records at once; 4; 5
Short Record list browsing is default window, not database dependent -and can apply to all lists (retrieved, imported, duplicates etc.): one record per line, can choose any field (up to 37); sort on any displayed field by clicking the column field bar. Quick retrieval lets select terms but only from Term Manager and launch <F12> a search (AND or OR) |
| Papyrus: 1 easy browsing database; expert: assisted command driven; 2; 3 quick find from journals, kw and names lists; 4; 5
Browsing mode depends on formats built-in or user defined; tabular -usually shorter- format is available |
2 Browsing indexes to search
|
| RefWorks (web based): 1, 3 |
| Biblioscape: 1 (can sort A/D on lookup list entry or count number of related documents); 3
2 relationship between records are indicated by an icon in the preview pane of the brief record list display |
|
Bookends: 1 3; the 4 built-in indexes/term lists and any other field based term list can be browsed to display the connected records in two situations: a) "Utilities" --> Term lists; b) when --> a full reference is displayed, --> the relevant term list button is pressed --> the brief view of records connected to that entry is activated; in both cases can swiftly switch list |
| Library Master : 3
entry lists can be used in command driven searching to pick up terms to insert in a query expression or on the general short list to quickly spot entry related records |
| Procite: 1; 3 |
| EndNote: n.a. (term lists are only accessible on the query menu window to pick up entries from and use as search elements) |
| Reference Manager: n.a. (see above Term Manager) |
| Papyrus: 1; 2 (kw); [3 not a contextual display but a quick search] |
3 Query expressions |
| RefWorks (web based): not really, but can use four boxes for queries and boolean operators |
| Biblioscape: yes, see above 1 Different levels and approaches for details |
| Bookends: not in easy module, yes SQL/Regex |
| Library Master: assisted by command buttons to select: fields, contents, previous queries, scope (subsets) |
| Pr: assisted by command buttons to select: fields, operators, terms, previous queries |
| En: assisted by template and buttons to select fields, operators, scope, (options: remote search, e.g. Z39.50, match full word, case, Full text Index (previously named Quick Index): was meant to avoid automatic left truncation -which is active by default with 'Contains' operator-, it has been replaced since v. X, by Word begins with or Field begins with); terms lists are available only to pick-up terms: due to the windows structure is almost impossible to create a complex, controlled, syntactically correct query expression |
| RM: assisted by command buttons to select: fields, operators, terms, previous queries |
| Papyrus: assisted by command buttons to select: fields, operators, terms |
4 Natural language queries |
| RefWorks (web based): no |
| Biblioscape: yes in Smart Search see above 1 for details |
| Bookends: no |
| LM: no |
| Pr: no |
| En: no |
| RM: no |
| Papyrus: no |
5 Search strategy : can save and recall search expressions |
| RefWorks (web based): no |
| Biblioscape: yes limited to: Dynamic blue folder, Quick Search, Advanced search (see above 1 Approaches for details) |
| Bookends: yes |
| LM: yes |
| Pr: yes |
| En: yes |
| RM: yes |
| Papyrus: yes (if the resulting set of retrieved records -group- is saved, the originating query is saved as well: can be re-run and edited) |
6 Shows hits of each search expression component |
| RefWorks (web based): no |
| Biblioscape: no |
| Bookends: no |
| LM: no, only total records number |
| Pr: no, only total records number |
| En: no, only total records number |
| RM: total number of records also for each line of a multiline query (but not for its internal components nor for the last line) |
| Papyrus: no, only total records number |
7 Refine (search within search result) |
| RefWorks (web based): no (but can search folders) |
| Biblioscape:no |
| Bookends: yes |
| LM: yes |
| Pr: yes |
| En: yes |
| RM: yes |
| Papyrus: yes |
8 Advanced search features
|
| RefWorks (web based): 1: ranking by relevance is on by default for Quick search -and cannot be customized- when more than one word are used; with single word Quick search only sorting (date | author)
3: authors, descriptors, journal titles (full & short), URL are all active links within this entirely web based catalogue |
| Biblioscape:2 (soundex), 3 |
| Bookends: no |
| LM: 2 |
| Pr: no |
| En: no |
| RM: no |
| Papyrus: 3
kw file allows links between entries, also records can be linked: search can be limited/expanded to selected/all types of links; number of levels for the same link can also be selected: up- down- posting (thesaurus-like) |
9 Highlighting search terms in result (and jump to next occurrence of term) |
| RefWorks (web based): highlight |
| Biblioscape: no |
| Bookends: highlight and jump both when searching within the result hit list or in the same reference |
| LM: yes, in the record editable display (no * "jump") |
| Pr: no |
| En: no (but "Go to" and "Next" commands, to find a R/L truncated string within a reference) |
| RM: yes in the Output display --not in the Standard editable one, (no * "jump") |
| Papyrus: no |
10 Indexing operation
|
| RefWorks (web based): 1 |
| Biblioscape:1 but can reindex and update indexes and lookup lists |
| Bookends: 1 automatic |
| LM: 1 automatic when saving a record |
| Pr: 1 automatic when saving a record |
| En: 1 automatic when saving a record |
| RM: 1 automatic when saving a record |
| Papyrus: 1 automatic when saving a record |
11 Scope of searching
|
| RefWorks (web based): 1 2 (all authors, all periodicals, but dates are scattered over several fields) 3 |
| Biblioscape: 1 2 3 4 (near operator, see above 1 Approaches |
| Bookends: 1 just one field + RT; 3; |
| LM: 1 yes with field indicator (RT included); (N.B. no cluster: e.g. different titles, authors, dates fields are to be searched for individually); 3 |
| Pr: 1 yes with field indicator (RT included); 2 limited to three clusters; author, title, date; 3 yes, default |
| En: 1, RT included; (N.B. no cluster: e.g. 5 different title fields, 4 authors, 2 dates: each is to be searched for individually) 3 any field |
| RM: 1 (RT included); 2 (predefined: indexed fields, non-indexed fields, authors, titles) |
| Papyrus: 1 (RT included); 2; 3 ("general" but does not include either kw or journals) |
12 Case sensitiveness |
| RefWorks (web based): no |
| Biblioscape: yes when SQL is acting |
| Bookends: yes in SQL/Regex |
| LM: yes (optional: if exact search command is selected) |
| Pr: no |
| En: yes if Match Case option is on |
| RM: no |
| Papyrus: no |
13 Diacritics make difference |
| RefWorks (web based): yes ("liberta" will not retrieve "libertà" and viceversa) |
| Biblioscape: yes, "liberte" will not retrieve "liberté", must search using diacritics |
| Bookends: "liberté" will retrieve only "liberté"; "liberte" will retrieve both "liberte" and "liberté" |
| LM: yes, they can make a difference (optional: if exact search command) |
| Pr: no difference, "Göthe" = "Gothe" |
| En: no difference, "Göthe" = "Gothe" ; "unità" = "unita" and viceversa (but Goethe is another name) |
| RM: yes, they make difference "liberta" not the same as "libertà" (can be used only in: Authors, kw, Titles, Notes) |
| Papyrus: no difference |
14 Can use and nest parentheses, create real query expressions |
| RefWorks (web based): no, automatically ruled and to a limited extent: according to its vertical priority, the up most query element is the first and inner most within the implicit search expression (A OR B) AND (C OR D) would become: (((A OR B) AND C) OR D); also: (A AND B) OR (C AND D) would become: (((A AND B) OR C) AND D), which is totallydifferent |
| Biblioscape: yes only in Indexed and SQL search (see above 1 Approaches) |
| Bookends: no: it can't nest in the easy module, yes in SQL/Regex |
| LM: yes |
| Pr: yes |
| En: no, automatically ruled and to a limited extent: according to its vertical priority, the up most query element is the first and inner most within the implicit search expression, e.g. A and B not C or D is equal to: (((A and B) not C) or D) = the whole first part result will be ored with D, therefore it is different from: (A and B) not (C or D) which cannot do. |
| RM: not really; to a limited extent and implicitly: according to its vertical priority, the up most query element is the first and inner most within the implicit search expression, e.g. A and B not C or D is equal to: (((A and B) not C) or D) = the whole first part result will be ored with D therefore it is different from: (A and B) not (C or D) which cannot do;
neither can do: (A or B) and (C or D) unless each couple (triple etc.) of values belongs to the same field [i.e. it is possible Titles [3,13,23] = {dolphins } OR {atlantic} OR {bottlenose} AND Authors [4,14,24] = {Au,W.W.} OR {Orso,Franco}] |
| Papyrus: yes |
15 Priority within search operators and queries |
| RefWorks (web based): vertically: first comes the upper most, see 14 above |
| Biblioscape: set by parentheses in Indexed and SQL search, "random" elsewhere (see above 1 Approaches) |
| Bookends: top most has got the priority; SQL/Regex use of parentheses |
| LM: standard : left to right; if AND operator is used, indexed fields come first; by using parentheses one can modify the order |
| Pr: set by using parentheses, the inner most comes first |
| En: vertically: first comes the upper most, see 14 above |
| RM: no explicit parentheses; vertically: the highest comes first, see 14 above |
| Papyrus: set by using parentheses, the inner most comes first |
16 Boolean operators
|
| RefWorks (web based): 1 2 4 |
| Biblioscape: 1 2 4 (see above 1 Approaches) |
| Bookends: 1 2 3 (just skip the first window and select NOT) 4 + SQL/Regex |
| LM: 1, 2, 3, 4, 5 indirectly |
| Pr: 1 2 3 4, 5 indirectly |
| En: 1 2 3 (as "omit from showing references") 4, 5 indirectly (two steps: OR + "omit" AND) |
| RM: 1 2 4 |
| Papyrus: 1 2 3 4, 5 indirectly |
17 Relational operators
|
| RefWorks (web based): no |
| Biblioscape:where SQL syntax is included (see above 1 Approaches) |
| Bookends: yes in SQL/Regex |
| LM: 1, 2, 3, 4, 5, 6, 7 for dates (or via: x > y and x < z), 8 |
| Pr: 1, 2, 3, 4, 5, 6, 7 for dates (or via: x > y and x < z), 8 |
| En: 1, 2 as "Omit from showing references" option, 3, 4, 5, 6, 7 (e.g. "1998 in Year Is greater than or equal to, And, 2000 in Year Is less than or equal to"; other finding options must not be checked), 8 |
| RM: 1, (3 only for earlier than today's date in Reprint status=On request); 7 in dates and RefID (RN) only; |
| Papyrus: 1, 3, 4, 5, 6, 8 (by adding a backslash to the search string, e.g.: Author=Smith,P\ will not match "Smith, Paul") |
18 Can combine boolean, relational operators, parentheses, truncation etc. |
| RefWorks (web based): no |
| Biblioscape: in Indexed search and wherever SQL syntax is included (see above 1 Approaches) |
| Bookends: yes in SQL/Regex |
| LM: yes |
| Pr: yes |
| En: yes (given the abovementioned constraints) |
| RM: yes (but only range and given the abovementioned constraints) |
| Papyrus: yes |
19 Truncated search (explicit: with / implicit: without wildcards, e.g. ? *)
|
| RefWorks (web based): 1 implicit 2 3 4 |
| Biblioscape: 1 explicit, 2 3 4, in Indexed search and wherever SQL syntax is included (see above 1 Approaches) |
| Bookends: 1 implicit 2 3 and 4 if the 'characters' option is selected + all options in SQL/Regex |
| LM: 1 yes explicit with wildcards (* or }); 2; 3; 4 |
| Pr: 1 yes (* ASCII 42) 2 (avoid right tr. by using "Ends with" operator); 3 (avoid left tr. by using "Begins with" operator); 4 : operator "contains"
"contains" is like "=" equal, with implicit l/r truncation; whereas explicit l/r truncation ( *xxx*) is used with "=" e.g. AUTHOR contains ale, AUTHOR = *ale*, no: AUTHOR contains *ale*,) |
| En: 1 l/r implicit; 2 right (avoid right tr. by using "Field ends with" operator); 3 left; 4 l/r "Contains" operator (unavailable when using Match words; avoid left tr. by using "Word" or "Field begins with" operator) |
| RM: l/r explicit in indexed fields (only indexed fields require truncation symbol); l/r implicit in non indexed fields (non-indexed fields will take * as a real character, reverting to \*) |
| Papyrus: 1 explicit; 2; 3; 4 |
20 Search for not/empty fields |
| RefWorks (web based): no |
| Biblioscape: where SQL syntax is included (see above 1 Approaches) |
| Bookends: yes (empty: enter nothing, not empty: enter * asterisk) |
| LM: yes both
and also if a field is present just as an element of a RT structure |
| Pr: yes (dedicated operators: EMPTY, NOT EMPTY) |
| En: yes,
empty: "field" is [blank];
|
| RM: "yes", only in indexed fields: look for records (RefID range) then exclude (NOT) or include (AND) any character * |
| Papyrus: yes |
21 Internal wildcards ("masking" e.g. ? * : m*ss, for miss mass mess mistress ..) |
| RefWorks (web based): no |
| Biblioscape:in Indexed search and wherever SQL syntax is included (see above 1 Approaches) |
| Bookends: yes in SQL/Regex (Regex \B) |
| LM: no |
| Pr: no |
| En:no |
| RM: no |
| Papyrus: yes * for any character |
22 Z39.50 Searching |
| RefWorks (web based): yes (can modify or create new connections) |
| Biblioscape: no |
| Bookends: no |
| LM: no
the specialized BookWhere?® package can be obtained at a special price through Balboa Software and offers direct export to LM format |
| Pr: yes,
embedds previous "companion" BookWhere?® package; use special -simplified and limited- search interface (e.g.: cannot use parentheses, see above 7.19: (A or B) and (C or D) will not be possible); can search different databases simultaneously; automatically converts and saves result in db, separate folder; can save search expressions; can modify or add new hosts and configure; can configure conversion filters which are separate individual files, but one single file for all the different hosts configuration and properties; cannot specify text characters set (ANSEL, Latin-1...); log file available in C:\Documents and Settings\[User name]\Application data\EndNote
|
| En: yes
embedded proprietary software; use same interface as normal searching function (with less options**); cannot search different databases simultaneously, but can launch more than one parallel search session; can save result in db without conversion; can batch import downloaded file (select from window and copy it to a new file); can modify or add new hosts and configure; can configure conversion filters; host configuration, connection properties and filters are individual files; can specify text characters set (ANSEL, Latin-1, Unicode UTF-8, Unicode UTF-16...etc.) and > 20 record format syntaxes.
|
| RM: yes,
embedds BookWhere?® package; use same interface as normal searching function; can search different databases simultaneously; automatically converts and saves result in db, separate folder; can modify or add new hosts and configure hosts and filters which are individual files, but one single file for all the different hosts configuration and properties; can specify text characters set (ANSEL, Latin-1...)
|
| Papyrus: no |
* Other features that could be taken into account
|
