We recently finished a successful customer project using Ytria XML Automation capabilities and we wanted to share how it went.

What’s in a name?

The idea of renaming resource rooms in your organization may not sound particularly complicated. Just change the name in the resource reservations database and everyone will catch on, right? Well, no. First, it’s important to remember that when we say “resource rooms,” we mean conference rooms and the like, but we could just as easily be talking about business equipment and other resources that everyone in your company needs to have access to.

But what happens if you need to rename the resource? In a growing company, there may come a time when you need to review your room naming strategy. This means you’ll need to change “Conference Room 1″ to something else to distinguish it from “Conference Room” in your Toronto or Hong Kong office.

A burden on the meeting owner

This is a problem one of our existing customers was dealing with. They were using the IBM Domino rooms and resources feature extensively, and had over 80 rooms across several sites and decided to change their room naming nomenclature.

Although the process of renaming is somewhat supported by the IBM platform (you can rename rooms directly from there, see fig. 1), the changes are not automatically applied in meetings across user mail files. Only the meeting owner receives a mail with a button and it is exclusively up to them to click to apply the changes on their meetings (and not those of invitees). That puts a lot of pressure on them, and if they forget it could cause confusion in other areas of the business.

Fig. 1 Renaming rooms directly in Notes.

Analyzing the challenge

The customer asked us if our tools could help go through their 3000+ email files, and rename all future meeting room information to reflect the room name changes.

To determine whether we could help, we did some analysis on how room information is stored in the organization’s document management system, and found that what we needed to do was:

  • Locate any documents using the “Appointment” or “Notice” forms where the StartDate item value was in the future, and the “Room” item’s value corresponded to one of the old room names.
  • Perform a Search & Replace on the room name, including the site information (see fig. 2).

An issue that we encountered during our preliminary tests had to do with recurring meetings: The way these were managed in the back-end was a problem. There was only one meeting document with a date/time item called “StartDateTime” which contained all dates and times a meeting was to repeat. The calendar view would then display the same document as multiple entries, according to the StartDateTime item values.

And since we were initially looking for meetings in the future only, these repeating meetings were missed.

Re-adjusting the formula to include these meetings, the formula we used to find them was:

Fig. 2 Searching by formula any documents using the “Appointment” or “Notice”, and executing a search & replace on the room name.

Creating the Automation XML

To create an automation file, notably because of the volume of databases and search strings, we first needed to figure out the best way to perform the task using scanEZ manually, which was by using the following steps:

  1. Open scanEZ on the mail file.
  2. Perform a Search by Formula using the above formula.
  3. Put all matching documents into a MySelection folder with the name of the room that was to be renamed.
  4. Highlight the MySelection folder and perform a Search & Replace on the “Room” item.
  5. Do this again for the next room names.

Going from manual to automatic

Since scanEZ can easily do this on a given database, the XML Automation API let us create an XML file that instructs the tool to perform all these required steps. We then used databaseEZ to select the mail files that needed to be processed, and had scanEZ go through all these mail files to perform the changes (see fig. 3).

By using our solutions, our customer finished the renaming project in just a couple of days, running the automation XML across 5 Virtual Machines, performing the Search & Replace procedure for 5 rooms per VM. Using the Ytria tools drastically reduced the tedium of the job so their team could focus on work of higher value. They also avoided potential confusion and other issues that might have caused downtime.

Fig. 3 Automating the process whereby scanEZ goes through all mail files in each database.

Future steps with scanEZ

With all rooms correctly renamed across meeting documents and over 3000 files, the next challenge was to remove the old meeting room names from each user’s “Preferred Rooms” list—this is an item in each mail file’s CalendarProfile, and can also be done using a scanEZ automation script. Stay tuned for our follow-up blogpost on how we did it.

If you are interested in automation or have a specific requirement we might be able to help with, or to find out more about Ytria XML Automation API, contact us today!

Keep me posted on more like this!

We’ll keep you up to date on new technical articles, tips and tricks, and upcoming events.

We don’t spam, and you can unsubscribe at any time.

Share This