Ahh okay . Then the ability to search with/without spaces can be handled in Christine's normalization requirements then. 

Hey  
Thank you!
All good about exact match for the 010 $a / 010 $z
But search by "naturalID" field was not added to search query in scope of current ticket. 
Example of used search query: "lccn="test"

Hey   - I believe   is writing a requirement to support normalizing LCCN search to support these various scenarios for "Q" release. 

For this story - I expect the user to select this search option and it is an exact match to what is stored for the 010 $a / 010 $z or what is stored as the naturalID.

Hi and  

was resolved, so now we can deal with this requirement "Trim leading and trailing spaces."
Looks like requirements for "LCCN" search option should be: "MARC authority record should be found using a query without spaces when "LCCN" (010 $a or $z) has (leading, internal, trailing) spaces".
For example:

• LCCN in 010 $a "n 79066095" - one prefix between prefix and value

• Users should be able to find an exact match with the following queries:

  • "n 79066095" (all spaces included)

  • "n79066095" (removing space between the prefix and the number)

• LCCN in 010 $a "n  79066095" - two spaces between prefix and value

• Users should be able to find an exact match with the following queries:

  • "n  79066095" (all spaces included)

  • "n79066095" (removing space between the prefix and the number)
    Question: Should user find record with query which has only 1 space? - "n 79066095"

• LCCN in 010 $a " n 79066095 " - one leading, one internal, one trailing space

• Users should be able to find an exact match with the following queries:

  • " n 79066095 " (all spaces included)

  • "n79066095" (removing space between the prefix and the number)
    Question: Should user find record with query which has only 1 space? - "n 79066095" or " n79066095"

FYI: looks like trim of leading and trailing spaces already supported. See screenshot:

So,  
Could you please summarize it and create a story in mod-search project?

Hey . For this requirement,  LCCN only searches what is stored in 010 $a and 010 $z. We need a mod-search requirement to search LCCN with all spaces removed (leading, internal, trailing) that it would still return an exact match.