What is the FOLIO Analytics repository
The FOLIO Analytics repository contains reports and other analytics developed for FOLIO and designed to run on the Library Data Platform. Reports developed for FOLIO are stored as code written in Structured Query Language (SQL). The SQL queries can be opened inside of database querying software to pull data out of the LDP.
You can read an introduction to the repository at its overarching README file on GitHub. The file describes the following:
- The two types of SQL queries to be found in the repository:
- Report queries, which you can copy and paste to run on your LDP.
- Derived table queries, which simplify and speed up report queries. A derived table is simply a table created using data from one or more other tables. These queries are managed behind the scenes through LDP administration so that they run automatically and generate the derived tables in the database.
- Documentation for the queries.
- Examples of the software queries can be run in.
- How the queries are organized in the repository.
The first section below outlines how to make use of the report queries in the FOLIO Analytics repository to generate reports on FOLIO data. Other sections of the documentation cover administration of derived tables and use of derived tables for ad hoc querying.
Using queries from the FOLIO Analytics repository
*Releases of FOLIO Analytics are tied to a specific flower release. Please refere to the version matrix for compatibility.
Report queries in the FOLIO Analytics repository are laid out in a particular structure that will make it easy for you to find the various areas you need as you build your knowledge of SQL.
- Introductory comments. Queries may start with a short block of text that is not part of the query. These “comments” often describe basic components of the query and give a brief description of the purpose.
- Parameters. To make things easier for the user, queries typically include a “parameters” section at the top that allows one to easily specify the values needed for filtering on a field.
- Subqueries. Queries may include several groups of smaller queries, which may be referred to as subqueries. These subqueries help simplify and rearrange different parts of the database to make the final query easier. (Note: The official term for these parts of the query is common table expressions, or CTEs. Calling them subqueries is meant to emphasize the role they play in the larger query.)
- Main query. The main query determines the final look of the report. Under the keyword
SELECT, you will see a list of the fields that will show up in the final report. After the keyword
FROM, there is a list of the tables the fields are coming from. The keyword
WHEREspecifies the filters that should be applied to limit the rows in the report. Additional keywords may appear after the
WHEREkeyword to further customize the output of the report. Comments can appear throughout the query to provide instructions or clarifications.
Locating queries in the repository
Report queries are stored in the sql/report_queries folder of the repository. To see an overview of the report queries in the repository, review the README file in the report_queries folder. You can also browse the subdirectories in the sql/report_queries folder. Each subdirectory contains one or more SQL queries, along with documentation that describes the purpose and output of the queries.
Running queries in a database query tool
Once you have located a desired report query, you can perform the following steps to run the query and generate a report:
- Copy the query code from GitHub.
- Open a database query tool.
- Connect to the LDP.
- Paste the SQL query code into a local file.
- Run the SQL query.
- Export the query results in the desired format.
The following section demonstrates this workflow using DBeaver, a database querying tool that has a free community edition and is available for Windows, Mac OSX and Linux operating systems.
Example of running a query using DBeaver
Copy the query code from GitHub
- In the sql folder of the FOLIO Analytics Repository, click on the report_queries folder.
- Click on the subfolder for the report you are interested in. For this example, open the ACRL Circulation query file by clicking first on the acrl subdirectory and then on the circulation subdirectory, and finally clicking on the acrl_circulation.sql file.
- To open the query file directly, click on the raw button located in the upper right corner of the file preview box.
- To copy the query code, type Ctrl-A (Cmd-A on Mac) to highlight all of the text, followed by Ctrl-C (Cmd-C on Mac) to copy the text.
Open a database query tool
- Install the DBeaver community edition corresponding to your operating system.
- Open DBeaver.
Connect to the LDP
- To add your LDP connection, click on the New Database Connection button toward the top of the Database Navigator tab. It should look like an electrical plug with a plus sign.
- In the Select your database window that pops up, click on the PostgreSQL symbol and then click Next.
- Fill out the connection dialog:
- You will need to get the following information from your local LDP administrator:
- Host (typically looks like a URL, like ldp.institution.edu)
- Port (typically 5432)
- Database name
- User name and password
- SSL mode (will likely be “require”)
- Note that a hosted LDP reporting database is currently available for the FOLIO community. It provides access to data from the FOLIO reference environment folio-snapshot and is updated hourly. For login info, please review the Reporting SIG wiki documentation.
- You will need to get the following information from your local LDP administrator:
- In addition to the first page of connection details, you must click on the SSL tab to select “require” under SSL mode.
- Finally, expand Connection Settings in the sidebar on the left and select the Initialization subheading. In the settings on the right, make sure the Auto-commit check box is selected.
- When you are done setting up the connection, you can double click on the connection name in the Database Navigator tab to connect to the database.
Paste the SQL query code into a local file
- To create a new script file, either click on the New SQL Editor button in the toolbar (it will look like a document with a plus sign) or select New SQL script from the SQL Editor menu.
- If you have multiple databases, DBeaver may prompt you to select the one you want to query. Select the correct database and click on select. The new script window should show up on the right, with the script editor on the top and the results window (currently empty) on the bottom.
- Paste the copied query code from GitHub into the script editor. (Once you paste in your copy of the script, you can change it however you want. This is your copy of the SQL. Read more about tailoring queries below, and note that you should pay special attention to the “parameters” section in your query.)
- To save the query, select “Save As” from the “File” menu and navigate to your preferred directory, using a filename with “.sql” as the file extension.
Run the SQL query
- To run the query, either click on the Execute SQL Script button on the left side of the script editor (it should be the third button from the top and look like a document with a “play” symbol inside of it) or select Execute SQL Script from the SQL Editor menu.
- The results will hopefully then appear in the results panel below the script. Note: When querying parts of the database with a lot of data, like the inventory tables, there may be a long delay before results are returned.
Export the query results as a CSV
- To export the results, right-click inside the results table and select Export data….
- Complete the data export wizard:
- Select “CSV” as the data transfer target type and click Next >.
- Adjust any data transfer settings and click Next >.
- Adjust any output settings (e.g., output directory, file name pattern) and click Next >.
- Confirm settings and click Start to export the file.
Many queries allow you to specify the correct values for report filters by editing the “parameters” sections at the top of the query. You should always review and update the parameters before running your query. If you do not update the values in the parameters section, the default values will be used, and in many cases these may be inappropriate for the data in your LDP.
To edit the parameter values, all you need to do is type in the measure value of interest between the single quotation marks at the start of one or more parameter lines. The values must be typed in exactly as they appear in the database. Possible values might be suggested in query comments (although those examples may not be in use at your institution). If you do not want to filter the data, you can remove anything between the single quotation marks.
To further tailor the query, consult the introduction to this section above to identify the different sections you may wish to review and modify. One edit you may want to make would be to add your own comments to guide yourself and others. Comment text will be gray (in DBeaver) and will not affect how the query runs. There are two ways to make comments. Typing
-- will create a comment out of the rest of that particular line of the file. To create a comment that spans multiple lines, use
/* at the beginning of the comment and
*/ at the end of the comment.
Another edit you may want to make would be to remove a field from the report. To do this, you can look for the
SELECT keyword in the main query section (which is usually where you will see the longest list of field names). Inside the list of fields after that
SELECT keyword, you can delete the lines that list fields you do not want to include. Just make sure that the last item in the list, the one that appears right before the
FROM keyword, is not followed by a comma.
For more advanced query writing techniques, refer to the documentation on ad hoc querying using LDP tables.
What to do if you do not get any results
- Check to see if a parameter was entered by the report writer that does not apply. If not, seek out additional training here or through your local (or the larger) FOLIO community.
What to do if there are errors
- Check to see if the error message indicates that a derived table is missing. These derived tables are stored in a schema called folio_reporting, so that schema name followed by a table name might appear in the error message. If a derived table is missing, contact your LDP administrator.
- If you edited the query, check to make sure you don’t have a comma appearing at the end of a list, like the list of the fields that occurs after the
- If you can’t determine what is causing the error, consult with your local LDP administrator or either your local or the larger FOLIO Reporting community.
Ad hoc querying using LDP tables
If the shared queries do not meet your needs, you can also develop your own “ad hoc” (or as needed) queries to pull data from the LDP. In addition to creating queries with different fields and table connections than the shared queries, ad hoc queries make it possible to connect FOLIO to other custom tables available in your local LDP. Because the LDP is built on standard relational database software, you can build ad hoc LDP queries in the same way you would build queries for any other database, such as writing an SQL query and using a database query tool to run the query.
To develop ad hoc queries, you will need to write query scripts using Structured Query Language (SQL). The table below includes a few resources for learning SQL.
|The Data School: Learn Introductory SQL Concepts||An interactive tutorial with an approachable style. The tutorial has built-in SQL evaluation, so you don’t need to set up a separate database tool to try the exercises.|
|Select Star SQL||An interactive book that teaches SQL concepts using real-world datasets and problems. The book has built-in SQL evaluation, so you don’t need to set up a separate database tool to try the exercises.|
|SQL Murder Mystery||The SQL Murder Mystery is designed to be both a self-directed lesson to learn SQL concepts and commands and a fun game for experienced SQL users to solve an intriguing crime. They also have a walkthrough for SQL beginners.|
|CodeAcademy:||A course called Learn SQL and a list of SQL Commands. Without a Pro account, course features are limited.|
|Linked In Learning||Linked In Learning provides access to several courses on SQL at many levels of expertise. Requires a paid subscription.|
LDP-specific query guidance
After learning how to use SQL, there are a few resources that outline specifics of how the LDP organizes FOLIO data.
- The LDP User Guide. This guide includes details about writing SQL that works for the LDP data model; note especially the sections describing the data model, JSON queries, and the differences between the relational attributes and JSON fields. The guide also includes a section that describes the historical data functionality within the LDP, which allows users to compose queries that explore how FOLIO data records change over time.
- SchemaSpy. This SchemaSpy installation is attached to the LDP reference environment, which pulls data from the FOLIO snapshot reference environment. SchemaSpy gives a concise list of LDP tables and fields and can be helpful when developing queries, if your local LDP uses the same software version as the LDP reference environment.
- FOLIO Schema Parser. This lightweight FOLIO Schema Parser automatically populates a spreadsheet using FOLIO’s data schema documentation, connecting FOLIO fields to LDP tables and fields. It can be helpful as a tool for quickly looking up what fields are available from FOLIO apps and what LDP tables include those fields.
- FOLIO Analytics shared derived tables. The derived tables developed for the LDP (found in the folio_reporting schema of the LDP) often serve as a better starting point for ad hoc queries than the FOLIO tables in the public schema. The derived tables combine and simplify the original FOLIO tables in ways that make query development much easier. You should work with your local LDP administrator to determine how your local LDP is using derived tables (e.g., what FOLIO Analytics release you are using, how frequently the derived tables are updated).
Sharing ad hoc queries
If your ad hoc query might be of use to other institutions, we encourage you to consider submitting it to the folio-analytics repository. Our contributing guidelines describe the requirements for new contributions to the repository.
Tips for using DBeaver to write an ad hoc query
Developing ad hoc queries using DBeaver follows a similar workflow to the example workflow above. You can either start with an existing report query or derived table query and modify it for your own uses, or you can write the SQL code from scratch.
An example of a simple ad hoc query might be:
SELECT group_name, COUNT(user_id) AS num_users FROM folio_reporting.users_groups GROUP BY group_name ;
This code specifies that the report should contain two columns:
group_name and a column that stores a calculation of the count of values in the
user_id column, which should appear in the query with the label “num_users.” The code then specifies that these columns are coming from the
folio_reporting.users_groups derived table. Finally, it specifies that the data from the original table should be separated into separate groups using values from the
group_name column, so that the
num_users calculation is done separately for each group. The result is a table where each value of
group_name is matched with a count of the number of users in that group.
As you are writing your query file in DBeaver, you may find it helpful to browse the LDP using the Database Navigator tab. For example, you can expand the connection, then expand the Schemas, then expand the folio_reporting schema, then expand Tables to see the available derived tables. Each table can be expanded to see its available columns. To browse the data in a table, right-click on a table and select View Data. Use the same procedure to browse the tables and columns available in the public schema.