FAQ to working in the RDB

Dear users of the recipe database. Please find below some frequent asked questions when working in the RDB. Michelle Tully from Creuna Stockholm is the person behind the answers, and is our true expert on the usability in the RDB.

Adding a recipe section:

Does the short vs. long name matter? Can you please explain which one will be used where on the site? If the full name fits into the short name, can we just use the full recipe name in both the short and long recipe name fields?

Answer: Long name is not currently being used. So only use the short recipe name.


Categories is not working for us. When we go to select a category nothing is clickable. 

Answer: You have currently only added top level categories. It’s the subcategories that are selectable and they need to be added in Admin. Add subcategories by clicking the top level category name. Please find attached file named “subcategories.jpg” to see where you type in the name.


Under "Ingredients and recipe description" do we need to fill out the "amount information" field? 

Answer: No. This is not used in your solution.


Does the Old recipe field matter? 

Answer: No. This is not used in your solution.


Under additional information what are "included recipes?" 

Answer: This is currently only being used in Denmark. It can be used when you reuse simple recipes like “broth” or “pastry dough”. So if you are creating a recipe like "chicken stew" the included recipe could be the "chicken broth”. This would save you the time of rewriting how to make a chicken broth and even shorten down the length of your recipe. 


What does serving suggestions mean?

Answer: This is a "recipe tip" and will link to another recipe on a recipe page. For example. If you have created a recipe for soup, the "serving suggestion" could be a recipe for a loaf of bread. Since loaf is nice with soup. This is different from the "included recipes" since it is not needed in other to create the recipe. It is only meant as a recommendation.

Extra note: The "tips" field is a free text field where you can write anything that is valuable for the user to know. For example. Important to cool for 30min before you put it in the freezer. Important to keep this short so the recipe view is not cluttered on the mobile.


What is the URL segment option in the Publishing section of adding a recipe? 

Answer: You should not edit this since it’s added automatically. 



Ingredients section:

When adding an ingredient, do "secondary units" matter? Can you please explain the difference? 

Answer: Secondary units is not needed and only meant to be an extra help for the end user. For example when a recipe has 200g of flour the secondary unit could be (approx.2dl) It would look like this on a recipe page:



200g flour (approx.2dl)

3dl parsley (approx. 150g)


To be able to have secondary unit as an option you first need to add these in Admin/Units. Secondly the secondary units need to be added on an ingredient level under secondary units. After this you can go to a recipe view and see a "plus icon” when adding ingredients that have a secondary unit added to them. The last step would than be to add the secondary unit information in these extra fields on the recipe view. 


Does the "primary unit type" drop down matter or should we be leaving this blank? Can you please explain?

Answer: Leave it blank for now. (this is because it is only used for mobile apps at the moment)



Admin section:

What is the purpose of the brands section within Admin? We don't see brands as an option when adding items to the ingredients list within the recipe. 

Answer: These are used when creating branded ingredients. For example. ARLA DOFINO®.

You would than add this brand in the admin and later be able to select it when creating an Arla ingredient. We do this so that branded ingredients later can be found and sorted on the web.


Can you please explain how shopping lists in general and specifically the "shopping lists categories" work. Do we leave blank for now?    

Answer: The shopping list is not fully developed yet and therefor not currently being used. You can therefor leave this blank for now.