Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Overview
The CLI tool is designed to inject perform following changes:
Inject new mapping rules for
...
the following fields:
010$z Canceled LCCN.
008 Date type.
Inject new mapping rules with the following Subject types based on field number:
653 - Uncontrolled
654 - Faceted Topical Terms
656 - Occupation
657 - Function
658 - Curriculum Objective
662 - Hierarchical Place Name
688 - Type of Entity Unspecified
Update default mapping for Subject types based on field
600 - Personal name
610 - Corporate name
611 - Meeting name
630 - Uniform title
647 - Named event
648 - Chronological term
650 - Topical term
651 - Geographic name
655 - Genre/Form
The CLI tool/script does not change existing mapping rules on the target host, but it only extends existing rules.
Script execution
CLI tool executable artifact for Ramsons: folio-update-bib
View file | ||
---|---|---|
|
|
...
Create JSON file with configuration (see: configuration file)
Open terminal (Mac OS or UNIX Systems) or Power shell (Windows)
Go to the folder where the CLI tool executable artifact is located
Run the CLI tool/script with the configuration file path parameter (just file name if the script is located in the same folder)
...
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:
|
for consortia tenants add, additional centralTenant field in configuration.json
|