Skip to end of banner
Go to start of banner

Update of mapping rules for the 050, 060, 082, 090 fields to adjust mapping for the classification field

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

MODSOURMAN-1052 - Getting issue details... STATUS

Overview

This CLI tool has been created to apply MARC-to-Instance mapping rules updates for the instance "classification" filed that were introduced for Poppy release (see MODDICORE-323 - Getting issue details... STATUS ).

Note that this CLI tool/script does NOT update existing Inventory Instances based on the updated mapping rules. The revised rules will only apply to Source = MARC Instances that are created or updated after the mapping rules changes are made. To refresh all existing instances against the updated rules, libraries will need to run a separate script. This refresh script will take a long time if the library has many instances.

Script execution

CLI tool executable artifact for Poppy: folio-mapping-rules-update-poppy.jar

java -jar folio-mapping-rules-update-poppy.jar configuration.json

In order to run the CLI tool you need the following:

  1. Create JSON file with configuration (see: configuration file )
  2. Open terminal (Mac OS or UNIX Systems) or Power shell (Windows) 
  3. Go to the folder where the CLI tool executable artifact is located
  4. Run the CLI tool/script with the configuration file path parameter (just file name if the script is located in the same folder)

CLI tool/script requirements:

  • Java 17



The CLI tool/script does not update mapping rules for the MARC fields whose mapping has been customized/changed by a user. In this case script will print MARC fields for which mapping rules could not be updated, and will suggest updating rules for such MARC fields manually using this guidance.


Configuration file 

  • okapiUrl          - your library okapi url. (Can be seen in the app settings → software versions → okapi services → okapi)
  • tenant             - target tenant
  • username        - admin user name
  • password        - admin user name password

Configuration file example:

{
  "okapiUrl": "https://folio-snapshot-okapi.dev.folio.org",
  "tenant": "diku",
  "username": "admin",
  "password": "secret"
}
  • No labels