As of Ramsons release, Subject types & Subject sources can now be indexed for display on Instance records in Inventory. This page will document default mappings, customization settings, and other details.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Default Mappings
Instance default mapping now includes the following coverage for Subject type and Subject source.
Panel | ||
---|---|---|
| ||
Subject type default mappingsSubject Type mapping is based on the 6xx field used for subject details in a MARC record (e.g.
|
Panel | ||
---|---|---|
| ||
Subject source default mappingsSubject source mapping is based on the value, 0 through 7, of the 2nd indicator in the subject line of a MARC record (e.g.
*Note: When 2nd indicator 7 is present, the system will look to match the value in subfield 2 with a corresponding custom Subject source as noted in Settings > Inventory.
|
Settings
Subject type and Subject source options can be controlled from the Inventory area of the Settings module. Please note, FOLIO users will need the following permissions in order to make adjustments to Subject type & Subject source settings:
Settings (Inventory): Create, edit, delete subject types
Settings (Inventory): Create, edit, delete subject sources
Panel | ||
---|---|---|
| ||
Subject type settingsSubject type settings can be found in Settings > Inventory > Subject types.
|
Panel | ||
---|---|---|
| ||
Subject source settingsSubject source settings can be found in Settings > Inventory > Subject sources.
|
Subject display in Inventory
Panel | ||
---|---|---|
| ||
Instance ViewSubject source & Subject type will display under the ‘Subjects’ accordion of an Instance, alongside corresponding Subject headings |
Panel | ||
---|---|---|
| ||
Instance Edit/CreateFor Source=FOLIO records, these fields can also be filled for during Create/Edit Instances processing |
Additional Information
The functionality described above was introduced in Ramsons release.
Work to support this functionality was completed by Folijet and Spitfire teams via the following projects:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4445 Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-3965
More information on requirements and other details in regarding this implementation can be found here:
Lref gdrive file url https://docs.google.com/presentation/d/100rtkp_fjyP4dk0s-_yJTNUZVm9fsxqqDyAq0qIAVYk/edit?usp=sharing