https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36027

David Nind <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA

--- Comment #36 from David Nind <[email protected]> ---
Everything still seems to work as expected.

However, I've Failed QA as any command run generates this line in the output,
which I don't think it should:

Subroutine CheckRelationshipsLoop redefined at
misc/maintenance/search_for_data_inconsistencies.pl line 708.

Updated testing notes (from comment #25)
=====================

Testing notes (using KTD):

1. Set up data so that there are inconsistencies:
   1.1 There is already one inconsistency in the sample data, for record 369
(encoding errors)
   1.2 I created an inconsistency for patron age and patron category type:
       . koha-mysql kohadev
       . update borrowers set categorycode = "K" where borrowernumber=49;
2. Step 3, ran check with: misc/maintenance/search_for_data_inconsistencies.pl
--check-status --check-age
3. Step 4, ran check with: misc/maintenance/search_for_data_inconsistencies.pl
--skip-status
4. Step 5, ran check with: misc/maintenance/search_for_data_inconsistencies.pl
--check-age --skip-status

Updated comments (from me, comment #25)
================

I'll file separate bugs for these comments.

1. The check-status option includes checking for item type issues (as described
in the help description), but it also checks for invalid MARCXML. I think that
the MARCXML check should have its own option (--check-marcxml Check for invalid
MARCXML in bibliographic records).
   1.1 I'm not sure how hard this to do (I am not a developer).
   1.2 I'm not sure whether there are other checks in the script that are not
included in the description and have their own options.
   1.2 Instead of --check-status, --check-itemtype

2. Instead of --check-branch, use --check-library. While branch is used in the
underlying code, the terminology guidelines suggest we should use library.
(https://wiki.koha-community.org/wiki/Terminology#L)

3. Warning when you use --check-* and --skip-* options in the same command
(step 5). I've made a wording change suggestion. The current text says to me
that if you use skip and check options in the same command, the skip options
are ignored. That is, it will ignore/not run the skip options:
   . Current warning: "Warning : skip options are ignored when check options
are provided"
   . Suggested warning: "Warning: The --skip-* option(s) were ignored. Only the
--check-* options in the command were run."

4. Description and help text. I think this needs some work with formatting and
the text. I will add a follow-up patch with some suggested changes.


Additional comments (from Katrin, comment #28)
===================

Just so that these don't get lost from Katrin's comments.

1. New parameters (not blocker)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I wonder if the chosen pattern is good as it requires that we add 2 new
parameters for every check that we add to the script. 

We do have something similar in cleanup_database.pl for action logs and it
seems more logical to me. 

   --log-module       Specify which action log modules to trim. Repeatable.
   --preserve-log     Specify which action logs to exclude. Repeatable.
   --logs DAYS        purge entries from action_logs older than DAYS days.
                      Defaults to 180 days if no days specified.

So instead of a unique parameter, you can use preserve-log with different
codes.

I am not sure what is better, just putting the question out here.

2. Script should not start without -c or any parameters... (not blocker)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is something for a separate bug. But we once said that scripts should
output help when run without parameter and require a confirmation flag. 
As this can run quite a time, this still seems a good idea... 
(leaving this here for filing later)

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to