Multiple people working on a same project

[Tart]

Hi!

We are multiple users working on the same Affinity Publisher file and we do not always know if someone has the file opened. Is it possible to set Affinity Publisher to be notified if someone else has a file opened? Some software for example would not open a file, if it is open somewhere else, that would be best.

Thank you!

[GarryP]

It is not recommended that you open and edit Affinity documents which reside on network/cloud/non-local storage for various reasons.

Working with documents which are stored non-locally could cause you to get corrupted documents, which are often unrecoverable.

It is recommended that you only work on documents which are on local storage devices.
(These documents can be copies of the documents stored on non-local drives.)

[Tart]

Hi!

 

We have files stored in our local server.

But the problem is if I work on a file and someone else opens it, they can just open it. We are used from Adobe Indesign to be informed that the file is open, so I could not open it then. I would then know someone else is in the file and we for sure not work in the same file at the same time.

[walt.farrell]

1 hour ago, Tart said:

We have files stored in our local server.

Local, in GarryP's description, means not on a server of any kind. For best reliability, The files should be copied to your local hard drive on your computer.

Note: I'm making several responses, rather than 1, as I'm having trouble getting them posted if I do it in one post....

[walt.farrell]

 

3 hours ago, Tart said:

We are multiple users working on the same Affinity Publisher file

The only way to do that safely, that I know of, is to break up the Publisher file into chapters, and make them separate files. Then have one user combine them into the final publication using the Book function in V2. Then tell each user which chapter(s) they (and only they) are allowed to work on.

--- 

Actually, I just thought of another. If you have a version management system implemented for your server, you could have each user "check out" a copy of the file to work on, and then check it in when they're done. The version management system thus provides your locking, and can also provide the local copy of the file you need for true reliability.

[Tart]

Oh now I understand thank you!

I am afraid that is not optimal or possible for us, because we work with all our softwares on a server and only Publisher has issues.
I will still test out if there are no issue when files are saved locally and keep you updated.

Thank you also for the work around about how to work on the same file.

 

[walt.farrell]

You're welcome.

[GarryP]

Just in case anyone is still reading this: As Walt rightly said a while ago, by “local storage” I meant a storage mechanism which is not easily disconnected from, and is usually attached inside, the machine you are physically interacting with.

Examples of local storage (not comprehensive):

• Internal HDD;
• Internal SSD;
• Internal RAM.

Examples of non-local storage (not comprehensive):

• Network Attached Storage (NAS);
• Hard drive in a network server (nearby or otherwise);
• USB connected drive;
• USB stick / thumb drive;
• Cloud storage.

Basically, if you need to take the machine apart to get to it then it’s local storage.

I think it’s worth noting that some people can use/share Affinity files over some networks without any issues.
However, you may not know if you will have any issues until you have them and, by then, you could have lost a lot of work.
It is, of course, entirely up to the individual user, or organisation, whether they want to use non-local storage for Affinity work.

[Tart]

Thank you!!