Changes between Version 16 and Version 17 of BadgesOld

Timestamp:

Nov 14, 2013, 8:14:48 AM (11 years ago)

Author:

brevilo

Comment:

--

BadgesOld

@@ -4 +4 @@
 
 == Note ==
-''The following represents a proposal, a basis for discussion. It's still work in progress! ''
+''The following represents a proposal, a basis for discussion. Consider it work in progress! ''
 
 == Requirements ==
@@ -10 +10 @@
 
  * Origin: badges should be assignable by projects and, eventually, in a cross-project way.
- * Numbers: the numbers of assigned badges shouldn't be constrained. The could be tens of badges per volunteer, so prepare to visualise those.
- * Assignment: assignments should support temporary (incl. renewal) and unlimited badges.
+ * Numbers: the numbers of assigned badges shouldn't be constrained. There could be tens of badges per volunteer, so prepare to visualise those.
+ * Assignment: assignments should support temporary (incl. renewal) and permanent badges.
  * Visibility: badges should be visible across the whole BOINC universe, at least in managers (desktop/mobile) and the web front-end (forums/profile), eventually even on the stats sites.
  * Types: badges should be represented by icons/images, supported by textual descriptions. There should also be the means to represent different levels of the same badge type (e.g. a "Continued Support" badge in "Bronze", "Silver" or "Gold")
@@ -32 +32 @@
  * Display
    * Forums
-     * Be sure to avoid clutter: limit number and link to full list
+     * Be sure to avoid clutter: limit number of badges displayed and link to full list
      * Make entire badge display optional via community preference
    * Support badges display as port of "user of the month" feature
-   * Show descriptive text when hovering over badge (mouse/tool-tip)
+   * Show descriptive text when hovering over badge (mouse/tool-tip), full glory as part of badge list in profile
    * Teams
      * Show team badges also in profiles of team members (somewhat separately)
+     * Should member badges be accumulated on team page as well?
    * Search (web)
      * Support user profile searches filtered by badges
@@ -86 +87 @@
 We refrained from adding another relation for tags and de-normalised this attribute in favour of performance. We could use MySQL's SET type to support a bitmap of up to 64 pre-defined tags. However, that list would become part of the data model and would hence be very inflexible. Thus we propose to use JSON as textual representation that can be searched using regular LIKE statements and can be modified easily by available JSON support, e.g. in PHP. Upcoming versions of MySQL and MariaDB are going to include JSON support and will allow more optimised processing. XML would be far too heavy-weight for this purpose.
 
-Badge assignments provide the means to expire old ones by filtering (or even removal) based on the `create_dt` attribute. Sorting of badge assignments can be done based on the `reassign_dt`, e.g. newest-first.
+Badge assignments provide the means to expire old ones by filtering (or even removal) based on the reassign_dt attribute. Sorting of badge assignments can be done based on create_dt, e.g. newest-first.
 
 === Badge assignment process ===
- * A script runs periodically (e.g. a project task) and updates all badge assignments
- * The script iterates over all defined badges (`badge` table) and executes the respective SQL rules
+ * A script runs periodically (e.g. a project task) and updates the badge assignments
+ * The script iterates over '''all''' defined badges (`badge` table) and executes the respective SQL rules
    * Each SQL rule (one per badge) returns a list if user IDs or team IDs (see next item)
-   * The attribute !badge:team defines a badge to be team or user assignable
+   * The attribute `badge:team` defines a badge to be team or user assignable
    * Upsert (insert or update) the user/team IDs for the current badge ID into the `user_badge` and `team_badge` tables respectively
      * An update (only) resets the `reassign_dt` attribute to the current time