mahara-contributors team mailing list archive

[Robert Lyon <1922837@xxxxxxxxxxxxxxxxxx>]

** Changed in: mahara
       Status: Fix Committed => Fix Released

-- 
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/1922837

Title:
  Create templates more efficiently on the institution and site level

Status in Mahara:
  Fix Released

Bug description:
  My story
  ==========

  As an institution admin I want to create a new template more
  efficiently that can be copied into new accounts.

  How
  ==========

  Changes are made to the collection 'Edit' screen for *institution and site portfolios only* (we already have an advanced sharing option of 'Copy to new members' that is only available on these two levels and thus might be used to tap into):
  * Add a switch 'Template' to the collection 'Add' screen. This is needed because it can't be guaranteed that the template is only created to be an auto-copied one.
    * If the switch on the collection is set to 'Yes' and the screen is saved, grey out all 'Template' switches on pages that are included in the collection or will be added in the future (and display 'Yes' in the greyed out state) so that it can inherit the settings. *Side note*: When a page is removed from the collection, it stays a template, but it's not auto-copied because the auto-copying functionality sits on the collection side of things.
    * If the switch on the collection is set to 'Yes' and the screen is saved, automatically turn 'Prevent removing of blocks' on because the placeholder blocks signal to pharmacists what the recertification requirements are and they should not be removed. However, it is still possible to reset this for individual pages by the admin or later pharmacists and thus doesn't become a locked template setting like the instructions, i.e. this switch is not greyed out.
    * If the 'Template' switch is set to 'No' on the collection again, upon saving, the individual 'Template' switches on the pages can be set separately (typical behaviour in Mahara for hierarchies). There is not going to be a change to the 'Prevent removing of blocks' switches.
    * If the 'Template' switch on the collection is set back to 'Yes', all 'Template' switches on the pages are greyed out again (see above) and the 'Prevent removing of blocks' switch is set to 'Yes' but not greyed out.
  * Add a switch for 'Current auto-copied template'. 
    * When ticked and the collection is saved, i.e. click the 'Next: Add pages' button, the previously auto-copied template in the institution has its status reset to 'No'. The switch can be put back to 'No' if no institution portfolio should be auto-copied so that there are no auto-copied templates in an institution or on the site level.
    * Since this is a destructive option, have modal that tells of the consequences, e.g. the only active template, name of the old template that is set to be inactive, auto-copying, old template gets sharing permissions dropped.
    * When the switch is flipped back to 'No', also bring up a modal that tells of the consequences, i.e. no template will be copied automatically.
  * Sharing when 'Current auto-copied template' is set to 'Yes':
    * Automatically share the portfolio with the institution, make it copyable, and use it as portfolio that is copied automatically into new accounts henceforth.
    * Automatically remove the sharing permissions for the old portfolio that is not considered institution template any more.

  When this portfolio template is copied, keep the collection title and prefix it with the display name. That way, the name is seen more easily than in the secondary information. Yes, it doubles up, but keeps it clear.
    * The name prefix is to be done only on portfolios marked as 'Template'. The portfolio authors can still change the collection title to something else once it's in their account.
    * Only prefix the collection title, not a every page. Page titles stay as they are.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1922837/+subscriptions