Hi,
Thanks for publishing ExplodedView — the callout-to-BOM mapping pipeline is genuinely well built, and the staged AI pipeline with the DocTR/PaddleOCR diagnostics saved us a lot of guesswork.
We're a company building a spare-parts assistant for forklift service teams. We evaluated ExplodedView internally against our own corpus of manufacturer parts catalogues (a few hundred PDFs) to see whether it could replace our manual figure-to-BOM linking. It handled the layouts well.
The repository currently has no LICENSE file, which by default means all rights are reserved, so we've kept the work strictly to an internal, read-only evaluation and have not shipped anything.
Would you consider adding an explicit open-source license — MIT or Apache-2.0? Either would let us use it properly and, more importantly, let us contribute back.
We do have things worth contributing. While evaluating we made a fairly large set of changes, mostly around not publishing uncertain mappings:
callout-to-BOM bindings are published only on exact normalised matches; edit-distance candidates go to a quarantine list as review evidence instead of silently claiming a BOM row;
pages that are hydraulic or electrical schematics are no longer paired as exploded views just because a BOM-like table sits next to them;
OCR is clipped to the diagram region when the diagram and the BOM share a page, so table cells and headings can't become hotspots;
glued PDF text such as 3031 is split only when the BOM allows exactly one segmentation;
around 30 additional tests covering the above.
We'd be glad to open these as pull requests if a license makes that possible, and equally glad to hear if you'd rather we didn't.
Either way — thanks for the work, and no pressure at all.
Best regards,
Hi,
Thanks for publishing ExplodedView — the callout-to-BOM mapping pipeline is genuinely well built, and the staged AI pipeline with the DocTR/PaddleOCR diagnostics saved us a lot of guesswork.
We're a company building a spare-parts assistant for forklift service teams. We evaluated ExplodedView internally against our own corpus of manufacturer parts catalogues (a few hundred PDFs) to see whether it could replace our manual figure-to-BOM linking. It handled the layouts well.
The repository currently has no LICENSE file, which by default means all rights are reserved, so we've kept the work strictly to an internal, read-only evaluation and have not shipped anything.
Would you consider adding an explicit open-source license — MIT or Apache-2.0? Either would let us use it properly and, more importantly, let us contribute back.
We do have things worth contributing. While evaluating we made a fairly large set of changes, mostly around not publishing uncertain mappings:
callout-to-BOM bindings are published only on exact normalised matches; edit-distance candidates go to a quarantine list as review evidence instead of silently claiming a BOM row;
pages that are hydraulic or electrical schematics are no longer paired as exploded views just because a BOM-like table sits next to them;
OCR is clipped to the diagram region when the diagram and the BOM share a page, so table cells and headings can't become hotspots;
glued PDF text such as 3031 is split only when the BOM allows exactly one segmentation;
around 30 additional tests covering the above.
We'd be glad to open these as pull requests if a license makes that possible, and equally glad to hear if you'd rather we didn't.
Either way — thanks for the work, and no pressure at all.
Best regards,