Using Personal Notes¶

Capture insights, reflections, and context alongside your timeline with ChronoScope's persistent notes feature.

Overview¶

What Are Notes For?¶

The User Notes feature provides a dedicated space for stream-of-consciousness writing alongside your timeline. Unlike timeline events (which are extracted from documents), notes are your personal observations, insights, and reflections.

Common Use Cases:

• 📝 Career reflections - Document patterns you notice in your career journey
• 💡 Meeting insights - Capture thoughts during timeline review sessions
• 🎯 Goal setting - Plan future directions based on past patterns
• 🔍 Pattern recognition - Note recurring themes across life events
• 📊 Analysis notes - Record observations about your timeline data

Creating & Editing Notes¶

Where to Find the Notes Section¶

The 📝 User Notes section appears below the main tabs on the ChronoScope home page:

┌─────────────────────────────────────┐
│  Timeline Tab | Duplicate Tab | ... │
└─────────────────────────────────────┘
            ↓
┌─────────────────────────────────────┐
│      📝 User Notes                  │
│  ┌───────────────────────────────┐  │
│  │ Note name: [text input]       │  │
│  │ Content: [text area]          │  │
│  │ [💾 Save] [🗑️ Delete]         │  │
│  └───────────────────────────────┘  │
└─────────────────────────────────────┘

Creating Your First Note¶

Step 1: Enter a Note Name

When you first open the app (with no existing notes), you'll see:

1. A text input field labeled "Note name:"
2. Placeholder text suggesting examples like:
3. "Meeting ideas"
4. "Career thoughts"
5. "Project notes"

Step 2: Write Your Content

Click in the text area below the note name and start typing. The text area supports:

• Multi-line text
• Markdown formatting (when you view the JSON)
• Up to ~10,000 characters comfortably (no hard limit)

Step 3: Save Your Note

Click the 💾 Save Note button. You'll see:

• ✅ Success message: "Saved '[note name]'"
• The page will refresh to show your saved note
• Character count and last modified date appear in the metadata column

Editing Existing Notes¶

For Multiple Notes:

1. Use the dropdown at the top to select which note to edit:

   Select existing note or create new:
   [Create New Note ▼]
      Create New Note
      Career Insights
      Meeting Notes
      Future Goals
   

2. Select a note from the dropdown

3. The note's content will load into the text area
4. Edit as needed
5. Click 💾 Save Note to update

Metadata Display:

When editing an existing note, you'll see metadata in the right column:

📊 245 chars
🕒 Modified: 2025-11-15

Deleting Notes¶

To permanently delete a note:

1. Select the note from the dropdown
2. Click 🗑️ Delete Note button
3. Confirm the deletion
4. ✅ Success message: "Deleted '[note name]'"

Understanding Your Notes Data¶

Where Are Notes Stored?¶

Your notes are stored in a JSON file on your local machine:

chronoscope/
└── data/
    └── user_notes.json  ← Your notes live here

Key Details:

• Variable name in app: st.session_state.notes_store
• Class: UserNotesStore (handles loading/saving)
• Format: JSON (human-readable text)
• Persistence: Survives app restarts
• Privacy: Local-only, never sent to cloud

JSON Structure¶

Here's what the user_notes.json file looks like:

{
  "notes": {
    "Career Insights": {
      "content": "I noticed a pattern of major role changes every ~2 years...",
      "last_modified": "2025-11-15T14:23:45.123456",
      "character_count": 245
    },
    "Meeting Notes": {
      "content": "Discussion with mentor about leadership opportunities...",
      "last_modified": "2025-11-14T10:15:30.987654",
      "character_count": 187
    }
  },
  "last_updated": "2025-11-15T14:23:45.123500",
  "version": "1.0"
}

Field Explanations:

Viewing Notes Outside the App¶

Reading Your Notes Directly¶

You can open user_notes.json in any text editor:

# Navigate to ChronoScope directory
cd /path/to/chronoscope

# View notes in terminal
cat data/user_notes.json

# Or open in editor
nano data/user_notes.json
# vim data/user_notes.json
# code data/user_notes.json  # VS Code

cd C:\path\to\chronoscope
notepad data\user_notes.json

Extracting Note Content¶

Using Python:

import json

# Load notes
with open('data/user_notes.json', 'r') as f:
    data = json.load(f)

# Print all notes
for note_name, note_data in data['notes'].items():
    print(f"\n=== {note_name} ===")
    print(f"Modified: {note_data['last_modified']}")
    print(f"Content:\n{note_data['content']}")

Using jq (command line):

