I just submitted an enhancement for this. I was just wondering if anyone else has a need for this?
What would be the need of multiple vaults vs 1? Just wondering
One example is to restrict access.
Why not just restrict access through permissions on one vault as needed?
As far as replicating vaults, can you just replicate certain sections of the vault?
About restricting access, I was throwing out a theoretical.
You can select folders for replication through the replication schema dialog box. Although, I don't work on the network side of things as Admin.
I recently saw two companies with each their vaults working together on a project. Let me tell you the exchange of files, updating versions, etc did not go smoothly
If there was a way to intelligently handle changes between two or more vaults, that would be very nice indeed.
In PDM Pro there is a process called replication of vaults. This is used where there is a main vault in 1 location and several other vaults handling other locations. The idea is that they update back/forth to the central location. A reason is so that there is less long-distance Internet transit times.
Yes. What is the SPR no? I want to see if it covers my needs.
I emailed a similar enhancement to a member of the product definition team we had onsite a few weeks ago to be able to paste as shared between vaults. We have multiple vaults because we operate essentially like an incubator and want to be able to send a project's data along with it as it matures, but would like the ability to share a common library between them.
Retrieving data ...