Searching processes
Zuletzt aktualisiert
Zuletzt aktualisiert
If you want to search for specific processes, you can use Goobi’s extended search function. To do this, select the menu bar option Workflow – Search for volume
.
In order to conduct a finely tuned search, Goobi’s Search for volume
dialogue box uses a filter syntax that makes it possible to identify the requested processes on the database.
The above diagrams show how a search is performed in Goobi using its internal search syntax based on the search details entered in the dialogue box. The search syntax generated by Goobi can be seen in the filter box Find processes above the table and can be extended to include additional parameters. It is also possible to save a search in case it is needed on future occasions. It will then appear in the drop-down list of pre-defined filters and can be executed at any time.
Below you will find an explanation of the background filter syntax. This is useful because manually combining the search parameters described below allows you to perform more detailed searches than is the case simply using the dialogue box. The following table contains a description of some typical search filters and how they work.
Filter syntax | Description of function |
---|---|
ab | Filter to display all processes from all projects that contain |
-ab | Filter to display all processes that do not contain |
ab -abc | Filter to display all processes that contain |
a?c | Filter to display all processes that contain |
a*c | Filter to display all processes that contain |
meta:Shelfmark:123 | Filter to display all processes with the condition that the metadata item |
meta:Author:Mustermann | Filter to display all processes with the condition that the metadata item |
"meta:Author:Max Mustermann" "meta:Author:John Doe" | Filter to display all processes for which both the authors |
meta:index.Person:Mustermann | Filter to display all processes that contain the value |
meta:*:123 | Filter to display all processes that contain the value |
-meta:Shelfmark:* | Filter to display all processes that have no |
batch:3 | Filter to display all processes allocated to the |
-batch:3 | Filter to display all processes which are not allocated to the |
journal:intranda | Filter to display all processes that contain the word |
project:sample_project | Filter to display all processes from the project |
"project:sample project" | Filter to display all processes from a project where the project name contains |
ab project:sample_project | Filter to display all processes from the project |
ab -abc "project:sample project" | Filter to display all processes from the project |
"-project:sample project" | Filter to display all processes that do not belong to the project |
stepDone:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepOpen:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepInFlight:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepInWork:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepLocked:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepDeactivated:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepError:7 | Filter to display all processes from all projects for which the workflow step with the sequential number |
stepDone:4 stepLocked:7 | Filter to display all processes for which at least workflow step |
stepInWork:Imaging | Filter to display all processes for which a workflow step with the name |
stepDone:Export "project:sample project" | Filter to display all processes belonging to the project |
"id:17 18 19" | Filter to display all processes with the internal Goobi |
template:123 | Filter to display all processes for which the |
template:shelfmark:123 intranda | Filter to display all processes for which the |
workpiece:intranda | Filter to display all processes for which the property of the associated |
workpiece:Artist:intranda | Filter to display all processes for which the workpiece property |
workpiece:Artist:intranda process:shelfmark:123 "project:sample project" stepDone:Imaging 456 | Filter to display all processes from the project |
processproperty:Font:fra | Filter for all processes whose |
project:Berlin |project:London | OR-Search for all processes whose |
"project:Palma de Mallorca" "|project:New York" | OR-Search for all processes whose |
"meta:TitleDocMain:1801" "|meta:TitleDocMain:1802" | Or search for all processes whose |
processdate=2021 | Search for processes whose |
processdate!=2021 | Search for processes whose |
"processdate<2020-01-01 12:00:00" | Search for processes whose |
processdate>2020-01-01 processdate<2020-12-31 | Search for processes whose |
stepdone:Scanning stepfinishdate:2021 | Search for workflow steps with the title |
stepstartdate:2021 | Search for workflow steps whose processing started in |
stepdone:Scanning "stepdone:Quality control" stepfinishdate:2021 | Search for workflow steps |
stepdone:Scanning stepfinishdate>2021-08-01 stepfinishdate<2021-08-31 | Search for workflow steps |
stepDone:Scanning processdate=2021 |processdate=2022 | Searches for processes that are created in the year 2022 or contain steps |
stepDone:Scanning (processdate=2021 |processdate=2022) | Searches for processes that contain steps |
Note: The operators <
and >
are interpreted in the background as less than or equal to
and greater than or equal to
. For example, searching for processdate>2022
will list all processes whose creation date is 2022 and later.
As you can see from the examples given above, it is possible to conduct some very complex filter-based searches by combining a wide range of parameters. Unlike the simple filters you can apply in the dialogue box, by using the correct filter syntax you can use the same parameters more than once with different values for a single search (e.g. to simultaneously retrieve both completed workflow steps and others that are still in progress).
All the parameters listed above can be combined with each other as required. Please note, however, that any parameters containing a blank space should be written inside double quotation marks.