# List all note names
jq '.notes | keys' data/user_notes.json

# Get specific note content
jq '.notes["Career Insights"].content' data/user_notes.json

# Export all notes to text files
jq -r '.notes | to_entries[] | "\(.key)\n\(.value.content)\n\n"' data/user_notes.json > all_notes.txt

Advanced Features¶

Managing Multiple Notes¶

Progressive Disclosure:

• 0 notes: Simple interface with "Create New Note" prompt
• 1 note: Direct editing with metadata display
• 2+ notes: Dropdown selector + metadata + "Other notes" preview

Other Notes Preview:

When editing one note, you'll see a preview of other notes at the bottom:

💡 Other notes: Meeting Notes, Future Goals, Timeline Review
... and 2 more

This helps you remember what else you've written without switching notes.

Character Counting¶

The app tracks character counts for each note:

📊 245 chars

Why Character Count Matters:

• Track note length over time
• Identify substantial vs. brief notes
• Monitor your writing habits

Timestamp Tracking¶

Every note tracks when it was last modified:

🕒 Modified: 2025-11-15

Full Timestamp in JSON:

The JSON file includes full ISO 8601 timestamps:

"last_modified": "2025-11-15T14:23:45.123456"

This precision is useful for:

• Sorting notes chronologically
• Understanding your writing patterns
• Data analysis and visualization

Backup System¶

The app includes an automatic backup system to prevent data loss:

How It Works:

1. Before saving, the app creates user_notes.json.backup
2. New content is written to user_notes.json
3. If save succeeds, backup is deleted
4. If save fails, backup is restored automatically

Manual Backup Recovery:

If something goes wrong and you have a .backup file:

# Check for backup
ls -la data/user_notes.json*

# Restore from backup
cp data/user_notes.json.backup data/user_notes.json

Best Practices¶

Note Organization¶

Strategies for Multiple Notes:

1. By Topic:
2. "Career Insights"
3. "Education Reflections"

4. "Personal Life Patterns"

5. By Time Period:

6. "2020-2023 Analysis"
7. "Current Goals (2025)"

8. "Long-term Vision"

9. By Purpose:

10. "Meeting Notes"
11. "Timeline Review Sessions"
12. "Pattern Analysis"

Writing Tips¶

Effective Note-Taking:

✅ Do:

• Date your entries within the content ("Nov 15, 2025: Noticed...")
• Use markdown formatting for structure (headings, lists, bold)
• Reference specific timeline events by name/date
• Capture "why" insights, not just "what" facts
• Review and update notes periodically

❌ Don't:

