Implement File-Based Integration with ILLIAD on New Fileserver

[kayiwa]

User Story:

As a user in resource sharing, I want to be able to scan an item for an ILLIAD request, place it on a designated file server with a transaction number, and have Figgy automatically process it, add OCR, and upload the OCR'ed file to a location where ILLIAD can complete the transaction.

Acceptance Criteria:

• A new (?) file server is set up with either SMB or NFSv4 protocol to avoid UID/GID issues associated with NFSv3.
• Figgy is configured to monitor a specific directory on the new file server.
• When a scanned item (with a corresponding transaction number in the filename) is placed in the monitored directory, Figgy

automatically:
* Processes the file.
* Performs OCR.
* Uploads the OCR'ed file to a designated directory monitored by ILLIAD.
* ILLIAD is able to detect the OCR'ed file and complete the associated transaction.

Tasks:

1. Set up new file server:

• Choose appropriate hardware/virtual machine for the file server.
• Install the operating system and configure networking.
• Install and configure either SMB or NFSv4 server with appropriate security measures.
• Create the necessary directories for incoming scans and processed files.

2. Configure Figgy:

• Update Figgy's configuration to monitor the designated directory on the new file server.
• Ensure Figgy can access the file server with the chosen protocol (SMB or NFSv4).
• Configure Figgy to perform OCR on the scanned files.
• Configure Figgy to upload the OCR'ed files to the ILLIAD-monitored directory.

3. Configure ILLIAD:

• Ensure ILLIAD is configured to monitor the designated directory for incoming OCR'ed files.
• Verify that ILLIAD can correctly associate the OCR'ed files with their corresponding transactions and complete the requests.
• connect the workstations where folks do the scanning work on with the new share (BigFix)

4. Testing:
   • Perform end-to-end testing with sample ILLIAD requests and scanned files to verify the entire workflow.
   • Test different file types and sizes to ensure Figgy can handle them correctly.
   • Test error handling and logging to ensure issues are identified and addressed.

Out of Scope:

• How the current file server is used as an attic. This ticket focuses on the new file server and its integration with Figgy and ILLIAD.

Dependencies:

• Availability of the new file server hardware/VM.
• Access to Figgy and ILLIAD configurations.
• Coordination with ILLIAD administrators for configuration and testing.

[stephayers]

Why are we building a new file share and not using one of our current file share systems?