Overview

I't great the have an ability to store your data in a consistent way, like in a database. On the other hand, a user will be glad to browse the full information within a particular entry, without switching between the related ones.

The Catalog app provides the attributes for linking (one entry – Directory; several entries – Multi Directory Items) and the read-only attribute Linked Catalog Entries that displays the linked entries information. They can be set up separately in any combinations to meet your needs.

There is only one direction of linking. Consider that there is always an object and its parameter(s), even if it is not always obvious. For example, in parent-child relationship, a parent(s) is a "parameter" of a child, not vice versa.

"One to many" linking

Link via: Directory attribute


Case 1. We have the Assets directory and going to define an owner of each asset by selecting from the Employees directory. We would also like to browse the list of assets owned by a particular employee.

  • Add the Directory attribute to the Assets directory and set it up to select from the Employees directory. Name it Owner.
  • Add the Linked Catalog entries to the Employees directory to be able to browse the list of assets owned by an employee. Name it Assets.


Case 2. We'd like to create a hierarchical structure within the Employees directory, as each employee has a manager and may have several subordinates. It also will be convenient to browse the list of subordinates and their statuses within the manager's entry.

  • Add the Directory attribute to the Employees directory and set it up to select from the Employees directory. Name it Manager.
  • Add the Linked Catalog entries to the Employees directory to be able to browse the list of assets owned by an employee. Name it Subordinates.


"Many to many" linking

Link via: Multi Directory Items attribute


Case 1. We have a kindergarten database and would like to keep information about children and their parents. We have two relevant directories – Children and Parents.

  • Add the Multi Directory Items attribute to the Children directory and set it up to select from the Parents directory. Name it Parents.
  • Add the Linked Catalog entries to the Parents directory to be able to browse the list of children. Name it Children.


Case 2. Each child has not only parents but also godparents (still from the Parents list). We need to differentiate these links.

  • Add the Multi Directory Items attribute to the Children directory and set it up to select from the Parents directory. Name it Parents.
  • Add the Multi Directory Items attribute to the Children directory and set it up to select from the Parents directory. Name it Godparents.
  • Add the Linked Catalog entries to the Parents directory to be able to browse the list of children. Name it Children. Specify the Parents attribute as a linker.
  • Add the Linked Catalog entries to the Parents directory to be able to browse the list of children. Name it Godchild. Specify the Godfather attribute as a linker.