Skip to content

Formalize review process for DCAT-US 3.0 schema changes #6026

@rshewitt

Description

@rshewitt

User Story

In order to ensure schema changes are reviewed consistently and safely, the datagov wants a formal review process for proposed schema updates.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

  • GIVEN schema changes need a consistent review process
    WHEN the current workflow is investigated
    THEN existing steps, stakeholders, and gaps are documented

  • GIVEN schema changes may impact multiple systems
    WHEN a proposed review process is drafted
    THEN reviewer roles, impact areas, and decision documentation are defined

  • GIVEN the investigation is complete
    WHEN the recommendation is documented
    THEN follow-up implementation tickets are identified

Background

Schema changes can affect harvesting, validation, catalog display, APIs, search indexing, migrations, documentation, and downstream consumers. We need to investigate the current process and define a lightweight, repeatable review workflow.

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

Document the current process, identify gaps, define reviewer roles, create a schema change impact checklist, and recommend where review decisions should be recorded.

Metadata

Metadata

Assignees

Labels

DCAT-US3Tickets related to DCAT-US3 release and support.

Type

No type
No fields configured for issues without a type.

Projects

Status
✔ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions