Networked Knowledge Organization Systems (NKOS) Registry
Help Document

Data Elements (* indicates that this element is required)

Product Name/Title Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the "official name" of the thesaurus, classification system, or other Knowledge Organization System that you are describing. Titles are best if they include words in the title that will distinguish it from other products and will indicate the nature of the product. Titles will be alphabetized as they are entered; therefore, do not start the title with an article such as "The" or "A". Capitalize all non-prepositional words. Do not put a period at the end of the title.

Example of title: Thesaurus of Feature Types

Variant Product Name/Title Type of field: text

Number of occurrences: Repeatable (or multiple titles in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Enter any other names/titles by which the product is known.

Example entry: ADL TFT

Type of Product Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter one of the following:

Example entry: Hierarchical thesaurus Author/Editor Type of field: text

Number of occurrences: Repeatable (or multiple titles in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Enter the author/editor names in direct, not inverted format.

Example entry: Linda Hill

Auxiliary Lists Type of field: text

Number of occurrences: Repeatable (or multiple titles in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Enter the names of any lists of terms or auxillary tables that accompany the basic vocabulary product.

Example entry: List of provisional terms under consideration.

Product Description Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry Guidelines: Enter a description of the product. There is no need to repeat the information that will appear in the other fields of the entry. This field should be used to provide additional description.

Example entry: The Thesaurus of Feature Types is designed to be used with a gazetteer to categorize the types of place/feature names for description and retrieval. It is designed according to the ANSI/NISO Z39.19 standard for thesaurus contsruction.

Current Version/Edition Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the edition/version number for the current product. If the product is in development and not yet published, enter an explanation of the status - e.g., "In the planning stage as of June 1998."

Example entry: Draft

Date of Current Version Type of field: date (dd-mm-yyyy)

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the publication date in the form of dd-mm-yyyy

Example entry: 16-11-1998

Product Update Frequency Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter a statement of update frequency, such as monthly, twice a year, annually, or every 3 to 5 years. Updates may be done continuously or irregularly or the product may not be currently maintained. Avoid the terms "biannually" and "biennially". There is wide-spread confusion about what these terms mean. It is clearer to say "twice a year" and "every other year".

Example entry: Irregular updates as the Thesaurus is being built.

Available Format(s) and Size Type of field: text

Number of occurrences: Repeatable (or multiple formats in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: For each format in which the product is available, i.e. print or electronic form, give the size if known.

Example entry: HTML, …bytes; Tagged version for loading into databases.

Online Availability Type of field: URL

Number of occurrences: Repeatable (or multiple products in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: If the thesaurus, classification system, etc. is accessible online, give the URL address or other brief instructions on how to get to it.

Example entry: http://www.alexandria.ucsb.edu/~lhill/html/index.html

Notes Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Enter here any explanations you would like to make about the formats available, online availability, versions, and other such information.

Example entry: There is currently no formal way of announcing when a new version is available and what changes have been made.

URL for Examples Type of field: URL

Number of occurrences: Repeatable (or multiple titles in one entry separated by semi-colons)

Required/Optional: Optional

Entry Guidelines: It is recommended that you put a subset of the Knowledge Organization product in a file so that potential customers can see examples of actual contents to give them a better idea of the nature of the product, if the whole product is not online. This could be images of printed pages or an html text file.

Example entry:

Major Subject Coverage Type of field: text

Number of occurrences: Repeatable (or multiple subject headings in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: The major topic areas covered by your vocabulary or classification product should be listed here. Select terms from the U.S. Library of Congress Subject Headings. Capitalize the first word. Do not end with a period.

Example entry: Geography

Minor Subject Coverage Type of field: text

Number of occurrences: Repeatable (or multiple subject headings in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: You have listed above the major topic areas covered by your vocabulary or classification product. List here any other topic areas that are also covered to a significant degree but that you do not consider to be primary coverage topics. Select terms from the U.S. Library of Congress Subject Headings. Capitalize the first word. Do not end with a period.

Example entry:

Used by (user community and application) Type of field: text

Number of occurrences: Repeatable (or multiple products in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: List the actual publications or databases for which the controlled vocabulary or classification system was designed or the general types of publications that use the vocabulary or classification tool.

Example entry: Alexandria Digital Library Gazetteer

Language(s) Type of field: text

Number of occurrences: Repeatable (or multiple languages in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: Enter the language(s) used by the vocabulary or classification tool. Capitalize the first word of the language. Do not end with a period.

Example entry: English

Type of Terms (e.g. concepts, geographic names, corporate names, etc.) Type of field: text (controlled vocabulary)

Number of occurrences: Repeatable (or multiple languages in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: Enter the types of terms used by the vocabulary or represented by the classification tool. Capitalize the first word of the type. Do not end with a period.

Example entry: Concepts

Description of Overall Structure Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Provide an overview of the organizational structure of the Knowledge Organization product and any particular design particulars that potential users might need to know. For Display Formats, use the Arrangement of Displays element.

Example entry: The Thesaurus of Feature Types has six top terms for the hierarchy. Terms can have more than one broad term; that is, exist in more than one hierarchy. Plural forms of the terms are used. Parenthetical qualifiers are used to disambiguate term meanings.

Source of New Terminology Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Describe how new terms or classification nodes are added to the Knowledge Organization System.

Example entry: Terms are added primarily in the process of converting an existing gazetteer to the ADL Gazetteer Content Standard. As new category terminology is found, an attempt is made to add this terminology to the Thesaurus of Feature Types either as preferred terms or as non-referred terms with a reference to an existing term. At the present time, the editor is making these decisions. When there are other users of the Thesaurus, a terminology advisory committee will be established to review decisions for adding terms.

Number of Preferred Terms or Nodes Type of field: number

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the number of preferred (valid) terms, the number of individual classification nodes, or the total number of "entry terms" if the KOS treats all terms the same. If not easily available, this number can be estimated and entered as a range.

Example entry: 207

Number of Non-preferred Terms Type of field: number

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Enter the number of non-preferred (invalid) terms for thesauri. If not easily available, this number can be estimated and entered as a range. Other types of KOS may not have the equivalent of non-preferred terms.

Example entry: 716

Types of Relationships Type of field: text (controlled vocabulary)

Number of occurrences: Repeatable (or multiple relationships in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: Enter the types of relationship types between terms. Include both the label and the full name for the relationship type for thesauri-type systems. For other types of KOS, indicate the types of hierarchical and synonymous and related relationships even if they do not have specific labels.

Example entry: Broad Term (BT) – Narrow Terms (NT); Use (USE) – Used For (UF); Related Term (RT); Scope Note (SN)
 

Arrangement of Displays (e.g., alphabetical, hierarchical, classified, graphical) Type of field: text

Number of occurrences: Repeatable (or multiple relationships in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Described the presentation formats for the products, for example alphabetical, hierarchical, tagged format, classification tree, rotated (permutated), facetted, graphical.

Example entry: "Top Term" listing showing the hierarchical arrangement of preferred terms; Alphabetical listing of all terms with their relationships; HTML browseable file of all terms with hypertext links; and "Tagged Format" for loading into another file or software.

Depth of Hierarchy (maximum number of levels) Purchase Price by Format Type of field: text

Number of occurrences: Repeatable (or multiple relationships in one entry separated by semi-colons)

Required/Optional: Required

Entry guidelines: Provide purchase price information by product format or a statement that the product is freely available. If the cost is dependent on use or who the user is, include this information.

Example entry: Freely available. Attribution to ADL requested.
 

Subscription Price by Format Type of field: text

Number of occurrences: Repeatable (or multiple relationships in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Provide subscription information, as appropriate, by product format.

Example entry:
 

Licensing Availability Type of field: text

Number of occurrences: Repeatable (or multiple relationships in one entry separated by semi-colons)

Required/Optional: Optional

Entry guidelines: Provide licensing information, as appropriate, by product format. Give the actual licensing fees or an indication of the approximate fees or general avaiability for each product format or media that is available for licensing.

Example entry:

Restrictions Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Describe any restrictions on the use of the product(s) or a general statement about how the arrangements for use can be made. Where there are no restrictions, confirm that with a statement to that effect.

Example entry: Copyrighted by the University of California, Santa Barbara

Vendor Name Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the name of the vendor who should be contacted about access to and use of the product.

Example entry: Alexandria Digital Library, University of California, Santa Barbara

Vendor Street/Post Office Box Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the address lines needed for a full address for mailing purposes between the name and the city. If multiple lines of address are needed, separte with semi-colons (;).

Example entry: Map and Imagery Lab; Davidson Library; University of California, Santa Barbara

Vendor City Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the city for the mailing address.

Example entry: Santa Barbara

Vendor State/Province Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the state or province for the mailing address.

Example entry: California

Vendor Country Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the country name or abbreviation for the mailing address.

Example entry: United States

Vendor Postal Code/ZIP Code Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the postal code or ZIP code for the mailing address.

Example entry: 93106

Vendor Voice Phone Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the main telephone number for the vendor.

Example entry: 805-893-8587

Vendor TDD/TTY Phone Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If there is a special phone number for the hearing impaired, enter the number here.

Example entry:

Vendor Fax Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Enter the telephone number for fax connections.

Example entry: 805-893-3045

Vendor Email Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Enter one email address for contacting the vendor.

Example entry: adl3help@alexandria.ucsb.edu

Vendor Logo URL Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If there is online access toa vendor logo, enter the network address here

Example entry: http://www.alexandria.ucsb.edu/...

Vendor Web Site URL Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If there is a vendor homepage, enter the network address here.

Example entry: http://www.alexandria.ucsb.edu

Vendor Hours of Service and Timezone Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Enter the beginning and ending times of office operation, including the time zone and days of the week.

Example entry: Monday-Friday, 9-4:30, U.S. Pacific Time

Vendor Service Description Type of field: text

Number of occurrences: 1

Required/Optional: Required

Entry guidelines: Describe the overall services of the producer or vendor so that potential users of the product(s) will have an understanding of the business environment of the organization.

Example entry: The Alexandria Digital Library is a research and development project in a university setting. The ADL is a georeferenced digital library. The Feature Type Thesaurus has been developed to use with the ADL Gazetteers.

Contact Name Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If a potential user needs to know the name or position title of a particular person to contact about the product, enter that information here. If the vendore information above is sufficient, there is no need to enter additional information here.

Example entry: Linda Hill

Contact Voice Phone Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If the contact has a different phone number from the vendor phone, enter the number here.

Example entry: 805-893-8587

Contact Fax Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If the contact has a different fax number from the vendor fax number, enter the number here.

Example entry:

Contact Email Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If the contact has a different email address from the one for the vendor above, enter it here.

Example entry:

Contact Web Site URL Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: If the contact has a different homepage connected to the product(s), enter the network address here.

Example entry:

More Contact Information Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Describe any additional information that potential users of the product should know about how to contact you.

Example entry: Email is a better contact method than the phone.

Comments to Registry Editor Type of field: text

Number of occurrences: 1

Required/Optional: Optional

Entry guidelines: Use this space to send comment about the form or the product description to the editor of the registry. These comments will not be part of the product registration but is a means to explain any unusual circumstances to the registry editor.

Example entry: