This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| 6000_case_study:0400_configuration:0700_operations:0500_find_item [2026/08/13 00:55] – ↷ Page moved from docs:6000_case_study:0400_configuration:0700_operations:0500_find_item to 6000_case_study:0400_configuration:0700_operations:0500_find_item localdev | 6000_case_study:0400_configuration:0700_operations:0500_find_item [2026/08/13 00:55] (current) – ↷ Links adapted because of a move operation localdev |
|---|
| ====== "Find item" operation ====== | ====== "Find item" operation ====== |
| |
| This operation is similar to the "[[docs:6000_case_study:0400_configuration:0700_operations:0200_find_member|Find member]]" operation. We could define the ''Item'' query that would find an item by author, title and code. In this case, however, we will give different categories of users different abilities to perform a search on items. Operators will have the ability to search by //any// attribute of the ''Item'' object using the form of the ''Item'' object. If an operator enters any information in any field on the form the system will perform a search based on the entered information only, ignoring any blank fields. For more details on how this works see "[[2000_concepts:0600_data_retrieval:0400_form_driven_queries|searching for data using forms]]". | This operation is similar to the "[[6000_case_study:0400_configuration:0700_operations:0200_find_member|Find member]]" operation. We could define the ''Item'' query that would find an item by author, title and code. In this case, however, we will give different categories of users different abilities to perform a search on items. Operators will have the ability to search by //any// attribute of the ''Item'' object using the form of the ''Item'' object. If an operator enters any information in any field on the form the system will perform a search based on the entered information only, ignoring any blank fields. For more details on how this works see "[[2000_concepts:0600_data_retrieval:0400_form_driven_queries|searching for data using forms]]". |
| |
| To give operators the ability to perform the form-based search we will configure a query called "Item using form". When adding this query we will click on the "Use form" property in the list of query properties and then select the form of the Item object to use. This will indicate that the query will not have any conditions – all conditions will be determined at run time when a user fills in the query form. | To give operators the ability to perform the form-based search we will configure a query called "Item using form". When adding this query we will click on the "Use form" property in the list of query properties and then select the form of the Item object to use. This will indicate that the query will not have any conditions – all conditions will be determined at run time when a user fills in the query form. |
| |
| We will also define the "Item" query that will search items by author, title and code – we will use this query for members only (we will cover this later). We can also allow operators to use this method as an alternative to a form-based search. Configuring such a query is very similar to configuring the "[[docs:6000_case_study:0400_configuration:0700_operations:0200_find_member|Member]]" query. | We will also define the "Item" query that will search items by author, title and code – we will use this query for members only (we will cover this later). We can also allow operators to use this method as an alternative to a form-based search. Configuring such a query is very similar to configuring the "[[6000_case_study:0400_configuration:0700_operations:0200_find_member|Member]]" query. |
| |