Identify how the episodes were created
Ask who recorded the data, what platform and collection process were used, and whether the source owns or distributes original records or derived exports. Keep collection identifiers and relevant configuration history. A catalog description can help locate a possible source, but it does not establish that a particular episode or requested signal is available for delivery.
Trace processing and aggregation
Record how media, actions, state, instructions, and labels were transformed or combined. Identify upstream sources when a collection pools several datasets. Preserve mappings and version references so a buyer can investigate a field or episode. A processed copy should not lose the information needed to understand its original control semantics and the source conditions under which it was generated.
Discuss the proposed use explicitly
Describe training, evaluation, internal sharing, distribution, retention, and other relevant requirements for source-specific review. Ask what documentation supports the proposed permission scope and any restrictions. Technical access or a public download link does not by itself answer every use question. This is a review framework, not a legal conclusion about a source or project.
Keep status and evidence distinguishable
A source offer, a sample review, and an approved delivery are different stages. Maintain clear status definitions and the supporting references rather than one unexplained cleared flag. Send Fiund the technical brief and intended use so feasibility, documentation, and remaining questions can be assessed together. No inventory, permission outcome, or delivery commitment is guaranteed by this category guide.
Review checklist
- Identify original and pooled sources
- Retain transformation history
- State intended use and handling
- Separate review stages and evidence