Using Image Wrapper Alt field

We are on WEM8.5 and it has Alt field for all the media items ... unfortunately this field is disconnected from the actual Static File. We created an Image Wrapper which holds reference to Static File as well as ALT field and other meta data. My question is how do we override the default Alt and use the one on our Image Wrapper? Any ideas?

TIA,
Stan

Find more posts tagged with

Comments

Evan_Bench

Is the wrapper part of the legacy content model? that is, the reason you're using a wrapper was to support migration from the previous model?

I would suggest using the Alt text field for the Media Type items instead. Then you can write your rendering code to support the use of Alt Text (and other meta-data) available in the Media Type Objects.

This also allows you to take advantage of the bean attributes (makes render code easier to write). Here's an example:

<c:set var="content" value="${component.results[0]}" />

       <%-- setup variables --%>
       <c:set var="name" value="${content.title}"/>

  <c:set var="Alt" value="${content.altText}"/>
       <c:set var="description" value="${content.teaser}"/>
       <c:set var="image" value="${content.altImage}"/>
       <templating:contentLink var="linkUrl" channelId="${currentChannel.system.id}" oid="${content.system.id}"/>

       <%-- render the altImage media item and look for a landscape format --%>


       <c:if test="${not empty image.VCMCM_DSX_MEDIA_FORMAT}">
           <c:forEach var='mediaformat' items="${image.VCMCM_DSX_MEDIA_FORMAT}">
               <c:if test="${mediaformat.FORMAT_MEDIAFORMATTYPE eq 'landscape'}">
                   <templating:contentLink var="imageUrlLarge" placementPath="${mediaformat.FORMAT_SOURCEPATH.placementPath}"/>
               </c:if>
           </c:forEach>
       <a href="${linkUrl}">
           <img src="${imageUrlLarge}" alt="${image.system.name}" title="${image.system.name}"/>
       </a>
       </c:if>

       <%-- render the Title and Teaser over the Banner Image --%>
       <div class="shapes">
               <h1 class="headline" data-left="0.12%">
                   <templating:textInlineEdit oid="${content.system.id}" attributexmlname="title">
                       ${name}
                   </templating:textInlineEdit>
               </h1>
               <h3 class="alt-text" data-left="0.12%">
                   <templating:textInlineEdit oid="${content.system.id}" attributexmlname="alt">
                       ${AltText}
                   </templating:textInlineEdit>
               </h3>

Stan_Livshin

This is not a legacy model. We set it up this way so you can manage images/meta data under a single content item, the wrapper. The work around you are proposing separates places where you manage image, meta-data and alt tags. In other words the alt tag is never directly attached to the image. Plus through our model we make alt field required thus forcing content editors to fill it out since this is our accessability requirement.

Mario_DAnna

I don’t understand why you used wrappers and not attributes on the StaticFile object type then.

-m

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: martedì 4 novembre 2014 15:26
To: eLink Recipient
Subject: Using Image Wrapper Alt field

Using Image Wrapper Alt field

Posted bystan.livshin@mountsinai.org (Livshin, Stan) On 11/04/2014 09:24 AM

[To post a comment, use the normal reply function]
Topic:	Using Image Wrapper Alt field
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Evan_Bench

it's an interesting way to do this (was done this way often in previous versions but not best way in 8.5). Instead either edit the static type (as Mario suggests) or edit the Media Type (to make desired meta-data required) then control this from either media type or static type... wrappers are not needed much anymore with 8.5... (just makes things more complex than is necessary when it can be done more simply).

Stan_Livshin

Well there is a limited amount of attributes one can add to Static File and meta data for Images for example is not always relevant to PDFs. Anyway even if i add the attrbite to Static File i am still stuck with the original dilemma ... how do i use this new attribute on Static File object type instead of the default Media one.

Stan_Livshin

I was able to resolve this issue by extending the ETLMediaTransformer class and overriding the toContentString() method like so:

@Override
    public String toContentString(Map propertyMap) throws ApplicationException, ValidationException
    {
        String contentString = super.toContentString(propertyMap);
        Map attributeMap = getAttributeMap(propertyMap);
        String mediaId = (String)attributeMap.get("filewrapper");
        ManagedObject moWrapper = ManagedObject.findByContentManagementId(new ManagedObjectVCMRef(mediaId));
        if (moWrapper.getObjectType().getData().getName().equals("mshsImageWrapper"))
        {
            Object attributeValue = moWrapper.getAttributeValue("alt");
            if (attributeValue != null)
            {
                String wrapperAltText = (String)attributeValue;
                contentString = contentString.replace("alt=\"\"", "alt=\"" + wrapperAltText + "\"");
            }
        }

        return contentString;
    }

I also made alt field hidden on the Media content type.