Page Comparison

...

1. field:  one of the defined field from https://github.com/folio-org/mod-gobi/blob/master/src/main/resources/mapping.json → properties.field
2. dataSource.default: default value
3. datasource.translation: defined and implemented method from https://github.com/folio-org/mod-gobi/blob/master/src/main/resources/mapping.json → properties.dataSource.properties.translation

How to map Vendor Code for libraries with unique and or multiple organization records

If there is NO "from" data source then FOLIO relies on the default value to look up the correct organization to use as a vendor. For the look up to work the default value must match the code of an existing organization in FOLIO that has a status of active and IS a vendor.

If the institution wants to have multiple Vendors used for orders created via the GOBI API. The library must mapped a local data field on the GOBI side to send a selected code that can be used instead of the default. In the example below the configuration expects to get a vendor code from the incoming xml file in the local data 4 field. If there is nothing present in that field FOLIO will fall back on the default value to try and find a valid organization for the incoming orders

 {
	"field": "VENDOR",
	"dataSource": {
		"from": "//LocalData[Description='LocalData4']/Value"
		"default": "GOBI",
		"translation": "lookupOrganization",
		"translateDefault": true
	}
}

Supported methods

Defined in the https://github.com/folio-org/mod-gobi/blob/master/src/main/resources/mapping.json → properties.dataSource.properties.translation

...