models: Validate Bibliographic::HostBibTask.email#11
Conversation
|
fascinating, neither of those tests fail on my local computer. |
This ensures we do not create jobs without email addresses. Additionally, add email address attributes to the test user data. Closes: AP-577
8d7527e to
2478d58
Compare
|
@awilfox I pulled the branch and tested it locally, when uploaded a bib batch, it gave a 500 error. Could you try it locally with these steps?
For the previous error 'ArgumentError: SMTP to address may not be blank: [].', I login in Calnet, how can my email is blank? All calnet user should have an email. We need some investigation on it. |
There was a problem hiding this comment.
This is using an email of a former employee in LIT. I think they probably put it in there but not sure if we should still be using it. Looks like it's used in several places
There was a problem hiding this comment.
I copied that from the same identifier in spec/data/alma_patrons - I agree it's not ideal, but it was for testing purposes.
|
I think I've figured out the underlying issue why emails were blank. We are receiving the email address as At any rate, I think that change needs to be separate from this one, so I will open a new branch for that change, and then rebase this one. |
This ensures we do not create jobs without email addresses.
Closes: AP-577
@yzhoubk since you were the one who was running into jobs without email addresses while testing #10, would you be able to try this branch out and see if this helps?
I'm wondering if one of the test jobs was firing off, since they didn't specify an email. At any rate, having this validation should help us catch out any places we're missing the email in the future.