These are the critical components to be addressed when changing the location hierarchy in either Sydney.com or Visitnsw.com.

Key Components:

• Agreed new region or area terminology and location structure
• Updated CMS structure + hierarchy
• Updated consumer facing content
• Comms for 
  - External Stakeholders involved > DN
  - DNSW Regional Hub
  - DNSW Consumer Marketing
  - DNSW PR & Partnerships info kit
  - DNSW Image Library

Turn-around time for Completion = 4 weeks once changes are approved

Step 1: Sign off on new location region/area names, and location structure

Who: Associate Director Digital Publishing & Distribution

What: Map out the new region/area/towns with consultation from DNSW internally

Steps: 
Confirm the “area” names - or any new location names including region changes, town mapping etc in consultation with Regional Hub Team.

Inform Website Development Team that changes to hierarchy are coming & log time with Associate Director of Website.

Step 2: Establish Latitude/Longitude for the new Region/Area/Towns that are incorporated in the change

Who: Associate Director Digital Publishing & Distribution, Consumer Marketing

What: Collaborate and consult with Regional Hub team to set geo location. 

Steps: After input/engagement with relevant stakeholders establish the new boundary lines and centre point for the new location that’s requested. 
This will impact maps, product placement, article tagging, ATDW urls etc. You need this for the roll out of the changes to give to the Developers + ATDW (and Alpaca if changes impact state maps).

Note: As regions can be quite large, and don’t follow straight lines, will need to establish which point is plotted as the main point pin – usually one of the town centres, as well as the extremities to show which towns are included or excluded. Can reference Google Maps points & council boundaries.

Step 3: Audit websites Sydney.com & Visitnsw.com for all impacted content

Who: Senior Digital Publisher & Digital Content Manager

What: Website developers to build new location in hierarchy and move subsequent locations

Steps: 
Run Monsido test to pull all links & content referencing both old and new locations
Consolidate + create list of all impacted consumer facing content/editorial/destination pages
Consolidate + create list of all impacted consumer facing website navigation (tiles/mega menu)
Consolidate + create list of all impacted consumer facing articles
Consolidate + create list of all impacted Road Trips (Alpaca)
Consolidate + create list of all impacted image titles, alt text + captions
Consult with Senior Digital Product Coordinator on impacted ATDW listings for slug rebuild

Step 4: Roll out structural hierarchy changes in CMS & ATDW

Part A

Who: Digital Projects Manager/Developers

What: Website developers to build new location in hierarchy and move subsequent locations

Steps: 
Delete/move old hierarchy location in CMS
Create new hierarchy locations in CMS
Dev team to change filters in Articles and run a script to move existing articles - old to new locations
Dev team to build new filter options in Product Lists
Dev team to build new location if required in Road Trip filters: Widget: itinerary tile

Part B

Who: Senior Digital Product Coordinator

What: Inform ATDW of new hierarchy

Steps: Inform ATDW of new hierarchy and which locations require API realignment

 

Part C

Who: Senior Digital Publisher

What: Rebuild ATDW Slugs

Steps: 
Rebuild slugs of the new area or region or town
Rebuild slugs of the old area or town – need to avoid duplication of listings in the old area – make sure both the original and new locations are treated the same with rebuilding to avoid bugs/duplicated content etc.


 

Step 5: Roll out consumer facing content changes in CMS for both Sydney & Visitnsw

Part A

Who: Digital Content Manager

What: Rewrite, edit & brief Senior Digital Publisher with new consumer facing content reflecting the new locations/hierarchy 

Steps: 
Edit existing copy or write new copy from the consolidated list in step 3, and brief Senior Publisher with new content: 
- Sydney & VisitNSW Destination navigation page
- All affected region & area destination pages – both old & new (intros/body/meta data)
- Website navigation (tiles/mega menu) - including high level navigation pages that regions are linked
> As an example on highest level accommodation page, midway down user to filter by location tile
- Articles
- Road Trips (Alpaca) > this is pending who is responsible for the Road Trip content

Update content plan & strategy docs to reflect new changes

 

Part B

Who: Senior Digital Publisher

What:  Roll out consumer facing content changes in CMS for both Sydney & Visitnsw

Steps: 
- Complete all briefs provided by Digital Content Manager relating to content updates
- Change page templates on affected pages
- Move parent & child pages in CMS hierarchy & regenerate slugs (urls)
- Confirm all Meta Data has been updated on old + new
- Implement all relevant redirects from editorial pages
- Update all image titles, alt text + captions impacted
- Update all Road Trip filters: Widget: itinerary tile
- Update all Product Lists on relevant Destination Pages to reflect new product results
- Update all Article tags if not completed by Website Development Team

 

Step 6: Deliver Comms to stakeholders announcing changes

Who: Associate Director Digital Publishing & Distribution

