amy
amy copied to clipboard
carpentries
Allow admin user to edit membership variants
The current member form allows these variants:
Can we have this list of variants be edited from the admin console?
@maneesha: yes, it's possible, but it requires adding a relationship.
Thanks @pbanaszkiewicz That would be useful for us so we can adjust membership categories depending on our programming.
@Talishask Asking you for now, and maybe you want to take this back to Elizabeth.
The current membership options for a site include Partner, Affiliate, Sponsor, etc., so they don't exactly match our membership models. We can have @pbanaszkiewicz change them if we want them to be some other categories. We can also have him set things up so we can change these categories ourselves as needed (which would be more time consuming for him). Do you see these changes as priorities?
Which of the following applies to when you want to see this fixed?
- Would like to see this fixed as soon as possible, in the next 1-2 development cycles (i.e., by September 2019)
- Would like to see this fixed later (by the end of 2019)
- Would like to see this fixed, but possibly as part of a larger project that needs more planning
- Not sure
- No longer relevant - OK to close
3 - Not by the end of the year, but this could be a part of a larger project to move the membership database into AMY. Our current membership options are available for us to use so that moves this out of a priority update to a 'would be nice' update. We are currently developing a sponsorship model and have on the list for the near future to evaluate our membership models. So eventually we may need to update these options but I don't forsee that happening until sometime next year at the earliest. At that time it should be okay to just change the labels, we shouldn't need to have the ability to change them ourselves as needed.
Revisiting this @pbanaszkiewicz We have had a few use cases in the past year where we would want to define membership levels ourselves.
Closing this because it is easier to update the choices in the codebase than to create a new interface. Keeping it in the codebase also ensures that all instances of AMY use the same variants.