Page Comparison

Executive Summary

...

Requirements

Functional Requirements

• Allow the library to export deleted MARC authority records via API. 
• Support providing deleted authority record UUIDs via API 
• Support authority record purge configuration to be set to Never per tenant

Non-functional Requirements

...

• Same tablespace as the active table. Table name pattern <original_table_name>_archive 
• Trigger on delete should be implemented to move the record to the archive table.
• Domain events should be distinct for soft- and hard-delete.
• Update lastUpdatedDate, updatedByUserId in metadata.
• Tenant-level retention policy should be provided through configuration parameters.

Process:

• Soft-delete:
  1. update
  of
  1. the soft-delete flag in the original table, send events
  2. after
  all
  1. events are
  sent and
  1. processed, move the deleted record to the archive table
• Hard-delete:
  • if the retention policy is set then, on schedule the archive table should be cleaned by lastUpdatedDate field
  • if the retention policy for the tenant is set to never then no clean up is required

Open Questions