Closed andrewhayward closed 10 years ago
Do we want a user to trigger the re-notification, or do we want aestimia itself to re-notify at regular intervals?
Hmm... I hadn't really thought about that option. Automation probably makes more sense - will pull @cmcavoy in on this one.
Ultimately, I suppose, it should be straightforward enough to write things in such a way that both task- and user-initiated calls can happen, should we want that.
Probably worth noting that, given application callback urls aren't technically required, we only need to worry about this in situations where the callback url is provided.
Decided this should be an automatic process for now.
As per #85, we need to allow a user to 're-notify' a client, if it becomes apparent that a review has not been picked up on. #87 allows for the creation of a
seen
attribute on<review>
models, and #88 makes this visible in the UI.90 makes it possible for clients to let the system know that a new review has been picked up on, but if a client doesn't respond to a callback in this way, an Aestimia user should be able to start the notification process over.