For the maintainer. Restricted features need a staff login; there are no other user accounts.
Admin
One admin site (/mizan/admin/) has a section per catalog. PPCaT tables are edited there directly; every
row has short note codes and long free-text remarks.
Databases
- default
django/dbase/django.sdb: users, sessions, admin log- simda
simda/data4db/simda.sdb; tracked text dumpsimda/data4db/simda.sql(simda/data4db/dump.sh)- ppcat
ppcat/dbase/ppcat.sdb(schema 3, Django migrations); tracked dumpppcat/dbase/ppcat.sql(ppcat/dbase/dump.sh)- PhysPar
physpar_slim.sdb, read only (settingPHYSPAR_DB)
After changing catalog data: run the dump script, review the diff of the .sql file, commit it.
The .sdb files are never committed.
PPCaT legacy import
python manage.py import_ppcat_legacy --dry-run shows what would be imported from the legacy tables
and ppcat/dbase/ppcat.csv, and lists values that need review; --replace re-imports (it
deletes all schema-3 rows first, so only use it before manual edits start). Then run
ppcat/dbase/dump.sh and commit ppcat.sql.
Curation
Corrections that must survive re-imports (merging duplicate bodies, satellite names) live in
ppcat/intake/curation.toml; python manage.py apply_curation ppcat/intake/curation.toml applies
them and can be rerun at any time.
Catalog updates
LCDB (light-curve data): python manage.py update_lcdb --download fetches the current public
release from minplanobs.org; --file reads a release ZIP or a summary file. The PPCaT copy and the
LCDB rotation rows of PPCaT objects are replaced as a whole. Staff can also use the button on
/ppcat/lcdb/. Afterwards run ppcat/dbase/dump.sh and commit.
Infrared observations (SBNAF/Konkoly IRDB): python manage.py update_irdb --file
~/Astronomy/Radiometry/Data/Konkoly/public.csv replaces the infrared observations of PPCaT bodies (used for the
heliocentric distance on the Explore page and, later, the thermal workbench).
Releases
Each catalog has its own tags (simda-v…, ppcat-v…); SiMDA releases go to Zenodo.
Developer documentation
In the repository: docs/ (data models and decisions), STATUS.md (state, plan, open
questions), AGENTS.md (rules for AI agents).