Testing the vercel nameing and PRs

Useful Links

Deployment / Development Flow

Create a new branch from develop
Make changes until happy
Push to github
1. It built successfully and youve playde with the preview?, Carry on to 5 and collect £200
2. Do not pass go, fix it and go back to 2
Squash chanegs onto develop with a good message combined mesage
Create a pull request to main if happy to "go live"
Merge Commit to main (one feature = one commit)

TODO

Both to think and discuss

Do we need the spreadsheet, could it be updated via a button in admin
On the day payments

Adam

Checked in at, by, using
Disclaimer on food choices
Default prose styles e.g. {{ markdown }}
Return page from checkout
Allow change name / email for attendee.
Clear cache on purchase

Connor

Thinking these might be on the wrong list because I don't remeber what they're for

Cutoff meal preferences

Karen

Video of dancing wide

When we have time

Stripe integration for passes
ticket upgrades
Human assisted table optimisation, human says these people must sit here and the magic places everyone else

Last Meeting

Draft Mode ✔️
Singage Dashboard ✔️
Screens ✔️
Git ✔️
Logo ✔️
Meal options ✔️
Preview deployments ✔️

Purchasing Rules

name: "Adam", email "Email" number_of_tickets: 1, line_items: [ { name: "Party pass", stripe_product_id: 456798, access: [1,0,0,1,0,1] }, { name: "Dinner Option", stripe_product_id: 456798, access: [0,0,1,0,0,0] }, ] price: 100

chgeckout emails

Data Structures

meal data

This is how the data will be stored in db.

TBD: Send in this structure in the checkout link request as below. Otherwise just process it in the request and store in db like this. (The former is better.)

{
  'choices': [1,0,1], 
  'dietary_requirements':{
    'selected':["nut allergy", "gluten free", ...], // list of requirements selected from a list
    'other': "Some specific additional dietary requirement"
  },
  'seating_preference': ["12345", "12678", ...] // list of ticket numbers of people they want to sit with
}

request checkout (no longer needed)

{
  'name': "John Doe",
  'email': "john_doe@example.com",
  'number_of_tickets': 1,
  'line_items': [
    {'name': "Party Pass", 'stripe_product_id': "prod_QQTrga8mShkzyo", 'access': [1,0,0,1,0,1]},
    {'name': "Saturday-Dinner", 'stripe_product_id': "prod_QQUJ8m2jrR6toK", 'access': [0,0,1,0,0,0]}
  ],
  'meal': {}, //meal data format (optional)
  'promo_code': "promo_******" // (optional)
}

dyanamodb customer info table

{
  'email': "john_doe@example.com",      
  'ticket_number': "123456789",
  'full_name': "John Doe",
  'active': True|False,
  'purchase_date': 1721571296,
  'line_items': {[
    'amount_total': 4500,
    'description': 'Party Pass',
    'price_id': "price_xxxxx"
  }],
  'access': [1,0,0,1,0,1],
  'schedule': {
    // tbd
  },
  'meal_preferences': None|{
    // meal data format (see above)
  },
  'ticket_used': "false"|"75014206", // time/date of ticket being scanned as string
  'checkout_session': "cs_xxxxxx",
  'status': "paid_stripe"|"paid_cash"|"refunded_stripe"|"refunded_cash",
  'student_ticket': True|False,
  'promo_code': None|{
    'code': "MLF",
    'value': 500
  },
  'meal_preferences_history': None|{
    // meal data format (see above) plus...
    'updated_date': 1722471022,
    'source': "admin"|"customer" // when we have users could be admin-name
  },
  'transferred': None|{
    'date': 1722472454,
    'ticket_number': "123456789", // Will be the same if only the name changed and not the email
    'email': "john_doe@example.com", // new details of who it was transferred to 
    'full_name': "Johnnie Doe",
    'source': "admin"|"customer"
  }
  'owner_history': None|[{
    'date': 1721297593,
    'ticket_number': "678912345"
    'email':"jane.doe@example.com",
    'full_name': "Jane Doe",
    'source': "admin"|"customer"
  }]
}

request transfer ticket (lambda transfer_owner)

{
  'ticket_number': "123456789",
  'email': "jane.doe@example.com",
  'email_to': "new.email@example.com", // could be the same email if they only want to change the name
  'name_to': "Jennie Doe",
  'source': "admin"|"customer" // really I should be checking where it comes from not you telling me (future API)
}

**** ENDPOINTS ****

** send my ticket *** *

lambda function: send_ticket
status: functional (test data)

url: https://ux66cekzyiffxqjobe3xbyuk7y0nzruu.lambda-url.eu-west-2.on.aws/?email={{email}}

description: Makes a query of the DynamoDB of customer tickets, if the email is present will send the ticket(s) to that email. If multiple entries for that email exist, customer will receive an email for each ticket.

method: GET

parameters: email- The query email

returns:status

status codes: 200 OK 405 Method Not Allowed

cURL example: curl -H "Accept: application/json"
'https://ux66cekzyiffxqjobe3xbyuk7y0nzruu.lambda-url.eu-west-2.on.aws/?email=connor1monaghan%40gmail.com'

curl -H "Accept: application/json"
'https://ux66cekzyiffxqjobe3xbyuk7y0nzruu.lambda-url.eu-west-2.on.aws/?email=adam.bardsley%40gmail.com'

*** customer data *** *

lambda function:
status: functional (test data)

url: https://x4xy6yutqmildatdl3qc53bnzu0bhbdf.lambda-url.eu-west-2.on.aws/

description: Retrieve the meal options of schedule options of a customer, searching the db is done only with ticket number which but be valid.

method: GET

parameters: requested- Comma separate list of type of customer data to return. Valid options: meal, schedule email- The customer email ticketnumber- The customer ticket number

returns:JSON of the 'meal options' entry and/or of the 'schedule options' entry

status codes: 200 OK 400 Ticket number does not exist 405 Method Not Allowed

cURL example: curl -H "Accept: application/json"
'https://x4xy6yutqmildatdl3qc53bnzu0bhbdf.lambda-url.eu-west-2.on.aws/?requested=meal,schedule&email=connor1monaghan%40gmail.com&ticketnumber=3911997684'

url: https://x4xy6yutqmildatdl3qc53bnzu0bhbdf.lambda-url.eu-west-2.on.aws/

description: Update a customer entry in the db with the provided meal options and/or schedule. Request data must include at least one of 'meal_options' or 'schedule'.

method: POST

parameters: email- The customer email ticketnumber- The customer ticket number meal_options- (optional) dict of meal options schedule- (optional) dict of schedule options

returns:status

status codes: 200 OK 400 Ticket number does not exist 405 Method Not Allowed

cURL example: curl -H 'Content-Type: application/json'
-d '{"email":"connor1monaghan@gmail.com", "ticket_number":1111111, "meal_options":{}}'
-X POST https://x4xy6yutqmildatdl3qc53bnzu0bhbdf.lambda-url.eu-west-2.on.aws/

bardsley/merseysidelatinfestival

Testing the vercel nameing and PRs

Useful Links

Deployment / Development Flow

TODO

Adam

Connor

Karen

When we have time

Last Meeting

Purchasing Rules

Data Structures

meal data

request checkout (no longer needed)

dyanamodb customer info table

request transfer ticket (lambda transfer_owner)