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

Doc: Conversion of V2 fares into V1 model #261

Merged
merged 2 commits into from
Jun 7, 2019
Merged

Doc: Conversion of V2 fares into V1 model #261

merged 2 commits into from
Jun 7, 2019

Conversation

prhod
Copy link
Contributor

@prhod prhod commented Jun 6, 2019

Only the two use cases needed for the moment.

woshilapin
woshilapin previously approved these changes Jun 6, 2019
src/documentation/ntfs_fare_conversion_v2_to_V1.md Outdated Show resolved Hide resolved
src/documentation/ntfs_fare_conversion_v2_to_V1.md Outdated Show resolved Hide resolved
prices.csv field | Source file | Source field | Notes/Mapping rule
--- | --- | --- | ---
"avant changement" | | | fixed value `*`
"après changement" | ticket_use_perimeter.txt | object_id | the content of the field must follow the pattern : "network=network:[object_id]"
Copy link
Contributor

@woshilapin woshilapin Jun 6, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand completely what would happen if one ticket was tied to multiple ticket_use_perimeter: which object_id should we use in this case? Is it handled by the section below?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this conversion, it's assumed there is only one ticket_use_perimeter. Do not be afraid ;)

@woshilapin woshilapin merged commit 64f6fa2 into hove-io:master Jun 7, 2019
@prhod prhod deleted the spec_tarif_v2_v1 branch October 15, 2019 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants