Allow group vocabulary customization

Created on 10 December 2024, 3 months ago

Problem/Motivation

It looks as if the GROUP_VOCABULARY constant is only being utilized in the LocalistManager. We could allow this to be modified, providing a taxonomy drop down to select an existing one, defaulting to localist_groups.

Steps to reproduce

  • Create a new taxonomy like `event_groups`.
  • Attempt to set up localist, seeing that it complains about `localist_groups` not existing as a taxonomy.

Proposed resolution

  • Move this constant into config, allowing the user to specify a taxonomy

Remaining tasks

  • Create config item for setting the group taxonomy, defaulting to `localist_groups` if it exists
  • Create an accessor for retrieving this easily from the LocalistManager
  • Replace references to the constant with this accessor
  • Remove constant
  • Update checks to use this to determine readiness
  • Add disclaimer to make proper modifications in the custom migration

User interface changes

  • Adding a new editable config item: `localist_groups_taxonomy`

API changes

Data model changes

  • Add new config for `localist_groups_taxonomy`

Motivation for change

For our proof of concept site, we already have an established name for the groups, which we'd like to re-use. It looks as if we can properly use it via custom migration, but the checks make it seem like it's not configured correctly. I can also see this being a motivation for changing the field name looked at as well in the future. (Maybe another issue ticket?)

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States dblanken Carmel, Indiana

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024