kitodo-production icon indicating copy to clipboard operation
kitodo-production copied to clipboard

Cannot filter for workflow steps whose names contain spaces in parenthesis

Open aetherfaerber opened this issue 1 year ago • 0 comments

Describe the bug The process list can be filtered based on workflow steps (stepopen, stepclosed). If the steps name contains space characters within parenthesis, the list is not filtered based on the name but all processes (from the current project in case one is selected) are shown.

To Reproduce Steps to reproduce the behavior:

  1. Create a new workflow with at least three steps, give the last one a name containing parenthesis with multiple words or a space character within „Ein guter Schritt (er ist gut)“. Assign the workflow to a project and create a process for the workflow.
  2. Go to the process list and filter for processes with the second workflow step open by name (which does not contain a space character inside parenthesis).
  3. Confirm that the process is not listed as the second step is not open.
  4. Filter for processes with the step open whose name contains a space character in parenthesis.
  5. See the process (and any other processes) listed although the step is not open.

Expected behavior Steps containing a space character in parenthesis should only be displayed if the step is actually open if a filter for an open steps is applied. All other processes besides the ones with the step containing a space character in parenthesis should not be displayed.

Screenshots 9785e324-6b8e-47fb-be2a-21f2ef0b00f8 eef30ce1-03ef-49c7-a192-339865d09e03 1d166f0e-bee9-4ae5-95cd-3c437fbbee26 31dcad60-ca86-41dc-a909-77856e08a807 acf52395-eba4-41b2-a2ec-891eb466d0ea e14c009e-e7d9-4fc0-84c4-a21312756cf0 70ca5500-78a8-41ed-9392-cd9cfe5aa7b9 91c3fb2e-7354-46db-8b06-8329e67111a3

Release 3.6.0 and 3.6.1

Desktop (please complete the following information):

  • OS: Kubuntu
  • Browser: Firefox
  • Version: 122.0

Additional context We assume the string is not passed correctly to ElasticSearch. If this is an underlying issue on side of ElasticSearch this could be resolved through the move to Hibernate Search.

aetherfaerber avatar Jan 31 '24 11:01 aetherfaerber