eddRequestable isn't serialized in response sometimes

[nodanaonlyzuul]

@ktp242 told me that:

Responses like the one to http://localhost:3000/api/v0.1/request/deliveryLocationsByBarcode?barcodes[]=33433062317023 have NO eddRequestable property in the response.
I've confirmed that, before jsonld serialization the item does have eddRequestable: false...and one can see as much in the logger.debug() statement in ItemResourceSerializer#serialize.

I haven't done any digging yet but my instinct is that something in the JSONLD serializers is stripping out that property. Here's the API's response as of writing.

{
  "@context": "http://127.0.0.1:3000/api/v0.1/discovery/context_all.jsonld",
  "@type": "itemList",
  "itemListElement": [
    {
      "@type": "bf:Item",
      "@id": "res:i15400083",
      "identifier": [
        "urn:bnum:b15990082",
        "urn:barcode:33433062317023"
      ],
      "uri": "i15400083",
      "holdingLocation": [
        {
          "@id": "loc:mal82",
          "prefLabel": "SASB M1 - General Research - Room 315"
        }
      ],
      "deliveryLocation": [
        {
          "@id": "loc:mab",
          "prefLabel": "SASB - Art & Architecture Rm 300"
        },
        {
          "@id": "loc:maf",
          "prefLabel": "SASB - Dorot Jewish Division Rm 111"
        },
        {
          "@id": "loc:map",
          "prefLabel": "SASB - Map Division - Rm 117"
        },
        {
          "@id": "loc:mag",
          "prefLabel": "SASB - Milstein Division Rm 121"
        },
        {
          "@id": "loc:mai",
          "prefLabel": "SASB - Periodicals and Microforms Rm 119"
        },
        {
          "@id": "loc:mal",
          "prefLabel": "SASB - Service Desk Rm 315"
        }
      ],
      "idBarcode": [
        "33433062317023"
      ]
    }
  ]
}

[nodanaonlyzuul]

This is happening in JsonLdSerializer#format() when it calls this.statements().

this.statements() is dropping the key.

[nodanaonlyzuul]

We should let the front end team know when this is fixed so they can remove some defensive code they've built around this bug.