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

Campaign | Posters: Requirements for posters #539

Open
JuliaFreitagBGSt opened this issue Jan 16, 2025 · 5 comments
Open

Campaign | Posters: Requirements for posters #539

JuliaFreitagBGSt opened this issue Jan 16, 2025 · 5 comments
Labels
BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:User Story Issue type User Story

Comments

@JuliaFreitagBGSt
Copy link

Is your feature request related to a problem? Please describe.
There are requirements from the city regarding how posters must be displayed (spacing/number/prohibitions). If this could be entered as static text in the “Posters” section of the KV, it would be great. So far, we have given it to the members as a note. But if it could be read in the app, it would help. For large KVs, it should be possible to enter the permits for different cities.

Describe the solution you'd like
Because there are so many different requirements we are not able to provide this information in the app for the users. But maybe we could implement an upload field for this for each KV, so that the members (or a designated person) themselves can enter or deposit the requirements known to them.

Describe alternatives you've considered
Alternatively, we could build this function into the atlas so that the coordinators enter this information there and it is displayed in the app (via an info field or similar)

@JuliaFreitagBGSt JuliaFreitagBGSt added BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:User Story Issue type User Story labels Jan 16, 2025
@Stift
Copy link
Contributor

Stift commented Jan 16, 2025

I assume it's much more complicated than just a simple info. In larger KV (in rural areas) each smaller area (city or village) may have some own rules, which make it hard to communicate a specific regulation. Also the information is depending on your location and not your assignment to a specific division.
Normally the rules are communicated during an introduction offline.

But I try to make a suggestion how we could accomplish this:

  1. we could have a list of KV/OV areas and let the KV/OV set a specific description and maybe a link to a summary, so that on the ground when setting a marker the rules are displayed according to the marker's location.
  2. In the Cockpit the campaign manager can define fenced areas + some text to show similarly as the above.

@JuliaFreitagBGSt
Copy link
Author

I wouldn't see it as that complex or define it so strongly.

Only the KVs, who know their special requirements, should be given the opportunity to disseminate the requirements independently via the app. This could perhaps be done by uploading a file to the Grüne Wolke (with a link in the app) or an info box that can be loaded via the atlas. It is not necessary for the requirements to appear specifically on the map or to be broken down into individual areas.

I don't want us or you to have to search for and enter any requirements. The KVs should be able to do this themselves or not at all.

@nscharioth
Copy link

nscharioth commented Jan 17, 2025

This issue needs a corresponding issue in gruene-netz-admin to describe - ideally with a wireframe - how the information would be imputed by the local role (Lokalkoordinatorin) in the Grüne Atlas. We also need an API issue.

@JuliaFreitagBGSt
Copy link
Author

This issue needs a corresponding issue in gruene-netz-admin to describe - ideally with a wireframe - how the information would be imputed by the local role (Lokalkoordinatorin) in the Grüne Atlas. We also need an API issue.

Done! See #60 (admin) and #137 (api)

@nscharioth
Copy link

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:User Story Issue type User Story
Projects
None yet
Development

No branches or pull requests

3 participants