NEPHIS is a string indexing system. In a string indexing system, computer software accepts source descriptions of indexed items and generates a set of index entries for each description. The index entries from a single source description usually provide the same, or similar, information, but each at a different place in the index.
For example, from the source description
@Use? of <Numeric <Data>>? in <Humanities? & <Social Sciences? & >> . 123NEPHIS software generates the index entries:
Most of a NEPHIS source description consists of words and phrases in ordinary language. To control the index entries produced, the indexer can use four different coding symbols: the left and right angular brackets ("<" and ">"); the "at" sign ("@"); and the question mark ("?").
The "<" and ">" mark off nested phrases within the source description. Examples of nested phrases in the source description above are:
Normally, the software produces one index entry corresponding to each of the nested phrases within a source description and one corresponding to the source description as a whole. An "@" at the beginning of a nested phrase or of the whole source description suppresses generation of the corresponding index entry. For example, the "@" at the beginning of the source description above means that there is no corresponding index entry beginning with "Use".
A "?" in the source description marks the beginning of a connective that is to be omitted from some of the entries. If the next coding symbol after the "?" is a "<", the connective is forward-reading; i.e., it normally connects some earlier term to the nested phrase that follows the "<" in the source description. Examples of forward-reading connectives in the source description above are " of " and the first " & ". If the next coding symbol after the "?" is a ">", the connective is backward-reading; i.e., it normally connects the nested phrase that ends at the ">" to some earlier term. In the source description above, the second " & " is a backward-reading connective.
As general guidelines for constructing NEPHIS source descriptions, prefer nouns or noun phrases as terms and prepositions as connectives. Adjectival terms are permitted where needed for good index entries. For coordinate or parallel terms, use of paired forward- and backward-reading " & " connectives is recommended; generally, do not bother with backward-reading connectives otherwise. A nested phrase should be normally be meaningful in itself: the positioning of the brackets should reflect the grammatical structure of the description.
Put the locator or other reference at the end of the source description; e.g., "123" in the source description above.
To terminate a session with NEPHIS32, click on the "X" button of the main application window, but first make sure you have stored your set of source descriptions if you want to use them again.
Generally, for the best results, adopt a consistent scheme of capitalization. Using lower case except on the initial letters of terms produces a good index display without too much indexer effort.
To insert a line for a new description, just press the Enter key. To delete a description, select it and press the Delete key.
If the source description is illegally coded, NEPHIS32 will point out the location of the first error. Otherwise, it will display the corresponding index entries in the Rich Text box in the bottom part of the main application window.
If the source description is illegally coded, error(s) will be pointed out at the end of the tree display.
To terminate the step-by-step demonstration, click on the special "Stop" button.
To shift to a source description by number, click on the "Jump to..." button; then type in the number of the source description desired and press the "Enter" key.
To retrieve a set of source descriptions from disk, first click on the "Retrieve" button. Then, use the standard dialog to select the file from which you want to retrieve the source descriptions. Note that the contents of the file will replace all the source descriptions that were previously in computer memory.
NEPHIS32 will point out the nature and location of the first error, if any; if this happens, press the Enter key to continue.
Extracts from sample formatted and unformatted indexes follow.
Computerized Bibliographic Networks
· Databases Accessible in Canada . 3 110-122
Computerized Bibliographic Systems
· Role of Intermediaries . 3 123-147
· Use in Reference Work . 1 15-29
DOBIS
. Canadian Version. Evaluation by National Library of Canada . 2 61-78
Data
· on Demand for Books . Use in Distribution of Books among Branches of Library Systems . 1 65-68
Computerized Bibliographic Networks. Databases Accessible in Canada . 3 110-122
Computerized Bibliographic Systems. Role of Intermediaries . 3 123-147
Computerized Bibliographic Systems. Use in Reference Work . 1 15-29
DOBIS. Canadian Version. Evaluation by National Library of Canada . 2 61-78
Data on Demand for Books. Use in Distribution of Books among Branches of Library Systems . 1 65-68
To view the HTML index that you have created, click on the "View" button to the right of the "HTML index" button. This should bring up a view of the HTML index in the browser associated with .htm extension on your workstation.
Data on Demand for Books
· Use in Distribution of Books among Branches of Library Systems . 1 65-68
Data
· Demand for Books . Use in Distribution of Books among Branches of Library Systems . 1 65-68
Canada
· Government . Information . Access by Citizens of Canada . 5 1-9
Canada
· History . Books in French Language cited in National Union Catalog Pre-1956 Imprints . Bibiliographic Control . Role of WHSTC Project . 5 115-123
Data
· on Demand for Books . Use in Distribution of Books among Branches of Library Systems . 1 65-68
Periodicals . see also #Newspapersa link would be created to the heading "Newspapers".
If active, this option takes precedence over "Entry ends in URL".
Brass==Alloys? of <Copper? & <Zinc? & >>
For satisfactory results, your initial source description should be an ordinary English noun phrase. The only words not beginning with capital letters should be connectives. It is better to add the locator or other reference after the automatic coding rather than before.
For example, given the uncoded source description
Computerized Systems in Public Librariesthe automatic coder will produce the coded source description
Computerized Systems in <Public <Libraries>>
Total input is limited to the amount of text that will fit in a standard Windows memo control.