Public bug reported:
Part of the outcomes portfolio blueprint:
https://blueprints.launchpad.net/mahara/+spec/outcomes-portfolio
# Outcomes portfolio setting and database tables
## High level overview
* Create the 'Outcomes portfolio' option as institution setting so that it can
be available for groups created in that institution
* Create database tables for outcome types and subjects to record necessary
details such as short names and colour code classes where appropriate.
> The colours are defined via classes in the stylesheet in the code, not
on the interface.
## Details
1. Create the 'Outcomes portfolio' option in the institution settings with
rules as for portfolio completion and SmartEvidence, i.e. if somebody is in
multiple institutions, they see it if at least one of their institutions has it
turned on.
* It can be used in conjunction with portfolio completion and SmartEvidence.
* It has characteristics of the portfolio completion page (rather than
SmartEvidence), i.e. it should be possible in the future to add further blocks
to that special first page.
* It will be the very first page if portfolio completion and / or
SmartEvidence are selected as well.
* Initially, it is only available on the group level (group owned
collections), but be open to future plans to have it available on personal,
institution, and site level as well
* Add a new field 'outcomes' into the collection table
2. New database tables for 'Outcome category' (lang string 'Outcome category')
and 'Outcome subject' (lang string 'Subject'). These are hard-coded / inserted
into the DB for each institution. It is not possible (at this stage) to add or
change them via the admin interface. The key value should be a number. The
category is created to future proof the functionality for when different
outcome portfolios are created that require different outcome types either
within one institution or across different institutions.
* 1 table for outcome categories (outcome_category): ID, outcome category
title [up to 100 characters], institution ID; e.g. here the category would be
'Foundation' (in the future, this could be displayed in the admin interface,
but currently is out of scope)
* 1 table for outcome types (outcome_type): ID, outcome category ID as
foreign key, title of the outcome type [up to 100 characters], abbreviation of
the outcome type [up to 10 characters], outcome type background colour which
refers to a class that is saved in here and defined in SCSS as a colour
(background and border) in ``theme/raw/sass/components/_outcomes.scss`` where
we will keep all the outcomes classes.
* 1 table for subject categories: ID, subject category name [up to 100
characters], institution ID, e.g. here the category would be 'Subject' (in the
future, this could be displayed in the admin interface, but currently is out of
scope)
* 1 table for subjects: ID, subject category ID as foreign key, title of
the subject [up to 100 characters], abbreviation of the subject [up to 10
characters]
** Affects: mahara
Importance: Wishlist
Status: Confirmed
** Tags: outcomes
** Description changed:
+ Part of the outcomes portfolio blueprint:
+ https://blueprints.launchpad.net/mahara/+spec/outcomes-portfolio
+
# Outcomes portfolio setting and database tables
## High level overview
* Create the 'Outcomes portfolio' option as institution setting so that it
can be available for groups created in that institution
* Create database tables for outcome types and subjects to record necessary
details such as short names and colour code classes where appropriate.
> The colours are defined via classes in the stylesheet in the code, not
on the interface.
## Details
1. Create the 'Outcomes portfolio' option in the institution settings with
rules as for portfolio completion and SmartEvidence, i.e. if somebody is in
multiple institutions, they see it if at least one of their institutions has it
turned on.
- * It can be used in conjunction with portfolio completion and
SmartEvidence.
- * It has characteristics of the portfolio completion page (rather than
SmartEvidence), i.e. it should be possible in the future to add further blocks
to that special first page.
- * It will be the very first page if portfolio completion and / or
SmartEvidence are selected as well.
- * Initially, it is only available on the group level (group owned
collections), but be open to future plans to have it available on personal,
institution, and site level as well
- * Add a new field 'outcomes' into the collection table
+ * It can be used in conjunction with portfolio completion and
SmartEvidence.
+ * It has characteristics of the portfolio completion page (rather than
SmartEvidence), i.e. it should be possible in the future to add further blocks
to that special first page.
+ * It will be the very first page if portfolio completion and / or
SmartEvidence are selected as well.
+ * Initially, it is only available on the group level (group owned
collections), but be open to future plans to have it available on personal,
institution, and site level as well
+ * Add a new field 'outcomes' into the collection table
2. New database tables for 'Outcome category' (lang string 'Outcome
category') and 'Outcome subject' (lang string 'Subject'). These are hard-coded
/ inserted into the DB for each institution. It is not possible (at this stage)
to add or change them via the admin interface. The key value should be a
number. The category is created to future proof the functionality for when
different outcome portfolios are created that require different outcome types
either within one institution or across different institutions.
- * 1 table for outcome categories (outcome_category): ID, outcome category
title [up to 100 characters], institution ID; e.g. here the category would be
'Foundation' (in the future, this could be displayed in the admin interface,
but currently is out of scope)
- * 1 table for outcome types (outcome_type): ID, outcome category ID as
foreign key, title of the outcome type [up to 100 characters], abbreviation of
the outcome type [up to 10 characters], outcome type background colour which
refers to a class that is saved in here and defined in SCSS as a colour
(background and border) in ``theme/raw/sass/components/_outcomes.scss`` where
we will keep all the outcomes classes.
- * 1 table for subject categories: ID, subject category name [up to 100
characters], institution ID, e.g. here the category would be 'Subject' (in the
future, this could be displayed in the admin interface, but currently is out of
scope)
- * 1 table for subjects: ID, subject category ID as foreign key, title of
the subject [up to 100 characters], abbreviation of the subject [up to 10
characters]
+ * 1 table for outcome categories (outcome_category): ID, outcome category
title [up to 100 characters], institution ID; e.g. here the category would be
'Foundation' (in the future, this could be displayed in the admin interface,
but currently is out of scope)
+ * 1 table for outcome types (outcome_type): ID, outcome category ID as
foreign key, title of the outcome type [up to 100 characters], abbreviation of
the outcome type [up to 10 characters], outcome type background colour which
refers to a class that is saved in here and defined in SCSS as a colour
(background and border) in ``theme/raw/sass/components/_outcomes.scss`` where
we will keep all the outcomes classes.
+ * 1 table for subject categories: ID, subject category name [up to 100
characters], institution ID, e.g. here the category would be 'Subject' (in the
future, this could be displayed in the admin interface, but currently is out of
scope)
+ * 1 table for subjects: ID, subject category ID as foreign key, title of
the subject [up to 100 characters], abbreviation of the subject [up to 10
characters]
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1991601
Title:
Outcomes portfolio (1): Setting and database tables
Status in Mahara:
Confirmed
Bug description:
Part of the outcomes portfolio blueprint:
https://blueprints.launchpad.net/mahara/+spec/outcomes-portfolio
# Outcomes portfolio setting and database tables
## High level overview
* Create the 'Outcomes portfolio' option as institution setting so that it
can be available for groups created in that institution
* Create database tables for outcome types and subjects to record necessary
details such as short names and colour code classes where appropriate.
> The colours are defined via classes in the stylesheet in the code,
not on the interface.
## Details
1. Create the 'Outcomes portfolio' option in the institution settings with
rules as for portfolio completion and SmartEvidence, i.e. if somebody is in
multiple institutions, they see it if at least one of their institutions has it
turned on.
* It can be used in conjunction with portfolio completion and
SmartEvidence.
* It has characteristics of the portfolio completion page (rather than
SmartEvidence), i.e. it should be possible in the future to add further blocks
to that special first page.
* It will be the very first page if portfolio completion and / or
SmartEvidence are selected as well.
* Initially, it is only available on the group level (group owned
collections), but be open to future plans to have it available on personal,
institution, and site level as well
* Add a new field 'outcomes' into the collection table
2. New database tables for 'Outcome category' (lang string 'Outcome
category') and 'Outcome subject' (lang string 'Subject'). These are hard-coded
/ inserted into the DB for each institution. It is not possible (at this stage)
to add or change them via the admin interface. The key value should be a
number. The category is created to future proof the functionality for when
different outcome portfolios are created that require different outcome types
either within one institution or across different institutions.
* 1 table for outcome categories (outcome_category): ID, outcome category
title [up to 100 characters], institution ID; e.g. here the category would be
'Foundation' (in the future, this could be displayed in the admin interface,
but currently is out of scope)
* 1 table for outcome types (outcome_type): ID, outcome category ID as
foreign key, title of the outcome type [up to 100 characters], abbreviation of
the outcome type [up to 10 characters], outcome type background colour which
refers to a class that is saved in here and defined in SCSS as a colour
(background and border) in ``theme/raw/sass/components/_outcomes.scss`` where
we will keep all the outcomes classes.
* 1 table for subject categories: ID, subject category name [up to 100
characters], institution ID, e.g. here the category would be 'Subject' (in the
future, this could be displayed in the admin interface, but currently is out of
scope)
* 1 table for subjects: ID, subject category ID as foreign key, title of
the subject [up to 100 characters], abbreviation of the subject [up to 10
characters]
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1991601/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
