1. Check if you can see the CSV button on the Library window:

• If not, submit a ticket using Access Web Content Tools and attach the approval from Lisa.

2. Select path, folder, or search for a keyword that you desire to export.

3. Click on CSV and choose a template. There are 3 templates available:

• csvExport – will extract required and editable columns only. Recommended!​
• default – will extract similar fields that you see in monthly CSV report.​
• viewtype – will extract ID, Name, Path, Type, LayoutVariant, and AssociatedLayoutVariant only.

4. Choose how you want the CSV file to be extracted. There are two options:

• Direct Export – will open a new tab and automatically download the file. Recommended!​
• Background Export – will be stored as a CMDownload type in the Studio user's home folder.

• The import file must contain the required fields and should not be edited:​
  • ID, Name, Type and Path
• Double-check that your CSV column headers exactly match the values in the export file. ​
  • "Subject tags" must be corrected to "SubjectTags.”​
  • The values in SubjectTags must be enclosed with “[ ]” and separated by a comma.​
    • Example: [/Product Assets/Product or Service Family/Product Category/Measurement Instrumentation/Pressure/, /Product Assets/Documents and Drawings/Data Sheets & Bulletins/Technical Note/]​
• Before submitting an import file, make sure to remove all "Document Type" Subject Tags (Slide 5). ​
  • Example:​ "/Product Assets/Document Type/Data Sheets/", "/Product Assets/Document Type/Brochure/". ​
    • Failing to remove these could cause issues during the import.​
• Assets such as images and teasers must be placed in the top row, followed by the Collection, and finally the Page. This arrangement will help us minimize the chances of unpublished changes.​
• Remove “LastModificationDate” and “VersionStatus” from the import file.​
• Ensure that your file name does not contain any spaces or any of the special characters. And file type must be .CSV.​

• In your CSV file for import, highlight the column called “SubjectTags” which includes any Tags associated to the line item ​
• With the column highlighted press Control+F​
• Enter */Document Type/* in the Find what: field, then click Find All button​
• Remove all instances of Document Type tags in the fields identified (shown right). ​
  • NOTE: Tags with /Documents and Drawings/ can be kept, only tags with /Document Type/ should be removed.​
• Failure to remove all Doc Type tags may result in a failed import, and a week or more delay in receiving the import timeline. 

• Submit a ticket using Emerson.com Enhancement.

Note:​

• The import file will be audited by the Digital Operations before it is assigned to IT.
• Please follow the format of Subject/Title in the screenshot by adding "Bulk Update:" at the beginning (for reporting purposes).
• Make sure to include the names of the tester(s) to validate the changes.
• Additionally, we must indicate whether we need to automatically publish the changes or not, as shown in the screenshot. ​
  • Note: If there are any changes that were not published, it’s the tester or Business’ responsibility to manually publish them.
• We can submit multiple import files ​(1 import file per locale) in 1 ticket. ​
• 3 Weeks SLA.​

• Extract the same CSV file from CoreMedia and see if there are any changes in the following fields:​
  • Last Modified​
  • Status​
• If there are any changes that were not published, it’s the tester or Business’ responsibility to manually publish them.​
• If there are no changes in Stage/Production and no errors with the import, please mention it in the ADO ticket by adding a comment.​
• When we are notified that it’s ready for testing, it should be tested within the week of notification.​