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

Feature suggestion: command add --dry-run #12

Closed
jneubert opened this issue Dec 28, 2016 · 1 comment
Closed

Feature suggestion: command add --dry-run #12

jneubert opened this issue Dec 28, 2016 · 1 comment
Milestone

Comments

@jneubert
Copy link
Collaborator

jneubert commented Dec 28, 2016

When I have an externally crafted mapping file, I currently cannot see a way to evaluate which of these mappings would "work" for wikidata - meaning: have a matching property value for the WDSOURCEPROPERTY column. The diff command does not provide this, the description of the not-yet-implemented check command seems to aim at a different use case.

An add --dry-run could provide the information where a WDTARGETPROPERTY would be added (plus warnings, where a different WDTARGETPROPERTY value is already attached, plus perhaps - with --verbose - messages where the actual property value is already in place).

In production use, the function would be very helpful to check input files in advance and avoid costly mistakes. I suppose, it could be useful in the development of wdmaper, too, because it can be run on live data again and again.

@nichtich nichtich modified the milestone: 0.1.0 Jan 3, 2017
@nichtich
Copy link
Member

already implemented (but not used as long as #24 has not been implemented)

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

No branches or pull requests

2 participants