huevosabio / firmas Goto Github PK

Requirements

• The form should have all the required fields, it should be able to call the phone's camera, send those pictures along with the form data, and it should send the geolocation of the capture.

Other Requirements

• if the post fails, it should explicitly say so.
• The form should have strict validation code. Electoral IDs are a certain length, other fields might also have patterns that can be enforced.
• It is very important to have the correct entries in the system, this is the base of the counting process which guides the strategy. Wrong entries are costly not only in the lost signature, but the erroneous information it provides to decision makers.

Useful Links

Requirements:

• I am an existing user, I click on log in with Facebook
• I am a recently invited user, I sign up with Facebook

Other requirements:

• Uninvited users should not be able to log in (we want to avoid fake users clogging the system)
• The sign up process should also send to the backend a pointer to who was the referee.

Potentially useful links:

• http://stackoverflow.com/questions/28252862/manage-invite-codes-for-registration-with-firebase

Requirements

• This is a security requirement. We want to keep electoral information visible ONLY to the people that gathered it and to the few admins.

Other Requirements

Useful Links

Requirements

• Admins and Users should have a little tab that shows the overall state of affairs.
• This should be in displayed in fractions {sections_covered}/{min_sections_req} and {number_of_signatures/signatures_required}
• Additionally, a breakdown of information should be provided in the form of maps for the sections. How many signatures are left for each section?

Other Requirements

• This will probably need storing the GeoJSON files statically in Firebase.

Useful Links

• http://huevosabio.com/plotting-the-task-of-postulating-as-an-independent-candidate-in-juarez.html
• http://leafletjs.com/
• https://github.com/tombatossals/angular-leaflet-directive

Requirements

• The formal submission is in the form of an official document with the list of all the signatures, their personal information, the signatures in ink, and attached the pictures in the same order.
• An potentially good assumption is that the order in those forms will be in the same as the timestamp of the entries in the DB.

Other Requirements

• It is possible that the timestamp will not be perfect match for the forms, or that one person will not be able to print pictures for everyone, so the service should be able to provide the pictures given an order of IFE card_ids

Useful links

Requirements

• The official submission is a long form with the voter information and the ink signatures in it and attached the corresponding, two-sided pictures of the electoral card. The voter should be able to print this form at all times.
• The forms should have a unique identifier somewhere in the page. This identifier should be a field in the form submitted by the application.

Other Requirements

Useful Links

Requirements

• Mexico has until now 4 types of electoral cards, they each have a manual way to check whether they are valid for the upcoming election. There is also a way online to find whether a specific card is valid, but it is under a CAPTCHA protectibon. The idea of this ticket is to by pass the CAPTHA site and find out whether any specific card is valid.

Other Requirements.

Useful Links

• http://listanominal.ife.org.mx/

Requirements

• Admins should be able, with the click of a button, to invite other people.
• This should be a one-time token.
• Invite button can be via WhatsApp or by phone messaging.

Other Requirements

Useful Links

Requirements

• An admin should see the list of all users, it should be able to upgrade/downgrade users to admin/non-admin.

Other Requirements

• There should be locks on avoiding this to be too easily done (popup: do you really want to do this?)

Useful Links

Requirements

• We would like to provide real-time orientation to the teams. Thus, they should be able to see where their peers are at any given time (or their last location)
• This should be overlaid, with markers, on top of the visualization maps of #4.

Other Requirements

• On click of one of these markers, it should pop up who the user is, and a contact number or even a call button.

Links

• https://github.com/firebase/geofire/