Spike: Updating existing datasets

[teeceeas]

As a Developer, I want to investigate the requirements and technical implications for enabling dataset updates in the data catalogue, so we can design a clear, user-friendly update process that ensures data integrity.

Acceptance Criteria

• Gather insights on common update use cases (e.g., editing metadata, updating ownership information).
• Define which users (e.g., data custodians, data stewards) should have update permissions and under what conditions.
• Identify key metadata fields that should be editable (e.g., descriptions, tags, last modified date, data quality indicators).
• Determine any metadata fields that should remain read-only to prevent unintended changes.
• Outline a potential workflow for updating datasets, including any required review, validation, or approval steps.
• Define user permissions and roles necessary to update datasets, ensuring only authorised users can make changes.
• Evaluate current catalogue infrastructure to understand what modifications are needed to support dataset updates.
• Identify potential risks (e.g., accidental data overwrites, inconsistent metadata) and any validation mechanisms needed to mitigate these.
• Determine if there are dependencies or integration points with other systems that could impact the dataset update process.
• Outline requirements for tracking changes to datasets (e.g., change logs, history, timestamps).
• Identify whether notifications or alerts are needed to inform relevant users of updates to datasets they rely on.
• Provide a summary of findings and recommended approach.

[YvanMOJdigital]

As a data steward I need to edit my assigned datasets that have been already ingested on the catalogue within the findmog service without technical knowledge or interaction with the team