Feedback and discussion options

[twagoo]

The component browser can be extended with methods for (logged in) users to provide ratings and comments for arbitrary components. This makes it easier to discuss public or shared (see #143) components and helps users to decide whether to use existing components and profiles and if so, which.

Rating can be done on a 5-point scale. Comments will form a thread or hierarchical set of threads that become available for a component.

[twagoo]

We have decided on the following (for now):

0. no ratings, only comments
1. linear comments, that is sorted by date (optionally reversed client side...) but not threaded
2. comments on profiles and components alike
3. REST calls for GETting and POSTing comments on a component/profile id:
   • GET ../rest/registry/profiles/{profId}/comments gives a listing of comments on that profile (just id's and titles)
   • GET ../rest/registry/profiles/{profId}/comments/{commentId} will return the specified comment
   • POST ../rest/registry/profiles/{profId}/comments will post a comment on that profile (only registered users)
   • DELETE ../rest/registry/profiles/{profId}/comments/{commentId} will delete the specified comment (admins only)
   • ...and likewise for /components/{comId}
4. In the Flex interface, there can be a tab next to View/XML that shows (loads) the actual comments. As a header, it could have 'Comments (x)' where x is the number of comments (to be inferred from the listing). Once it is selected, the actual comments can be loaded.

[twagoo]

The comments should be stored in the database (one table with reference to user id and profile/component should suffice)

[twagoo]

Comments will be ComponentRegistry-1.11

[twagoo]

User name is taken from Shib common name rather than taking the user's specified name from the DB (see #156)

[twagoo]

Replying to twagoo:

User name is taken from Shib common name rather than taking the user's specified name from the DB (see #156)

Fixed in r1836