Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] rating_product: Rating system for Products & Variants #253

Closed
lasley opened this issue Apr 17, 2017 · 1 comment
Closed

[RFC] rating_product: Rating system for Products & Variants #253

lasley opened this issue Apr 17, 2017 · 1 comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@lasley
Copy link

lasley commented Apr 17, 2017

This module will provide ratings for products by using the rating module provided by Odoo (v10) core. It will add rating to product.product, with another computed rating on the product.template containing an aggregate rating for the variants.

It will add a new model product.rating will be created that will allow for the abstract scheduling of product rating requests. This will allow for the module to be used in all contexts of a product (sales, purchases, etc), without requiring glue modules. The model will allow for the choice of:

  • Model to act on
  • Domain filter for matching records that should have a rating requested (similar to the way server actions work)
  • Email template used for ratings requests
  • product_field_id - This is the field on the record for the product that is being rated
  • rater_field_id - This will set the rating.rating.partner_id to the value of this field. The rating request email will be sent to this partner's email.
  • rated_partner_field_id - if defined, this will set the rating.rating.rated_partner_id to the value of this field

A scheduled task will be added that will iterate the active product.rating records, search the model for the defined domain, then send the defined email to the rater.

If a partner has already rated the product variant, they will be ignored from this task. On that same note, a partner should not be able to rate the same product variant twice. They should, however, be able to rate two different product variants of the same template - because they are technically different products.

Plan seems simple enough IMO. Anyone know of some pre-existing code/strategies, or see a hole in the plan?

@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant