Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

BugFest installation of Fees/Fines History, Fee/Fine Details and New Fee/Fine does not match other test sites

Description

UPDATED DESCRIPTION (December 13, 2019):
Holly talked to Zak and learned that this problem is due to the translation file not being correct for both Sweden and GB. What I am seeing at https://bugfest.folio.ebsco.com/ for Chalmers is exactly what is in the translation file. Zak is not sure why the English was never converted properly for Sweden and GB. This is what needs to be corrected...

Fee/Fine History
"barcode" should be "Barcode" for Sweden and GB
"billed" should be "Billed" for Sweden and GB
"remaining" should be "Remaining" for Sweden and GB

Fee/Fine Details
"Created At" should be "Created at" for Sweden and GB

New Fee/Fine (aka charge fee/fine)
"Item Status" should be "Item status" for Sweden and GB
"Comments" should be "Additional information for staff" for Sweden and GB

````````````````````````````````````````
UPDATED DESCRIPTION (December 11, 2019):
While testing for Q4 BugFest, Holly found that the same issues still exist, plus she found similar issues with the New Fee/Fine page. The new screen prints are attached. They have file names that begin with "Q4-".

````````````````````````````````````````

ORIGINAL DESCRIPTION:
As part of Q3 Bug Fest, Holly is testing several features at https://bugfest.folio.ebsco.com (the test installation for Chalmers). When testing Fees/Fines History and Fee/Fine Details, she noticed that there were capitalization differences between what Chalmers and Daisy/Snapshot have. Also, the Outstanding Balance is missing in one place on Chalmer's version of FF History, but not Daisy/Snapshot. The two attached images show exactly what is happening. It's not a big problem, but it is odd.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5
  • 11 Dec 2019, 09:43 PM
  • 11 Dec 2019, 09:43 PM
  • 11 Dec 2019, 09:43 PM
  • 16 Sep 2019, 08:33 PM
  • 16 Sep 2019, 08:33 PM

Checklist

hide

TestRail: Results

Activity

Show:

Holly Mistlebauer December 18, 2019 at 2:59 PM

Thanks Peter!

Peter Murray December 16, 2019 at 10:11 PM

Peter Murray December 16, 2019 at 5:04 PM

Okay – I've set an automatic fill rule in Lokalise to copy updates from `en_US` to `en_SE` and made a batch copy from those two languages. I'll run the lokalise-push process to get those changes into the code repos.

By the way, there is a similar issue with `en_GB` in that no one is monitoring changes to that language. That is a bit trickier because of the U.K. spelling of a lot of words, so it is going to need someone actively managing that translation.

Lisa Sjögren December 16, 2019 at 4:48 PM

Hi! Yes, is right about how en_SE is being used. No one at Chalmers is maintaining it, so it would be great if - for now at least - it could just follow the English one.

Cate Boerema December 16, 2019 at 11:56 AM

I think the translations for en_SE should just be the same as en_US The purpose of using en_SE instead of en_US is just to get the correct date/time format for Sweden. Would it be possible for you to update en_SE when updating en_US?

+

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Development Team

UNAM

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 16, 2019 at 8:29 PM
Updated December 18, 2019 at 2:59 PM
Resolved December 16, 2019 at 10:11 PM
Configure
TestRail: Cases
TestRail: Runs

Flag notifications