Analyze Global Search and Print

[lmullane]

Title of ticket:

Description

Summarize issue

Dependencies

Are there any dependencies?

DOD

• [x] Global search across all documents in a records package, #3849
• [x] 1st look at PDFTron search; second look a customization
• [x] Print, Download, Save all pages in a records package
• [x] Preview Pane for all documents needs to be stitched
• [x] Present options: Stitch vs Global Search
• [x] Estimation - review with DEVs and indicate to Business
• [ ] MCFD folder structure

[abin-aot]

' MCFD folder structure ` - Any User Research documentation around Folders on MCFD - @lmullane . @JHarrietha-AOT @m-prodan ?

[abin-aot]

As indicated on this task , analysis has been done to incorporate a global search on content across all gathered records and search across comments, annotations on all documents / records gathered. As elaborated during the meeting on 30/May refinement. There are 3 options to stitch the records package together to utilize PDFTron's GLOBAL search on records content, comments etc and enable a global PRINT, PREVIEW etc.

1. Client side stitching - stitching executions' on user 's Browser using PDFTRON clientside JS API - Demo'd to all!
2. Server side / Back end Stitching
3. Hybrid Approach - Client Side and Server Side

My personal suggestion is to move ahead with the Option #3 - since both the option has PROS and CONS when it comes to RECORD's PACKAGE SIZE. Means, client side stitching works well for kind of RECORD(s) that are small-medium in size and can have performance issues when total size of all the RECORDS crosses certain limit - we need to FIND it!. There comes option #2 where we stitch documents on Backend and present it to reviewer app as a singular document. This options(#2) also has CONs when it comes to adding additional records, deleting and replacing records, since a re-stitch is required!!!. As discussed during demo meeting @lmullane , @m-prodan agreed on the idea of appending new, replacement records in the end of main large document, rather than re-stitiching from scratch to match SORT algo of stitching when initial document was created.

FROM A STRATERGICAL POINT OF VIEW on development, lets starts with Option#1 and see whether things get deteriorated! and we can take a call for making HYBRID pattern based on that findings.

[abin-aot]

MCFD folder structure or creating FOLDER structure or partial releases or BRINGING in FOLDER on RECORDS management has been postponed to a later date - and IS NOT part of this analysis. @lmullane @m-prodan

[abin-aot]

closing this task, elaborated to DEVs, Business.