@costdev noticed that while the DID field in FAIR package metadata should be simply id, it's served as did in the package metadata returned by the _fair=1 hack, probably because it's stored in a column named did, whereas id would be the internal UUIDv7 of the database row. The /packages endpoint takes the step of remapping the column in the json response, the embedded hack likely forgets to do this.
https://api.aspirecloud.net/packages/did:plc:m5tfrwxd3btacxlstcvop2ib (correct, uses id)
https://api.aspirecloud.net/plugins/info/1.2/?action=plugin_information&slug=pp-glossary&_fair=1 (uses did)
@costdev noticed that while the DID field in FAIR package metadata should be simply
id, it's served asdidin the package metadata returned by the_fair=1hack, probably because it's stored in a column nameddid, whereasidwould be the internal UUIDv7 of the database row. The /packages endpoint takes the step of remapping the column in the json response, the embedded hack likely forgets to do this.https://api.aspirecloud.net/packages/did:plc:m5tfrwxd3btacxlstcvop2ib (correct, uses
id)https://api.aspirecloud.net/plugins/info/1.2/?action=plugin_information&slug=pp-glossary&_fair=1 (uses
did)