@manthey mentioned that @marySalvi is working on this code and might be able to implement it while working on it.
Summary
Add a DELETE large_image/folder/{id}/tiles endpoint to mirror the existing PUT large_image/folder/{id}/tiles endpoint, allowing bulk removal of large_image items from a folder.
Background
The existing PUT large_image/folder/{id}/tiles endpoint allows bulk creation of large_image items in a folder. However, there's currently no corresponding bulk deletion endpoint, requiring clients to iterate through items and delete them one by one using individual API calls.
Use Case
In our application, when uploading a new multi-source metadata file, we need to:
- Upload a new JSON file that becomes a large_image item
- Remove large_image status from all other items in the folder (or in some cases, all items, including the new one)
Currently, this requires fetching all items in the folder and making individual deletion requests with retry logic, which is inefficient and error-prone.
Proposed API
DELETE large_image/folder/{id}/tiles
Parameters:
recursive (boolean, optional, default: false): Whether to recursively process subdirectories/subfolders
exclude (array of item IDs, optional): List of item IDs that should be excluded from large_image removal
Response:
- Success/failure status
- Count of items processed
- List of any errors encountered
Example Usage
DELETE large_image/folder/abc123/tiles?recursive=false&exclude=xyz456
This would remove large_image status from all items in folder abc123 except for item xyz456, without recursing into subdirectories.
@manthey mentioned that @marySalvi is working on this code and might be able to implement it while working on it.
Summary
Add a
DELETE large_image/folder/{id}/tilesendpoint to mirror the existingPUT large_image/folder/{id}/tilesendpoint, allowing bulk removal of large_image items from a folder.Background
The existing
PUT large_image/folder/{id}/tilesendpoint allows bulk creation of large_image items in a folder. However, there's currently no corresponding bulk deletion endpoint, requiring clients to iterate through items and delete them one by one using individual API calls.Use Case
In our application, when uploading a new multi-source metadata file, we need to:
Currently, this requires fetching all items in the folder and making individual deletion requests with retry logic, which is inefficient and error-prone.
Proposed API
Parameters:
recursive(boolean, optional, default: false): Whether to recursively process subdirectories/subfoldersexclude(array of item IDs, optional): List of item IDs that should be excluded from large_image removalResponse:
Example Usage
This would remove large_image status from all items in folder
abc123except for itemxyz456, without recursing into subdirectories.