DRS - MHR Integration Correct Document ID
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
From OPs ticket https://sbc-registries.atlassian.net/browse/ITOPS-184208
Staff Ticket Description: DRS – filed electronically and need to scan the originals to the same transaction and document id as provided by the system
Follow up staff note:
I filed the documents that I had electronically using a system generated document ID#, however, the issue and concern is that if we do this and still receive the original documents, we have to file them, box them and somehow account for them. I created a barcode with the same document ID on it as the system generated for me -in hopes that the scanner would recognize it exists and proceed- however it does not. I have dragged the electronic version into the DRS for the filing now and tried scanning it again.. with same result. So now therefore, I am uncertain how to handle the original documents on hand. I need this concern to be known and addressed by PO and policy team as well as Dev team - because I think this will be an ongoing concern.
Developer note:
Staff incorrectly created a MHR registration with a generated document ID instead of a barcode document ID for paper documents submitted by the client. It looks like staff is asking to have the ability to update the document ID in DRS and MHR after the registration has been created.
Recommendation:
Staff provide an 8 digit barcode that works with the scanning app in an OPs ticket: a MHR and DRS data fix is applied to replace the generated document id with the staff supplied barcode.
Application Changes:
Require the desktop scanning application with the DRS API integration to accept the DRS generated document ID's.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the desktop scanning application and its DRS API integration, then trace how document IDs are accepted for electronically filed and scanned documents. Confirm the expected handling of DRS-generated document IDs and verify that the scanning flow accepts them without requiring a separate barcode document ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100