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

[Feature] Validation errors for multi marked fields like roll number #214

Open
Udayraj123 opened this issue Sep 21, 2024 · 2 comments
Open

Comments

@Udayraj123
Copy link
Owner

Is your feature request related to a problem? Please describe.
This feature would be useful to separate out a bucket of OMR sheets which contain invalid identifiers like the roll number

Describe the solution you'd like
We want to support field-level configuration for validating if the field is allowed to be multi-marked (in the same column/row).
The solution should be generic enough for user to configure any field/custom label to be an identifier.

Describe alternatives you've considered
We already have a flag by the name filter_out_multimarked_files which is currently False by default. This flag when turned on creates a separate CSV output for the "multimarked" files. But this is not granular to the field level yet. This idea can be extended.

Additional context
Additionally we should consider a top level validation schema for all such field level validations.

@Prasadayus
Copy link

The solution would involve implementing a field-level configuration that allows users to specify if a particular field (such as roll number) can be multi-marked. This configuration should be flexible enough for users to designate any field or custom label as an identifier.

Additionally, this solution should extend the existing filter_out_multimarked_files flag to be granular at the field level. Users should be able to define which fields are validated for multi-marks, allowing more precise filtering of invalid sheets.

@Udayraj123 Can I work on this?

@Udayraj123
Copy link
Owner Author

Interesting, @Prasadayus this is a medium sized issue which can take around a week usually to implement. so I'd prefer if you started with a smaller issue first. I'm still assigning this to you but first raise a PR for an issue that will take shorter time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants