Skip to content

[formrecognizer] Address Feedback from JS/Java UX Studies #11882

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
8 of 11 tasks
kristapratico opened this issue Jun 8, 2020 · 2 comments
Closed
8 of 11 tasks

[formrecognizer] Address Feedback from JS/Java UX Studies #11882

kristapratico opened this issue Jun 8, 2020 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Cognitive - Form Recognizer
Milestone

Comments

@kristapratico
Copy link
Member

kristapratico commented Jun 8, 2020

To follow up:

@kristapratico kristapratico added Cognitive Services Client This issue points to a problem in the data-plane of the library. FormRecognizer labels Jun 8, 2020
@kristapratico kristapratico added this to the [2020] July milestone Jun 8, 2020
@kristapratico kristapratico self-assigned this Jun 8, 2020
@rakshith91
Copy link
Contributor

rakshith91 commented Jun 19, 2020

Some initial feedback from Java/JS UX study

  • Add documentation to clarify getFieldValue() and getValueText()

  • Order fields in position for the document (unsupervised map of fields). Currently, field ordering is not maintained.

  • Helper function to search and return fields to shortcut getFields().get("FieldName") (Might need more discussion).

  • Helper/accessor to get Table cell data more easily (Table indexer or getRow() like Js has)

  • [Service follow up] Cannot understand the breaking for FormLines. For a line "* = Exceeds Maximum: Indicates the service exceeds patient/group benefit year maximum." why is it breaking on "=" or "*"

  • Models exposed to users to have toString() method for formatting purposes.

  • Add readme code snippet pointers for statements in key concepts.

  • For Copy, hard to find resource id and region. Add docstrings to clarify this more.

  • Consider adding a mix of fromUrl and stream overload code snippets in the main readme.

  • Consider adding a sample showing an example for converting a recognized form to known predefined fields. [receipt sample]

  • Consider moving TrainingDoucments errors to top level training result (needs more discussion)

DEBRIEF

  • Data returned must not be sorted - model data to match the order of the form

  • clarify what receipt is on documentation

  • begin_recognize_receipt rename to **_form_stream vs **_from_uri - or use a helper method to read from uri

  • value vs value_text in receipt result was not intuitve (consider renaming?)

  • recheck copy api documentation

  • LAYOUT API is ambigious - should the onfo be included in the recognized form results?

  • highlight what fields are available in the receipt returned

  • valueText vs fieldText vs labelText - naming confusion

@kristapratico
Copy link
Member Author

Spun off new issues for anything pending, closing this issue

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Cognitive - Form Recognizer
Projects
None yet
Development

No branches or pull requests

3 participants