You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm imagining a scenario where one rule can resolve conflicts in both, say, format and mimetype, or for cases where the message property (however that is generated?) reflects the conflict, once could resolve the conflict in format/mimetype and update the message. Updating a message would require issue #35 to be resolved.
Another case where it might be useful is in updating the Puid property where they also conflict or are non-existent.
Of course, this only matters if there are cases where there are problems with multiple properties which could be resolved with a single rule. I'm not sure if those cases exist.
Just something to think about as you're redesigning the conflict rule process.
The text was updated successfully, but these errors were encountered:
I've just found such cases - although that may just be a function of how the histograms are behaving. As you can see from this picture, on the current filter both mimetype and format are showing as conflicted:
Perhaps this is related to issue #30 as per this comment? However, unlike in that issue, here looking at the Object metadata of the first object in the set shows that both the format and mimetype need to be resolved:
So this does seem to be a case where multiple actions would need to be applied. And from the sampling I did on the set, this seems to be true across this entire filtered set.
I'm imagining a scenario where one rule can resolve conflicts in both, say, format and mimetype, or for cases where the message property (however that is generated?) reflects the conflict, once could resolve the conflict in format/mimetype and update the message. Updating a message would require issue #35 to be resolved.
Another case where it might be useful is in updating the Puid property where they also conflict or are non-existent.
Of course, this only matters if there are cases where there are problems with multiple properties which could be resolved with a single rule. I'm not sure if those cases exist.
Just something to think about as you're redesigning the conflict rule process.
The text was updated successfully, but these errors were encountered: