Auto-Indexing Specific Software Requirements Sample Clauses

Auto-Indexing Specific Software Requirements. The Software shall: 1. Use custom indexing rules as detailed in the County Indexing Manual and The County Recorders Association of California Document Reference Manual/General Rules for Indexing. 2. Automatically create an index from electronic images of documents mostly related to property transactions. 3. Use Optical Character Recognition to capture index data and seamlessly integrate with the County’s end-to-end LandDocs™ land records system from Granicus LLC. 4. Present the “auto-indexed” document and corresponding image to the user for verification within LandDocs™ data entry panel. 5. Guide the user through the verification process by automatically finding and highlighting the extracted information in the displayed image. 6. Have a Data Entry Panel that shall: a. Allow the user to swipe pre-OCR’ed text without incurring the performance penalty of doing OCR after rubber band operation. b. Only require relevant data entry fields for the current document type and display a completely different field layout that is switched dynamically at run time. c. Allow for auto complete based on database lookups. d. Allow for complex data validation logic on a per field basis including but not limited to regular expression patterns and database queries to confirm validity of data. 7. Contain an extensive library set of data capture rules, the set shall contain production tested rules established by County for more than 30 data types, including parcel ID, grantor, grantee, legal description and other user and state-defined data fields. 8. Classify scanned documents/instruments based on content. 9. Be expected to achieve 90% accuracy on County’s four primary document types, which include: a. Deed of Trust b. Reconveyance c. Substitution of Trustee d. Substitution of Trustee and Full Reconveyance 10. Obtain an overall accuracy rate of at least 70% on all other document types. 11. Handle multi-title documents and provide the appropriate index data including party names as required for each title. 12. Be able to automatically map extracted data to conform to County’s naming conventions 13. Have the ability to easily reformat its output to meet specifications and send data to multiple downstream systems simultaneously. 14. Allow the Data Entry Panel to easily be updated or enhanced in the future based upon custom requests without the need to upgrade or reinstall software.
Sample 1
AutoNDA by SimpleDocs

Related to Auto-Indexing Specific Software Requirements

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!