-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR - Could not find material type #47
Comments
Doing some triage... it looks like the app is checking the material type against a preconfigured array in Constants. folio-order-import-tool/src/main/java/org/olf/folio/order/listeners/ConfigurationCheck.java Line 333 in 16fd746
And that array doesn't include "physical" as a type. I see that there's a method in the default MarcToFolio mapping materialTypeId() which uses that map. folio-order-import-tool/src/main/java/org/olf/folio/order/mapping/MarcToFolio.java Line 602 in f1e65fc
It's overridden in the sigma mapping to actually query FOLIO for possible material types. folio-order-import-tool/src/main/java/org/olf/folio/order/mapping/MarcMapSigma.java Line 58 in f1e65fc
But a) you're using the default (chi) mapping and b) that function doesn't seem to be used in the initial validation check, possibly for good reason. @nielserik expertise probably needed here. |
"Physical" is one of our material types. Is it fair to say if we set the material type to something in the list, the app will complete the check? EDIT: I set the material type to "unspecified" and was able to pass the check. |
I am setting up the order import tool and have run into a snag. During start up, it can't seem to find the material type set in the import.properties file. When I run start.jar, all of the checks pass except for material type:
The credentials are correct, the user the app runs on has the correct permissions, and the material type does exist. What am I missing? I cloned the Github repo and so should be on the latest version. Here is my import.properties file:
The text was updated successfully, but these errors were encountered: