Notion Database Schema Upgrade Template

For: stcmastery-vscode-what-is-toolset-260121 Chart Reference: chart_1768989886902 Status: Ready for implementation

Current Schema

Proposed Additions

New Properties to Add

1. ToolSet Name (Text)

• Description: Identifier for the ToolSet group this research applies to
• Format: Hyphenated lowercase (e.g., stc-toolset, ncp-tools, mission-260120-tools)
• Values: Free text or linked to ToolSet registry
• Purpose: Enable grouping research by ToolSet context

2. JSON Snippet (Code Block)

• Description: Example JSONC configuration for this research item
• Format: JSONC code
• Purpose: Store working examples directly in Notion for copy/paste into .vscode/toolsets.jsonc
• Example Template: ```json { "toolset-name": { "tools": ["tool1", "tool2"], "description": "Description from research", "icon": "icon-name" } } ```

3. MCP Server (Select - Multi)

• Description: Which MCP servers this ToolSet involves
• Values:
  • Notion
  • Slack
  • GitHub
  • VSCode Built-in
  • Custom/Other
• Purpose: Cross-filter by MCP integration type

4. Registry Fit (Checkbox)

• Description: Does this research validate a production ToolSet pattern?
• Values: Yes/No
• Purpose: Filter items ready for live registry vs exploratory research

5. GitHub Issue Links (Relation)

• Description: Related issues in vscode, vscode-copilot-release, or project repos
• Format: Link relation to GitHub issues (if integration exists) or URL references
• Values:
  • vscode#260438
  • vscode-copilot-release#12647
  • Other project issues
• Purpose: Cross-team coordination, trace discussion history

6. Related Action Steps (Relation)

• Description: Links to structural tension chart action steps
• Format: Text or linked relation
• Values: Action step titles from chart_1768989886902
• Purpose: Tie research to implementation milestones

Updated Schema Table

View Recommendations

1. Registry Readiness View

Filter: Registry Fit = Yes Sort: Priority (High → Low), Category Purpose: Identify production-ready ToolSet patterns

Columns:

• ToolSet Name
• Category
• MCP Server
• JSON Snippet (preview)
• Application Potential
• Status

2. By MCP Server View

Group By: MCP Server Sort: Priority Purpose: See all research grouped by platform (Notion, Slack, etc.)

Columns:

• Research Item
• Priority
• Status
• Application Potential
• ToolSet Name

3. Action Steps Tracking View

Filter: Related Action Steps is not empty Sort: Due date of action step Purpose: Monitor research supporting specific implementation milestones

Columns:

• Research Item
• Related Action Steps
• Status
• GitHub Issue Links
• Registry Fit

4. GitHub Integration View

Filter: GitHub Issue Links is not empty Sort: GitHub issue number Purpose: Track cross-team discussion and coordination

Columns:

• Research Item
• GitHub Issue Links
• Category
• Related Files
• Status

Data Migration Strategy

Phase 1: Add Properties (No Data Loss)

1. Create 6 new properties in Notion
2. Leave blank for existing entries
3. No existing data affected

Phase 2: Backfill Existing Entries

For each existing research item:

1. Identify applicable ToolSet Name from category
2. Add MCP Servers involved
3. Convert "Related Files" URLs → GitHub links
4. Set Registry Fit based on "Application Potential"
5. Link to action steps if applicable

Phase 3: New JSON Snippets

For items with Registry Fit = Yes:

1. Create JSONC template in JSON Snippet field
2. Copy working versions to production toolsets.jsonc
3. Link GitHub issue for tracking

Implementation Checklist

• Create ToolSet Name (Text) property
• Create JSON Snippet (Code) property
• Create MCP Server (Multi-Select) property with 5 default options
• Create Registry Fit (Checkbox) property
• Create GitHub Issue Links (URL) property
• Create Related Action Steps (Relation) property
• Set up Registry Readiness view
• Set up By MCP Server view
• Set up Action Steps Tracking view
• Set up GitHub Integration view
• Backfill existing entries (5-10 initial items)
• Test JSONC snippets in .vscode/toolsets.jsonc
• Document in README.md or wiki

Benefits

Organization:

• Group research by ToolSet context
• Filter by MCP server type
• Track implementation readiness

Operationalization:

• Copy JSON directly from Notion to VSCode
• Link to GitHub for team discussions
• Connect to structural tension chart milestones

Governance:

• Registry Fit filters production vs exploratory
• GitHub links enable cross-team coordination
• Action Steps tie research to delivery timeline

Example Entry After Upgrade

Chart Reference: chart_1768989886902 (Action Step 5: due 2026-02-04) Last Updated: 2026-01-21