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

As a magstock registration admin, I would like to pre-assign sites to attandees before getting on-site #58

Closed
bds002 opened this issue May 12, 2016 · 5 comments

Comments

@bds002
Copy link
Contributor

bds002 commented May 12, 2016

When onsite @ Stock there is a manual process of look at the available sites and assigning attendee groups to the site, based on available sites and number of attendees in each Tent group / number of tents etc.

--The camp ground has an interactive map at : https://www.sunrisereservations.com/reservation/selectSiteCriteria?cgId=411

--That list all the sites, we also have a papercopy of all available sites under the MAGStock name.

-- There is an Admin-only field on the Attendee registration page that says: "Site Number" that is used on site plug in the information. This is the field I would like to fill in before event as much as possible.
@migetman9 has the drop down list I believe for this purpose.

@binary1230
Copy link
Contributor

quick thing: when making these issues, it's helpful if an issue is easily distinguishable as something broken vs something that is new functionality.

To that end, for feature requests like this one, it's helpful if we follow the user story format like: "As a STOPs admin, I would like to pre-assign sites to attandees before getting on-site". It's also helpful if (as you did here) you describe why this is an important thing and what problem it will solve.

There's a huge amount of stuff we could add in regarding campsites, maps, attendees, and it's helpful for our code team to have as much context as possible when prioritizing what gets done and what won't be able to get done, and also in figuring out which issues are ready to be coded vs issues that need more design or thought put into them.

@binary1230 binary1230 changed the title Pre-assign sites to attandees. As a magstock registration admin, I would like to pre-assign sites to attandees before getting on-site May 12, 2016
@kitsuta
Copy link
Member

kitsuta commented May 12, 2016

Yeah, I have to say that I don't understand the coding change you want
here. You should be able to go to attendees right now and fill in their
sites.

On Thu, May 12, 2016, 20:18 Dominic Cerquetti notifications@github.com
wrote:

quick thing: when making these issues, it's helpful if an issue is easily
distinguishable as something broken vs something that is new functionality.

To that end, for feature requests like this one, it's helpful if we follow
the user story format like: "As a STOPs admin, I would like to pre-assign
sites to attandees before getting on-site". It's also helpful if (as you
did here) you describe why this is an important thing and what problem it
will solve.

There's a huge amount of stuff we could add in regarding campsites, maps,
attendees, and it's helpful for our code team to have as much context as
possible when prioritizing what gets done and what won't be able to get
done, and also in figuring out which issues are ready to be coded vs issues
that need more design or thought put into them.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#58 (comment)

@bds002
Copy link
Contributor Author

bds002 commented May 12, 2016

I want Uber to be able to tell me:

  • How many people are assigned to each site and how many more we can put in there.
    Currently there is no link that I am aware to show who's assigned to what site....

I see this along the lines of the Hotel plug in, but a little different.
@EliAndrewC is somewhat aware based on how things have been done onsite in the past.

@kitsuta
Copy link
Member

kitsuta commented Jun 6, 2016

OK, after further discussion with @bds002 I've found out that the change needed is that we need a dropdown for the "camping site" field, populated via config as a list of the camp's sites. Admins should also be able to easily find people based on who they entered as their tent leader/coming with group.

kitsuta added a commit that referenced this issue Jun 16, 2016
This is the most basic fix for #58. It requires running a DB migration. It simply converts the site_number field to a dropdown, and adds all the sites in via development-defaults.ini.
kitsuta added a commit that referenced this issue Jun 16, 2016
This is the most basic fix for #58. It requires running a DB migration. It simply converts the site_number field to a dropdown, and adds all the sites in via development-defaults.ini.
kitsuta added a commit that referenced this issue Jun 16, 2016
* Add Magstock-specific fields to ATD admin workflow
Requires magfest/ubersystem#1866. Fixes #84.

* Use dropdown for site numbers for consistency (#89)

This is the most basic fix for #58. It requires running a DB migration. It simply converts the site_number field to a dropdown, and adds all the sites in via development-defaults.ini.

* Change check-in food text for clarity
The text now tells volunteers to give someone a food wristband rather than "True"
@kitsuta
Copy link
Member

kitsuta commented Jun 16, 2016

Fixed by #89. See #71 for the rest of this issue.

@kitsuta kitsuta closed this as completed Jun 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants