Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register locos and adresses for a meeting #7

Open
fjallemark opened this issue Jul 13, 2023 · 0 comments
Open

Register locos and adresses for a meeting #7

fjallemark opened this issue Jul 13, 2023 · 0 comments
Labels
blazor Issue regarding blazor database Issue regarding databases enhancement New feature or request

Comments

@fjallemark
Copy link
Member

In order to prepare for a meeting, users should be able to register locos with the following data:

  • Address (mandatory)
  • Operator signature (selected from the operators list?)
  • Class (type of loco)
  • Vehicle number, for modern locos the EVN number.

Vehicle data will be saved for loco registration at a later meeting.

Address reservation can be made in two ways:

  • FREMO reserved adresses will be reserved to the user registering for a meeting layout.
  • Per meeting layout address reservation.

When an address conflict occurs, FREMO reserved addresses wins over per meeting reservations, and secondly first user reserving an address wins over others trying reserving same address. If a per meeting address is reseved before a FREMO member claims that address, the address will be transferred to the FREMO member.

@fjallemark fjallemark added database Issue regarding databases enhancement New feature or request blazor Issue regarding blazor labels Jul 13, 2023
@fjallemark fjallemark transferred this issue from tellurianinteractive/Tellurian.Trains.ModulesRegistryApp Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blazor Issue regarding blazor database Issue regarding databases enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant