SUSHI Confirmation page error

[dineshranjan]

When the usage is updated for previous year via SUSHI, the upload confirmation page by default takes the current year. I hope its caused by the $checkYear parameter which is taken as the current year. The year should be taken from the xml file stored in the SUSHI store. I am trying to figure out where to make the changes for obtaining the correct year from the xml file during upload confirmation.

[jeffnm]

This is more than just the confirmation page display. It actually impacts which year in the database the imported data is entered into. This is a serious problem.

[jeffnm]

I think one solution is to have the SushiService.php function that writes the import file that is kept in archive/ create the standard header for a regular import file, rather than just the values as it currently does. Then the standard import code could be used to parse the year out of the column names.

[coraladmin]

This seems like a fine solution to me. The overall bug is very significant and needs to be addressed asap. It has severely messed up our usage data.

Steve

From: Discussion List for CORAL ERM Administrators <CORAL-ADMIN@LISTSERV.ND.EDUmailto:CORAL-ADMIN@LISTSERV.ND.EDU> on behalf of Jeffrey Mudge <notifications@github.commailto:notifications@github.com>
Reply-To: ndlibersa/usage <reply@reply.github.commailto:reply@reply.github.com>
Date: Monday, December 7, 2015 at 11:26 AM
To: "CORAL-ADMIN@LISTSERV.ND.EDUmailto:CORAL-ADMIN@LISTSERV.ND.EDU" <CORAL-ADMIN@LISTSERV.ND.EDUmailto:CORAL-ADMIN@LISTSERV.ND.EDU>
Subject: Re: [CORAL-ADMIN] [usage] SUSHI Confirmation page error (#25)

I think one solution is to have the SushiService.php function that writes the import file that is kept in archive/ create the standard header for a regular import file, rather than just the values as it currently does. Then the standard import code could be used to parse the year out of the column names.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-162599644.