We would like to have a facetable boolean field in the Elasticsearch index to quickly filter records that have a link to an electronic resource in 856$u. The facets should have labels that makes the purpose clear. We can use "Digitally available" and "Only in print" for the negative.
Created attachment 147769 [details] [review] Bug 33139 Added "has e-resource" facet for Elasticsearch
Created attachment 147770 [details] [review] Bug 33139 Map boolean field has-eresource to MARC21 856$u
Created attachment 147771 [details] [review] Bug 33139 Map boolean field has-eresource to MARC21 856$u Sponsored-by: VTI, Statens väg- och transportforskningsinstitut
Created attachment 147772 [details] [review] Bug 33139 Map boolean field has-eresource to MARC21 856$u Sponsored-by: VTI, Statens väg- och transportforskningsinstitut
856 can hold a lot of types of e-resources. Some might only be used for scans of TOCs or a front cover scan. I feel like this might be more useful if also the indicator could be taken into account: https://www.loc.gov/marc/bibliographic/bd856.html It looks like second indicator 0 or empty (and maybe 3 and 4) could be useful and would not hurt libraries not setting it.
(In reply to Katrin Fischer from comment #5) > 856 can hold a lot of types of e-resources. Some might only be used for > scans of TOCs or a front cover scan. Yeah there can be a lot of links in 856$u that are not really e-resources so I'm not sure about this one...
Currently indicators cannot be specified in the field mappings. We should specify some syntax for doing this, though. Maybe: has-eresource: label: has-eresource mandatory: ~ mappings: - facet: 1 marc_field: 856[14,]u marc_type: marc21 sort: ~ suggestible: '' - facet: 1 marc_field: 856[7,02]u marc_type: marc21 sort: ~ suggestible: '' opac: 1 staff_client: 1 type: boolean Or: has-eresource: label: has-eresource mandatory: ~ mappings: - facet: 1 marc_field: 856u indicator1: "14" marc_type: marc21 sort: ~ suggestible: '' - facet: 1 marc_field: 856u indicator1: "7" indicator2: "02" marc_type: marc21 sort: ~ suggestible: '' opac: 1 staff_client: 1 type: boolean But this should be a separate issue.
No longer applies cleanly in current master.