Added the necessary boilerplate to disable auditing on the rated node during rating.
Added some asserts to the RatingService JUnit test code to test same.
Also some trivial doc changes.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@22708 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Without an explicit requirement for multiple rating schemes being applied to a node by a user and in order to simplify
the code and ease maintenance, the RatingService now only supports one rating scheme per node per user.
A rating can be applied, removed and a new rating in another scheme applied. But if the first is not removed, an exception will be thrown by the service.
This change was a simple edit in the model with changes to the service implementation and test code.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21585 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This is a preliminary JavaScript API for the RatingService.
The intention is to get something committed to enable possible feedback and to lay the basis for any improvements that be needed later.
It's the normal Alfresco JS API changes. The root object is 'ratingService' and all the methods are on that object.
Highly non-OO.
But it is tested.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21145 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
I've changed the ratings 'score' from an integer to a float as fractional ratings seems like a reasonable idea to me.
This had impact all through the Java layer, the REST layer, the model and the test code.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21128 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Added some of the REST API for the rating service. (Work in progress)
GET ratingdefinitions url=/api/rating/schemedefinitions
GET ratings url=/api/node/{store_type}/{store_id}/{id}/ratings
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21068 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Users can't rate their own content any more.
Added a RunAs(System) so that users can rate content they don't own, which is all they can rate!
First stab at adding rating totals, means and counts - to be tidied tomorrow.
Miscellaneous improvements & doc'ing.
Tests for the above. Refactored existing tests to run as different users (all were running as admin previously).
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21013 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
The RatingService will allow users to apply ratings to content nodes in the repository.
There will be a number of built-in Rating Schemes and support to add more by the usual extension mechanism.
Out of the box, we envision a 'likes' scheme (user X likes this document) and a 'star' rating
(user X gave this document 3 out of 5 stars).
Content model for ratings.
Spring config includes two out-of-the-box rating schemes
Various basic infrastructure classes for Ratings, RatingSchemes and the service itself.
Basic CRUD for ratings in a Java foundation layer.
Associated JUnit tests.
The next contribution will add support for per-node average and total ratings and associated tests.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21000 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
