‌ [https://www.loom.com/share/c5ddd2ebe5c74cffb6f60341a65c35be](https://www.loom.com/share/c5ddd2ebe5c74cffb6f60341a65c35be "smartCard-embed") - 1st page Basic Info - Pass the searched name to the AddFactiii via prop - Check factiii is unique the way username does when we sign up - Select Space should be dropdown of spaces the user is allowed to add factiiis too - Default to factiii - Need to discuss but factiii likely makes sense and then we can push it elsewhere as needed as well as approve it - Factiii Types specify a width for the div in the bubbles so it does not move when text changes. - Place the Label on top of switch and see if it looks better - Hide Premium for now - 2nd Page - Advanced Requirements - Data Requirements - Call this factiii type instead of data requirements - Default instead of “Select a data requirement” change to “Basic factiii” - We have icons on the factiii search for the factiii, try to use them in this drop down as appropriate - rename each label and offer an explanation - DATA REQUIRED - Require additional data (place this one on the bottom, debating on hiding it as it’s very general - INTEGER REQUIRED change to Number tracking then explain it can be used to track counts etc - Disappearing Data - Need a good name, but this is meant for publicly opening the factiii then making it private once someone adds data so maybe Community Help - This makes the post Public but it goes private to you when someone adds the data you are looking for - HUMAN SOURCE to Human source - This is the best source for factiii and point to a specific human on earth - GOVERNMENT SOURCE - Government Source - This is the 2nd best source as it comes from something within the governemnt - ENTERPRISE SOURCE…3rd best - ANON…worst source but still usefil - Hide none, I don’t think we use it but double check - Approximate location should go into Select a location dropdown by default it will use device and set to approximate to render - Explain in location drop down what location required and device location are vs the back end name. I think something like Require a locaiton to be attached, Automatically get my location, and Approximate my location so you can make a quick bubble - 3rd Page - Rules Section - so we can add the rules for the factiii immediately - Check if we can reuse the sidebar rules component we have on spaces already - Footer shift the buttons to the right - Make a blurb that factiiis cannot be edited currently - You can delete them and remake Update Logic to be edited DO NOT DO YET - Make camera factiii attach a separate factiii in the process factiiis so you end up with 2 factiiis if you have camera factiii turned on - Make sure process factiiis - Migration will be weird but not too bad - Figure out how to handle multiple requirements - Maybe put the association in the postFactiii - Apply same logic for all default factiiis