Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: are there rule cases where more than one action needs to be applied? #36

Open
jhmann opened this issue Apr 13, 2016 · 1 comment

Comments

@jhmann
Copy link

jhmann commented Apr 13, 2016

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.

@jhmann
Copy link
Author

jhmann commented Apr 15, 2016

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:
image
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:
image
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant