unitedworldwrestling / arena-public

14 stars 5 forks source link

Adding athlets' date of birth into Arena #110

Open theswix opened 1 year ago

theswix commented 1 year ago

In which application you miss a feature Arena 1.5.84.1

Is your feature request related to a problem? Please describe. Sometimes it is really hard to tell apart athletes from the same weight class AND region, AND with same first/last/patronimic - it does happen pretty often in competitions where there are lots of participants in highly populated areas with some ethnic background (e.g. Muslim in Russian North Caucasus where they share identical names very often)... Adding the date of birth in the supported locale format to .xlsx/.ods import file and Arena subsequently would really ease the dealing with such a problem. I suggest to make it optional for printing via checkbox so that when there is no clear need for that we do not put extra rubbish info onto the page in the entry list and, believe me, people who really need it will happily live with a bit condensed printing output. :)

Describe the solution you'd like Add D.O.B. to current entry list and make its including into printing optional. By default - not to print D.O.B.

Describe alternatives you've considered None so far :(

Additional context

csabavirag commented 1 year ago

Have you thought about using the Custom ID field for your athletes? That could uniquely identify them if eg. a national registration number is used. It might be on your wrestling accreditation card as well.

At the moment Entry list only shows AthenaID, but it can be easily extended to show the Custom ID if that's defined. This way you can even link your Arena with an external system(s) (via API) and making a link between your 3rd party app and Arena via the Person's CustomID attribute.

Using a Custom ID is strongly recommended in case if you use your Arena for multiple events (if you do not reset/reinstall your Arena between events) anyway, because if there is a person with a Custom ID in Arena, no new Person record will be created at every further import, but the existing one is re-used. Thus no duplications will be for the same person.