Open in TheBrain

Archive: Location: Template

Location Franchise Table Template

Purpose

Create a standardized table showing baseball team franchises that played in a specific location.

The table should:

Required Source Data

Use a reliable location source, preferably a StatsCrew “sports places” page.

The source should provide:

If the source data has been pasted into the location thought’s notes, read that pasted content directly. Do not rely only on the source page title or a manually summarized list.

Source-Table and Final-Table Column Order

The pasted source table may use this order:

\| League | Team | Years |

This source order must not be treated as the required final order. When executing this workflow, preserve the source values but reorganize the completed location table into this standardized order:

\| Team | League | Years |
\|---|---|---:|
\| [Franchise Thought] | [League] | [Years] |

The Team column comes first because the table is primarily a list of franchise thoughts associated with the location. The League column is supporting classification information. Do not confuse the source-table order with the required final order.

Standard Final Table Format

Teams that played in **[Location]**

\| Team | League | Years |
\|---|---|---:|
\| [Franchise Thought] | [League] | [Years] |

Source: [StatsCrew — [Location]]([StatsCrew Location URL])

Formatting Rules

Thought-Matching and Franchise/Season Hierarchy Workflow

For every team franchise in the source list:

  1. Read the pasted source content directly and extract each League, Team, Years, and StatsCrew team URL value.
  2. Ignore the source column order when constructing the final table; map values by their headings or list structure.
  3. Search the Baseball brain for the exact franchise name.
  4. Prefer an existing franchise-level thought whose name does not include a season or year.
  5. Never use a thought named in the form Team Name - YEAR as the franchise link when a franchise-level thought exists.
  6. If the franchise-level thought does not exist, create a new thought using the team franchise name exactly as listed by the source, without appending a year.
  7. Link the franchise-level thought as a child of the location thought.
  8. Preserve any existing relationships the franchise thought already has.
  9. Do not delete, rename, or replace existing year-specific team thoughts.
  10. Link each applicable year-specific thought beneath its corresponding franchise-level thought as a child. Year-specific thoughts should remain named with their appended year, such as Team Name - 1904.
  11. If an existing franchise thought is already a child of the location thought, do not create a duplicate link.
  12. If an existing year-specific thought is already a child of the franchise thought, do not create a duplicate link.
  13. Generate a valid internal thought link for the franchise-level thought.
  14. Place the internal franchise link in the first column of the final table, not in the League column.

Important Distinction

The location table represents franchises, not individual seasons. For example:

Location thought
└── Corsicana Oil City Oilers
    └── Corsicana Oil City Oilers - 1904

The table links to Corsicana Oil City Oilers; it must not link directly to Corsicana Oil City Oilers - 1904.

Franchise Thought Naming

Use the franchise name as listed by the source, without adding unnecessary years.

Examples:

Pawtucket Red Sox
Pawtucket Indians
Pawtucket Rovers
Pawtucket Tigers

Use a year in the thought name only for a season-specific child thought when the source or existing brain structure clearly identifies that season.

StatsCrew URL Workflow

For each franchise:

  1. Obtain the franchise’s resource URL from the pasted source data.
  2. Attach that URL to the corresponding franchise-level thought.
  3. Use a descriptive attachment title, such as StatsCrew — [Team Name].
  4. Do not place the StatsCrew team URL in the location table.
  5. Keep the StatsCrew location/source URL in the location thought.
  6. If a StatsCrew team URL is already attached to another thought, do not duplicate the attachment. Record that the URL is intentionally shared or already represented elsewhere.

Icon Workflow

Icons provide a visual status cue, but icon absence must not be used to infer that a source URL is missing.

Internal Thought Links

Use TheBrain’s generated internal thought URL format:

brain://api.thebrain.com/[brain-id]/[thought-id]/[thought-name]

Mandatory Internal-Link Safeguards

Example:

[Pawtucket Red Sox](https://app.thebrain.com/brain/7f601502-fd8b-40ea-ba42-6843c4d95fbd/00000000-0000-0000-0000-000000000000)

The generated internal link belongs in the Team column of the final table.

Link Validation

Before finalizing the table:

If a franchise thought ID cannot be resolved or a valid internal link cannot be generated:

Location Source Link

Retain the source link at the bottom of the location note:

Source: [StatsCrew — [Location]]([StatsCrew Location URL])

The source link may remain external because it identifies the location source, not a team thought.

Preservation Rules

When updating a location thought:

Completion Checklist

Recommended Name

Location Franchise Table Template

Alternative names:

This is a reusable template and operating procedure. A fully automated implementation would be a script.

Versioning Record

Recovery Notice

The previous workflow instructions were unintentionally overwritten during the v2.1 update. The archive thought [[thought:18823dda-2af0-4e01-aaea-2401186ca50f|Location: Template — Archive — v2.0 — 2026-09-14]] records the prior version identity, but the original text could not be recovered from the available tool state. No further note edits will be made without explicit confirmation.