In the search results table, click the Details link for an object to open the Details area immediately below the Registry Objects area.
This section has a row of buttons and a row of tabs:
The buttons are Apply, Save, Cancel, Approve, Deprecate, Undeprecate, and Delete. The buttons represent actions that you can perform on the object.
The tabs represent the object’s attributes. The tabs vary depending on the object type.Table 1–4 describes the tabs and the objects they apply to.
Tab Name |
Applies To |
---|---|
Object_Type Detail |
All objects (Object_Type is the object type name) |
Slots |
All objects |
Classifications |
All objects |
External Identifiers |
All objects |
Associations |
All objects |
External Links |
All objects |
Audit Trail |
All objects |
Postal Addresses |
Organization, User |
Telephone Numbers |
Organization, User |
Email Addresses |
Organization, User |
Users |
Organization |
Organizations |
Organization |
Service Bindings |
Service |
Specification Links |
ServiceBinding |
Concepts |
ClassificationScheme, ClassificationNode |
Registry Objects |
RegistryPackage |
Affected Objects |
AuditableEvent |
Click a tab to find out if the object has any values for the attribute. If it does, click the Details link for the attribute value to open a web browser window with the details for the attribute value.
The Audit Trail tab does not produce a table with a Details link. Instead, this tab produces a table that contains the following information:
The event type
The date and time of the event
The name of the User that caused the event
For most objects, the Details area fields are as follows:
Unique Identifier. For every object, the Unique Identifier is an active link. Click this link to view the XML for the object in a web browser window. All registry objects are stored in XML format.
Logical Unique Identifier. The Logical Unique Identifier is usually the same as the Unique Identifier. If you turn versioning on, the Logical Unique Identifier remains the same for all versions of the object, while the Unique Identifier for the new version receives a suffix that indicates the version number.
Name
Description
Status (usually Submitted, meaning that the object has been published to the Registry)
Version
VersionComment
For many objects, the fields are largely self-explanatory (the postal addresses for an Organization, for example). For some objects, the fields require some explanation. The following sections describe these fields.
The Details area for an Association object contains the following additional fields:
Source Object ID and Target Object ID. For the source and target objects of the association, the panel shows both the unique identifier and the logical identifier. The Confirmed By Source Owner checkbox indicates whether or not the association was confirmed or approved by the source object owner. The Confirmed By Target Owner checkbox indicates whether or not the association was confirmed or approved by the target object owner. These checkboxes are always selected for intramural associations.
Association Type. The menu displays the selected type of the Association.
Is Extramural. This checkbox is selected if at least one of the two associated objects is owned by a User other than the User who created the Association. Otherwise, the Association is defined as intramural.
The Details area for a ClassificationScheme object contains the following additional fields:
External Classification Scheme checkbox. This checkbox is selected if the classification scheme is defined outside the Registry (that is, if it has no concepts). An internal classification scheme is a classification scheme whose concept hierarchy is defined within the Registry.
The Value Type menu, which contains one of the following selections:
Unique: This value indicates that each node of the taxonomy has a unique code assigned to it. This value is the default when you create a classification scheme in Service Registry.
EmbeddedPath: This value indicates that the unique code assigned to each node of the taxonomy also encodes its path.
NonUnique: In some cases nodes are not unique, and it is necessary to use the full path (from the ClassificationScheme to the node of interest) to identify the node. For example, in a geography taxonomy, Moscow could be under both Russia and the USA, where five states have cities that are named Moscow.
The Details area for an ExtrinsicObject object contains the following additional fields:
Content Version and Content Version Comment. The Details area shows the version and optional comment for the repository item associated with the extrinsic object.
MimeType. This field contains the MIME type of the extrinsic object.
Is Opaque checkbox. This checkbox is selected if the repository item content is not readable by the Registry (for example, if it is encrypted).
Object Type. This field contains the subconcept within the ObjectType/ExtrinsicObject tree.
View Repository Item Content link. Click this link to view the repository item in a web browser window.
The Details area for an ExternalLink object contains a Display Content link under the External URI field. Click this link to view the contents of the URI in a browser window.