如何扫描入/至 Web 应用程序

发布于 2024-10-01 02:26:30 字数 1457 浏览 6 评论 0原文

一段时间以来，我一直在考虑如何处理 Web 应用程序中的纸质文档输入。主要问题是如何统一元数据和扫描的 PDF。为了这个例子，我将提出一个假设的费用索赔申请。到目前为止我考虑过的方法：

Web 1.0，打开网页，创建费用报销&输入数据，切换到扫描应用程序，扫描到文件，切换到浏览器，单击“选择文件”导航到扫描文件上传。优点：编码简单。缺点：糟糕的工作流程，每个工作站都需要扫描仪（以及驱动程序和磁盘空间等/可能不适用于瘦客户端：Citrix / iPad）
条形码样式打开网页，创建费用报销& ;输入数据，保存，打印条码贴纸，将条码粘贴到纸上。一天结束时，扫描所有带有条形码的纸张。批量上传它们并根据条形码将它们分配给费用报销。（扫描中的 OCR 条形码是一个已解决的问题，例如，请参阅 exactCODE）良好的工作流程，每个部门一台扫描仪就足够了。缺点：每个工作站都需要条形码标签打印机（比扫描仪更容易，但并不便宜），扫描的纸张仅在几个小时后才可用
Web 2.0 风格 使用本地扫描仪扫描到 [Dropbox] 文件夹。 Web 应用程序使用 Dropbox API 检测新扫描，将其呈现给用户并要求他们输入元数据数据。优点：良好的工作流程。缺点：每个人都需要一个扫描仪，Web 应用程序不能只是弹出并说“有一个新的扫描可用”。
批量样式 有人扫描所有文档，按必须处理这些文档的人员（或按文档类型：费用索赔、发票、订单）分隔它们。文档在队列中批量上传（例如作为 ZIP）到 Web 服务器。现在，一个人必须处理这个队列并输入所需的元数据。优点：只需维护一个扫描仪。缺点：工作人员手头不再有纸质文件，只有在线版本。我的同事认为这是一个大问题。
条形码批量 有人对所有传入文档进行条形码标记，将它们扫描到单个文件夹中并将它们批量上传到存储库，然后以老式方式将纸张分发到不同的部门。处理费用报销的人员还输入纸上的条形码编号。 Web 应用程序联系存储库并根据扫描文档的条形码编号检索并将其与元数据一起保存。优点：编码简单，缺点：大量纸张仍在四处徘徊，文档可能会被扫描，而这些文档可能永远不应该进入数字存储库 - 例如医疗记录）
桌面应用程序编写TWAIN 基于小型桌面应用程序，用于扫描、上传到 Web 应用程序并打开浏览器窗口以添加元数据。优点：良好的工作流程，缺点：每个桌面一台扫描仪，不是 Web 应用程序/平台问题

对于更好的解决方案有什么建议或对上述方法之一有评论吗？

I have contemplating how to handle paper document input in Webapps for some time. The main problem is how to unify metadata and a scanned PDF. For the sake of this example I will present a hypothetical Expense Claim Application. Approaches I have considered so far:

Web 1.0, Open a webpage, create an expense claim & enter data, switch to scanning app, scan to file, switch to Browser, click on "choose file" navigate to scanned file upload it. Pros: simple to code. Cons: terrible workflow, every workstation needs a scanner (and drivers and disk space, etc. / might not work with thin clients: Citrix / the IPad)
Barcode Style Open a webpage, create an expense claim & enter data, save, a barcode sticker is printed, stick barcode onto paper. At the end of the day scan all barcoded papers. bulk upload them and assign them based on the barcode to the expense claims. (OCRing barcodes in scans is a solved issue, e.g. see exactCODE) Pros: decent workflow, one scanner per department is enough. Cons: need barcode label printers at every workstation (easier than scanners but not cheaper), scanned papers become only available after a few hours
Web 2.0 Style Scan with a local scanner to a [Dropbox] folder. Webapp uses the Dropbox API to detect new scans, present them to the user and ask them for entering the Meta-Data. Pros: nice Workflow. Cons: Everybody needs a Scanner, Webapp cant just pop-up and say "there's a new scan available".
Batch Style Somebody scans all documents separating them by person which has to process them (or by type of document: Expense Claim, Invoice, Order). Documents get batch uploaded (e.g. as an ZIP) to the Webserver in a queue. A person now have to work through this queue and enter the required meta data. Pros: Only a single Scanner needs to maintained. Cons: Staff doesn't have the paper at hand anymore, only the online version. This is considered a big show stopper by my colleagues.
Barcode Batch Somebody barcode-labels all incoming documents, scans them in a single folder and bulk-uploads them to a repository, then distributes the paper the old fashioned way to the different departments. People processing an expense claim also enter the barcode number from the paper. The Webapp contacts the repository and retrieves based on the barcode number the scanned document and saves it together with the metadata. PPros: simple to code, Cons: lot of paper still wandering around, documents might gat scanned which probably never should enter a digital repository - e.g. medical records)
Desktop app Write an TWAIN based small Desktop application which scans, uploads to the Webapp and opens a browser window to add the metadata. Pros: nice workflow, Cons: One scanner per desktop, Not a Webapp/platform issues

Any suggestions for a better solution or comments on one of the approaches above?

分享到QQ

分享到微博