User:SolSash7/Place Imports View history

No edit summary
(→‎SCR Place Import Guidance (For Reference Only): Changed the SCR section to match our current guidance.)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:


== Proposed USA Guidance ==
== Proposed USA guidance ==


''...Loading...''
=== Place imports ===


== New SCR Guidance (For Reference Only) ==
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.


...Being discussed by SCR Leadership
===== 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.


== Original SCR Place Import Guidance (For Reference Only) ==
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.
=== <br />Place Imports ===


It is recommended to [[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.
===== WazeParking1 & WazeParking2 =====
There is no back-end data that will be lost if the import is not retained.


===== Waze3rdParty =====
===== Navads_Import =====
'''For Gas Stations:''' keep existing <em>Waze3rdParty</em> Places. These <em>Waze3rdParty</em> gas stations have hidden backend data to remotely update gas prices. Other <em>Waze3rdParty</em> Places (not gas stations) may be removed in favor of a <em>Yext_Import</em> Place.
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.


===== Yext_Import =====
'''Waze3rdParty''' - Gas Station Imports
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 <em>Yext_Import</em> places that allow for remote updates of operating hours and services. Every effort should be made to preserve this data by keeping the <em>Yext_Import</em> Place. Copy/paste correct data from the existing non-Yext place to replace incorrect data in the new <em>Yext_Import</em> place. Then, delete the old non-Yext place.


'''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.
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''' - Parking Lot Imports


===== WazeParking1 & WazeParking 2 =====
'''Navads_Import''' <br />
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.<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.

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