v0.3.0

Some changes in the way errors from Omeka are handled:

• Omeka responses with HTTP status codes in the 400s and 500s will now generate exceptions rather than return nothing or some unexpected JSON. This should make for more consistent handling of responses, and easier bug checking.
• If Omeka has returned something that can't be parsed as JSON, the raw response text will be displayed (to help with debugging) and a JSONDecodeException will be raised

I think the only major impact will be in calls to get_resource_by_id() which previously returned None if the resource didn't exist. A non-existent resource will now generate an HTTPError triggered by a 404 status code.

v0.2.0

Major changes:

• add_media_to_item() now lets you supply a metadata payload so you can add whatever properties you want to the media file. You can also specify a template and resource class. This should be backwards compatible.
• If you supply a template id but not a resource class id to either add_media_to_item() or add_item() they will now apply the template's default resource class (if it has one) to the item. If you supply a resource class id, your value will override the template's value.

v0.1.1

Fixes a bug that meant items weren't being added to the specified item set (#1).

v0.1.0

Added new methods for updating and deleting resources, as well as methods for managing templates. These include:

• add media to items
• add markers to items (assuming you have the Mapping module installed)
• prepare and upload a resource template that has been exported from another Omeka instance

v0.0.5

Include CITATION.cff file and bump version for Zenodo.

v0.0.4

Minor changes:

• the paths to media files can now be either strings or pathlib Path objects
• if no title is supplied for a media file, the file name will be used