Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

currencyCode and currencySymbol have the same values, remove the currencySymbol field and obtain correct values from Dict #36

Open
maddy-at-work opened this issue Feb 8, 2019 · 6 comments
Labels
enhancement New feature or request

Comments

@maddy-at-work
Copy link
Contributor

Currently,
currencyCode: Variable values - USD
currencySymbol: Variable value - USD instead of $
For most airlines where currencySymbol cannot be captured using farenet, currencyCode is duplicated in that field. Instead of this redundancy if we can remove this field altogether and obtain symbols using the dictionary.

@maddy-at-work maddy-at-work changed the title currencyCode and currencySymbol have same values for most airlines, remove currencySymbol field from farenet and obtain correct values from Dict currencyCode and currencySymbol have same values, remove currencySymbol field from farenet and obtain correct values from Dict Feb 8, 2019
@maddy-at-work maddy-at-work changed the title currencyCode and currencySymbol have same values, remove currencySymbol field from farenet and obtain correct values from Dict currencyCode and currencySymbol have same values, remove currencySymbol field and obtain correct values from Dict Feb 8, 2019
@maddy-at-work maddy-at-work changed the title currencyCode and currencySymbol have same values, remove currencySymbol field and obtain correct values from Dict currencyCode and currencySymbol have the same values, remove the currencySymbol field and obtain correct values from Dict Feb 8, 2019
@BigDataKatha BigDataKatha added the enhancement New feature or request label Feb 11, 2019
@BigDataKatha
Copy link
Contributor

Table: farenet_001
Type: https://github.com/EveryMundo/emDataStandards/blob/master/types/offer.schema.json
Issue: Remove currencySymbol property under priceSpecification attribute on the offer-level because the symbol usually cannot be captured from the IBE and is currently being populated with the currency Code.

"priceSpecification": {
      "description": "Price Specification",
      "type": "object",
      "properties": {
        "currencyCode": {
          "description": "The currency (in 3-letter ISO 4217 format) of the price.",
          "type": "string",
          "example": "USD"
        },
        "currencySymbol": {
          "description": "Currency symbol",
          "type": "string",
          "example": "$"
        }
      }
    },

@AnahieM @unoriginalbanter @danielsan @neilgoldman @howardem @renecairo @AVivero @yartiles
Please review the above and let us know if you are using the FareNet field currencySymbol or if we can go ahead to remove it. Thank you!

@annisuu
Copy link
Contributor

annisuu commented Feb 15, 2019

Hi @BigDataKatha, PMM does not use the field from FareNet, we have been working with our own mapping data for our price formatting in DPI.
I will just double check with Vincent when he's back next week in case he uses it for reporting or another internal tool.

@BigDataKatha
Copy link
Contributor

Leaving a comment that it was confirmed that FareWire does not use that field.

@BigDataKatha
Copy link
Contributor

@AnahieM did you follow up with Vince on this issue?

@annisuu
Copy link
Contributor

annisuu commented Apr 17, 2019

@BigDataKatha Sorry, it took so long to reply, Vincent does not use this in any of his projects.

@BigDataKatha
Copy link
Contributor

According to Maylin, airlines can have in their settings "Display Currency Symbol" checked, so they need to keep the currencySymbol in the Sputnik MS output fields, so TRFX can use that data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants