Errors When Library Attempt to Access Upgrades and Unselected Subscriptions from Prior Years

[CClennon]

This was first pointed out to us by Lake Forest College this morning. When attempting to masquerade as them and access Fiscal Year 2018 Upgrades and Unselected products they (and we) get the following error message:

Unknown error
Cannot read property ‘filter’ or undefined

I just tried again and was able to access the FY18 pricing. But for all other earlier periods I receive the error messages. There were also times when a report would populate but it contained the FY18 products and pricing (when the request was not for FY18 data).

As it includes pricing data I will email a screen capture so you can see the results of attempting to retrieve data for any period other than FY18.

[mekane]

@CClennon I looked into this, but I couldn't reproduce the error on my local copy or on the test server. So I assume it's a problem with the data. It would be helpful to get test reset to production. Should I ask Gordon to do that or ask him to enable me to do that?

[CClennon]

Hi Marty, That sounds like a good plan. Please proceed. Have a great weekend, Cindy Cindy Clennon Director of Electronic Resources Consortium of Academic and Research Libraries in Illinois (CARLI) 100 Trade Centre Drive, Suite 303 Champaign, IL 61820-7233 Ph: 217-333-4895 Fax: 217-244-7596 clennon@uillinois.edu www.carli.illinois.edu<http://www.carli.illinois.edu/> "Under the Illinois Freedom of Information Act (FOIA), any written communication to or from university employees regarding University business is a public record and may be subject to public disclosure." From: Marty Kane <notifications@github.com> Sent: Friday, June 8, 2018 2:25 PM To: CARLI/select <select@noreply.github.com> Cc: Clennon, Cynthia <clennon@uillinois.edu>; Mention <mention@noreply.github.com> Subject: Re: [CARLI/select] Errors When Library Attempt to Access Upgrades and Unselected Subscriptions from Prior Years (#57) @CClennon<https://github.com/CClennon> I looked into this, but I couldn't reproduce the error on my local copy or on the test server. So I assume it's a problem with the data. It would be helpful to get test reset to production. Should I ask Gordon to do that or ask him to enable me to do that? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#57 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Afj_ZnXgj-rw-0DNMNC7U0X5-LX3DhDsks5t6s91gaJpZM4UDyIq>.

[mekane]

Turns out this is a duplicate of #52 which has already been fixed but not yet pushed to production.