Viewers: in countries Watching now:
In this course, author Tom Geller demonstrates how to use the Views module and other add-ons in Drupal to present dynamic, data-rich content. This course examines several real-world examples of effective data visualization and describes the Drupal data-storage model. The course also shows how to create, format, and style views; control access to data; improve data administration with Views Bulk Operations; and display content as custom maps and slide shows.
You already know a fair amount about data in Drupal. To recap, you define data models using something called content types. And you can see a list of those by clicking Structure and then clicking Content types. Here we see the Article and Basic page that come with Drupal by default, as well as the Employee content type that we created. If you click Manage fields, you can see that each content type comprises a bunch of fields, including several that we added in the last video.
Content types form templates for nodes, which you then create by clicking Add content and here we see the same fields. But as it happens, the model that you just saw goes well beyond content types and nodes. You can also create templates for people, comments and taxonomies. That might be a little confusing right now but don't worry. It's easier to show than to tell. We will start with people. And we go up there by clicking People. If we look at any one of these at the moment we only have one user myself admin and click Edit.
We cane see that it's a group of fields, the Username, password, email address, and so on. Some of these are built-in. You can't add or remove them because they're essential to Drupal's configuration and the way that it works. But you can add fields to that. I can show you that by going up to Configuration and Account settings. This Setting screen which you see in the tab up here is very much like the edit screen for a content type. You have some control over basic information. Otherwise you can see the two screens are quite different. Where Content types and Account settings are the same however, is that you can add fields to both.
You do that by clicking Manage Fields. I am going to Add a field here. It will say what committees that an individual person is on. Let me call Committees and it'll be a List of Text items. And we will just leave it as Select list and Save. As usual, there are a whole bunch of options that we could enter for that particular field. I am going to allow only a few values.
These are the committees that I want people to be able to join. I will go down and Save field settings. And then I have some additional settings that I can make. I am going to Display this on user registration forms. That means that when people join the system, they can say what committees they are on. And I will scroll down to the bottom and Save settings. We can see the effect that had by looking at our own user profile, go up to Hello admin. Remember we are admin and Edit. As we scroll down, we now see that Committee selection list right here.
And I will say that I want to be on the Hiring Committee and Save. If we go back to that Account Settings, again we click Configuration and Account settings. You can go back and edit that field if we want. For example, I can change how many values it allows. I am going to allow people to join as many committees as they want, scroll down, Save settings then go back to our profile to see that. When I scroll down, I can now Command+ Click or Ctrl+Click on Windows to select as many as I want, just as expected.
As I said, there's a similar interface for both taxonomies and comments. I will just quickly show you the taxonomies one. To get there click Structure and Taxonomy. We already have one Vocabulary in here called Tags. If I edit that vocabulary, we see the same Manage Fields and Manage Display tabs up here. So we could actually keep adding fields to Taxonomies in very much the same way. So you see how you can store data in any of these four things which are called Entities. That raises a question.
Why not build our employee directory using people instead of nodes? That's really an architectural decision and it's full of subtleties that you will start to learn after you start spending time with people and nodes and taxonomies and so forth. I'm going to use nodes throughout this course. But you could build it by adding fields to people. That way, each employee could sign in and manage their own records more easily. I'm doing it in more of an administrator focused way and I want the administrator to be able to control all of the nodes without the employees being able to control them.
The point is that Drupal is very flexible and how it stores data. That's good in the long term, but I know it can be a little confusing when you first come across it. Don't worry. I'll show you all about how the system of entities works, as we go through the course.
There are currently no FAQs about Drupal 7: Reporting and Visualizing Data.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.