User:SolSash7/Place Imports

Proposed USA Guidance

...Loading...

New SCR Guidance (For Reference Only)

...Being discussed by SCR Leadership

Original SCR Place Import Guidance (For Reference Only)

Place Imports

It is recommended to 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

For Gas Stations: keep existing Waze3rdParty Places. These Waze3rdParty gas stations have hidden backend data to remotely update gas prices. Other Waze3rdParty Places (not gas stations) may be removed in favor of a Yext_Import Place.

Yext_Import

This is only a taste of a much larger database. At this time, additional Yext imports are being held until additional WME Place editing tools are released. There is hidden backend 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. Copy/paste correct data from the existing non-Yext place to replace incorrect data in the new Yext_Import place. Then, delete the old non-Yext 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.

Only a very small percentage of Yext places have been imported. At this time, additional Yext imports are being held until additional WME Place editing tools are released.

WazeParking1 & WazeParking 2

Duplicates can be removed and favoring the existing parking lot is fine. There is no back-end data that will be lost if the import is not retained.

Navads_Import

Duplicates can be removed and favoring the existing place is fine. There is no back-end data that will be lost if the import is not retained.