Skip to content

Issue 5: WRAP Integration - #6

Draft
klondikemarlen wants to merge 17 commits into
mainfrom
issue-5/wrap-integration
Draft

Issue 5: WRAP Integration#6
klondikemarlen wants to merge 17 commits into
mainfrom
issue-5/wrap-integration

Conversation

@klondikemarlen

Copy link
Copy Markdown
Member

Fixes #5

Relates to:

Context

Add ability to insert files from WRAP and received with a confirmation payload.
This should be a simpler process that creating all the dependent entities individually.

This is currently implemented on the DigitalVault side as https://github.com/icefoganalytics/digital-vault/blob/17c091c8d2d5be3e31b093158cf45786a16e1ac2/api/src/controllers/integration-controller.ts
On the WRAP side nothing exists, though the solution will be similar to the other integrations in https://github.com/icefoganalytics/wrap/tree/ea184b2d824cbfe312be8e23cd664877b4e6a017/api/src/integrations

Describe the solution you'd like

  • Ability to insert files from WRAP and respond with a confirmation payload.

Endpoint:

POST /api/sources/:sourceId/submissions

Payload will include:

  • workflow title
  • workflow category
  • workflow users (by OID not by email - make sure that this is built in a flexible enough way that it could support by email for other projects)
  • workflow routing slip
  • workflow attachments

Response should include:

  • id: -> ArchiveItem identifier
  • url: -> of archive item access page in app
  • submittedAt -> submission confirmation timestamp

Additional context

  1. Use Bearer Auth for connection? Maybe https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow/call-your-api-using-the-authorization-code-flow

Implementation

TODO

Screenshots

TODO

Testing Instructions

  1. Run the test suite via dev test (or dev test_api)
  2. Boot the app via dev up
  3. Log in to the app at http://localhost:8080

@klondikemarlen klondikemarlen self-assigned this Oct 28, 2025
@klondikemarlen klondikemarlen added the enhancement New feature or request label Oct 28, 2025
@klondikemarlen
klondikemarlen force-pushed the issue-5/wrap-integration branch from 3610a28 to 0cbe5cd Compare October 28, 2025 22:44
Policy logic should be as simple as possible to avoid access loopholes.
Will replace with sources/:sourceId/submissions setup.
TODO: delete all reference once they have been recreated in Submissions.CreateService.
Why? Easier to find and and avoid duplicates.
@klondikemarlen klondikemarlen moved this from Backlog to In progress in Digital Vault Oct 29, 2025
@klondikemarlen klondikemarlen moved this from In progress to Ready in Digital Vault Oct 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Status: Ready

Development

Successfully merging this pull request may close these issues.

WRAP Integration

1 participant