Question

How do normalization rules, merge rules, and brief level rules impact metadata import for resources purchased on Rialto?

Answer

Any changes to drools syntax (normalization rules, merge rules, brief level rules, indication rules) can be handled by the Rialto Technical Support Team. 

Following are a few examples of common changes requested:

• Can I add a local extension (9XX) MARC field upon import of MARC record?

  • Adding a 9XX to identify the e-platform origin would be an example of one use for this customization. 

• Can I define rules concerning the creation of brief records?

  • This typically applies to IZ MARC fulfillment and all physical MARC fulfillment. 

• Is it possible to configure the behavior of record matching upon order?

  • This change configures the matching behavior when a cart item matches to an in-repository MARC.

All examples listed above may require adjustments to the RialtoMatch profile, which is only accessible by technical support. This profile is designed to help differentiate between the existing Print records and the incoming Ebook orders, so that electronic records do not overlay the existing Print records. This rule is used internally at the point of purchase and matches on the ISBN. This can be augmented with any custom rules you might have for the Merge method. This profile is not visible to customers, but changes can be requested to be added any point by reaching out to support.

For assistance, please contact us via live chat or submit a support ticket here.

For more information on:

• RialtoMatch profile see Rialto Default Configurations
• Normalization rules see Working with Normalization Rules.
• Brief records see Working with Brief Record Levels.
• Working with merge rules see Working with Merge Rules.
• Configuring cataloging see Configuring Cataloging.

• Article last edited: 29-Jun-2021