Table 6.223 — DRM_Responsible_Party

Property

Description

Class

  • <DRM Responsible Party>

Superclass

Subclass

  • None.

Definition

An instance of this DRM class provides identification of, and means of communication with, person(s) and organization(s) associated with the data set being described.

In the documentation for this class, the phrase the term the data set refers to the collection of environmental data being described by the <DRM Responsible Party> instance. This, in turn, refers to the object tree rooted at the aggregate of the <DRM Responsible Party> instance.

If a <DRM Responsible Party> instance is shared by multiple aggregates, the data set refers to the collection of object trees rooted at its various aggregates.

If supplied, the individual_name field specifies the name of the responsible person, in the form surname, given name, title separated by delimiters.

The organization_name field specifies the name of the supporting organization.

If supplied, the position_name field specifies the role or position of the responsible person.

The contact_information field specifies the address of the responsible party.

The role field specifies the function performed by the responsible party.

Clarifications

None.

Class diagram

Figure 6.268 — DRM_Responsible_Party

Inherited field elements

Field name

Range

Field data type

None

   

Field elements

Field name

Range

Field data type

individual_name

 

String

organization_name

 

String

position_name

 

String

contact_information

 

Contact_Information

role

 

CI_RoleCode

Associated to (one-way) (inherited)

  • None.

Associated to (one-way)

  • None.

Associated by (one-way) (inherited)

  • None.

Associated by (one-way)

  • None.

Associated with (two-way) (inherited)

  • None.

Associated with (two-way)

  • None.

Composed of (two-way) (inherited)

  • None.

Composed of (two-way)

  • None.

Composed of (two-way metadata) (inherited)

  • None.

Composed of (two-way metadata)

  • None.

Component of (two-way) (inherited)

  • None.

Component of (two-way)

Constraints

Example(s)

  • Consider a data provider creating a instance for a MEL thesaurus consulted in creating information. The for the instance in this example contains the following data.

    individual_name     = { DEFAULT, 0, "" }
    organization_name   =
        { DEFAULT,
           34,
           "Master Environmental Library (MEL)" }
    position name       = { DEFAULT, 0, "" }
    contact_information =
        { voice_phone           =  { DEFAULT, 0, "" },
           fax_phone            =  { DEFAULT, 0, "" },
           tdd_tty_phone        =  { DEFAULT, 0, "" },
           address              =  { DEFAULT, 0, "" },
           online_resource      =  { DEFAULT, 0, "" },
           hours_of_service     =  { DEFAULT, 0, "" },
           contact_instructions =  { DEFAULT, 0, "" }}
    role                = POINT_OF_CONTACT