Datacap Fingerprint Service
Hi All
Here's a quick question / observation -
Scenario -
Datacap Application utilising fingerprints and the Fingerprint Service.
Fingerprint matching uses the web service URL & if 'TRUE' is specified it will create a new fingerprint at runtime (which is presumably loaded into the web service as it is made aware of this).
Now if I am using the fingerprint web service & create a new fingerprint in either Datacap Studio or Fastdoc the fingerprint service is not made aware of the new fingerprint, and by using the Fingerprint Service Testing Tool I can confirm this.
If the use case requires customers to use Datacap Studio /OR FastDoc for fingerprint maintenance / creation how can the fingerprint service be utilised? Other than getting them to manually kick off a fingerprint web service load (via the maintenance tool or web service call)?
This seems a little lacking to me.
Appreciate any comments, suggestions or further information on the service.
Kind regards
That is a size that probably needs the service.
They need to scan in the images anyway, why not just give them a job that does the scanning and the profiler task just creates the fingerprint-- No need for anything after that including verify or export in that job. Then after they scan into that job ,they can do into DStudio or FastDoc and define the zones/pagetype/classification. The advantage would be that you are replicating exactly what the runtime images will look like at the time of fingerprint matching (imagefix, rotation, etc). In other words, instead of scanning to disk, then adding it by searching the disk for the images to manually add in DStudio or FastDoc, a job takes care of all of that for them.
We do have an action that creates fingerprints (CreateFingerprint), but I think that the AddFingerprint ruleset doesnt use it (it creates the fingerprint implicitly). If you put that in there, you are likely to get two fingerprints out of it.
As you mentioned, it will pick these up the next time that the fingerprint service is restarted. I think it is fair to say that applications that have enough fingerprints to warrant using the fingerprint service are probably using the DNA (learning) technologies to populate it, so it is a simple matter to run the image through the system and create it that way instead of using DStudio and/or FastDoc. Once the fingerprint is created, you can add or touch up the zones and also classify the fingerprint either automatically (through intellocate actions) or with DStudio or FastDoc.
If you are talking about a system with a fixed number of Fingerprints (so you would use FindFingerprint(FALSE), then you probably don't need the fingerprint service at all.
Tom
Thanks for your input Tom.
I mention this as we have a very large customer interested in replacing their current system with Datacap. They have around 12,000 'form types' which will essentially be replaced with Fingerprints. They receive around 15 new 'form types' per day, which will all need to be fingerprinted.
The current system is ancient and requires a full restart for each new form type. Having the ability to load the new fingerprint into the service is definitely a hot seller.
These fingerprints will make use of a lot of OMR boxes - my initial impression suggests that DNA technologies would not be suitable (it seems rather hard to zone these appropriately using Datacap Desktop, though I can't say I've ever tried.).
One thought would be to add an action to the 'Fingerprint Add' ruleset which causes a 're-load' of the fingerprint service. But I'm not sure of the feasibility of this (both performance & whether the ruleset will actually allow this - I'm unfamiliar with how it's invoked).
I'm currently involved in a long-term engagement with IBM so I'm limited on time to investigate this pre-sales opportunity, hence I thought I'd seek the community knowledge here. Any ideas would be greatly appreciated - it may be a case to involve IBM directly.
Many thanks.
Thanks Tom.
I'll pass this onto the team. It's food for thought right now, but the requirement to provide a fairly seamless method for fingerprint creation is a must-have. A job which performs all the steps in one would definitely be beneficial.
Regards