Skip to content

feat: Add “Save to Corpus Server” Functionality

Description: Currently, the application saves data locally or through existing mechanisms. There is a need to implement an additional feature that allows users to directly save transcriptions/records to the Corpus Server.

Requirement:

  • Add a new “Save to Corpus Server” option in the UI.
  • On trigger, send data directly to the Corpus Server via API.
  • Ensure proper request structure as per Corpus API.
  • Handle authentication if required.

Expected Behavior:

  • User can click “Save to Corpus Server” and data is successfully stored in the Corpus platform.
  • Proper success and error messages are displayed.

Scope:

  • Do not modify existing save functionality.
  • Extend current workflow with an additional save option.

Acceptance Criteria:

  • Data is sent using a POST request to the Corpus API.
  • Payload meets all validation requirements (e.g., description length, valid location).
  • Error handling and user feedback are implemented.
  • Feature works reliably for different inputs.

Next Steps:

  • Implement API integration
  • Add frontend validation
  • Test end-to-end flow with Corpus Server