Element Attributes when converting to structured (FM2019)

[QuintinSeegers]

In our unstructured documents, we have a table (nt Notes Table) we use to insert various notes. We use a paragraph style (ns Notes) to format the note text. We also use diffent paragraph styles to insert an appropriate image, depending on the type of note, e.g.:

• nti  Notes Table - Important Notes Icon
• ntg Notes Table - General Notes Icon
• ntr Notes Table - Reference Notes Icon, etc.

In our EDD, we have a NoteType attribute against our Notes Table Element that identifies the type of note, e.g. Important, General, Reference, etc.

In our Conversion Table, we have the following:

The conversion correctly converts all the elements. Our problem is that the NoteType attribute isn't assigned correctly. It is always assigning the "General" attribute value, which is the last one in the list.

I know it's probably one of those "can't see for looking" mistakes I've made in the conversion table.

Asking the EDD gurus 🙂

[frameexpert]

All of the T:nt Notes Table entries in the left-column are the same, so the last one wins. You need a way to distinguish the tables in the first column of the table.

[QuintinSeegers]

We use the same table format regardless of the note type. I am open to suggestions on how to achieve what you're suggesting.

[frameexpert · Accepted solution]

You may need to pre-process the document so that you assign a different table format to each type of note table. It probably makes more sense to post-process the document to assign the correct attribute to each structured table. In my experience, a conversion table can get you to about 80% of where you want to go and the rest needs to be accomplished after the conversion. Some post-cleanup can be done with scripting, while others may need a human decision maker.

[QuintinSeegers]

I did consider changing the attribute to be used against the note icon element (which is what really identifies what type of note it is) rather than the table, but felt it was hampering the process because the writers would first add a Note element (which inserts the right table format), then they have to insert the Note icon (and select the type of note). Whereas having the attribute on the table element, meant that writers would insert the Note element (which inserts the right table format and populates the first cell in the table with the correct Note Icon element). I may need to revisit this again.

[frameexpert]

You can do some amazing cleanup on your newly structured document using FrameSLT from West Street Consulting. I don't have any financial interest in recommending the plugin, I am just a long-time satisfied customer.

[frameexpert]

I think an important goal is to make things easier for the users, even if it means more effort in the conversion. You don't want to make things more difficult for authors and editors just to simplify the conversion.

[QuintinSeegers]

I agree. I'd rather deal with the clean-up post-conversion. I was just wondering/hoping there was an easier way 🙂

[frameexpert]

If you have a lot of these, I can help you with a post-processing script solution. Please contact me offlist. Thank you.

rick at frameexpert dot com

[QuintinSeegers]

Thanks for the offer. I'll keep that in mind.