Is your feature request related to a problem? Please describe.
The GURU3 phonebook is used as the main place to find people's numbers at events, but some numbers are not created through the system and so they can't be made discoverable. My specific use-case is to add our assembly's payphone and stationary phones, which are connected to the EWSD, to GURU3 so people can contact us.
Describe the solution you'd like
Some way to register such "externally managed" numbers in the phonebook. Could be implemented as a new extension type in the dropdown with no options other than number, name, location.
What kind of constraints (if any) would be put on the numbers would need some discussion. It might be useful to make it a per-event configurable pattern (e.g. at 39C3 you can only register the EWSD 91xxxx pattern).
Describe alternatives you've considered
Someone could set up an independent phone book for events where multiple number registries exist, which could automatically pull from GURU3 as well as allow externally-managed number registration. This would probably be even more flexible, but at the cost of discoverability. Everyone looks for numbers in GURU3, so getting people to switch would take a lot of time and "marketing".
Additional context
I'm opening this as a FR so I don't forget. Happy to discuss options or help implement whatever ends up being "chosen" at a more reasonable time of year.
Y'all enjoy yourselves, happy new year and thanks for keeping us all connected at 39c3!
Is your feature request related to a problem? Please describe.
The GURU3 phonebook is used as the main place to find people's numbers at events, but some numbers are not created through the system and so they can't be made discoverable. My specific use-case is to add our assembly's payphone and stationary phones, which are connected to the EWSD, to GURU3 so people can contact us.
Describe the solution you'd like
Some way to register such "externally managed" numbers in the phonebook. Could be implemented as a new extension type in the dropdown with no options other than number, name, location.
What kind of constraints (if any) would be put on the numbers would need some discussion. It might be useful to make it a per-event configurable pattern (e.g. at 39C3 you can only register the EWSD 91xxxx pattern).
Describe alternatives you've considered
Someone could set up an independent phone book for events where multiple number registries exist, which could automatically pull from GURU3 as well as allow externally-managed number registration. This would probably be even more flexible, but at the cost of discoverability. Everyone looks for numbers in GURU3, so getting people to switch would take a lot of time and "marketing".
Additional context
I'm opening this as a FR so I don't forget. Happy to discuss options or help implement whatever ends up being "chosen" at a more reasonable time of year.
Y'all enjoy yourselves, happy new year and thanks for keeping us all connected at 39c3!