How to Handle Case Sensitivity Issues When Validating CSV Against JSON Schema in Data Curator?

[megin1989]

I am using Data Curator to validate CSV files against a predefined JSON schema. However, I am encountering a case sensitivity issue during validation.

Problem:

• The CSV data contains values like Other, but the corresponding enum field in the JSON schema defines the valid value as other.
• When the validation runs, it throws an error stating that the value doesn't conform to the enum because of the case mismatch.

Questions:

1. Is there a way to handle or ignore case sensitivity when validating CSV data against an enum in the JSON schema?
2. Can Data Curator be configured to treat values like Other and other as equivalent, or should I manually update the CSV or schema to match case?
3. Are there best practices for managing case sensitivity in enum fields for consistent validation?

Any advice or solutions would be really helpful. Thank you!