Feature request: include doi & # occurrences in each gbifDownloadKey in the literature API

[dshorthouse]

Although the number of occurrence records included in a gbifDownloadKey is discoverable through the occurrence API, it would be far more performant for my particular use-case if these were additionally included in the literature API. I recognize however that this might alter the structure of the gbifDownloadKey array to an array of hashes something like this with three keys that include the UUID, the DOI, and a count of occurrences:

"gbifDownloads": [
{"gbifDownloadKey": string, "doi": string, "occurrenceCount": integer}, ... 
]

At present, the download DOIs are known by an awkward regex at my end to parse the tags array whereas these should probably be afforded more prominent placement in the response.