[UIU-2916] Distinguish 'due date' and 'return date' in Spanish translation Created: 27/Jun/23  Updated: 18/Jul/23  Resolved: 03/Jul/23

Status: Closed
Project: ui-users
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Amelia Sutton Assignee: Unassigned
Resolution: Done Votes: 0
Labels: i18n, localization, translation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Due Date and Return Date Translation.jpg     JPEG File Due Date and Return Date Translation2.jpg    
Sprint:
Development Team: None
CSP Request Details: Describe issue impact on business:
Tenants using the Spanish, Spanish (Spain), or Spanish (Latin America) languages cannot distinguish between "due date" and "return date", leading to frequent confusion

What institutions are affected?
All tenants using a Spanish, Spanish (Spain), or Spanish (Latin America) locale

What is the workaround if exists?
Switch the session and/or tenant locale to English

What areas will be impacted by fix (i.e. what areas need to be retested)
none; this is not a code change

Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high)
Cherry pick the translation commit onto the release branch. LOE is < 1 hour. Updating a translation is extremely low risk since it is not a code change

Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.
Set the session locale to "Spanish" and view the details for an open loan to validate that fields are correctly labeled, repeat this for Spanish (Spain), and Spanish (Latin America). LOE is < 1 hour.

What is the roll back plan in case the fix does not work?
Restore the previous translation file
Potential Workaround: Julian Ladisch: Backport the latest translations into ui modules that have already been released: https://wiki.folio.org/display/I18N/Backport
RCA Group: Legitimate regression
Affected releases:
Orchid (R1 2023), Nolana (R3 2022)

 Description   

Current situation or problem:

  • Currently with a tenant with language set to Spanish, Spanish (Spain), or Spanish (Latin America), when viewing the list of a user's closed loans and viewing the details of a closed loan, the fields that in English are labeled "Due date" and "Return date" are both labeled "Fecha de devolución"

In scope:

  • Change the Spanish translation for "Due date" to "Fecha de vencimiento"
  • Change the Spanish translation for "Return date" to "Fecha de devolución"
  • Change the Spanish (Spain) translation for "Due date" to "Fecha de vencimiento"
  • Change the Spanish (Spain) translation for "Return date" to "Fecha de devolución"
  • Change the Spanish (Latin America) translation for "Due date' to "Fecha de vencimiento"
  • Change the Spanish (Latin America) translation for "Return date" to "Fecha de devolución"

Use case(s)

  • Distinguishing between these two columns will reduce confusion for library staff


 Comments   
Comment by Amelia Sutton [ 06/Jul/23 ]

This change has been made and will be included in the next release.

Comment by Zak Burke [ 07/Jul/23 ]

Amelia Sutton, thanks for getting this squared away so quickly!

I moved this into UIU since that's where the fix was applied, and changed the "Type" from "New Feature" to "Bug". Can we get this into the next Orchid CSP since it's a very low-risk fix (just a translation file change, not a code change) and it would clear up a lot of confusion for our Spanish-locale tenants?

I'm not sure what to put for "RCA" since none of the options really fit, so maybe "Legitimate regression"? Likewise, there is no TestRail case to link since we only test in English. Here's what I think we need for the "CSP Request Details" field

  1. Describe issue impact on business Spanish tenants cannot distinguish between "due date" and "return date", leading to frequent confusion
  2. What institutions are affected? (field “Effected Institutions” in Jira to be populated) All tenants using a Spanish locale
  3. What is the workaround if exists? Switch the session and/or tenant locale to English
  4. What areas will be impacted by fix (i.e. what areas need to be retested) none; this is not a code change
  5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high) Cherry pick the translation commit onto the release branch. LOE is < 1 hour. Updating a translation is extremely low risk since it is not a code change
  6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Set the session locale to "Spanish" and view the details for an open loan to validate that fields are correctly labeled. LOE is < 1 hour.
  7. What is the roll back plan in case the fix does not work? Restore the previous translation file

CC: Sobha Duvvuri 

Comment by Amelia Sutton [ 07/Jul/23 ]

Zak Burke Thank you for updating things on here. I am new to being a PO and am still becoming familiar with how things are done in Jira.

I think that "Legitimate regression" does seem like the most accurate RCA value for this. What you've written up for the CSP request details looks good, should all of that information be added directly to that field or does some of it need to be added elsewhere?

Additionally, I have updated the ticket to clarify that these changes were made for all three Spanish language localizations Spanish, Spanish (Spain), and Spanish (Latin America).
 

Comment by Zak Burke [ 10/Jul/23 ]

Amelia Sutton , the CSP process is new for me too I think that whole blob of points 1-7 gets pasted into the "CSP request details" field. 

Comment by Amelia Sutton [ 12/Jul/23 ]

I have added those CSP details to the ticket.

Comment by Sobha Duvvuri [ 17/Jul/23 ]

Amelia Sutton : Thank you! Could you please let us know the fix version that's compatible with Orchid since this seems to be an Orchid-CSP candidate? is it going to be part of Orchid-CSP#3? cc:Oleksii Petrenko 

Comment by Amelia Sutton [ 17/Jul/23 ]

Sobha Duvvuri There should not be any compatibility issues with these changes as there are no changes to the code. I would say that having it as a part of Orchid-CSP#3 would be excellent as this is a fairly important change for Spanish language institutions. 

Comment by Sobha Duvvuri [ 17/Jul/23 ]

Zak Burke : Would a new release of ui-users needs to be released for this change to appear in Orchid-SP#3? Could you please help me with the next steps here? Thanks!

Comment by Zak Burke [ 18/Jul/23 ]

Sobha Duvvuri, yes, translations are bundled with the code so we need a new release of ui-users for this to appear in a Service Patch release. Regrettably, after I updated this ticket with the CSP info I forgot to formally request the fix on Slack#release_bug_triage. I'm sorry. I've done that now.

Comment by Khalilah Gambrell [ 18/Jul/23 ]

Amelia Sutton - what is the priority of this issue? If this is not a P1 then it is not eligible for CSP https://folio-org.atlassian.net/wiki/display/REL/Critical+Service+Patch+Process 

Comment by Amelia Sutton [ 18/Jul/23 ]

Khalilah Gambrell It is P2 so it would not be eligible for CSP, thank you for sharing that document.

Generated at Fri Feb 09 00:39:29 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.