Saved queries

A saved query is a filtered table with a name. Build the view once — the filters, the search, the sort, the columns you want — save it, and anyone on staff can open it again from the table’s button: Saved menu. While it’s open, that menu’s button carries its name, so you can always tell which view you’re looking at.

It is live: opening it runs the filters again, so it shows what matches today, not what matched when it was saved. A saved query is not an OPAC list, which is a hand-picked set of items patrons browse.

Where you’ll find it

Every table that has filter chips has a button: Saved menu beside button: Columns. Its button names the view the table is showing: button: Default view until you open a saved query, then that query’s name. It’s on these tables:

navigation path: Catalog then Items, on both the tab: By item and tab: By copy tabs
navigation path: Circulation then Active Loans
screen: All Holds, screen: To Pull and screen: To Re-shelve under navigation path: Holds
screen: Patrons, in a library and in a school
the patron list on navigation path: Circulation then Check Out

Each table keeps its own queries. A query saved on tab: By item doesn’t appear on tab: By copy, and one saved on a library’s screen: Patrons doesn’t appear on the school’s.

The one exception is a library’s patrons. screen: Patrons and the list on screen: Check Out are the same table, so a query saved on either one shows up on both, and so do the columns you pick.

Saving one

Set the table up the way you want it: add filter chips, type in the search box, sort by a column, and show or hide columns. The button: Saved button now reads button: Default view Edited.
Select button: Save query at the end of the filter row. You can also open button: Saved and choose menu item: Save query… at the bottom.
In the dialog: Save Query dialog, give it a name of up to 40 characters and select button: Save.

The button: Saved button now carries the name you gave it, which is how you know it saved.

A saved query keeps four things: the filters, the search text, the sort, and which columns are shown, in what order. It doesn’t keep the page you were on or how many rows a page shows.

Saving is there even when nothing matches. A query for overdue loans is worth keeping on a day when nothing is overdue.

Names are unique within a table, ignoring capitals, so a second query called

Overdue 4th graders on the same table is refused. The same name on a different table is fine.

Dates stay relative

A date filter saved as In the last… 30 days means the 30 days before whatever day you open it. It is not the 30 days before the day you saved it. The same holds for More than… ago, In the next…, This… and Today. That is the point of saving one: a query for books added this month keeps up on its own.

To pin a query to fixed days, build its date filter from a fixed date instead (Between two dates, for example).

Opening one

Open button: Saved and select the query. The table takes its filters and search, replacing whatever was set, and its sort. Its columns, in their saved order, become your columns for that table, just as if you had changed them in button: Columns, and they stay that way until you change them.

button: Default view is always first in the menu. It puts the table back the way it first opens: no filters or search, its usual sort, and its usual columns in their usual order. It can’t be renamed or deleted, and it’s there even when nothing has been saved.

The query you opened has a check beside it, or button: Default view does if you haven’t opened one. Each saved query also says how many filters it applies and who last saved, renamed or updated it. The link to the page keeps the query too, so a bookmark or a reload still names it.

Change a filter, the search, the sort or a column after opening a query and

Edited appears beside its name. Nothing is saved until you choose to: the query itself is unchanged until then.

Changing one

To keep changes to the query you opened, select button: Save changes at the end of the filter row once it says Edited. The bottom of the button: Saved menu has the same choice, and

menu item: Save as new query… to keep the changes as a separate query instead.

Each query in button: Saved also has a ⋯ menu:

menu item: Rename… changes its name.
menu item: Update to current view replaces what that query keeps with what the table shows now, and makes it the open query. It is unavailable on a query that already matches the table, because there is nothing to update.
menu item: Delete removes it for everyone, after you confirm. This can’t be undone. Deleting the query you have open leaves the table as it is, now named button: Default view Edited .

Who sees them

Saved queries are shared, and the top of the button: Saved menu says so. Every staff member who can open the table sees every query saved on it at that library (or, for the school’s screen: Patrons, at that school). Any of them can save, rename, update or delete one, whoever saved it, and that includes limited circulation staff.

A saved query only names a view. It never shows anyone rows they couldn’t see already, because each table still applies its own permissions to whoever opens it.