loading

Module Assessment

loading Open Dropdown
You must include a first name and last name in your profile to create challenge environments.

Background

You’ve learned more about how Turtlehead Tacos wants to feature information about the Restaurants, Events, and Community Stories.

As a reminder, in general, they want to:

  • List their Restaurants
  • Build pages for their Restaurants, FAQs, Events and Community Stories
  • Feature Restaurants, Events, FAQs, and Community Stories in Answers

For the Commmunity Stories

  • They want users to be able to search based on related events

  • There are Non-Profits involved with each and they believe it’s important for their customers to know about these. They do not want dedicated pages for the non-profits, but if they decide to build pages for the Community Stories, they want the non-profit name to be visible in a bulleted list and they want to make sure they can filter on the field in Answers. This means this can be a field on Community Story type, but does not need to be an entity type.

  • They want to be able to publish the URL of the pages to a field, so you’ll want to add the Landing Pages URL field.

For the Restaurants

  • The restaurants host a number of events – these may need their own pages and may even go to Listings so you’ll want to make sure these are their own entities, but linked to the Restaurants.

  • Additionally, They have 2 different kinds of Restaurants – some are semi-permanent Food Trucks style eateries while others are dine-in Restaurants. While they’ve been approved to send both to Google Maps via Listings so they should all be of type “Restaurant”, they want their local pages to look a bit different so they need to keep track of which is which.

  • They also have a big initiative around Delivery this year so they want to make sure they feature Delivery hours on their site – with a disclaimer, of course – in case the delivery experience is negative.

  • Finally, they want to highlight certain features at each restaurant, like outdoor seating, live music, or accepting reservations.

As their Admin, it’s your job to make sure they have the right data model so that their account is a success. Let’s get started!

Your Challenge

Based on this new information, you’re ready to finish up the fields for the Community Story.

  1. Navigate to Account Settings > Manage Entity Types and click in to “Edit Fields” for Community Story type. Add all new fields to “Core Information” for now.

  2. Add a new Promoting Events field to the Community Story type that only allows a user to select from Events in the Knowledge Graph. Add to the “Core Information” section for now.

    • Name: Promoting Events
    • API name: c_promotingEvents
    • Field Specification
      • Type: Entity List
      • Validation: Check off Events so users can only select Events
  3. Add a new Local Non-Profits field to the Community Story type to list the non-profits involved. Add to the “Core Information” section for now.

    • Name: Local Non-Profits
    • API Name: c_localNonProfits
    • Field Specification - Type: Text List
  4. Add the built-in Landing Page URL field to the Community Story type. Add to the “Core Information” section for now.

  5. Save the Community Story type and return to Manage Entity Types.

  6. Now it’s time to update the schema for the Restaurant entity type. Click “Edit Fields” for the Restaurant type. Add all new fields to the “Business Details” section for now.

  7. Add the Promoting Events field you created above to the Restaurant type as well. Add to the “Business Details” section for now.

  8. Add a new Restaurant Type field to the Restaurant type. Add to the “Business Details” section for now.

    • Name: Restaurant Type
    • API name: c_restaurantType
    • Field Specification
      • Type: Single-Option Select
      • Available Options: “Food Truck” and “Dine-in Restaurant”
  9. Add a new Delivery Hours custom field to the Restaurant type. Add to the “Business Details” section for now.

    • Name: Delivery Hours
    • API Name: c_deliveryHours
    • Field Specification - Type: Hours
  10. Add a new Delivery Disclaimer field to the Restaurant type that you can feature on Answers and Pages. Add to the “Business Details” section for now.

    • Name: Delivery Disclaimer
    • API Name: c_deliveryDisclaimer
    • Field Specification
      • Type: Multi-line Text
      • Validation: maximum character count of 200 characters
  11. Finally, add a new Restaurant Features field to the Restaurant type to highlight all of the special features at each Turtlehead Tacos location. Add to the “Business Details” section for now. .

    • Name: Restaurant Features
    • API Name: c_restaurantFeatures
    • Field Specification
      • Type: Multi-option select
      • Available Options: Outdoor Seating, Live Music, Accepting Reservations, Dog Friendly, Breakfast for Dinner, Sells Merchandise

Make sure that you name the fields and options exactly as provided

loading Open Dropdown
You must include a first name and last name in your profile to create challenge environments.
Challenge account expires in <% util.expirationHours > 24 ? Math.round((util.expirationHours * 1.0) / 24) : util.expirationHours %> <% util.expirationHours > 24 ? (Math.round((util.expirationHours * 1.0) / 24) == 1 ? 'day' : 'days') : (util.expirationHours == 1 ? 'hour' : 'hours') %>.
Challenge account has expired. Please create a new account.
Report Card
Create the Promoting Events custom field
Create the Local Non-Profits custom field
Add all the new fields to the Community Story entity type
Add the Restaurant Type custom field
Create the Delivery Hours custom field
Create the Delivery Disclaimer custom field
Add Restaurant Features custom field
Add all the new fields to the Restaurant entity type
Common Issues
Make sure you spelled the field and API names exactly. expand/collapse module
You need to spell the field display names and API names exactly as specified in the challenge. This includes casing – if the challenge says to name a field “Title” you should name it “Title” and not “TITLE”.
Previous Submissions
Attempt #<% submission.attemptNumber %>
<% submission.date %>
Score: <% submission.numericScore %>
Pending