Local and Network revisions show at same time in search results
I can see an older local version of a package in the search results along with the newer network version by doing the following steps:
1. Save new package to Local+Network
2. Edit title
3. Save only to Network
4. Launch the open dialog and see the two revisions -- the newer network one and the older local one.
This is somewhat accurate in that it captures exactly what versions are store where, but I do not think we want this behavior. Only the network (newest) revision should show. This may just be a search result merge issue.
#2 Updated by ben leinfelder almost 8 years ago
When there are many local documents, it can take a long time to check the network for newer versions of the document. I'm not yet sure how to get around this. We can't really cache the SystemMetadata where obsoletedBY is stored since SM is mutable.
We could invert it so the Network results are examined to see if there are local objects in the results that are obsolete, but we'd still be looking at a lot of recursive calls to MN.getSystemMetadata() to find out this information.
#3 Updated by ben leinfelder almost 8 years ago
Jing's idea is to process the network search results to see if the local hits are in the older versions of the network matches. This should make the open dialog perform much more quickly, but it could make network search results take even longer to appear.
#4 Updated by ben leinfelder almost 8 years ago
Now only filtering if there are network results to filter. This is an improvement, but still means we check if the network version obsoletes the local version for all local docs.
I am also thinking we should just take out the network search that happens when you use Open and are logged in. Why not just use the search panel for this? Maybe add a checkbox for "include only packages I own"