Author Topic: Search anomaly  (Read 3020 times)

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Search anomaly
« on: June 17, 2023, 03:55:48 AM »
I have a drive named Raws copy 230612. When I search my catalog for path "Raws copy 230612" I get 0 files found. When I search for path "Raws copy" I find 1,496 files and they are all on the drive named 'Raws copy 230612'. Why are they not found in the first search? See attached screenshots.

Am I missing something obvious?

David Hoffman

Offline ahoward

  • Camera Bits Staff
  • Hero Member
  • *****
  • Posts: 973
    • View Profile
Re: Search anomaly
« Reply #1 on: June 20, 2023, 12:27:59 PM »
Maybe the pixels are just blending together due to image compression or resizing, but the second double-quote character in your first search looks quite different from the first one. Did you paste in the folder name form somewhere or did you type it out manually?

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #2 on: June 20, 2023, 01:53:35 PM »
I thought that you had it but no. It's the vertical line for the text entry point obscuring one blip of the quote mark. I've just tried again, copying it from the drive name in the finder, typing in the search term and pulling it up from the past search list with consistent results.

"Raws copy 230612" is the name of an external drive on my 2012 Mac Pro. The 1496 files found in a search for path "Raws copy" are all on that drive.

David

Offline ahoward

  • Camera Bits Staff
  • Hero Member
  • *****
  • Posts: 973
    • View Profile
Re: Search anomaly
« Reply #3 on: June 20, 2023, 02:10:49 PM »
If you just search for the numeric portion of the search that you are performing, does the search return the images in the catalog from that drive?

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #4 on: June 20, 2023, 11:27:26 PM »
The search

path "230612"

finds zero items. Same without the quotes.

230612 refers to the date June 12 2023 and the only item in the catalog (file, folder, drive) with that term in the name is the external drive named Raws copy 230612.

David

Offline ahoward

  • Camera Bits Staff
  • Hero Member
  • *****
  • Posts: 973
    • View Profile
Re: Search anomaly
« Reply #5 on: June 21, 2023, 11:04:06 AM »
Please open Mac Terminal and enter the following command:

ls /Volumes

Press return on your keyboard and the output should be the drives that are mounted to your computer. Paste the output in your reply.

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #6 on: June 21, 2023, 11:18:48 AM »
Result below. It corresponds with what I'm seeing.

[192:~] davidhoffman% ls /Volumes
Macintosh SSD      Pinky         Raws copy 230612
Mercury         Popeye         Scratch
Perky         RAWs

Offline ahoward

  • Camera Bits Staff
  • Hero Member
  • *****
  • Posts: 973
    • View Profile
Re: Search anomaly
« Reply #7 on: June 21, 2023, 03:51:03 PM »
Thanks. We are not sure why you are having this issue. I tried formatting a drive and named it similarly and had no issue with pulling up results. Perhaps the best next step is for us to set up a phone call so we can troubleshoot this issue in real-time rather than on the forum. Usually that reveals something that I would otherwise not think to ask about. Feel free to email support@camerabits.com to set something up.

Best regards,

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #8 on: June 23, 2023, 12:15:58 AM »
Thanks, I'd like to resolve this problem and I will contact support but my priority is to get the catalog back into full use after the drive rebuild. If the issue remains after this I'll mail support next week.

In the meantime I have one question. I have 2 catalogs that both contain images on a drive "Raws copy 230612". A folder on that drive is mirrored on another drive "Raws". If, in catalog 1, I reset the location of that folder to drive "Raws" will catalog 2 still refer to the files in the folder on "Raws copy 230612" or will the paths in that catalog also be reset?

Re the search problem - I tried the same search with that same drive on a temporary catalog on my Macbook Pro and there was no problem, all worked as expected.

David

Offline Bob Russell

  • Camera Bits Staff
  • Sr. Member
  • *****
  • Posts: 276
    • View Profile
    • Camera Bits, Inc.
Re: Search anomaly
« Reply #9 on: June 23, 2023, 01:58:46 PM »
Hi David,

When you Update the folder location in one catalog, Photo Mechanic will also update any other catalog(s) that have included that folder. Use the Forget option in the Catalog Management dialog, for each catalog that includes the folder to be relocated, if you do not want their folder path to be updated. Once you have Updated the folder location in the one catalog, you can Reintegrate the forgotten catalog(s).

regards,

--Bob

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #10 on: June 24, 2023, 12:05:34 AM »
Thanks Bob, that's what I needed to know.
David

Offline DavidHoffmanuk

  • Sr. Member
  • ****
  • Posts: 315
    • View Profile
Re: Search anomaly
« Reply #11 on: July 03, 2023, 09:54:05 AM »
Thanks. We are not sure why you are having this issue. I tried formatting a drive and named it similarly and had no issue with pulling up results. Perhaps the best next step is for us to set up a phone call so we can troubleshoot this issue in real-time rather than on the forum. Usually that reveals something that I would otherwise not think to ask about. Feel free to email support@camerabits.com to set something up.

Best regards,

I finally got all the files restored to the 'RAWs' drive and back in the catalog. I removed the 'Raws copy 230612' drive's files from my catalog. I made another catalog with just the 'Raws copy 230612' drive. The search now works as expected on both drives whether I have both catalogs active or just either one. I'm mystified but relieved. I did have debugging on while this problem was present. Would the log be of any interest?

David