Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODSOURMAN-1052

...

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

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDICORE-323
).

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.

...

  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 argument path parameter (just file name if the script is located in the same folder)

...

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 
Anchor
configurationfile
configurationfile

...