[Resolved] Tags missing on Network Drive Quick Search

[neil9090]

I have a networked drive Z:
I have a directory called Z:\test
I have tagged items within the Z:\test
If I use the address bar and type Z:\Test? <return> (different case than the actually case on the filesystem) the search works, but all of the tags created under Z:\test do not match and fail to show.

This appears only to effect network drive connect, i.e. it works ok on C:\Test? or C:\test?

[admin]

Check out the database contents using
Tools | List Management | Tagged Items...

Probably the paths are listed in UNC format. Automatic conversion is not supported for performance reasons.

[neil9090]

Yep, as I thought in the tag list (tags.dat)
Files tags are stored in the source file system case.
e.g.
Z:\Test\New Text File.txt|0|test||||||

Thus when Z:\test? is entered in address bar the results must be using the text in the address bar (wrong case) in conjunction with the tag lookups
Could you resolve the folder existence to ensure the correct case is being used perhaps?

[admin]

This will fix the case:

Configuration / Tags / Options / Database Check...

[neil9090]

Extract from Tags.dat
Z:\Test\New Text File (2).txt|0|testUpper||||||
Z:\Test\New Text File 3.txt|0|testUpper||||||
Z:\test\New Text File (2).txt|0|test3||||||

The folder is stored Z:\Test is manually navigated via clicks etc... but if I use a category item with goto Z:\test it responds with the folder Z:\Test

if I use an item to also do a quick filter Z:\test? it returns only the tag with Z:\test\New Text File (2).txt <not the other entries tagged items

but if I use the Z:\test? and then add a tag it adds and entry in the same case as the address bar i.e. Z:\test\.. (this would appear to be incorrect)

I guess its something to do with adding tags when the address bar doesn't have the correct case.
I know the tags.dat is binary matched in case etc.. but I expect the tagging process would identify the correct case when adding/editing a case.

[admin]

Are you maybe using a Locked Tree? This is the only way I can reproduce it at the moment.

Anyway, it's one way too much -- a clear bug! Fix comes...

[neil9090]

Nope,
Haven't used a locked tree yet...

Thanks Don

[admin]

Okay, I found another way (to end up with paths with wrong capitalization): Quick Search! I guess that was your way.