Bug: The 'culture' filter on /object endpoint fails when using culture names

[Aofled]

Description

The culture parameter on the /object endpoint no longer filters items correctly when using a CULTURE NAME (e.g., "Greek"). It returns zero records. However, filtering by CULTURE ID (e.g., 37527534) still works as expected.

According to the documentation, both names and IDs should be supported. This behavior used to work previously.

Steps to Reproduce

1. Requesting by Culture Name (Broken):
   https://api.harvardartmuseums.org/object?culture=Greek&apikey={YOUR_API_KEY}

Response:

{
  "info": {
    "totalrecordsperquery": 10,
    "totalrecords": 0,
    "pages": 0,
    "page": 0,
    "responsetime": "15 ms"
  },
  "records": []
}

2. Requesting by Culture ID (Working):
   https://api.harvardartmuseums.org/object?culture=37527534&apikey={YOUR_API_KEY}

Response:

{
  "info": {
    "totalrecordsperquery": 10,
    "totalrecords": 810,
    "pages": 81,
    "page": 1,
    "responsetime": "24 ms"
  },
  "records": [...]
}

Culture Metadata Context

The cultural record for "Greek" confirms the name match and existence of items:

{
  "id": 37527534,
  "name": "Greek",
  "objectcount": 9203
}

Expected Behavior

Filtering by culture=Greek should return the same results as filtering by culture=37527534.

[Aofled]

The same applies to the "century" parameter.

[jeffsteward]

Thanks for reporting this. I'm working on a patch to get things working again.