Suppression enhancement for FOLIO instances in Locate DCB
Description
Attachments
2
is duplicated by
Activity
Show:
Tim Auger March 27, 2025 at 5:30 PM
the updated MARC view of the FOLIO instance with the addition of a 999$t1
Tim Auger March 27, 2025 at 5:27 PM
In the staging environment, I’ve updated this record in FOLIO within the mobius-staging environment. I have confirmed that prior to updating the record with a MARC 999$t1 should be suppressed in the DCB union catalog.
Ian Ibbotson (Use this one) March 27, 2025 at 4:48 PM
Numerous changes in here - FOLIO OAI Ingest Source now overrides inferSuppression from it’s superclass to allow FOLIO specific OAI feeds to react to 999$t=1 which is an in record indication of suppression. Adding test cases now
Jag Goraya November 1, 2024 at 11:42 AM
Can this not be handled through NONCIRC material type mappings? If not, is this something you can configure a suppression rule for using the existing bib suppression ruleset mechanism?
Details
Assignee
UnassignedUnassignedReporter
Tim AugerTim AugerPriority
TBD
Details
Details
Assignee
Unassigned
UnassignedReporter
Tim Auger
Tim AugerPriority
TBDCreated October 31, 2024 at 7:02 PM
Updated March 27, 2025 at 5:30 PM
Background
Currently, FOLIO member libraries can suppress instance records from being displayed OpenRS Locate DCB by the same “suppress from discovery” option that local Locate and discovery systems. In addition to this, libraries have large numbers of electronic resources that they’d like to display in local OPAC and Discovery but do not want to display in the OpenRS union catalog because of access and usage restrictions.
Initially, we considered the use of statcode but there are technical challenges with that solution. So, instead, customers would like to use a MARC 9xx field to store data flagging the instance for suppression in OpenRS Locate DCB. This would be a simple value in text format or whatever is agreeable by stakeholders. This value will be consistently applied in a single tenant so, for example, “s” is in a single subfield within a single MARC field. No need for transforms of the data nor any other action taken than suppression.
cc: