New in Looker 6.16, the Looker IDE supports folders to help you organize your LookML project files. See this documentation page for information.
A Looker project is a collection of LookML files that tell Looker how to connect to your database, how to query your data, and how to control the user interface’s behavior.
Project files are shown in the side panel of the Looker IDE:
You can automatically generate a model file and view files based on your database when you create a new project. For existing projects, you can create new files manually by clicking the + icon next to Add in the IDE.
Project File Extensions
All project files have extensions, although the extensions are hidden in the IDE list. The types of project files and their extensions are:
- Model files with extension
- View files with extension
- Dashboard files with extension
- Data files with extension
- Documentation files with extension
- Project manifest files with extension
- Locale strings files with extension
- Other files with any file extension not listed above (including Explore files with extension
A model file specifies a database connection and the set of Explores that should use that connection. This is where you’ll define which data tables should be used (as included views) and how they should be joined together, if necessary.
For more information on model files, see the Understanding Model and View Files and LookML Terms and Concepts documentation pages.
A view file specifies a table to query and the fields (dimensions and measures) to include from that table.
For more information on view files, see the Understanding Model and View Files and LookML Terms and Concepts documentation pages.
Looker supports both user-defined dashboards and dashboards that are built directly into your project using LookML. If your project contains LookML dashboards, they will be defined in dedicated dashboard files.
For more information on LookML dashboards, see the Creating LookML Dashboards documentation page.
In Looker, you can use TopoJSON files to specify custom maps for your visualizations. If your project contains TopoJSON-based custom maps, they will be defined in dedicated files in your project’s data section.
For more information on using data files for custom mapping, see the Map Options and
map_layer LookML parameter documentation pages.
You can write documentation and other notes about your project using GitHub-flavored markdown in one or more documentation files.
For more information, see Documentation Files on the Understanding Other Project Files documentation page.
Your project may contain a project manifest file that lists files from other projects to import into the current project, or may contain customized localization settings.
To have the option of adding a manifest file, the Looker admin must enable the Project Import experimental Labs feature.
Locale Strings Files
If you are localizing your project, it may contain files with translation strings corresponding to different languages.
For more information, see the Model Localization documentation page.
Your project may also contain other files whose file types are not recognized by Looker’s IDE as belonging to one of the categories above, such as Explore files used for a native derived table or used to extend an Explore across models.
For more information on file types that are likely to be stored in the Other category, and on moving files from the Other category, see the Understanding Other Project Files documentation page.
Accessing Project Files
To view existing projects on the LookML Projects page, click the Develop menu and choose Manage LookML Projects.
The projects you see in those lists depend on the following things:
- Your Permissions: The projects and models you see on the Develop menu and the LookML Projects page depend on your permissions.
- Your Current Mode: You may see additional entries on the Develop menu and the LookML Projects page when you view them in Development Mode versus Production Mode. For example, if you created a new model in Development Mode that you have not yet pushed to production, then that model would be visible only when you are in Development Mode.
For more information, see the Accessing and Editing Project Information documentation page.