AdminManagement

AdminManagement is the project workspace for the current QDB-native administration and checking workflow. The repository combines the operational application, supporting design documentation, handover notes, legacy reference material, and local tooling used to run the system.

Primary focus

The active direction is QDBAdmin v1.0.0 with a QDB-native checking, issue, and comment workflow. The design intent is to use QDB as the system of record and to rebuild useful validation logic in QDB terms rather than porting legacy RS checks directly.

Repository layout

• QDBAdmin/ - current application code, settings, templates, and handover material.
• Documentation/ - current design guidance, startup notes, and reference material.
• changelog/ and QDBAdmin/changelog/ - historical change notes and release documentation.
• handover/ and QDBAdmin/handover/ - handover and versioning documentation.
• entities/ - schema and entity definitions.
• Test API/ - older API/test tooling retained for historical reference.
• templates/ and shared app folders - supporting project files and front-end scaffolding.

Current architecture

• QDBAdmin provides the active web application and admin workflow.
• Documentation files explain the intended model, constraints, and current product direction.
• Historical RS validation material is kept as reference only and should not be used as a live data source unless it has been migrated into QDB tables.
• The project is designed around a QDB-backed workflow with issue tracking, comments, actions, data-change events, and integrity checks.

Local development

From the project root, start the local app with:

start_server.bat

This opens the application at:

http://localhost:8998/qdbadmin/

Manual equivalent:

cd QDBAdmin
python -m pip install -r requirements.txt
python manage.py runserver --settings=qdbadmin.settings2 8998

Important project rules

• Use qdbadmin.settings2, views2.py, and urls2.py for current work.
• Treat legacy RS material as historical context, not a direct source of truth.
• Prefer verified changes and careful documentation updates; this repo has a history of Windows-mounted write corruption issues.
• Do not expose database credentials or local system secrets in project docs.

Recommended next work

The current build focus is workflow hardening: user attribution, 30-day purge for deleted issues, richer issue-context details, and per-check parameter prompts in the Integrity page.