[gaurav]

POST /get_setid answers with an object keyed by input index ({"0": {...}, "1": {...}}) because Tornado refuses to write a top-level list. NodeNorm Redis returns a list, and the clients were written against it. This PR lets NodeNormalizationBaseHandler write lists, and then returns the SetIDResponse objects as a list in input order, as the OpenAPI document now says. This is a breaking change for any client of NodeNorm ES that reads body["0"].

The babel_version query parameter still selects one Babel release for every set in the POST, and the response still carries X-Babel-Version.

Calls worth overruling

• Lists are allowed in the base handler, not serialized by hand in one handler. Tornado's refusal guards against JSON hijacking through <script> tags in very old browsers, which doesn't matter for a public JSON API that allows any origin. Allowing lists in the base handler means the next handler that returns a list doesn't hit the same 500 /get_allowed_conflations did. The comment on write() in handlers/base.py says why.
• The sets in one POST are normalized concurrently with asyncio.gather. One POST can now make as many concurrent Elasticsearch requests as it has sets (see Is there a limit to how many simultaneous CURIEs NodeNorm ES can support? #22 on cluster load). It's the last commit, so it can be dropped on its own.

What's here

• POST /get_setid returns a JSON array; the unreachable "empty result → 500" check after the loop is gone. The OpenAPI document's 200 response for it is now an array of SetIDResponse.
• A unit test for the base handler's list output, and a POST unit test in tests/test_openapi.py that mounts the handler with a fake generate_setid() patched through unittest.mock, so the fake doesn't leak into tests/test_set_identifiers.py when pytest-randomly runs that later. The existing tests of POST errors and of multi-Babel release selection (tests/test_babel_endpoints.py) now read the list, and an empty body is tested to get a 400.
• The integration test in tests/test_set_identifiers.py expects a list.

Before merging

• Decide whether to bump the API version. info.version is still 1.2.0, the version Update OpenAPI for SmartAPI registration and preserve multi-Babel behavior #58 set. This PR changes the shape of a response, and /status reports info.version, so if 1.2.0 has been or will be deployed without this, it should become 1.3.0, with a line in the README's "OpenAPI document" section.

Verification

On bc8fb41, all 290-odd tests pass except the four integration tests that need the su10 host (test_node_normalization_get and test_node_normalization_post in test_normalized_nodes.py, test_get_endpoint and test_post_endpoint in test_set_identifiers.py), which weren't run. So the list-expecting integration test hasn't been run.

🤖 Generated with Claude Code