User:SolSash7/Place Imports View history

Revision as of 19:04, 12 September 2019 by Jm6087 (talk | contribs) (→‎SCR Place Import Guidance (For Reference Only): Changed the SCR section to match our current guidance.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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.

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 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