API change
alex
changed. I don't see any discussion of this here or in the zotero
forums, and I wanted to confirm.
What I observe is the following, in both the atom feed and the xml for
an "item":
zapi:itemID has been replaced by zapi:key
"key" values are different from the previous "itemID" values
different data types - key is a string, itemID was a number
key is now used as unique identifiers for items in the "self" and
"alternate" urls
previous urls (using itemID) redirect to the new urls
And I just realized, it looks like "key" in the API is the same as
items.key in the sqlite database client-side. That's convenient as
previously the relation between client and server IDs was rather
mysterious.
Could Dan or someone in the know confirm that?
I'll limit the editorial commentary here, but Zotero has published
this API and it has at least one user, me! LOL. :-D No big deal in
this case, but sheesh, it is an API after all...
Sean Takats
Editorial commentary fully justified! We made the change from IDs to keys as part of the general overhaul of the server architecture last week, which went live over the weekend. Although we were working directly with the major known users of the Zotero API, we neglected to announce this change more widely, for which I apologize.
As you note, keys make a great deal more sense, and the shift should require very few changes in any consuming code. We have some more major improvements to the API in the pipeline, and we'll try to get those announced in advance of any switchover.
Best regards,
Sean
> --
> You received this message because you are subscribed to the Google Groups "zotero-dev" group.
> To post to this group, send email to zoter...@googlegroups.com.
> To unsubscribe from this group, send email to zotero-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/zotero-dev?hl=en.
>