doc-rq-data

To define data quality requirements for public archive data, you create an RQ-DATA document specifying non-functional thresholds for completeness, uniqueness, and accuracy. This ensures measurable quality criteria are established for your archive.

Maintain traceability between data quality requirements and SnowCard by linking the RQ-DATA document to related designs. This verifies dependencies with RQ-RDR, BD-DATA, and BD-ERD documents according to diopside conventions.

Non-functional requirements for data completeness and accuracy define specific quality thresholds, such as acceptable missing data rates or reflection times. They ensure public archive data meets measurable operational standards.

Yes, the doc-rq-data skill verifies dependencies with BD-DATA and BD-ERD documents. It ensures your data quality requirements maintain clear traceability and structural links to related design documents.

Yes, you can revise existing data quality requirements to align with Obsidian operational rules. The skill facilitates document compliance by updating RQ-DATA files to meet diopside conventions.

You should set quality thresholds for missing data when defining new requirements for the public archive. Use this process to ensure the specified quality thresholds are measurable and correctly linked to design documents.