Summary: | Add help to search_for_data_inconsistencies.pl | ||
---|---|---|---|
Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
Component: | Command-line Utilities | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | magnus, robin |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37725 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143 |
||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Katrin Fischer
2022-07-02 21:52:25 UTC
Should we add a parameter like "--run" to make the script do it's actual job? So that if it is run without parameters or with "-h" it just prints the help/usage from the POD and then exits? (In reply to Magnus Enger from comment #1) > Should we add a parameter like "--run" to make the script do it's actual > job? So that if it is run without parameters or with "-h" it just prints the > help/usage from the POD and then exits? I feel like we have another pending bug changing a lot of these params. But if we do, -c | --confirm would be preferred (for more consistency) |