zotero use case

[zippy.rsshead]

we're thinking of using zotero as a the front end of purchasing system
for our
library. what we have imagined so far,
users or library selectors would save items into one or more shared
folders --
data would be pulled via the zotero api into an ordering system,
approved or rejected, and the progress of the order tracked throughout
the process. if the api supported deleting, then we would remove the
items from the folder.

I have several questions about this.

1) i don't know how to introduce changes into the zotero model for
new bits of info that should be available everywhere.
Here's what i mean -- we go to save an item -- we should save the
price with it, (if available), so i'd like a hook attached into all
the translators that would make that possible.
2) Also as part of the request, the selectors need to specify a 'fund
code' so there should be a new field for that also.
3) Ideally, when an item is saved into the group library, there would
be a call back, into the ordering system, telling that system new
items are available and they should be sucked into the ordering system
right way. This is a sort of ping back, or callback; it might be that
supporting PubSubHubBub on shared folders (or all folders) on the
zotero server would make this possible.
I'm not sure.


Order Front End <-------Polls ------- Zotero Server / shared folder
for orders <--------inserts item requests --------- Zotero Plugin

Does this make sense? Would supporting Hubbub on zotero folders make
sense?
how about hooks into translators?

Thanks for any ideas about this,
Rick