Feature Request - Add tag(s) to LicenseHolder export and import

[stuartlynne]

We have multiple race organizers setting up to use RaceDB this season. While they will maintain their own RaceDB systems and competitions it would make sense to share LicenseHolder information.

This would reduce data entry, help keep data consistent across the systems, and allow sharing of the RFID tags.

The export and import via Excel should work. It does not contain the license holder's RFID tag(s) information.

Could we get the tag(s) data into the Excel file and support import etc.

Possibly there are other fields I have not thought of that should also be included.

Thanks!

[esitarski]

Are you also sharing bib numbers as well? Do you need those in the Excel file?

…

On Sun, Mar 10, 2024 at 5:12 AM Stuart Lynne ***@***.***> wrote: We have multiple race organizers setting up to use RaceDB this season. While they will maintain their own RaceDB systems and competitions it would make sense to share LicenseHolder information. This would reduce data entry, help keep data consistent across the systems, and allow sharing of the RFID tags. The export and import via Excel should work. It does not contain the license holder's RFID tag(s) information. Could we get the tag(s) data into the Excel file and support import etc. Possibly there are other fields I have not thought of that should also be included. Thanks! — Reply to this email directly, view it on GitHub <#60>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKNLVGWWJ75PGLUADYDYXQPXDAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TONRRGU4TMOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Edward Sitarski

[stuartlynne]

BIB numbers are usually per organizer and then per event or series. It could get somewhat confusing to try and propagate all bib numbers for all organizers. But I could see some benefit to doing so, i.e. a column for each Number Set. If you do that, it would be best to limit it to a calendar year (perhaps the last 12 months keeping Cross in mind and the Southern Hemisphere.) It might be an idea to limit the selection of number sets in competitions in the same way. Does anyone use the same number set for more than a year? I have not run any events since 2020, but from 2014 to 2020 I have over forty number sets defined. On Tue, Mar 12, 2024 at 8:57 AM Edward Sitarski ***@***.***> wrote:

…

Are you also sharing bib numbers as well? Do you need those in the Excel file? On Sun, Mar 10, 2024 at 5:12 AM Stuart Lynne ***@***.***> wrote: > We have multiple race organizers setting up to use RaceDB this season. > While they will maintain their own RaceDB systems and competitions it would > make sense to share LicenseHolder information. > > This would reduce data entry, help keep data consistent across the > systems, and allow sharing of the RFID tags. > > The export and import via Excel should work. It does not contain the > license holder's RFID tag(s) information. > > Could we get the tag(s) data into the Excel file and support import etc. > > Possibly there are other fields I have not thought of that should also be > included. > > Thanks! > > — > Reply to this email directly, view it on GitHub > <#60>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AABGXKNLVGWWJ75PGLUADYDYXQPXDAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TONRRGU4TMOI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- Edward Sitarski — Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACIUWNGTK5YL46HDVISTE3YX4QVTAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRHE4TMOJWGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

--

__________O___________ _______-\<,____________ _____(_)/_(_)___________

_________________________ ***@***.***>____604-518-1749(m)__604-461-7532(h)

[esitarski]

OK! Bib numbers need to be separate from chip tags in the import. FYI, it isn't necessary to declare a Number Set if you are issuing numbers for a one-off Competition. If you don't assign a Number Set to the competition, the bib numbers will remain local and won't be used for other competitions. On Tue, Mar 12, 2024 at 12:59 PM Stuart Lynne ***@***.***> wrote:

…

BIB numbers are usually per organizer and then per event or series. It could get somewhat confusing to try and propagate all bib numbers for all organizers. But I could see some benefit to doing so, i.e. a column for each Number Set. If you do that, it would be best to limit it to a calendar year (perhaps the last 12 months keeping Cross in mind and the Southern Hemisphere.) It might be an idea to limit the selection of number sets in competitions in the same way. Does anyone use the same number set for more than a year? I have not run any events since 2020, but from 2014 to 2020 I have over forty number sets defined. On Tue, Mar 12, 2024 at 8:57 AM Edward Sitarski ***@***.***> wrote: > Are you also sharing bib numbers as well? > Do you need those in the Excel file? > > On Sun, Mar 10, 2024 at 5:12 AM Stuart Lynne ***@***.***> > wrote: > > > We have multiple race organizers setting up to use RaceDB this season. > > While they will maintain their own RaceDB systems and competitions it > would > > make sense to share LicenseHolder information. > > > > This would reduce data entry, help keep data consistent across the > > systems, and allow sharing of the RFID tags. > > > > The export and import via Excel should work. It does not contain the > > license holder's RFID tag(s) information. > > > > Could we get the tag(s) data into the Excel file and support import etc. > > > > Possibly there are other fields I have not thought of that should also > be > > included. > > > > Thanks! > > > > — > > Reply to this email directly, view it on GitHub > > <#60>, or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AABGXKNLVGWWJ75PGLUADYDYXQPXDAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TONRRGU4TMOI> > > > . > > You are receiving this because you are subscribed to this thread.Message > > ID: ***@***.***> > > > > > -- > > Edward Sitarski > > — > Reply to this email directly, view it on GitHub > <#60 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AACIUWNGTK5YL46HDVISTE3YX4QVTAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRHE4TMOJWGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- __________O___________ _______-\<,____________ _____(_)/_(_)___________ _________________________ ***@***.***>____604-518-1749(m)__604-461-7532(h) — Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKLEHB7CQNVVI6UMFNDYX4X6HAVCNFSM6AAAAABEOZ3J3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJSGEZTGOJRHA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Edward Sitarski