Build song-centric manifests directly from real audio directories
Constraint: Keep the current fused 4-table workflow while reducing manual JSONL authoring for onboarding real audio files into live PostgreSQL. Rejected: Require hand-authored manifests as the only path into the song-centric importer | It slows real data onboarding and raises operator effort. Confidence: high Scope-risk: narrow Directive: Prefer build_songcentric_manifest_from_directory.py -> import_songcentric_manifest_live.py as the default Phase-1 path for real file-directory onboarding. Tested: /usr/local/miniconda3/bin/python acr-engine/scripts/build_songcentric_manifest_from_directory.py on a real local wav smoke directory; imported the generated manifest into postgres://d2:d2pass@127.0.0.1:5432/d2 schema acr_songcentric_test; reran the import and verified counts remained media_entity=9, audio_object=22, feature_fact=9, set_membership=9; git diff --check; /usr/local/miniconda3/bin/python scripts/check_markdown_links.py --root docs returned OK for 11 active markdown files Not-tested: non-wav duration probing and very large directory trees
Showing
9 changed files
with
277 additions
and
0 deletions
acr-engine/data/pgvector_eval/music20/songcentric_directory_manifest_import_report_rerun.json
0 → 100644
No preview for this file type
No preview for this file type
-
Please register or sign in to post a comment