Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Some Source=MARC records are not accessible via quickMARC

Description

Overview: When trying to edit records in quickMARC, some will not open, even though the source = MARC and the user can View source from the Instance

Current workaround: None

Steps to Reproduce:

  1. Log into FOLIO-snapshot-load as diku_admin

  2. Go to Data Import and import the attached file using the secret button

  3. Go to Inventory

  4. Do not enter a search; instead filter by Source = MARC

  5. Click View source and make sure you can view the source record

  6. Click "Edit in quickMARC"

Expected Results: the MARC record should open in quickMARC edit screen

Actual Results: Sometimes there is a red toast saying that the record could not be loaded into the quickMARC edit screen

See attached video. I think this was happening a while ago, but we fixed it. I've marked it as a regression. I think this is a QM bug rather than an SRS bug, but if it belongs to SRS, please reassign to Folijet and alert Ann-Marie. Thank you!

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Viachaslau KhandramaiOctober 26, 2020 at 10:08 AM

Verified on https://bugfest-honeysuckle.folio.ebsco.com. Record can be opened and saved.

Viachaslau KhandramaiOctober 23, 2020 at 10:15 AM

thank you very much! We have already updated schemas and released QuickMARC Bugfix.

Kateryna SenchenkoOctober 23, 2020 at 8:46 AM

Hi ,
It was an oversight from our side. We do have a point to create a check list to follow in case of schemas update. I'll make sure we add this checklist to the raml-storage doc and ensure we go through it every time a PR is merged. This should prevent such things from happening again.

Victoria_SmelovaOctober 23, 2020 at 8:11 AM

, if schema was updated, I guess the corresponding interface version should have been updated as well. Otherwise all the other teams can hardly know about some schema changes. Could you clarify if my understanding is correct and for some reason interface was not updated, thus Firebird team was not aware about any schema changes affecting quickMARC?

Viachaslau KhandramaiOctober 23, 2020 at 8:04 AM

Thank you, , I have already updated QM reference to the actual schemas.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Firebird

Parent

Fix versions

Release

Q3 2020 Bug Fix

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 20, 2020 at 9:05 PM
Updated November 2, 2020 at 7:56 AM
Resolved October 23, 2020 at 10:17 AM
TestRail: Cases
TestRail: Runs