Provide an Example Mapping from Your Schema to Ours

Registration Information

Host name of your CCSO server (e.g. ds.uiuc.edu):

Port number of your CCSO server (e.g. 105):



CCSO Schema Mapping Registration Using a Local Entry

Did you know that the public CCSO servers use more than 900 different attribute names? Nomenclator can integrate the commonly used attributes into a global schema of people information, but we need your help. We need to map the schema at your CCSO server to the Nomenclator schema. The information collected by this form and the next form will help us to create an approximate mapping for your site. We will then verify the mapping with the CCSO administrator who you registered earlier.


A Note on Data Types

Most CCSO servers have one set of attributes that describe people. Some servers have different or conflicting attributes for different types of people. For example, address might be the organization address for a person of type="faculty" but the home address for a person of type="student."

Check here if your database has different or conflicting attributes for different types of people.

If you have this kind of database, please choose one type of person and fill out this form for that type. You can optionally repeat this form later for different types of people.


If you have different types of information in your database, please enter the attribute name and value that identifies the type of information in this example:
Example: type="person"
Example: type="faculty"
Example: type="faculty" or type="student"

Please select a typical entry of this type in your database and give us a query that will allow us to retrieve it from your database:
Example: alias="g-emlin"

Please show us what that entry would look like in our database by filling in the fields in this section. You may have to break up fields in your selected entry to fill in the fields in our schema. That's fine. You may need to supply information that everyone knows, e.g. your country, but that is not listed explicitly in the your database entry. You can also leave fields blank if the information requested is not supported by your database.

Name_First: the given name of the person.
Example: Grace

Name_Middle: the middle or second given name of the person
Example: Rita

Name_Last: the surname or family name of the person.
Example: Emlin

Name_Suffix: a suffix for the full name of the person.
Example: Senior

Email: the external Internet electronic mail address of the person.
Example: gre@research.att.com

MHSmail: the external MHS (X.400) electronic mail address of the person.
Example: C=us;ADMD=123mail;PRMD=us;O=some;S=person;g=e.x.

WWW_Homepage: the URL of the person's World-Wide Web homepage.
Example: http://www.cs.att.com/csrc/nomen/nomen_join_ccso_d.html

Organization: the organization to which the person belongs.
Example: AT&T

Division: the organization division to which the person belongs.
Example: Bell Laboratories

Department: the organization department to which the person belongs.
Example: Computing Science Research Center

Title: the title or role of the person in the organization.
Example: Member of Technical Staff

Building: the building and room in the person's organization address.
Example: MH 2C-501

Street: the street in the person's organization address.
Example: 600 Mountain Avenue

City: the city in the person's organization address.
Example: Murray Hill

State_or_Province: State or province name in the person's organization address.
Example: New Jersey

Postal_Code: the postal code or zipcode in the person's organization address.
Example: 07974-0636

Country: the country in the person's organization address.
Example: USA

Phone: the full organization telephone number of the person including country code, city/area code, number and extension.
Example: +1 908 582 4148

Home_Apartment: the apartment number in the person's home address.
Example: U

Home_Street: the street in the person's home address.
Example: 13300 East Capitol Street

Home_City: the city in the person's home address.
Example: Toronto

Home_State_or_Province: State or province name in the person's home address
Example: Ontario

Home_Postal_Code: the postal code or zipcode in the person's home address.
Example: 0A724

Home_Country: the country in the person's home address.
Example: CA

Home_Phone: the full home telephone number of the person including country code, city/area code, number and extension.
Example: +2 202 555 1212

Last_Modified: the date the record was last modified.
Example: Wed Apr 12 23:42:40 EDT 1995


Please supply queries for three additional records in your database that we can use to test our mappings: Example: alias="j-ordille"


Are the fields in your database in a fixed format, perhaps because they are automatically generated from a personnel database, or does the format vary?

The fields in our database have a fixed format.

Some fields in our database have a fixed format. The fields that have a fixed format are listed below. Field names are separated by commas. Commas in field names are preceded by a backslash, e.g. "\,".
Example: name, phone, email, city\,state

The fields in our database vary in format.


Are there any fields in our database that you always or typically abbreviate in your database? For example, you may always abbreviate Country and sometimes abbreviate State_or_Province.

Please supply the names of the fields that are always abbreviated below. Please separate field names by commas.
Example: Country, Home_Country

Please supply the names of the fields that are sometimes abbreviated below. Please separate field names by commas.
Example: State_or_Province, Home_State_or_Province


Please supply the names of any fields in your database that do not correspond to fields in our database BUT that you would like included in Nomenclator. Please separate field names by commas. Commas in field names should be preceded by a backslash, e.g. "\,"
Example: secretary_phone, picture






 Return to the Nomenclator Home Page.


Copyright © 1996, 1997 Lucent Technologies. All rights reserved.

Last modified: January 27, 1997.
joann@bell-labs.com