The system interpretation of dates that contain years made out of 1 or 2 digits (e.g. MM-YY or MM-Y) is not clearly indicated to users.
For example: a user could attempt to look for events that took place on the 31st of January, and subsequently enter 31-01. The fact that the system interpretation of that value is actually January of the year 31 is not apparent in the UI.
Solution idea: Use an era marker to indicate BCE and CE besides the years in the parsedValue string.