search

quicko-software / clubmanager

The TYPO3 module for managing clubs, foundations and associations. With Clubmanager, you get the tool to manage the organization AND public relations of your club or association in a cost-saving and effective way.
0 stars 1 forks source link

Question about the difference between members and locations #9

Open mediaessenz opened 1 year ago

mediaessenz commented 1 year ago

After playing a bit arround with the provided basic module, I came to the conclution that it is nearly useless.

Why e.g. is the member detail page connected via the location assigned to a member?

What is the function of this location at all, since all address datas already included in the member model?

If it is the location of the club, why is it only possible to assign one location per member? This makes no sense.

Or is just the manual unclear or uncomplete?

Btw.: I created a fork with several TYPO3 12 adjustments. Maybe there is something interesting for you: https://github.com/mediaessenz/clubmanager/

WirkWerk commented 1 year ago

First of all, thank you for your feedback.

We have chosen the data model to ensure the greatest possible flexibility. The data of a member record is mainly intended as internal administrative data. It should be possible to display them in the frontend, as this makes sense in some cases, e.g. to offer a complete member list in a login area. Basically, however, this is the administrative data necessary for a club.

The locations assigned to a member, on the other hand, are intended for publication in an online directory. So with the clubmanager we create the possibility that administrative data and data to be published can differ from each other. In many cases the data is identical, but not always, hence this data model.

Furthermore, our data model provides that each member can have "only" one main-location, but many more sub-locations. Have you overlooked the button for the sub-locations? The presentation in the frontend is freely selectable via fluid templates. So it is not mandatory to make a difference between main- and sub-location, but possible.

In principle, you have to look at the club's requirements in advance and decide how you want to use the clubmanager. For example, a small club will not need an online directory of its members. The management level via the member records is then sufficient. However, this becomes exciting for larger associations that want to offer their members an online directory for their locations. Especially with the seamless interlocking modules Clubmanager Pro, Billing, Zip-Search etc.

I will describe the data model in more detail in the manual. Thanks also for the tip on this!

mediaessenz commented 1 year ago

Are the main_location and sub_locations the locations of the member or the club?

WirkWerk commented 1 year ago

Each member can have multiple locations. If the Clubmanager is used by a professional association, for example, it is of course possible that the members themselves are clubs (see field person_type).

If you want to manage the departments of the "home club" as well as the member locations with the club manager, you can make sortings via the member categories (see tab Categories) and then display them in different places in the frontend. For example, you create a separate member record for the "home club", which is the only one that gets the category "homeclub". This way you can organize its departments in the Locations tab and output them at any place in the frontend.

mediaessenz commented 1 year ago

Is there a visual overview (UML or similar), which shows the structur behind this idea?

I'm currenty building up a website for a small association (about 200 active members, all in one location), and try to find a solution to manage there members in the backend or frontend. Basically I need a filterable list of all members of this only one club and a detail view of a single member showing its full address, bank accounts etc.

Do you think clubmanager is the right tool for it, or is it more "using a sledge-hammer to crack a nut"?

WirkWerk commented 1 year ago

No, there is no visualization so far. :-(

Unfortunately, I can't really imagine your case of need. Do all members have the same address? Do you want to be able to assign the same location to the members? We currently only offer sorting functions for the location records in the frontend, because they are basically intended for publication in our model. However, you can also access data from the member record in the list and single view of the locations and display it via fluid in the frontend (account data, etc.).

What sorting functions do you need in the frontend?