I don’t understand whether the user is supposed to start by creating a new site, cloning an existing site, or editing an existing site in order to switch to a new GDS. This topic discusses how to set up a new site but isn’t explicit about where the new site comes from.

Linda - Cloning an existing site is the first step in creating a new site. Cloning would typically be done from the outgoing GDS template to the new GDS template.
After the site has been created, the agency will update the settings that pertain to the incoming GDS.
So for example, a site with Worldspan is adding TravelPort +. They would use their existing Worlspan template to clone when creating the TP+ template. Cloning will copy the Worldspan settings, and the agency would edit the existing Worldspan formats to TP+. They will use that template to test before they copy it over to existing domains.

I don’t understand the need for a separate topic on this subject. How is this different from either setting up a new site or cloning an existing site and editing it per the Implementation - Cloning Guide? It seems you would just do that and choose the new GDS. The page title seems to be a misnomer, as this procedure seems to walk though simply setting up a whole new site, not changing settings on an existing site.

Also, the minimum settings for a new site in that topic are different than listed here - should they be the same? https://deemadmin.atlassian.net/wiki/spaces/EN/pages/2394161153/Implementation+Guide+-+Clone+and+Create+Sites#Configure-the-new-site

SME comments said that these instructions also work for adding a second PCC or GDS to the same site. Should those also be listed as objectives of this procedure? If so, specifically how do you use multiple GDs / PCCs for the same site?

Removed description here about GDS conversion providing the “benefit of self service” suggested by Dave Nygaard. It doesn’t seem to be self service at all because some steps require user to open a Deem Support Case, including for new Web Services and GDS Emulation.

Is this SME comment addressed in the Web Services section of this page?:

“For Galileo and Sabre, we need to add an addendum section on Web Services.  For Galileo we will need a Web Services Access Group and and IPCC for Sabre.  This is configured on the Superdomain.  Galileo will also need their Superdomain Travel Configuration updated to read "GDS Web Service" for the Low Fare Search method.”

I reorganized this topic per Dave’s request to simplify based on mandatory and “other” steps. Please verify this reorg is in line with that comment.

I was unable to save on this screen and kept getting the error *JavaScript Error (We're sorry, but the javascript you have entered is not valid. Please enter a valid javascript.) We need to provide additional information here about that error and how to resolve.

Step 7 - I did not see any link or setting for the PNR Mask requirements. Do you have to save first or how do you get to this?

What are the Examples above examples of? Where should they entered?

Please clarify whether whether all Web services require a Deem support case, or only new ones, or if only the applicable procedure here is required.