Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
Folijet Sprint 99
-
1
-
Folijet
-
Q3 2020
Description
Purpose: To provide info on why so many field of the Instance field mapping screen are not mappable
As a staff person working with Data Import field mapping profiles
I want information on why so many Instance fields are not mappable
So that I can better understand the field mapping screen
Scenarios
- Scenario 1
- Given the Field mapping profile Create-Edit screen
- When the FOLIO record type = Instance
- Then add the following sentence below the Field mapping , Instance header, and above the Administrative data accordion:
- Inactive fields cannot be mapped because they are controlled by the system or by the library's MARC-Instance mapping profile
- NOTE: the wording in the mockup is slightly different. Use the wording in the Jira description
- Scenario 2
- Ensure this story passes Accessibility testing
- Scenario 3
- Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2551 NFR: Data Import (Batch Importer for Bib Acq) & PubSub Q3 2020 Technical, NFR, & Misc bug work
-
- Closed
-