regex extractor node

Hello @NabilEnn
About the page# numbers :thinking: … “Let’s go in parts! as Jack the Ripper said.”

  1. You aren’t currently giving too much feedback. Like if the workflow’s latest update is currently working for you, or if it’s somehow satisfying your expected output.

  2. Matching the page with regex needs some context together with the name/patient extract. Then, if its related to this particular pdf sample; you shouldn’t split your solution in more than one topic. Because you will have to integrate the solution at some point.

  3. Working with regex requires a representative sample and use context. The current ‘Dummy Filev1.pdf’ is a one page pdf, then it will be hard to test multi-pages.
    Furthermore, the solution has different non functional requirements depending on page distribution: one pdf per page, or multipage pdf…

I think that I can deliver any of these outputs, even with this non representative sample. I have previous developments deployed with similar requirements… so I can figure out how it will perform on different functional requirements. But my dedicated time is limited too; so working without a clear target is not good for both of us either.

Please comment.

BR

4 Likes