Bidge Collections are Content-Free

[Jack]

In all past restarts, Bridge opened with all collections repopulated. This time, however, that did not occur. Path names to image folders refer to my user name, rather than to the external drive where the images actually reside.

I _can_ manually recreate the some of the important collections, but am not optimistic about survival after a restart/shutdown.

After posting this I will, however, make a complete shutdown, see if any improvement occurs, and will post a reply here.

Thanks in advance.

[Jack]

After shutdown and restart, there is still no content in Bridge collections residing i external drives, although collections residing on my local system _are_ surviving. Problem is, collection derived from external drives are too big for local hard drive. I need access to those via external drive.

[Jack]

Further, strange results: a query to fetch all images in which all metadata contain __ or all metadata contain __, and so forth, a total of (7) 'or' clauses, yields far more than the desired set, perhaps close to the entire population. I have no clue what is going on here. Everything had been behaving so well in the past has gone . . . berserk. I don't know how else to describe it.

Next step may be to try to refine the query to a single property, that I can find, and/or perhaps revise the entire dataset so that it will be more easily/reliably searchable, etc.

[Jack]

I think I have this resolved. For some reason a single attribute (among the seven 'or's) was returning the entire collection. When I changed that (from first name to last name), the result was much more 'civilized'.  The seven-clause 'or' query, which had succeeded in the past, was now breaking. I found that I can build individual sub-collections using multiple, single, queries, omitting duplicates and otherwise refining the result, prior to adding each result to the main collection. Much more orderly. So, I have completely rebuilt the original collection, and made it much more robust.