search

dancerfly / django-brambling

Event website manager, specifically designed for dance weekends or other events with multiple simultaneous tracks of classes.
BSD 3-Clause "New" or "Revised" License
11 stars 3 forks source link

Consider removing transfer feature #931

Open melinath opened 5 years ago

melinath commented 5 years ago

The transfer feature was not added based on a pressing business need; rather, it was thought that it might serve as a differentiator between Dancerfly and other event services. From a business perspective, the purpose of the feature is to reduce the administrative overhead of transfers for organizers by automating the process.

Currently, less than 1.5% of transactions are transfers, and there are several open bugs related to transfers because the implementation was haphazard.

This leads to a couple of questions:

  1. Does the existing transfer process actually reduce administrative overhead significantly?
  2. How often do users attempt to transfer items and fail? (Perhaps there is high interest but the UI is prohibitively difficult.)

If the reduction to administrative overhead is only small and there isn't a large group of users attempting to transfer items and failing, we should remove the feature and re-implement it later at a time when the data shows it is needed.

harrislapiroff commented 5 years ago

This might be a good question for a Dancerfly organizer survey/interviews