About names of objects in a project

Project objects have two types of identifiers:

• Projects, streams, and folders have names. Activities have headlines and IDs.

  Names and IDs are unique among all objects in a PVOB.

  (In a graphical user interface (GUI), headlines provide a way to refer to an activity that is easier to remember and more meaningful to you. Headlines (which apply only to activities) do not need to be unique.)

• Object selectors provide an identifier that is unique among all objects in all PVOBs in your organization. An object selector uses the following syntax:

  
  [ object-type: ] alphanumeric-string [ @/PVOB-tag ]
  

  The alphanumeric string must be unique to the current PVOB; if you do not provide a string, one will be provided for you. For example, the selector that is provided for the pat_1.4_cropcircle stream is stream: pat_1.4_cropcircle_02442@/projects.

  On the UNIX® system and Linux®, the argument @/PVOB-tag is not required for mkactivity and setactivity if you issue those commands from a view attached to the stream in which you make or set the activity.

See the Object Name section in the cleartool reference page for information about object naming rules. When you use DevOps Code ClearCase® and Rational® ClearQuest® graphical user interfaces, you use the name or ID of an object. For example, when the Project Explorer lists the streams and activities for a given project, it displays the stream names and the activity IDs. These identifiers, which may not be unique among all objects in all PVOBs, are usually sufficient for the context in which they are displayed.

When you use the command-line interface (CLI), which gives you greater flexibility, you may use only the alphanumeric string part of the object selector if the context is correct. If you plan to work primarily from the command line, supply meaningful names and IDs when you create and work on objects.