Improve Booleian searching in repository by including 'not' option
Currently there is no option to use a 'not' function in a repository search, there is only 'and' & 'or'. The ability to exclude certain records from a search is vital to enable correct records to be isolated for editing/updating. Not having the 'not' option makes it very difficult to narrow down results.

In addition to our Product Manager Moshe Shechter’s comments on this idea of a few months back, we would like to add the following:
Alma’s search indexes have been designed and built to provide a whole new set of possibilities for searching for inventory based on the full set of bibliographic details and indexes. As a result of this combined enriched bibliographic and inventory search index, certain queries which retrieve the bibliographic titles but also use inventory indexes, can lead to non-intuitive results when used in conjunction with NOT operations. An example of this is the search for titles that don’t have items in library A. If a title has items in library B and in library A, it will still be retrieved. This is a correct result as there is an item that matched the search query, but it is not intuitive to the staff user.
Ex Libris will be developing a related search function for NERS (“New Enhancement Request System”) whereby it will be possible to search using ‘contains’, ‘does not contain’, ‘is empty’, ‘is not empty’, ‘begins with’ for a prioritized list (provided by NERS) of 10 indexes. We believe that this will give the functionality very close to the Boolean ‘not’ function.
-
As part of NERS #7948, Add “Not contains” or “Not equals” to Alma Titles and Inventory Search Indexes Where "Contains" or "Equals" Currently Exist, we will be adding not operators to search indexes where this was not available.
Please note that, since Alma offers combined enriched bibliographic and inventory search index, and it is possible to search titles by inventory information, the behavior of queries which retrieve bibliographic titles using inventory indexes with NOT operators will be as follows: When searching with a lower-level index "not contains" or "not equals", the search will retrieve all results where one or more inventory entities match the query. For example, searching for titles with location "not equals" library A will retrieve a title which has items in both library B and library A, as there is an item that matched the search query.
This behavior was agreed upon with the NERS representatives. -
Mars Tertop commented
Upgrading the level of customer satisfaction is the goal of this service. The https://cvwritingservicesuk.com invests much time in understanding the requirement to provide the best results. The experts on the site enable a newbie to choose the best writer. By discussing the project earlier
-
LANG, Wolf-dieter commented
referring to Moshes explanation from May 01, 2016 16:42,
Can you elaborate with specific queries you’re looking into implementing? :
The Austrian library network uses a network zone for shared cataloging. In the Gesamtkatalog (http://aleph23-prod-acc.obvsg.at/F/LVXMALJ2A2UTVP8DKB1BURDRUD9TAEH473MIA5F1PJ9JHSSCUS-03329?func=find-c-0&local_base=acc01)
i can search for books of a certain publisher, which have NOT arrived in my legal deposit library, e.g. wve=Loecker AND wyr=2018 NOT wnb=OeB*
In ALMA I cannot create search sets for the Network Zone (this is only possible in aInstitutional Zone IZ)Is there a solution for this problem (btw this is known since 2014)
regards
wolf -
mcorby commented
Using the 'not' option is critical for database cleanup. When I work on headings cleanup, I often need to find the bibliographic records that have "x", but not "y". For example, if a heading needs to have a fuller form of the name, I would input find Xxxxx Xxxxx, but not Xxx. Using a "not" search is critical for determining if all headings have the correct form of the date, to determine if death dates have been added, etc. The cleanup work is somewhat better now that we have the browse headings options, but we still need booleian not.
-
D. Moynihan commented
The ability to create a single logical set for use by student employees doing inventory at closing would be ideal as our desk machines are secured and cannot download/upload files for combining sets.
-
Chris Sloan commented
I find using the combine sets option unnecessarily complicated and involved. A "Not", or "Is not empty" option would streamline so many tasks
-
Stefan Kandera commented
Another important reason to have the 'not' option is, that by now you can't create logical sets with exclusive criteria from the 'not' operator. Once you combine sets they become 'itemized'. This is extremely limiting for OAI publishing.
-
Israel Yanez commented
I didn't submit this idea, but I gave it 3 votes. Sometimes it is easier to exclude certain values and without a NOT operator or a "does not equal" or "does not contain" criteria, it makes it very difficult. The combine sets approach should be viewed as a temporary workaround. The AND NOT operator (used for exclusion) is a major part of Boolean logic. As such, it should an option in advanced search.
A hypothetical example, let's say I want to do an electronic titles search, but I want to exclude titles from ebrary Academic Complete. I should be able to set as a criteria for the collection name: "AND NOT" ebrary Academic Complete or "does not equal" ebrary Academic Complete or "does not contain" ebrary Academic Complete. And I should be able to do this with an advanced search, instead of having to do two separate queries, save sets, and then combine the sets.
-
Alma’s indexes are well optimized for positive and multi-tier search queries that involve different parts of the repository, such as search queries that include bibliographic data as well as inventory related attributes.
Alma also supports searches on certain indexes that check for an ‘empty’ value, i.e. records that do not have a specific field populated. This can be achieved by searching using the Advanced Search ‘Is Empty’ attribute. In addition, Alma also supports the ‘is not’ operator on specific, controlled list based indexes e.g. records where the language is not English.
This is described in the “Empty Indexes and ‘Is Not’ Searches” section of the “All You Wanted To Know About Repository Searching in Alma” document. See https://knowledge.exlibrisgroup.com/@api/deki/files/39152/All_You_Wanted_To_Know_About_Repository_Searching_in_Alma.pdf.
In addition, ‘Is Not’ searching may be achieved by using the Combine Sets option -
1. Search for the required titles and save the search result as a set using the ‘Save Query’ option
2. Search for the ‘not’ required titles and save the search result as a set using the ‘Save Query’ option
3. Use the ‘Combine sets’ option that is available in the ‘Manage Sets’ menu to create a new set of titles that are in found in set 1 but not in set 2More information on search queries and sets management can be found at - http://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/Resource_Management/020Using_the_Repository_Search/Managing_Search_Queries_and_Sets
Can you elaborate with specific queries you’re looking into implementing?
-
Jaymie Turner commented
This would be extremely helpful in both the advanced repository searches and when creating sets for both orders and resource management.
-
Alasdair MacDonald commented
Currently, the word "not" appears to be treated as a logic function in the Search External Resources menu, even when doing a phrase search. It would be great if NOT were available as a search option but treated as a word in the search box.