Version management for Graphics | Community
Skip to main content
sschnelbach
Level 5
April 16, 2026
Question

Version management for Graphics

  • April 16, 2026
  • 1 reply
  • 8 views

What are the best practices for managing graphics and ensuring the most recent copy uploaded to the repository is the current VERSION, not just a working copy?

All documentation on version control I’ve found for Guides is specific to the DITA files, not graphics objects.

When we upload/copy an updated graphic, the popup windows asks us if we want to create a version of the EXISTING working copy. It does not ask about creating a version for the correction we are uploading. It looks like whatever we last uploaded remains a working copy, not an actual version, which means graphics sent out for translation may not be the most recent and correction file.

Does this mean any time we upload a corrected graphic, we have to drag/drop twice. Once to upload and force the system to create a new version of the existing working copy and the new graphic become the existing working copy. Then a second time to force that correction to be the newest version?

I’m seeing graphics that I know have been changed/corrected being sent out for translation since the translation project creation process only sends out the most recent VERSION of all content.

    1 reply

    Level 1
    April 16, 2026

    If you sending translations via baseline, then we’ve encountered the same issue. Seems to be a bug as sending current working copy includes the most recent version of graphics. The baseline indicates that the most recent of the graphic is included but it is not.

    We have a ticket open for this.

    sschnelbach
    Level 5
    April 16, 2026

    We do not typically send files out via baseline. We most often send out the latest version.

     

    Good to hear that we’re not the only ones seeing some of these issues! Thank you.