Uploaded image for project: 'mod-erm-usage-harvester'
  1. mod-erm-usage-harvester
  2. MODEUSHARV-32

Reports without report items should be considered as failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: TBD
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.0.1
    • Labels:
      None
    • Template:
    • Sprint:
      Leipzig Sprint 111
    • Development Team:
      Leipzig
    • Release:
      R1 2021 Bug Fix

      Description

      Scope:

      The harvester should validate a report before saving, to make sure that at least one report item is included.

      If the report does not contain any report items, it should be handled as failed, flagged accordingly and provide an error info message like "No report items."

       

      Background:

      Currently, for several reasons reports appear in the system that seem to be "empty", but are marked as successfully harvested.

      This is caused e.g. by providers that do not comply exactly to the standard, because they include a report header with an exception message. So instead of displaying the error message like "No valid customer id", Folio stores the report according to the information provided in the header and handles it as successfully harvested. 

      As a result, the user can never be sure if a report marked as successfully harvested really has been downloaded.

      As the eUsage havester directly relies on the sushi specification, there is no sensible way to handle such incorrect reports. Users should contact the provider.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Tino Ryll Tino Ryll
                Reporter:
                annikadomin Annika Schröer
                Tester Assignee:
                Annika Schröer Annika Schröer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases