|
RE: SAPing etiquette
Quote: Jellyn I recently SAPed a book and wrote my review of it while it was still fresh in my head. Obviously with the SAP function down, that review still can't be posted. Which is kind of annoying. But if I'd waited to write the review, I probably would have forgotten stuff and had to reread the book. Or at least had to look at it again.
Now I'm thinking about reading a new book that isn't in the db. Should I SAP it before I read it? Then maybe it'll be in there by the time I finish? (Not that it's terribly likely)
Or is it better to wait until I've actually read it, since I might not finish it or might decide it's not worth reviewing or.. whatever?
Is it wasting the CLs' time to SAP a book you never review?
Or is it okay, since at least now it's in the db and someone else can come along and review it?
Go ahead and SAP it if you want to. We don't keep a strict accounting of who is posting reviews and how fast. If you want to be sure to get a 'first review' out of it, wait until you know you'll be able to get a review up quickly. If you don't care about a firstie, SAP it when you see fit.
One reason to wait until the review is actually ready - sometimes products do actually appear in the database on their own and 'real' listings always have better links than SAPed products which, presumably, means that they will generate better IS. Just something to think about.
Amy |