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

Visitor App Additional Feature: Bulk Signins/Admin Signins #644

Open
edwardwptc opened this issue Jan 18, 2019 · 2 comments
Open

Visitor App Additional Feature: Bulk Signins/Admin Signins #644

edwardwptc opened this issue Jan 18, 2019 · 2 comments

Comments

@edwardwptc
Copy link

Some admins would like the ability to capture user headcounts without user input.

An interim function achieving this will soon exist with "sign in by name" where an admin can simply type a name in for a particular person.

However, a more robust system for this is something that would be beneficial longer term. This is designed to allow admins to sign people up easily without their input, or to curate large groups of people for example theatre productions where you need to be able to process large volumes of people, or simply where people have tablets monitoring groups in a building i.e. headcounts.

Potential idea so far:
Login to the admin area
Have an additional section called "Bulk Signins" or some such name
Create a name for the activity (not necessarily one on the list, for example, once annual theatre productions etc)
Set a date for the activity (default to today)
Have a list called "Attendees"
Produce a list of all people signed up with alphabetical buttons along the top.
Tapping "M" brings up every registered user with a name starting with M
Tap the name
Name greyed out/visually distinct in some way registered as being "there".
Page continues to be browsable for selecting other names etc.

Anonymous Users created by the CB would be visible under whatever letter they start with - usually A.

Questions:
Could it be done in such a way as to allow multiple tablets to edit it? This isn't necessary but could be beneficial i.e. "Door open" at a theatre event. Having 2-3 staff, saying "Are you registered with us?" if so, Name, tap, done, next person, if not, anon. Limiting this process to 1 tablet would slow things down.

@astroash
Copy link
Contributor

NOTE: check above issue to cross reference previous requirements

@astroash
Copy link
Contributor

astroash commented Apr 9, 2019

Twine team Scoping

(1 = low probability; 10 = high probability) Total
Sales: Will this contribute to new users? 4
Retention: Will it improve user retention? 7
Operations: Will it improve our operational effectiveness? 3
Development: How much effort will this be to develop? 7
Total. 7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants