create a json object of the user include all the userhomepage features. friends. hobbies. weight
marcus
1
urgent
important
zfrika
how do i measure if this is complete? List each field that is being considered.
see file /javascript_exercise/DOM/testinghtml/sample_json_table_user_profile.json { 2 "_id": "ObjectId('675f2c1a...')", 3 "username": "Boy_wonder", 4 "email": "kkironyo@gmail.com", 5 "status": "active", 6 7 "profile": { 8 "name": { 9 "first": "Marcus", 10 "last": "Kironyo", 11 "display": "Marcus Kironyo" 12 }, 13 "identity": { 14 "gender": "male", 15 "age": 18, 16 "heightCm": 188, 17 "profilePicture": "44353245fdf24", 18 "ipAddress": "242028420442", 19 "guestAccount": "2424erewr" 20 }, 21 "ancestry": { 22 "tribe": "kikuyu", 23 "race": "African", 24 "ethnicity": "kenyan", 25 "language": ["swahili"] 26 }, 27 "education": { 28 "highschool": "Rosslyn Acadamy", 29 "college": "Toronto Community College", 30 "university": "UC Davis", 31 "profession": "Software Engineer", 32 "technicalSkills": ["Carpenter"] 33 }, 34 "address": { 35 "street": "1524 Main st", 36 "city": "Walnut Creek", 37 "state": "CA", 38 "country": "United States" 39 }, 40 "contact": { 41 "phone": "505-585-5895", 42 "instagram": "optimusnairobi", 43 "linkedin": "linkedin: Marcus kironyo", 44 "tiktok": "dancebears" 45 }, 46 "relationship": { 47 "status": "single" 48 }, 49 "location": { 50 "currentCountry": "United States", 51 "userCountry": "Botswana", 52 "nationality": "Kenya" 53 }, 54 "interests": ["bowling", "tennis", "cooking"] 55 }, 56 "stats": { 57 "friendCount": 0, 58 "postCount": 0, 59 "businessCount": 1 60 }, 61 62 "settings": { 63 "language": "en", 64 "timezone": "Africa/Nairobi", 65 "visibility": { 66 "contact": "private", 67 "education": "public", 68 "location": "friends" 69 } 70 }, 71 72 "external": { 73 "dataToken": "29420eee8204024" 74 }, 75 76 "createdAt": "2024-01-01T00:00:00.000Z", 77 "updatedAt": "2024-03-15T10:30:00.000Z" 78 }
dont include any data that will keep expanding in the json. ai suggestion: Use consistent keys across all documents Avoid extremely nested objects (MongoDB has a depth limit ~100 levels). . Core Principle — “Documents, not Tables” MongoDB stores data as documents (BSON, a binary JSON), and each collection can have documents with slightly different shapes. Your goal is to model your JSON structure so that each document: Represents a real-world entity (like a user, post, event, message, etc.) Groups data that is frequently used together Avoids deep nesting or extreme duplication Collection Design Strategy Use one collection per entity type. { "users": [...], "cars": [...], "events": [...], "messages": [...] }