CMS: Planning Your Database Model
4 min read
Note:
You might want to learn About Database Collections before you read this article.
This article highlights some things you might want to consider before adding database collections.
The most important thing to keep in mind is that it's generally not a good idea to duplicate information. It wastes time and space, and it also increases the likelihood of errors and inconsistencies in your information. The best way to avoid duplicating your data is to divide your information into different collections based on their subject matter and permission levels.
The most important thing to keep in mind is that it's generally not a good idea to duplicate information. It wastes time and space, and it also increases the likelihood of errors and inconsistencies in your information. The best way to avoid duplicating your data is to divide your information into different collections based on their subject matter and permission levels.
Important:
For a deeper understanding of how collection permissions play a part in the security of your site, read this overview.
Spend Some Time Thinking About Your Information
It is worth spending some time thinking about what you want to do and planning out your database collections before you start creating them.
- Start by identifying the purpose of your site. What kind of information will you be storing? Will you be collecting user input? For example, you might have a site that showcases your favorite recipes and also allows visitors to sign up and become paying members.
- Think about the different types of data you will be storing and how it all fits together. How are you planning on displaying your data to your visitors? Do you want to create dynamic pages? How do you envision your collections working together?
- Determine who will be using the information in each of your collections so you can set their permissions correctly. Will your visitors only be viewing the information in your collection or will you offer them the ability to add and modify the information?
Now you're ready to plan out your collections.
Naming Your Collections and Fields
Name your collections and fields with care. It is important that their names be clear to you when you are connecting elements to them (or writing code for them if you're using Velo by Wix). Collection and field names appear in the Editor when you are connecting elements to data, so it's important that they be clear.
Keep in mind that you cannot rename collections after you've created them.
Keep in mind that you cannot rename collections after you've created them.
Velo by Wix Users: Remember that while you can change the name of a field, you can't rename its field ID. The field ID is what you'll use when writing code, so make sure it's easy to identify.
Make Sure Your Data Has Unique Identifiers
If you are going to be creating dynamic item pages for the data in a collection, make sure you have at least one field whose values uniquely identify each item. This makes sure that each page can have a unique URL.
For example, let's say you want to create a dynamic item page that showcases information about each recipe in your collection. If you have several different recipes for chocolate cake in your recipe collection and you call them all "chocolate cake," their dynamic pages will all have the exact same URL (for example, mysite/recipes/chocolate-cake). This means that you will not be able to control which chocolate cake recipe is displayed on your dynamic page. See here for more information.
The same applies if you plan on creating reference fields that point to a given collection. Make sure that the Main field in your collection has unique values so that you can select the correct item in your reference fields.
For example, let's say you want to create a dynamic item page that showcases information about each recipe in your collection. If you have several different recipes for chocolate cake in your recipe collection and you call them all "chocolate cake," their dynamic pages will all have the exact same URL (for example, mysite/recipes/chocolate-cake). This means that you will not be able to control which chocolate cake recipe is displayed on your dynamic page. See here for more information.
The same applies if you plan on creating reference fields that point to a given collection. Make sure that the Main field in your collection has unique values so that you can select the correct item in your reference fields.
Work in a Spreadsheet and Then Import Your Data
If you already have your data in a spreadsheet application such as Excel, you can easily save it to a CSV file and then import it into your collection. Similarly, if you need to make global changes to your data, you can export it to a CSV file, work on it in your spreadsheet application, and then import it back into your collection.
Adding a Designated Field for Sorting
If you want to display your items in a specific order but do not have a field that allows you to sort them by that order, you can add a number field so that you can sort the items. For example, if you want your recipes to be in a specific order other than alphabetical, a number column can help you maintain this order.
Reference Fields
Reference fields create a connection between collections that is defined in the collection itself. Each reference field points to a specific collection and displays a value that comes from that collection.
The advantage of reference fields is three-fold. First, they help maintain data integrity because their value is taken directly from the referenced collection. Second, they help eliminate data duplication. And third, when you dynamically display information, reference fields let you access information in the referenced collection as well as in the main collection. This allows you to create master-detail pages.
Considerations for Storing User Input
If you want to have a form for your users to fill out, you will need to create a collection for storing the information they supply. Best practice is to have each form connect only to one collection, and then connect each user input element to a field in that collection.
Spend some time thinking about the types of information you want your users to give you, and then design your form and database collection accordingly. If you want to have a dropdown list, consider where you want to store the values in the list. If you want your users to have the option to sign up for your newsletter, you'll need a boolean field that you can connect to a checkbox.
Also, make sure you give collections that will store user input the appropriate permissions, so that your users can save their information.
Spend some time thinking about the types of information you want your users to give you, and then design your form and database collection accordingly. If you want to have a dropdown list, consider where you want to store the values in the list. If you want your users to have the option to sign up for your newsletter, you'll need a boolean field that you can connect to a checkbox.
Also, make sure you give collections that will store user input the appropriate permissions, so that your users can save their information.
Did this help?
|