• Duplicate timeline event data (it's already in the events)
• Use notes as a to-do list (use external task manager)
• Store sensitive credentials or passwords
• Let notes grow excessively long (split into multiple notes)

Example Well-Structured Note:

# Career Patterns Analysis
Last Updated: November 15, 2025

## Key Observations

### Role Changes (Every ~2 Years)
- 2018: Started at StartupCo → 2020: Moved to TechCorp
- 2020: Junior Dev → 2022: Senior Dev → 2024: Team Lead
- Pattern: Growth happens after major learning investment

### Education → Promotion Correlation
- AWS Cert (2019) → Promotion (6 months later)
- ML Course (2021) → New role (4 months later)
- Insight: Certifications accelerate career transitions

## Future Actions
- [ ] Pursue management certification (2026)
- [ ] Target next role change (2027)
- [ ] Focus on leadership skills

## Questions to Explore
- Why do I change roles every 2 years?
- Is this sustainable long-term?
- What patterns do successful leaders follow?

Troubleshooting¶

Note Not Saving?¶

Symptoms: - Click "Save Note" but content doesn't persist - No success message appears - Note disappears after refresh

Solutions:

1. Check file permissions:

   ls -la data/user_notes.json
   # Should be writable by you
   
   # Fix permissions if needed
   chmod 644 data/user_notes.json
   

2. Check disk space:

   df -h .
   # Ensure you have available space
   

3. Check for corruption:

   # Validate JSON structure
   python -m json.tool data/user_notes.json
   # If invalid, restore from backup
   

4. Look for error messages:

5. Check Streamlit console output
6. Look for red error alerts in the app

Finding Your Notes File¶

Can't locate user_notes.json?

# Search from ChronoScope root
find . -name "user_notes.json"

# Expected output:
# ./data/user_notes.json

File doesn't exist yet:

The file is created the first time you save a note. If you haven't saved any notes yet, the file won't exist.

Recovering Deleted Notes¶

Option 1: Use Automatic Backup

Check for .backup file immediately after deletion:

# Within seconds of deletion
cp data/user_notes.json.backup data/user_notes.json

Option 2: Manual Backups

If you made manual backups (see Backing Up Your Notes):

# Restore from manual backup
cp ~/chronoscope-backups/user_notes_20251115.json data/user_notes.json

Option 3: Time Machine / System Backups

# Use Time Machine
# 1. Open Time Machine
# 2. Navigate to chronoscope/data/
# 3. Find previous version of user_notes.json
# 4. Restore

# Use File History or Previous Versions
# 1. Right-click user_notes.json
# 2. Properties → Previous Versions
# 3. Select earlier version
# 4. Restore

# Use timeshift, btrfs snapshots, or similar
# Check your system's backup solution

Migrating Notes to New Installation¶

Moving notes to a new computer:

1. Export from old machine:

   cp data/user_notes.json ~/Downloads/user_notes_backup.json
   

2. Transfer the file:

3. USB drive
4. Cloud storage (Google Drive, Dropbox)
5. Email to yourself

6. Git (if not in .gitignore)

7. Import to new machine:

   # In new ChronoScope directory
   mkdir -p data
   cp ~/Downloads/user_notes_backup.json data/user_notes.json
   

8. Verify:

9. Start ChronoScope
10. Check that all notes appear in the dropdown

Backing Up Your Notes¶

Manual Backup Script¶

Create a simple backup script:

#!/bin/bash
# save as: backup_notes.sh

BACKUP_DIR=~/chronoscope-backups
DATE=$(date +%Y%m%d_%H%M%S)

mkdir -p $BACKUP_DIR
cp data/user_notes.json $BACKUP_DIR/user_notes_$DATE.json

echo "✅ Backup saved: $BACKUP_DIR/user_notes_$DATE.json"

# Keep only last 10 backups
ls -t $BACKUP_DIR/user_notes_*.json | tail -n +11 | xargs rm -f

chmod +x backup_notes.sh
./backup_notes.sh  # Run anytime

# save as: backup_notes.py
import shutil
from datetime import datetime
from pathlib import Path

backup_dir = Path.home() / "chronoscope-backups"
backup_dir.mkdir(exist_ok=True)

timestamp = datetime.now().strftime("%Y%m%d_%H%M%S")
source = Path("data/user_notes.json")
dest = backup_dir / f"user_notes_{timestamp}.json"

if source.exists():
    shutil.copy(source, dest)
    print(f"✅ Backup saved: {dest}")
else:
    print("❌ No notes file found to backup")

python backup_notes.py

Automated Backup Schedule¶

Using cron (macOS/Linux):

# Edit crontab
crontab -e

# Add line (backup daily at 2am)
0 2 * * * cd /path/to/chronoscope && ./backup_notes.sh

Using Task Scheduler (Windows):

1. Open Task Scheduler
2. Create Basic Task
3. Set trigger (e.g., Daily at 2:00 AM)
4. Action: Start a program
5. Program: python
6. Arguments: C:\path\to\chronoscope\backup_notes.py

Cloud Sync for Backups¶

Sync backup directory to cloud:

# Example: Dropbox sync
mkdir -p ~/Dropbox/chronoscope-backups
ln -s ~/Dropbox/chronoscope-backups ~/chronoscope-backups

# Now backups automatically sync to Dropbox
./backup_notes.sh

Privacy & Security¶

Local Storage Only¶

Your notes are stored only on your computer:

• ✅ Not sent to any cloud service
• ✅ Not transmitted to OpenAI API
• ✅ Not included in any telemetry
• ✅ Completely under your control

Protecting Sensitive Notes¶

If your notes contain sensitive information:

# Restrict file permissions (you only)
chmod 600 data/user_notes.json

# Use OS-level encryption
# macOS: FileVault
# Windows: BitLocker
# Linux: LUKS/dm-crypt

Version Control Considerations¶

The .gitignore includes data/user_notes.json by default:

# Personal Data
data/timeline_events.json
data/user_notes.json

git status
# Should NOT see data/user_notes.json in the list

FAQ¶

# Search all notes for keyword
grep -i "keyword" data/user_notes.json

# Or use jq
jq '.notes[] | select(.content | contains("keyword"))' data/user_notes.json

Related Documentation¶

• 📊 Timeline Events - Understanding timeline data vs. notes
• 🔒 Privacy & Security - Data storage and security
• 📤 Export & Sharing - Exporting timeline and notes data
• 🛠️ Architecture Guide - Technical details for developers

Have questions or suggestions for the notes feature?

• 💬 Join Community Discussions
• 🐛 Report Issues