Uh oh!
There was an error while loading. Please reload this page.
feat(ingest): guide users from dataset to creating a use case - #232
Merged
Conversation
The end-of-ingest "What's next" said "ready for training jobs" and linked only the metadata page — which led a customer (Charité) to expect ingested data to appear in their benchmark automatically. It does not: ingest registers a standalone DATASET; to train/benchmark you create a use case and select it. New copy names the actual next step and links both destinations: Your data is registered as a dataset. View it at https://ai.tracebloc.io/metadata To train or benchmark models on it, create a use case at https://ai.tracebloc.io/my-use-cases Pick this dataset when you set it up. Prod-hardcoded on purpose (dev/stg are internal-only). Refs backend#1073. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jul 12, 2026
Closed
saqlainsyed007
approved these changes
Jul 13, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rewrites the CLI's end-of-ingest "What's next" message so it bridges the mental-model gap that confused a pilot customer ([redacted]/[redacted]): ingesting registers a standalone dataset — to train or benchmark on it you must create a use case and select that dataset. The old copy ("ready for training jobs", metadata link only) implied the data would just become trainable, which it doesn't.
Before (
internal/submit/summary.go):After:
Notes
/my-use-cases(the real Next.js route;/myusecases404s).summary.go;go build+go test ./internal/submit/...green; gofmt clean.Part of the onboarding-discoverability fix in backend#1073 (item 1). The backend error-message + docs items in that ticket are separate follow-ups.
🤖 Generated with Claude Code
Note
Low Risk
User-facing copy only in the ingest summary printer; no logic, URLs beyond hardcoded prod links, or data-path changes.
Overview
Updates the CLI "What's next" block after a successful ingest so it matches the product flow: ingest only registers a dataset, not a trainable job.
Instead of implying the data is ready for training jobs with a single metadata link, it now states that registration explicitly, links
/metadatato view the dataset, and directs users to/my-use-casesto create a use case and select that dataset for training or benchmarking. A hint reminds them to pick the dataset during setup.Reviewed by Cursor Bugbot for commit 63ec886. Bugbot is set up for automated code reviews on this repo. Configure here.