Version control with linked assets

[Adoptt Limited]

I’m trying to standardize our workflow and I’m interested to see how others treat linked files when moving through versions of their indd files.

Our company uses this file structure:

• file-v1.indd
• file-v2.indd
• file-v3.indd
• Links

The problem is when we update a link (for example change an image to black and white) the change is also reflected in v2 and v1, which is not what we want.

How do others deal with this? Do you either duplicate the linked file, rename it, amend it as required and link to this file, or do you keep everything from each version in a separate directory (including all assets), for example:

• File V1
  • file.v1.indd
  • Links
• File V2
  • file.v2.indd
  • Links
• File V3
  • file.v3.indd
  • Links

Thanks in advance.

[Laubender]

"The problem is when we update a link (for example change an image to black and white) the change is also reflected in v2 and v1, which is not what we want."

In this case you do not update an asset, you create a new one.

So treat it like that. Give its duplicate a new name and update the one link with the new asset where you need to do this.

Avoid by all means assets that have the same name, but different contents.

Regards,

Uwe Laubender

( ACP )