Module aws_sdk_textract::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules§

  • Builders
  • Error types that Amazon Textract can respond with.

Structs§

  • An adapter selected for use when analyzing documents. Contains an adapter ID and a version number. Contains information on pages selected for analysis when analyzing documents asychronously.

  • Contains information on the adapter, including the adapter ID, Name, Creation time, and feature types.

  • The dataset configuration options for a given version of an adapter. Can include an Amazon S3 bucket if specified.

  • Contains information on the metrics used to evalute the peformance of a given adapter version. Includes data for baseline model performance and individual adapter version perfromance.

  • Summary info for an adapter version. Contains information on the AdapterId, AdapterVersion, CreationTime, FeatureTypes, and Status.

  • Contains information about adapters used when analyzing a document, with each adapter specified using an AdapterId and version

  • Used to contain the information detected by an AnalyzeID operation.

  • A Block represents items that are recognized in a document within a group of pixels close to each other. The information returned in a Block object depends on the type of operation. In text detection for documents (for example DetectDocumentText), you get information about the detected words and lines of text. In text analysis (for example AnalyzeDocument), you can also get information about the fields, tables, and selection elements that are detected in the document.

  • The bounding box around the detected page, text, key-value pair, table, table cell, or selection element on a document page. The left (x-coordinate) and top (y-coordinate) are coordinates that represent the top and left sides of the bounding box. Note that the upper-left corner of the image is the origin (0,0).

  • A structure that holds information regarding a detected signature on a page.

  • The input document, either as bytes or as an S3 object.

  • Summary information about documents grouped by the same document type.

  • The Amazon S3 bucket that contains the document to be processed. It's used by asynchronous operations.

  • Information about the input document.

  • The evaluation metrics (F1 score, Precision, and Recall) for an adapter version.

  • Returns the kind of currency detected.

  • An object used to store information about the Value or Label detected by Amazon Textract.

  • The structure holding all the information returned by AnalyzeExpense

  • Breakdown of detected information, seperated into the catagories Type, LabelDetection, and ValueDetection

  • Shows the group that a certain key belongs to. This helps differentiate between names and addresses for different organizations, that can be hard to determine via JSON response.

  • An object used to store information about the Type detected by Amazon Textract.

  • Contains information extracted by an analysis operation after using StartLendingAnalysis.

  • Information about where the following items are located on a document page: detected page, text, key-value pairs, tables, table cells, and selection elements.

  • Shows the results of the human in the loop evaluation. If there is no HumanLoopArn, the input did not trigger human review.

  • Sets up the human review workflow the document will be sent to if one of the conditions is met. You can also set certain attributes of the image before review.

  • Allows you to set attributes of the image. Currently, you can declare an image as free of personally identifiable information and adult content.

  • The structure that lists each document processed in an AnalyzeID operation.

  • Structure containing both the normalized type of the extracted information and the text associated with it. These are extracted as Type and Value respectively.

  • The results extracted for a lending document.

  • Holds the structured data returned by AnalyzeDocument for lending documents.

  • Holds the normalized key-value pairs returned by AnalyzeDocument, including the document type, detected text, and geometry.

  • Contains the detections for each page analyzed through the Analyze Lending API.

  • Contains information regarding DocumentGroups and UndetectedDocumentTypes.

  • A structure that holds information about the different lines found in a document's tables.

  • A grouping of tables which contain LineItems, with each table identified by the table's LineItemGroupIndex.

  • Contains information relating to dates in a document, including the type of value, and the value.

  • The Amazon Simple Notification Service (Amazon SNS) topic to which Amazon Textract publishes the completion status of an asynchronous document operation.

  • Sets whether or not your output will go to a user created bucket. Used to set the name of the bucket, and the prefix on the output file.

  • The class assigned to a Page object detected in an input document. Contains information regarding the predicted type/class of a document's page and the page number that the Page object was detected on.

  • The X and Y coordinates of a point on a document page. The X and Y values that are returned are ratios of the overall document page size. For example, if the input document is 700 x 200 and the operation returns X=0.5 and Y=0.25, then the point is at the (350,50) pixel coordinate on the document page.

  • Contains information regarding predicted values returned by Amazon Textract operations, including the predicted value and the confidence in the predicted value.

  • Each query contains the question you want to ask in the Text and the alias you want to associate.

  • Information about how blocks are related to each other. A Block object contains 0 or more Relation objects in a list, Relationships. For more information, see Block.

  • The S3 bucket name and file name that identifies the document.

  • Information regarding a detected signature on a page.

  • Contains information about the pages of a document, defined by logical boundary.

  • A structure containing information about an undetected signature on a page where it was expected but not found.

  • A warning about an issue that occurred during asynchronous text analysis (StartDocumentAnalysis) or asynchronous document text detection (StartDocumentTextDetection).

Enums§

  • When writing a match expression against AdapterVersionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against AutoUpdate, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against BlockType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ContentClassifier, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against EntityType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against FeatureType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against JobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against RelationshipType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against SelectionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against TextType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ValueType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.