The parse option uses /rmeta and then conflates all the keys together so that users can't tell which metadata goes with the primary file and which metadata goes with which embedded file.
Would it be possible to warn users of the current behavior and offer an option to get the raw json from the /rmeta endpoint?
The parse option uses /rmeta and then conflates all the keys together so that users can't tell which metadata goes with the primary file and which metadata goes with which embedded file.
Would it be possible to warn users of the current behavior and offer an option to get the raw json from the /rmeta endpoint?