What:  Create and deliver new terminology, official destination names and structure, to all relevant stakeholders both internally and externally.

Steps: 
Inform Destination Network and DNSW Regional Hub
Inform all DNSW Consumer Marketing – in particular Social Team/PR 
Inform DNSW Image Library (to reflect changes in naming conventions on image assets + search)
Create and provide information summary kit/FAQs for external stakeholders

As context, every single image the producer uploads requires the following mandatory criteria:

 So as a concise list, these 3 pieces of information are needed for the producer to upload any image:

1. What the image is of
   If natural attraction or place = name of it + location
   If of product = what is it of + business name
2. Photographer Credit
3. Where the image came from
   If ATDW = ATDW - listing name
   If DNSW Image Library = ID
   If other Gov Library = their acronym + their ID
   If direct = business name

Unfortunately it does take a bit more time to get this information, but without it, it's really hard to be able to move forward with a brief and fill in information as a producer. When that information is missed the producer has to then go and try and find all this information, which takes quite a lot of time.
 

It's important to always log into ATDW to obtain the information for image credits and image copyright separately, rather than saving an image from the product list page on one of our sites Sydney.com or Visitnsw.com

Reason being, is that when an image is sent to the producer like so:

This is the amount of information the producer has not been given: 

So then the producer needs to go find all of this - but the folder name isn't the ATDW name, which means the producer also needs to try track that down: 

ATDW - Lolita's Mexican Cantina - Lamb Tacos - Credit Kristy Mason Photography Copyright PLB Group

Instructions for downloading an image from ATDW at full res size. Below is a screenshot of the steps and each number matches the point below:

1. In the ATDW listing, go into “Photo’s”, which sits in the vertical orange bar on the left hand side
2. Click on one of the images you want so it appears in a larger size within your screen at the top and right click
3. With your mouse over the image, right click, and click on “inspect”
4. A bar will appear on the right hand side of the screen or it'll be in a section at the bottom. At the top of this grey pop-out bar, you’ll see “sources”. It should be the third option along. If you click that, there’s a drop down of heaps of options.
5. Click on the one that has an icon of a cloud and then says: “assets.atdw-online.com.au” – this is just you accessing the code of the database, and then you’ve now navigated to where the files are saved. 
6. Click on the “images” folder – all the images will appear in a long list. If you click through each one, you’ll see what image it is. 
7. Find the one you’re after and right click and open in a new window.
8. In the url at the top of your image opened, just backspace out the characters that appear after the “.jpeg” or “.jpg” – the characters are just making your image display smaller than it really is. By backspacing that out you can see the quality of the image at its full size and then save it to your own files. NOTE: please save the file name as: ATDW - name of the listing - credit photographer or owning org. 
   E.g. ATDW - Sydney Opera House - Credit Opera Australia | ATDW - Wild Flower Tour - Credit Eugene P Photography 
   If you're saving multiple images, just include what the image is of after the name of the listing e.g. ATDW - Wild Flower Tour - aerial of flower field - Credit Eugene P Photography
9. You don’t have to start from scratch for this process per image, you can just go back to that list of images in the sources bar

Note: if you get sick of having to scroll through that super long list of images to choose from, refresh the webpage, and it’ll start that list from just the ones on the page you’re on

FROM ATDW:

If there are images available from an ATDW listing, the fastest method is to include the URL to the live listing, and have a selection of images.

E.g. Choice of 1,3,4,6 or 10 from: https://www.visitnsw.com/destinations/north-coast/the-tweed-area/kingscliff/food-and-drink/lolitas-mexican-cantina

FROM OPERATOR:

If there are images available from the Operator, can the folder name be saved as the correct business name, including the image credit. Can there be some reference of detail as to what the images are of, so the producer can fill out ALT text and the rest of the fields when uploading an image?

FROM IMAGE LIBRARY:

Please keep the ID as the file name, and include in the folder where the images are saved the downloadable PDF of the image details, so when the producer uploads the image they have the relevant information to do so (location/details).

FROM EXTERNAL GOV LIBRARY:

Please include the image ID numbers with the relevant Gov Abbreviation - e.g. OEH 156822, but also include the downloadable PDF of the image details in the folder, so the producer can include which library it's been sourced from, and the relevant information about it (location/details).

Just as a friendly reminder this is the required information for the producer each time: 

1. What the image is of
   If natural attraction or location = name of it + location
   If of product = what is it of + business name
2. Photographer Credit
3. Where the image came from
   If ATDW = ATDW - listing name
   If DNSW Image Library = ID
   If other Gov Library = their acronym + their ID
   If direct = business name

WHAT TO AVOID:

Avoid briefing images like this: 

When this is all the information that's readily available: 

Please make sure the copy is without any comments through it, and has been proof read before submitting.

If copy is provided that isn't clean, the producer has to manually remove from the source code the comments individually, which takes 4x longer.

What to avoid: