Jira Legacy |
---|
server | System JiraJIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODSOURMAN-1081 |
---|
|
Overview
This CLI tool has been created to detect mapping rules customizations for the "classifications" (050, 060, 082, 090 MARC fields) and "contributors" (100, 110, 111, 700, 710, 711, 720 MARC fields) instance fields.
The CLI tool/script does not change existing mapping rules on the target host but merely lists MARC fields whose mapping rules have been customized/changed by a user.
Script execution
CLI tool executable artifact for mod-source-record-manager Poppy release: folio-detect-mapping-rules-customizations.jar
Code Block |
---|
|
java -jar folio-detect-mapping-rules-customizations.jar configuration.json |
...
CLI tool/script requirements:
In order to run the CLI tool you need the following:
- 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)
...
In case there are no customizations in mapping rules for the "classifications" (050, 060, 082, 090 MARC fields) and "contributors" (100, 110, 111, 700, 710, 711, 720 MARC fields) instance fields, then the CLI tool will print an appropriate message.
Configuration file
Anchor |
---|
| configuration_file |
---|
| 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:
Code Block |
---|
|
{
"okapiUrl": "https://folio-snapshot-okapi.dev.folio.org",
"tenant": "diku",
"username": "admin",
"password": "secret"
} |
Related Jira tickets
Jira Legacy |
---|
server | System JiraJIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICORE-347 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDICORE-323 |
---|
|
...