• State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 138 subscribers
  • Views 3429 views
  • Users 0 members are here
Options
Related

Update an image

Steven Ridley

Hello all - is there a way to update an image in a publication from publication manager? i have a newer version of a screenshot and I just want to upload the latest.  I am new to the community and I tried to see if this was already answered (or in the help file), so apologies if it is already here...
Rate translation
×
Suggest better translation
×
  • 0
    You can do this:
    1. Check out the image (from the Content pane in PM).
    2. Find the image in your local cache (which is likely C:\Users\*your-userid*\Documents\SDL\InfoShare\*some-number*\*your-userid*\images
    3. Rename the checked out image file to something slightly different (example, add -temp at the end of the name).
    4. After copying the updated image file to the same folder, rename the new image file to the original name of the checked out image file (before you added -temp or similar).
    5. Using PM, check the image back in.

    This will check in the updated image that you copied to the local cache folder. Your previously checked out image will remain available in the local cache as a backup, and you should be able to access the previous revision of the image via the web client (if you ever need to restore it).
    Paul M.
    McAfee
  • 0 in reply to CMS Administrators2

    That seems like a really primitive workflow for a really common function; is that the expected workflow from SDL?
  • 0 in reply to Jeff Hooker

    You can update the image from the web client, but not from Publication Manager. 

    I believe that the reason you can't update an image from Pub Manager is that the image might exist in other resolutions and even languages (if the image has localized versions). PM only shows you the image in one language (the system default, typically English) and one resolution. So if PM would have this feature, it would let you replace the English, hi-res image, but you would be unaware that you also need to replace, say, the English lo-res, Japanese hi-res, German hi-res, Japanese lo-res and German lo-res versions of the same image.

    To update the image in the web client:

    1. Log in using the same credentials as for Publication Manager
    2. Select Content Manager from the slideout menu.
    3. Select Repository from the top menu.
    4. In the tree menu, navigate to the folder that contains your image.
    5. Select the image object you want to update in the list at top right.
    6. At bottom right, find the correct version of the image, and the correct resolution and language, if the image exists in multiple resolutions and/or languages.
    7. At this point you may want to create a new version of the image, just to make sure that your existing image isn't lost.
    8. Select the checkbox on the right hand side of the correct version, resolution and language.
    9. Select Upload from the menu at bottom right.
    10. From the local file selection dialog that opens, go to and select your updated image, and open it.
    11. The new image is uploaded and replaces your existing image. The existing image is now lost, unless you created a new version of the object.
    12. Repeat these steps for other languages and/or resolutions of the image (except step 7, making a new version).
  • 0 in reply to Mathijs Panhuijsen

    I have heard the web client way.  I have also been told by folk at SDL that you can just reference a new image.  I wonder how that works with the translation aspect?  In fact, how images work with the translation workflow with World Server (just starting to implement this software now)..  I need to find out more on that and will post what I learn.
  • 0 in reply to Mathijs Panhuijsen

    Well, if you're correct, that's still...not good.

    I've never seen a CMS that restricts the actions you can take on its main language stream just because it's going to require changes to the other languages; document's aren't composed in multiple languages at the same time. They're composed in their "home" language and then the CMS guides you concerning the parts of the other languages which will require updates as a result. That's just normal change management.

    When you say "lost" you mean it's no longer the head version of the resource, right? Not irrecoverably lost?

    At that point, assuming that the author is working in Publication Manager to work on their document, we're swapping between two different applications to replace one image. That is still, frankly, unacceptable. I don't mean to whine, but updating images is a flawlessly normal act; it should be a right-click away at all times. If the problem with Publication Manager is that the author doesn't have all the information they need to make an informed decision, then that's GUI that should exist. 

    Anyway, I'm just coming up to speed on SDL after years of using a competitor's system; some things, like the map editor in Publication Manager, are a welcome change. Some things a just a little shocking in the other direction.
  • 0 in reply to Steven Ridley

    Hi Steven- the thing to remember for translation is that the CMS looks for 3 things when it determines whether or not to send an object to translation. If 3 three things exist in the repo already, it doesn't sent to to translation. GUID + version + Language of object. If any of these three things is missing for the object, the translatable object will be created for the translators.
  • 0 in reply to Jeff Hooker

    I should point out that I'm an end user, so I don't know the ins and outs of the product design decisions. I'd agree with you that it would be an improvement if PM let you replace the image in a new version of the image object, which would then automatically cause it to be included in any future translation jobs (assuming, of course, that the object is configured for translation). But you'd still need to offer a way to update multiple resolutions of the image.

    By "lost" I just mean that, without creating a new object version, an end user like myself would need to jump through some hoops to get at the original, replaced image. I'd rather not take any risks.

    As a fellow end user, I would also like to have the image-update option within PM, at least if the image exists in only one language and only one resolution --which is often the case for me.

    I guess what it comes down to is whether your organization considers replacing an image a Big Deal. In your and my cases, it might not be. But it's not hard to imagine an organization where it is, and where it might even be managed by a separate person or even team.