Work through the decision
Record actual published, updated, fetched and checked dates separately. Set review triggers appropriate to technical data, validity, source rights and product changes. Validate endpoint body/schema and current identity before activating an adapter. A successful homepage response or plausible feed path does not prove usable current data or permitted ingestion.
A fictional worked example
A fictional connector returns an HTML challenge at a feed URL. The learner records the failed capability check and retains the last lawful source reference. Retrieval time is not substituted for an unknown article publication date.
Evidence and authority limit
A freshness timestamp or configured URL does not establish a live parser, publication licence or current product suitability.
Put it into practice
Create a source check record with one genuine update date, one unknown date and an inconclusive endpoint.
Keep this record: Separate date fields, technical/rights state and actionable review triggers.
- Dates retain their actual meanings.
- Unknown dates remain unknown.
- Connector health follows real body and policy checks.
