Personnel


Definition

<Personnel> defines the point of contact for more information about the service or the metadata.

  • The contact personnel are defined by the <Role>, which include:
    • Technical Contact The person who is knowledgeable about the technical content of the service (software development, development methods, software support).
    • SERF Author The person who is responsible for the content of the SERF. If the responsibility shifts from the original author to another person, the SERF Author field should be updated to the new responsible person.
    • Service Provider Contact The person who is responsible for the distribution of the service.
  • <First_Name>, <Middle_Name> and <Last_Name> are the first, middle and last name of the person or organization defined in the <Personnel> field. Initials may be used for the <First_Name> and <Middle_Name>.  Organizational names may be substituted for personal names.
  • <Email> is the email address of the personal or organization. Note: Authors may use “@” in formatting email addresses, however the “@” symbol will not be displayed to the public to avoid potential spam attacks.
  • <Phone> is the telephone number of the person or organization. Telephone extensions are allowed. If not in the U.S. or Canada, use the two-digit country code followed by the phone number. Otherwise, use the 10-digit phone number including area code.
  • <FAX> is the FAX number of the person or organization. The same rules for <Phone> apply to FAX numbers.
  • <Contact Address> contain the address information of the person or organization. It consists of:
    • <Address> is the organization name, department, mail stop, street address, etc. of the person organization.
    • <City> is the city or town of the person or organization.
    • <Province or State> is the province (particularly Canadian provinces, region or state (particularly in the United States).
    • <Postal Code> is the postal code of the person or organization.
    • <Country> is the country of the person or organization.
 
Syntax

<Personnel>
     <Role>Personnel Role Keyword</Role>
     <First_Name>Text up to 80 characters</First_Name>
     <Middle_Name>Text up to 80 characters</Middle_Name>
     <Last_Name>Text up to 80 characters</Last_Name>
     <Email>Text up to 80 characters of the form   “janedoe@domain”</Email>
     <Phone>Text up to 80 characters of the form “xxx-xxx-xxxx”. Outside of the US and Canada, the country code should be added (+xx-xxx-xxxx)</Phone>
     <Fax>Text up to 80 characters (see syntax for <Phone>)</Fax>
      <Contact_Address>
        <Address>Text up to 80 characters</Address>
        <City>Text up to 80 characters</City>
        <Province_or_State>Text up to 80 characters</Province_or_State>
        <Postal_Code>Text up to 80 characters</Postal_Code>
        <Country>Text up to 80 characters</Country>
       </Contact_Address>
      </Personnel>

  • Characters may be selected from the UTF-8 character set.
 
Usage
  • The <Personnel> field is highly recommended and may be repeated.
  • The <Role> field is required and must be selected from the Personnel Role keyword list (see definitions above).  The <Role> may be repeated. A person may have more than one role, such as Technical Contact and SERF Author.
  • The <First_Name> and <Middle_Name> of the personnel are optional. If the <Personnel> field is populated, the <Last_Name> is required. Names may be personal names or organizational names.
  • The  <Email>, <Phone> and <Fax> fields are optional and may be repeated.
  • The <Address> field may contain multiple lines and is repeatable.
  • <City>, <Province_Or_State>, <Postal_Code> and <Country> are not repeatable.
  • <Phone> and <Fax> are optional and may be repeated.
  • <Country> is optional and may not be repeated. <Country> should always be included in the address.
  • Note: If personnel retire, particularly investigators, it is desirable to keep their full name, delete their <Phone>, <Email> and <Fax> number, or in the <Address> subfield, state that they are retired or deceased, keeping the name of their affiliation.
 
Examples

Example of personnel with a role of SERF Author
  <Personnel>
    <Role>SERF AUTHOR</Role>
    <First_Name>MICHAEL</First_Name>
    <Last_Name>MORAHAN</Last_Name>
    <Email>Michael.P.Morahan.1@xxx.xxx.gov</Email>
    <Phone>301-555-5555</Phone>
    <Fax>301-222-2222</Fax>
    <Contact_Address>
      <Address>Goddard Earth Sciences Data and Information Services Center</Address>
      <Address>Code 610.2</Address>
      <Address>NASA Goddard Space Flight Center</Address>
      <City>Greenbelt</City>
      <Province_or_State>MD</Province_or_State>
      <Postal_Code>20771</Postal_Code>
      <Country>USA</Country>
    </Contact_Address>
  </Personnel>


Example of organizational personnel with a role of Technical Contact

<Personnel>
    <Role>Technical Contact</Role>
    <Last_Name>WDC/PALEOCLIMATOLOGY, BOULDER</Last_Name>
    <Email>paleo@xxxx.gov</Email>
    <Phone>555-555-5555</Phone>
    <Fax>222-222-2222</Fax>
    <Contact_Address>
      <Address>World Data Center for Paleoclimatology</Address>
      <Address>NOAA/NCDC Code E/GCx3</Address>
      <Address>325 Broadway</Address>
      <City>Boulder</City>
      <Province or State>CO</Province or State>
      <Postal_Code>80303/Postal_Code>
      <Country>USA</Country>
    </Contact_Address>
  </Personnel>

 

This document should be cited as:
Service Entry Resource Format (SERF) Writer's Guide, 2014.
Global Change Master Directory.
National Aeronautics and Space Administration.
[http://gcmd.nasa.gov/add/serfguide/].

NASA Logo - nasa.gov
Link to Web Site