1.1.5 Content tagging

Maximise

Figure 6 Content tagging stage

Show description|Hide description

A graphic showing the steps to be taken at Stage 6 Content tagging/proofread. DDE: Review feedback and amends. Author: Review changes. PE: Check/proof content including transcripts. DPA: Tag content, embed asset and interactives and build quizzes.

Content tagging stage

The DDE/AE has been working hard with the client on getting the content edited and, now they have a clean document (or as clean as possible), they will ‘mark it up’ as described in the next section 'Mark up and oXygen [Tip: hold Ctrl and click a link to open it in a new tab. (Hide tip)] '. This document will then be passed to the you (the DPA) who will create the XML file and render to the website.

You will use the marked-up Word file to create the XML file in oXygen and then render it to the website. The word ‘render’ is used to define the process by which the XML file is fed into the website and displayed. If any of the assets discussed previously are ready, you will need to include these in the XML. When we say ‘ready’, we mean, for example, that the image has been cleared, a high-resolution version has been provided and you have made sure the image is the correct size. Likewise, AV assets are ‘ready’ when they have cleared.

Comments and queries

Whilst tagging the document, the Editor might ask you to leave an ‘editor comment’. This is to flag any issues or queries for the client. You can also add your own editor comments for issues that you may have. Do try to flag your issues with the Editor and get them resolved before it goes back to the client, but if you do need to leave a comment in the XML, make sure to add you initials to it so it’s clear it’s from you. Editor comments will show up on the website and must all be resolved prior to the site going live.

[Editor: This is an editor comment.]

As you can see above, an editor comment displays in pink. Note in the contents on the left of the screen, there is clear indication that editor comments are present, so it is easy to check if they are all sorted. Figure 7 shows this, the number one in brackets (1) after 'Project life cycle' indicates one editor comment overall and the next one in brackets (under '1.1.5 Content tagging') shows where the comment is.

Figure 7 How an editor comment displays in the contents on OLC

Show description|Hide description

A screenshot of the contents menu that appears on the left-hand side of the screen on a course on OpenLearn Create. (1) appears in pink font and italics next to the main content heading 'Project life cycle' and again below next to '1.1.5 Content tagging'.

How an editor comment displays in the contents on OLC

Editor comments can be used for a number of reasons; these include (but are not limited to):

• Unresolved query for the author.
• Acting as a placeholder for images or other assets.
• Query from the DPA that has cropped up during tagging (again, if your query is for the Editor, try to bring this up with them directly rather than through an editor comment).

The DDE will refer to the website version (known as the render) and should resolve as many of these queries as they can. Once resolved, the Editor may ask you to update the file. Once the DDE is satisfied with the render, they will pass it onto the Assistant Editor with a brief for them to carry out the proofread. Normally, this stage is done when the whole website has been completed. However, for larger projects, this might be done in stages. The AE has complete autonomy here and will make any changes they feel are needed.