tldr first: I work at a government office and we want to do the probate court upstairs a favor and scan in and index a large collection of paper wills (10,000+). This is a simple use case and I'm wondering if OpenKM community is overkill.
=====
Our requirements are:
Associate scanned copy of the will with plain text indexed data (person's name, date of birth, etc)
Search indexed data by any field
Open source and installable without a third party (we have an existing proprietary software we can use, but the reason I'm looking around is to avoid the taxpayer expense of licensing a separate database instance)
Nice to have, but not necessary:
Ability to scan directly from the application (rather than scan to a folder and import)
OCR
Verification queue (index data is entered, then put in a queue to proofread by a second person)
That's more to illustrate how simple our use case is than to ask about features (it looks like OpenKM can do all but the verification queue).
We have a spare server well within requirements, so hardware is not an issue.
This is mainly for archival purposes, and the documents, once recorded, will rarely be accessed or modified.
Mostly looking for feedback if the set up and overhead of running and maintaining OpenKM is worth it for a system storing a large number of a single document type.
Thanks for any advice the community can provide.
=====
Our requirements are:
Associate scanned copy of the will with plain text indexed data (person's name, date of birth, etc)
Search indexed data by any field
Open source and installable without a third party (we have an existing proprietary software we can use, but the reason I'm looking around is to avoid the taxpayer expense of licensing a separate database instance)
Nice to have, but not necessary:
Ability to scan directly from the application (rather than scan to a folder and import)
OCR
Verification queue (index data is entered, then put in a queue to proofread by a second person)
That's more to illustrate how simple our use case is than to ask about features (it looks like OpenKM can do all but the verification queue).
We have a spare server well within requirements, so hardware is not an issue.
This is mainly for archival purposes, and the documents, once recorded, will rarely be accessed or modified.
Mostly looking for feedback if the set up and overhead of running and maintaining OpenKM is worth it for a system storing a large number of a single document type.
Thanks for any advice the community can provide.
