AdminManagement

AdminManagement is the repository workspace for the current QDB-native administration and checking workflow. The main application is QDBAdmin, and the repository also contains design material, handover notes, historical reference content, and local startup tooling.

Purpose

The active product direction is to build a QDB-native checking, issue, and comment workflow. The project intentionally avoids directly porting legacy RS checks; instead, it uses RS material as historical context and rebuilds useful checks in QDB terms.

Repository structure

• QDBAdmin/ - the active web application, settings, templates, and app-level handover material.
• Documentation/ - current product guidance, startup notes, design documents, and reference material.
• changelog/ and QDBAdmin/changelog/ - historical release and change notes.
• handover/ and QDBAdmin/handover/ - handover summaries and versioning notes.
• entities/ - schema and entity definition files.
• templates/ - shared templates and supporting UI files.
• Test API/ - older API/test tooling retained for historical context.

Current architecture direction

• QDBAdmin is the active application and operational interface.
• The design focus is a QDB-backed workflow with checks, issues, comments, actions, event queue support, and integrity pages.
• Legacy RS validation material is reference-only unless it has been intentionally migrated into QDB tables.

Local development

From the repository root, start the local application with:

start_server.bat

This opens the app 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 RS content as historical context rather than the current source of truth.
• Avoid exposing database credentials or other sensitive configuration.
• Prefer verified edits; the repository has a prior history of Windows-mounted write corruption issues.

Current build focus

The next recommended work is workflow hardening: real user attribution, a 30-day purge for deletion-marked issues, richer issue-context details, and per-check parameter prompts in the Integrity page.