Skip to content
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

As a user, I want the labelling option extracted #28

Open
Tracked by #229
k-allagbe opened this issue Sep 6, 2024 · 1 comment
Open
Tracked by #229

As a user, I want the labelling option extracted #28

k-allagbe opened this issue Sep 6, 2024 · 1 comment

Comments

@k-allagbe
Copy link
Member

k-allagbe commented Sep 6, 2024

Description

Context
Labelling options indicate whether a fertilizer uses "record keeping" or "no record keeping":

  • Record keeping: The label does not list active ingredients, using a generic statement like "Active ingredients derived from registered and exempt materials."
  • No record keeping: The label explicitly lists active ingredients, e.g., "Active ingredients derived from: Composted turkey litter, etc."

Problem Statement
We need to add a field in the pipeline that identifies the labelling option, indicating whether record keeping is used or not.

Acceptance Criteria

  • Implement a field in the pipeline to extract and indicate whether the labelling option is "record keeping" or "no record keeping" (e.g., a boolean).
  • Ensure that the pipeline accurately extracts this information from the provided data.
  • Validate the implementation with clear test cases.

Additional Information

@k-allagbe k-allagbe changed the title Labelling options (requirements to be elucidated) Labelling options Sep 10, 2024
@k-allagbe k-allagbe moved this to Todo in FertiScan Sep 10, 2024
@k-allagbe k-allagbe moved this from Todo to Blocked in FertiScan Sep 18, 2024
@k-allagbe k-allagbe changed the title Labelling options As a user, I want the labelling option extracted Oct 28, 2024
@k-allagbe
Copy link
Member Author

This issue is on hold due to an insufficient number of sample labels needed for solution design. For now, we will implement the field in the backend with a hardcoded default value. The user will be responsible for determining whether record keeping is present. The frontend will provide an input option for users to manually enter this information.

@k-allagbe k-allagbe moved this from Paused to Won't do in FertiScan Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Won't do
Development

No branches or pull requests

1 participant