| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| dev:web_api:v3:changes_from_v2 [2014/07/02 13:31] – dstillman | dev:web_api:v3:changes_from_v2 [2017/11/12 19:53] – external edit 127.0.0.1 |
|---|
| | <html><p id="zotero-5-update-warning" style="color: red; font-weight: bold">We’re |
| | in the process of updating the documentation for |
| | <a href="https://www.zotero.org/blog/zotero-5-0">Zotero 5.0</a>. Some documentation |
| | may be outdated in the meantime. Thanks for your understanding.</p></html> |
| | |
| | |
| ====== Changes in Zotero API v3 ====== | ====== Changes in Zotero API v3 ====== |
| |
| * ''meta'' contains non-editable system-generated properties like ''createdByUser''/ ''lastModifiedByUser'' (for group items), ''creatorSummary'', and ''numChildren''. | * ''meta'' contains non-editable system-generated properties like ''createdByUser''/ ''lastModifiedByUser'' (for group items), ''creatorSummary'', and ''numChildren''. |
| * Other Atom-specific feed properties (''title'', ''author'', ''published'', ''updated'') have been removed. | * Other Atom-specific feed properties (''title'', ''author'', ''published'', ''updated'') have been removed. |
| | * Clients sending ''application/atom+xml'' in the ''Accept'' header will continue to receive Atom responses if no other format is requested |
| * For ''format=json'', ''include=data'' has replaced Atom's ''content=json'' and is now the default mode, with a top-level ''data'' object containing the editable fields. As with ''content'', additional comma-separated types can be requested (e.g., ''include=data,bib''). The requested types are provided as top-level properties. ''content=html'' remains the default in Atom. | * For ''format=json'', ''include=data'' has replaced Atom's ''content=json'' and is now the default mode, with a top-level ''data'' object containing the editable fields. As with ''content'', additional comma-separated types can be requested (e.g., ''include=data,bib''). The requested types are provided as top-level properties. ''content=html'' remains the default in Atom. |
| * Multi-object writes now take an array of JSON objects directly, rather than an object with an ''items''/''collections''/''searches'' property containing an array. | * Multi-object writes now take an array of JSON objects directly, rather than an object with an ''items''/''collections''/''searches'' property containing an array. |
| ==== tl;dr for existing Atom consumers ==== | ==== tl;dr for existing Atom consumers ==== |
| |
| | * Request ''format=atom'' explicitly, or send ''application/atom+xml'' in the ''Accept'' header |
| * Use ''zapi:parsedDate'' instead of ''zapi:year'' | * Use ''zapi:parsedDate'' instead of ''zapi:year'' |
| * Use ''Total-Results'' HTTP header instead of ''zapi:totalResults'' | * Use ''Total-Results'' HTTP header instead of ''zapi:totalResults'' |
Upgrade Storage