Configuring Relationship Types

From CollectiveAccess Documentation
Jump to: navigation, search

This page explains how to create or edit Relationship Types using the online user interface. If you have not installed CollectiveAccess yet, you may want to configure your Relationships using Installation Profiles.

Viewing Relationship Types

To access the Relationship Types Editor, Navigate to Manage > Administration in the Global Navigation menu. Select "Relationship Types" from the left sidebar to open the Relationship Types viewer.

The left-most column displays all of the possible relationships between your records. These are not editable and simply represent different combinations of the Primary Types, for example, the relationship between two objects, or between a place and an entity.

Click one of these relationship headings to see the different Relationship Types that have been defined for your system. For example, common Relationship Types between two entities include "spouse of," "child of," and "related to." These qualifiers define the nature of the relationships between your records.

Editing Relationship Types

To edit a Relationship Types, navigate to your chosen relationship (see above) and select the Relationship Type you wish to edit. Click the gray arrow icon to open the Relationship Type Editor. The Editor contains the following information that you may now edit:

  • Typename (forward sense) - This is the display name for your Relationship Type. These are often named so that they complete a sentence. For example, in an Entity to Place relationship, you may have a Relationship Type named "was born at," as in "Caroline Jones was born at St. John's Hospital."
  • Typename (reverse sense) - This allows you to name the inverse relationship of the same two records. Using the previous example, to say that "St. John's Hospital was born at Caroline Jones" wouldn't work, even though we are referring to the same relationship. Therefore you could specify that the reverse Typename is something like "was the birthplace of."
  • Locale - If you have more than one language configured for your system, select the language here. Click the "add title" button to create Typenames in an additional language.
  • Relationship type code - This is a unique name that is used to refer to your Relationship Type throughout the system
  • Is Default? - This specifies whether this is the default Relationship to appear in the Relationship Type Bundle
  • Sort Order - Determines the order of the Relationship Types as they appear in a drop-down menu. 1 will be first, 2 will be second and so on.
  • Type Restrictions for "left" side of relationship - You may not want your Relationship Types to extend to ALL the records of a Primary Type. This option allows you to restrict your relationship to a chosen subtype. For the "Birthplace" example, you may want to restrict your Relationship Type to "Individuals," as Organizations often don't have places of birth. This setting automatically generates a list of your configured subtypes for the "left" side of your relationship.
  • Type Restrictions for "right" side of relationship - same as above, but automatically generates a list of your configured subtypes for the "right" side of your relationship.
  • Hierarchy Bundle

Creating Relationship Types

To create a new Relationship Type, navigate to Manage > Administration in the Global Navigation menu. Select "Relationship Types" from the left sidebar to open the Relationship Types viewer.

Select the Relationship to which you would like to add a new type. In the Hierarchy viewer, click the "add" button with the message "Add under [relationship] new item," where [relationship] is the relationship for which you would like to add a new Relationship Type. This opens the Relationship Type Editor. You can now enter the relevant information for your new Relationship Type (see above).

sphinx

Namespaces

Variants
Actions
Navigation
Tools
User
Personal tools