Appearance
Link items
Linking items lets you connect related things across collections without merging them into a single record.
Links create relationships while preserving each item's identity and history.
What linking does
A link represents a relationship between two items.
Each item continues to live in its own collection, with its own timeline and attributes. The link simply records that the two are related in a specific way.
This avoids duplication and keeps responsibilities clear.
When to link items
Link items when:
- One item refers to another
- Items participate in a shared context
- You want relationships without flattening structure
Common examples:
- A book linked to an author item
- Equipment linked to a project
- An asset linked to a purchase record
- Inventory linked to a location item
Step 1: Choose the source item
Start from the item you want to link from.
This is usually the item whose context you are enriching. For example, a piece of equipment that belongs to a project.
Step 2: Create the link
Add a link to the related item.
The link records:
- Which item is being linked
- The type or purpose of the relationship
- Any optional metadata that describes the connection
Once created, the link appears on both items.
Step 3: Understand how links behave
Links do not copy data.
Changes to one item do not overwrite the other. Each item's state remains derived from its own events.
The link itself has history. If a relationship changes, that change is recorded rather than overwritten.
Why links matter
Links let you model real-world systems.
Most systems are networks, not trees. Items belong to multiple contexts at once. Linking lets you represent those relationships without forcing everything into a single hierarchy.
What you get from linking
Linking items allows you to:
- Keep collections focused
- Avoid duplicated records
- Preserve clean histories
- Build richer models over time
Once you are comfortable linking items, Anchorline starts to feel less like a set of lists and more like a connected system.