[x] Allow searching/filtering by any metadata field in the user_envelope
[x] Allow searching/filtering by any field inside the resource data
[x] Allow date oriented retrieval (aka "list-records" in LR 1.0)
Apply some filters to a query, and then retrieve "everything I haven't seen yet."
[x] Allow retrieval of metadata by specialized identifier
In the Credential Registry, there will be a unique identifier called a CTID, which is a kind of URN. CTI wants CR to be able to resolve this CTID. An example of that resolution in the API might look like: /api/credentialregistry/id/urn:ctid:6726c341-7119-4ed8-bf37-efb036dd104b
One challenge is to identify in the metadata schema so that it's possible to locate where the id field is (and what it's called) in the schema.
/api/credentialregistry/id/urn:ctid:6726c341-7119-4ed8-bf37-efb036dd104b
id
field is (and what it's called) in the schema.