Large NTT editorial changes

Hi Ramesh & Manasa,

Per our conversation with Manasa a few minutes ago, there are a few things where tech support could potentially save us dozens of hours on editorial work in the coming weeks. We’d like to know about the possible scope and availability of help with these three actions:

1) Scanning all ad or keyword files in the system for specific text strings.

a. For example, we might send a list of 20 Japanese words or phrases, with the goal of returning a list of all BAIDs in which the keyword or ad file contains any of those words.

b. The goal would be to assemble one single master list of all “bad words” that NTT doesn’t like, provide the list to you all at once and get one list from tech-ops with all files that contain any of those words (i.e. We won’t want to do this over and over for multiple words or sets of words – just one sweep all at once)

c. “Find all BAs that contain x” is something that’s been done before, so we’re hoping that setting this up won’t be difficult.

2) For keyword files, we’d like to explore the possibility of removing all keywords that contain a particular string or set of strings.

a. In other words, one step further than #1 above – the request would be in the form of, “remove from all repositories any keywords that contain the string ‘x’.

b. Manasa suggested this might be a much longer and more complicated project.

3) A script that converts csvs back to xlsx files.

a. We already have and use a script created by Dan that converts our xlsx files into the appropriate csv format that will maintain the JP characters.

b. However, we have no way of converting them back to xlsx in bulk if we need to make changes.

Let me know if any questions.

Thanks!

Nate