We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new "manifests" property needs to be added to Hydra Image class and mapped from DB entity and returned for any read/write endpoints.
"manifests"
{ "@context": "https://api.dlcs.digirati.io/contexts/Image.jsonld", "@id": "https://api.dlcs/customers/2/spaces/1/images/first", "@type": "vocab:Image", "id": "first", "manifests": ["m123", "aadopsi0"] }
This property should be rendered, if set, everywhere the Hydra image class can be returned:
GET|PATCH /customers/{c}/spaces/{s}/images
POST /customers/{c}/allImages
GET|PUT|PATCH /customers/{c}/spaces/{s}/images/{i}
GET /customers/{c}/queue/batches/{b}/images
GET /customers/{c}/queue/batches/{b}/assets
POST /customesr/{c}/queue
POST /customesr/{c}/queue/priority
For updates, "manifests" can be:
["foo", "bar"]
null
[]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The new
"manifests"
property needs to be added to Hydra Image class and mapped from DB entity and returned for any read/write endpoints.This property should be rendered, if set, everywhere the Hydra image class can be returned:
GET|PATCH /customers/{c}/spaces/{s}/images
POST /customers/{c}/allImages
GET|PUT|PATCH /customers/{c}/spaces/{s}/images/{i}
GET /customers/{c}/queue/batches/{b}/images
GET /customers/{c}/queue/batches/{b}/assets
POST /customesr/{c}/queue
POST /customesr/{c}/queue/priority
For updates,
"manifests"
can be:["foo", "bar"]
) - this will replace any currently saved valuesnull
- this will savenull
if new asset, or leave any existing"manifests"
if update[]
- this is explicitly clearing the values, sonull
in database.The text was updated successfully, but these errors were encountered: