Skip to content

CEL Resource Hub

I'm Christina Sun, and I put this hub together while offboarding from the California Education Lab (UC Davis). It links the CEL code repositories I'm handing off and collects the workflows I've leaned on for getting research done here.

None of it is official lab policy — it's just what's worked for me, shared in case it's useful to you too.

Whether you've inherited one of my projects or you're a GSR just trying to get something running on Scribe, I hope there's something here for you.

Who this is for

Maybe you inherited one of my CEL projects, or you're a GSR or labmate getting set up on Scribe, or you're the lab's data-management custodian or IT contact. I assume you:

  • are comfortable with Stata,
  • may have never used git or Claude Code, and
  • run analysis (or are about to) on the lab's Scribe server over SSH.

Why a personal hub?

My projects get handed off when I leave, and often there's no named successor at the time — so the documentation has to stand on its own. I'd rather write down how I actually work than leave you to reverse-engineer it.

Start here

  • Offboarding repositories

    Every CEL code repository I'm handing off — links, server locations, status, how to run each one, and where the project's Google Docs are archived.

    Browse offboarding repositories

  • Offboarding standards

    The bar I try to hold my own projects to before I leave them behind — my handoff checklist and README template.

    Offboarding standards

  • Workflow tips

    The workflows I use (edit locally, sync, run on Scribe) and the tools behind them: VSCode, git, Scribe & SSH, keeping data safe.

    Workflow tips

  • Resources

    What tools you need and how to get access.

    Resources

How I set up my repos (a pattern you'll see across mine)

Most of my CEL analysis repos share the same shape, so once you learn one you can read them all:

  • All Stata code lives under do/, driven by a single entry point do/main.do.
  • File paths are defined in one place, do/settings.do (often branched by machine, e.g. Scribe vs. local).
  • Code and documentation live on GitHub; the confidential data lives only on Scribe.
  • The pipeline runs on Scribe with stata-mp -b do do/main.do.

The va_consolidated repo is my most fully documented example of this pattern (it ships a plain-English HANDOFF.md) and is a good one to read first.

Maintaining this hub

This site is built with MkDocs Material. To edit, change the Markdown under docs/ and run mkdocs serve for a live preview. See the repo README.md for setup.