BML Loop 1
Hypothesis: Catalogers will increase their understanding and productivity using a Graph RDF UI rather than a form-based Linked Data editor. Comparison editors this loop: Sinopia and Marva (both Blue Core Project).
Metric needed
Wall-clock time from "record loaded" to "record saved/exported," with per-phase splits (load → edit → validate → save).
Gap
No timing/event logging exists anywhere in the app today — no analytics dependency in package.json, no event hooks in src/state/graphStore.ts.
Task
Add lightweight, privacy-respecting local event timestamps (e.g. a sessionLog array in graphStore), exportable as JSON/CSV for later analysis. No hosted analytics SaaS — the app is entirely client-side with no backend, so this should stay that way.
Feeds into
Task-completion-time and abandonment-rate measure tickets for this loop's pilot comparison against Sinopia and Marva.
BML Loop 1
Hypothesis: Catalogers will increase their understanding and productivity using a Graph RDF UI rather than a form-based Linked Data editor. Comparison editors this loop: Sinopia and Marva (both Blue Core Project).
Metric needed
Wall-clock time from "record loaded" to "record saved/exported," with per-phase splits (load → edit → validate → save).
Gap
No timing/event logging exists anywhere in the app today — no analytics dependency in
package.json, no event hooks insrc/state/graphStore.ts.Task
Add lightweight, privacy-respecting local event timestamps (e.g. a
sessionLogarray ingraphStore), exportable as JSON/CSV for later analysis. No hosted analytics SaaS — the app is entirely client-side with no backend, so this should stay that way.Feeds into
Task-completion-time and abandonment-rate measure tickets for this loop's pilot comparison against Sinopia and Marva.