A small guide sample can demonstrate a parsing or mapping issue without sharing an entire private source. Include only synthetic or appropriately redacted channel and programme records, preserve their structure, and remove account-bearing URLs. The aim is to show the data relationship rather than distribute a live guide credential.
Keep the sample internally consistent
If you replace a channel id, replace its programme references with the same synthetic key. An inconsistent redaction creates a new mapping error that was not present in the original. Keep the relevant timestamp and text structure intact.
Remove hidden private fields
Artwork URLs, source links and document comments can carry account tokens or identifying hostnames. Inspect more than the visible title. A sample attached as a file can contain information that a screenshot does not show.
Explain what you changed
Tell the recipient that identifiers and URLs are synthetic while the structural problem is preserved. That prevents someone from treating example.invalid as a failed production endpoint. Keep the original only in your private diagnostic records.
A practical sequence
- Reduce the sample to one channel and a few programmes.
- Replace secrets consistently with synthetic values.
- Explain the original error and what was redacted.
An example
A sample using channel id demo.station and programme channel demo.station preserves the relationship without revealing the real service identifier or guide URL.
Questions about this topic
Can redaction make a sample invalid?
Yes. Inconsistent replacement can break the structure you are trying to demonstrate.
Should the full source URL remain in a comment?
No. Remove private URLs from comments as well as visible fields.
