mahara-contributors team mailing list archive

[Russell Boyatt <1881868@xxxxxxxxxxxxxxxxxx>]

Discussed at Mahara developer meeting #80 on 22nd July 2020.  The issue
of existing fields was discussed:

If fields are not used, should they be converted to custom fields?  We
agreed they could be removed.  These fields would also not be added in
new installs.

Should custom fields have different types?  Do we want to retain a fixed
drop-down list for these fields (seen as part of the original motivation
to address).  We agreed these should be moved to free text fields.

For custom fields where data is in place, should an administrator be
able to remove?  Agreement that it should be possible but the
administrator should be given a clear indication for the number of users
who have already used this field.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1881868

Title:
  Add support for custom fields to resume

Status in Mahara:
  In Progress

Bug description:
  The resume currently has a number of fields covering personal
  information, employment history, education history and certifications.
  The fields are fixed in terms of their name and, in some cases, the
  options available.

  To give more flexibility with the resume, add support for custom
  fields.  This is with the aim of being able to remove some of the
  hard-coded fields, e.g. gender, martial status, visa status, but
  retain them where required (or already used) as custom fields.

  Using an interface in the admin section it would be possible to be
  customise resume fields to the particular requirements of the
  institution.

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