Hi, On Oct 10, 2010, at 11:45 PM, Dan Scott wrote: > I've just pushed a new bzr-based branch of Evergreen to > http://bzr.coffeecode.net/evergreen-social
Cool! > The reason it's a branch, instead of a commit directly to trunk, is > because it's all very tentative. Thank you for giving us the opportunity for to provide feedback before it hits trunk. > Also in the yet-to-add camp is the actual UI for adding a rating, > review, or tag to a given item. I've sketched out a rough schema for > each, but the schema built in some assumptions that I'm now questioning. > For example, I put "approver" and "approval_date" columns on the > social.user_review table, thinking that libraries would want to approve > every user-generated review before it is publicized, but I'm leaning > towards providing a user-flagging mechanism instead (so that users' > reviews would be published immediately, but other users could flag the > review as offensive and that would push it into an assessment queue). I believe that some libraries will want to manually approve every review before it is published, but I too would prefer that the default be to publish reviews immediately with a mechanism to allow other users to flag offensive or spam reviews - the more responsive the review interface is, the more likely it will actually be used. Giving the moderation system hooks for dictionaries and filters (e.g., Akismet) would also help address concerns about inappropriate content sneaking in. > * Figuring out how to match bibs between systems so that once > everybody has Activity Streams for their bibs, we can start to > aggregate reviews / ratings / tags between library systems And this could extend beyond Evergreen libraries - for example, it could be useful to exchange tags and reviews with SOPAC users. Regards, Galen -- Galen Charlton VP, Data Services Equinox Software, Inc. / Your Library's Guide to Open Source email: [email protected] direct: +1 352-215-7548 skype: gmcharlt web: http://www.esilibrary.com/
