(Created page with " == New SCR Guidance == ...Being discussed by SCR Leadership ==Original SCR Place Import Guidance== === <br />Place Imports === It is recommended to Places#Merge_places|m...") |
(→SCR Place Import Guidance (For Reference Only): Changed the SCR section to match our current guidance.) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
== | == Proposed USA guidance == | ||
=== Place imports === | |||
It is recommended to [[Places#Merge_places|merge places]] when possible to ensure that any hidden back-end data is not lost. Below is a list of some of the types of imports you may come across with some additional information about each. | |||
It is recommended to [[Places#Merge_places|merge places]] when possible to ensure that any hidden | |||
===== Waze3rdParty ===== | ===== Waze3rdParty ===== | ||
These Waze3rdParty gas stations have hidden back-end data to remotely update gas prices. | |||
===== Yext_Import ===== | ===== Yext_Import ===== | ||
There is hidden back-end data on Yext_Import places that allow for remote updates of operating hours and services. Every effort should be made to preserve this data by keeping the Yext_Import Place. | |||
There is hidden | |||
Imported descriptions can be longer than the max character counts, and editors may truncate descriptions to allow for saving other edits. However, there is no initiative to adjust all Yext descriptions. | Imported descriptions can be longer than the max character counts, and editors may truncate descriptions to allow for saving other edits. However, there is no initiative to adjust all Yext descriptions. | ||
===== WazeParking1 & WazeParking2 ===== | |||
There is no back-end data that will be lost if the import is not retained. | |||
===== | ===== Navads_Import ===== | ||
There is no back-end data that will be lost if the import is not retained. | |||
===== | == SCR Place Import Guidance (For Reference Only) == | ||
=== Place Imports === | |||
You should [[Places#Merge_places|merge places]] when possible to ensure that any hidden backend data is not lost. Below is a list of some of the types of imports you may come across. | |||
'''Waze3rdParty''' - Gas Station Imports | |||
'''Yext_Import''' <br /> | |||
Imported descriptions can be longer than the max character counts, and editors may truncate descriptions to allow for saving other edits. However, there is no initiative to adjust all Yext descriptions. | |||
'''WazeParking1 & WazeParking 2''' - Parking Lot Imports | |||
'''Navads_Import''' <br /> |
Latest revision as of 19:04, 12 September 2019
Proposed USA guidance
Place imports
It is recommended to merge places when possible to ensure that any hidden back-end data is not lost. Below is a list of some of the types of imports you may come across with some additional information about each.
Waze3rdParty
These Waze3rdParty gas stations have hidden back-end data to remotely update gas prices.
Yext_Import
There is hidden back-end data on Yext_Import places that allow for remote updates of operating hours and services. Every effort should be made to preserve this data by keeping the Yext_Import Place.
Imported descriptions can be longer than the max character counts, and editors may truncate descriptions to allow for saving other edits. However, there is no initiative to adjust all Yext descriptions.
WazeParking1 & WazeParking2
There is no back-end data that will be lost if the import is not retained.
There is no back-end data that will be lost if the import is not retained.
SCR Place Import Guidance (For Reference Only)
Place Imports
You should merge places when possible to ensure that any hidden backend data is not lost. Below is a list of some of the types of imports you may come across.
Waze3rdParty - Gas Station Imports
Yext_Import
Imported descriptions can be longer than the max character counts, and editors may truncate descriptions to allow for saving other edits. However, there is no initiative to adjust all Yext descriptions.
WazeParking1 & WazeParking 2 - Parking Lot Imports
Navads_Import