Page Comparison

...

Overrides/Supersedes 

When applicable, provide links to all DRs that this DR overrides or supersedes 

RFC 

Provide links to all relevant RFC'sThis decision was migrated from the Tech Leads Decision Log as part of a consolidation process.  The original decision record can be found here.

RFC 

N/A

Stakeholders

All Backend Developers

...

This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.

Background/Context Explain the need that triggered the need for making a decision

To translate messages it returns a back-end API needs to know the locale of the client.

Example message: "No item with barcode {itemBarcode} exists", for details see https://wiki.folio.org/display/I18N/How+To+translate+FOLIO

Example locale: de for German

Two ways to pass the current locale to a back-end API have been proposed:

• accept-language HTTP header line
• lang query parameter

For details see Image AddedFOLIO-3196 - DECISION: Localisation parameter for back-end CLOSED

While it may be possible that Stripes supports multiple ways to pass the locale FOLIO should agree upon a single way that all back-end modules should use.

This was discussed among front-end devs during multiple stripes-architecture meetings with conclusions in Image AddedSTRIPES-750 - DECISION: Which module should host back-end translation files? CLOSED , and then by the Tech Council on 2021-06-09 and 2021-06-16.

Assumptions

List all assumptions that were made when making the decision

...

Document the thought process, list reasons that lead to the final decision

DecisionShort summary of the decision goes here

Back-end modules shall read the HTTP Accept-Language header, as specified in RFC-7231 Section 5.3.5, to determine the desired locale of the response.

Implications

• Pros
  • Provide a link to RFC when applicableN/A
• Cons
  • Provide a link to RFC when applicableN/A

Other Related Resources