min_date_value and max_date_value are treated as NUMERIC

[wardweistra]

Call:
api.new_constraint(concept='Demographics:BIRTHDATE', max_date_value='1-1-1980')
Is translated to:

{  
   "type":"and",
   "args":[  
      {  
         "type":"concept",
         "conceptCode":"Demographics:BIRTHDATE"
      },
      {  
         "type":"value",
         "valueType":"NUMERIC",
         "operator":"<=",
         "value":315615599999.0
      }
   ]
}

This returns 0 patients.

While Glowing Bear translates this to (excluding the patient subselection):

{  
   "type":"and",
   "args":[  
      {  
         "type":"concept",
         "conceptCode":"Demographics:BIRTHDATE"
      },
      {  
         "type":"time",
         "field":{  
            "dimension":"value",
            "fieldName":"numberValue",
            "type":"DATE"
         },
         "operator":">=",
         "values":[  
            "1950-01-01T00:00:01.000Z"
         ]
      }
   ]
}

Code treats is as numerical value, not date:

transmart-api-client-py/transmart/api/v2/constraints/atomic.py

Line 116 in e831b1f

class MinDateValueConstraint(MinValueConstraint):