Scope and Use case based Routing and Redirection (SURR)
Opened this issue · 2 comments
japsu commented
First path component in URLs should be a Scope that can be either an Event or an Organization
This would allow eg. implementing Surveys for Events and Organizations without duplicating code.
It would also allow for cleaner URLs:
https://kompassi.eu/SCOPE/…
https://kompassi.eu/tracon2024/surveys/expense-claim
https://kompassi.eu/tracon-ry/surveys/expense-claim
And in the future, if we implement UseCase or similar under Scope, this could further be simplified into
https://kompassi.eu/SCOPE/USE-CASE/…
https://kompassi.eu/tracon2024/expense-claim
https://kompassi.eu/tracon-ry/expense-claim
japsu commented
What is Scope called in the UI? Scope is too technical and has no good Finnish translation. It may be we need to use different translations for different use cases. For example, in the profile responses view:
- Event or organization (tapahtuma tai yhdistys): Accurate but too long.
- Recipient (vastaanottaja): As the respondent, I fill in a form and then send it to a recipient. However, this clashes with a field ”Recipient” on the expense claim form.
- Related to: Flexible but no good Finnish translation.
- No column header: The user will organically discover it contains events and organizations.