Project Sharing 2.0 – Project sharing was introduced with Vectorworks 2016. It worked really well, but it did require that all the users be on the same network. this can work fine when you’re in the same office, but it didn’t work well if you weren’t in the same office, you would require a Virtual Personal Network in order to do this. Many people they work with others that are not in the same office, but still wanted use project sharing. Now, project sharing can be carried out using a range of cloud-based systems. There are several other cloud based storage systems, but not every one of the systems is supported. In basic terms Vectorworks needs to be able to look at the file that stored in the cloud, and detect whether that file has been updated or not. It also needs to be able to write to that file.
Edit The Workspace For Project Sharing – One of the suggestions that I have had is that the location of the save and commit command should be moved closer to the save command. As we have already covered, when you save your project it doesn’t commit the information to the project file.
Revert – This command allows you to throw away all of the changes you’ve made in your current working file and replace them with the latest data from the project file.
Saving – Because of the way that Vectorworks are structured the Working Files and the Project Files, saving has to be dealt with in a slightly different way.
Checking Out A Layer – The basic strategy of sharing is checking out a layer. This means that you will have to organise your work so that users can check out the required layers. It was announced at the Vectorworks Design Summit 2016 that the next iteration of project sharing will allow users to check out objects or groups of objects. This should make it easier to organise your files.
Project Sharing Privileges – Not everybody should be given the same rights to it edit information on the project. Project sharing allows you to set the privileges for different users.
Setting Up a Project for Sharing – Setting up a project for Project Sharing is reasonably straightforward, but before you commit to Project Sharing, ensure that the project is set up correctly with stories, layers, classes, and resources. While you are able to make changes to these later, it will be easier to ensure that they are all created before the project is shared.
Referencing DXF/DWG Files – Import the drawing from the consultant. Check it for accuracy. Then reference the consultant drawing to your project.
When you get a revised drawing, import it into a new document and save it with the same name as the old consultant’s drawing, overwriting the old file. When you open your drawings, you will see the new work from the consultant. This will allow you to easily update your drawings.
Referencing PDF Files – As with image files, PDF files can be drag-and-dropped into a Vectorworks file, or you can use the Import PDF… command. In either case when you import a PDF file, you have the choice of whether to import the file directly or whether to reference the file.
Referencing Image Files – When you import an image file you can choose to have the image file placed directly in the drawing, or you can choose to reference the image file. Why would you prefer one method over the other?
If you are working with others and they are updating the images files, referencing the image files would allow you to update the images files easily.
Normally, you can only have one person working on the file at a time. So, you could divide the file up of the pots, you could divide the file open to parts that you can reference, we could set up a system that shared all of the information. Either way, it is all about sharing information on the project – Project Sharing.
Some projects need more than one person to work on them. Maybe the project is large, maybe the deadline is short, but either way, you need more than one person on the project. Normally, you can only have one person working on the file at a time. So, you could divide the file into parts, you could divide the file into parts that you can reference, or you could set up a system that shared all of the information. Either way, it is all about sharing information on the project – Project Sharing.
At present we are not allowed to create project sharing on dropbox. Project sharing has to be set up on a network system, either in an office, or using a VPN (Virtual Personal Network). Sharing systems like dropbox, box, et cetera use a system that project sharing will not work with at the moment. I have no way of knowing, but I hope this will change in the future.
We are covering Project Sharing in the May archoncad Interactive Workshops, Book Now!
When you are setting up a project sharing project you will want to limit the privileges of the users. Not everybody should have administrator privileges. There are a range of privileges that allow users different access to the file. The administrator has full privileges allowing them to add or remove users, change the privileges of users, change any resource in the file, etc. you can also create users that have limited access to parts of the file. The restricted access to the file can prevent people from updating or creating new layers, updating or creating new classes, editing resources, and is also a read-only privilege that doesn’t allow any changes at all.
Project sharing is the ability to have several people working on a project where all theinformation is saved in a single project file. In the past you could use Reference Files, but these only shared information in one direction. Project sharing allows several people to share the information in both directions. We will be covering this in manual and online sessions in May 2016. Book Now…
When you have completed your task on the project, you should release the layers you been working on. Remember, nobody else can work on the layers that you have checked out, so in order for other people to work on those layers you have to release them. You can choose to release the layers, but when you do, if you haven’t save saved and committed the work to the project file, you will be asked whether you want to commit this work or discard it.
Because your working file is separate from your project file, when you save your working file, the information is not automatically transferred to the project file. This allows you to save your work without updating the project file. This might seem strange, but it would be a good idea if you wanted to try out a new design without changing the project file for everybody else on the team.