[Koha-bugs] [Bug 30520] Command line stage and import broken since 21.11.

[bugzilla-daemon at bugs.koha-community.org]

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

David Nind <david at davidnind.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david at davidnind.com

--- Comment #3 from David Nind <david at davidnind.com> ---
Hi Andreas.

I would like to test (using koha-testing-docker), but I am not familiar enough
with the importing records from the command line using misc/stage_file.pl and
misc/commit_file.pl.

Are you able to provide a test plan for this that has some more detail?

I had a go, but there are some steps I'm not sure how to do in steps 1 and 2:

1. Stage and import a record using the staff interface (this should work
successfully both before and after the patch is applied):
   . Have a sample file with records (for example, export some records from
Koha with these settings, change the title in the file)
     . 
     . 
     => Record successfully imported and record updated with new title

2. Stage and import the records using the command line:
     . Stage the records for importing with these settings: perl
misc/stage_file.pl --file koha-bz30520-test.mrc --add-items (notes: default
--match rule is to match to ISBN or title; default action is to replace) 
     . Identify the batch number of the staged records: perl
misc/commit_file.pl --list-batches (or lookup in the staff interface: Tools >
Catalog > Staged MARC record management)
     . Commit the records for importing with these settings (where # = the
batch numbere): perl misc/commit_file.pl --batch-number # --framework BK 
   . What the "crash" or "broken" looks like - error message, error in log
files, silent fail, etc.

3. Apply the patch.

4. Repeat steps 1 and 2.

5. Expected result: records are successfully staged and imported - search for
XYZ record, should find.

6. Sign off!

Also, presumably if you use the staff interface you are already logged in, so
it won't produce an error? Or is this just to check that records can still be
successfully staged and committed  using the staff interface after the patch is
applied?

David

-- 
You are receiving this mail because:
You are watching all bug changes.