Try Now
More in this section

Forums / Developing with Sitefinity / Lists, Categories, Tags?

Lists, Categories, Tags?

2 posts, 0 answered
  1. Harry
    Harry avatar
    1 posts
    23 Aug 2010
    17 Mar 2011
    Link to this post
    Hi All,

    I'm relatively new to Sitefinity so I very much appreciate your help in figuring out the right direction about the issues below.

    My client is a manufacturer and distributor of alcoholic beverages. I am building them a website of drink recipes and there are several design issues that I am trying to work with. First I'll try to give a brief overview of some of the functional requirements.

    A recipe may has several attributes that at first glance, look like categories.  For example, a recipe has a color (red, green). I may have one or more spirits (vodka, rum, gin) and oen or more flavors (orange, chocolate, sweet, sour). A recipe also contains one or more ingredients (orange juice, lemon slice). Additionally an ingredient entry will have a quantity and unit (ounce, teaspoon, slice).

    When an editor enters a recipe, he or she will need to select these values from a predefined list, a list of colors, a list of spirits, etc.

    The problem is that categories won't work for colors or flavors because there are more than one of these attributes. Tags won't work because the values have to be collected into categories and the possible values restricted to those that are in the database.

    I suspect that using a list for ingredients can be problematic as the same ingredient may be used by multiple recipes. I want the user to be able to add ingredients to the recipe by picking from a list of ingredients.

    Looking for ideas and advice.

    Thank you,

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    25 Oct 2016
    17 Mar 2011
    Link to this post
    Hello Harry,

    You can actually use custom meta fields. For each content based module you can add unlimited number of metakeys  and they can be added  programmatically without config registration, so you can create a meta field builder for a given module. These metafields are automatically persisted, so you would not need a data layer for them. If you implement a selector for the metakeys you can easily associate them, so there would not be a hierarchical problems. The metakyes values could be of type LongText, so you can use comma separated values when hierarchical relation is needed. Additionally you can combine the custom metakeys with the categories and tabs.

    Kind regards,
    Ivan Dimitrov
    the Telerik team
2 posts, 0 answered