Amanda wrote:amanda
We've been having trouble in teamwork with creating viewsets when signed in as a teammate. Is it only the Team Leader that can do this or are we missing something?
viewsets are a weird breed: they are 'owned' by teammates in the same way that a teammate can 'own' and edit elements from the project file, however there is no way to transfer this ownership so that another teammate can sign-in to them. i.e. you cannot signout of viewsets like you can for the rest of the project.
this means that although any teammate can create viewsets, they, and only they, are then allowed to edit them or 'share' them to the rest of the teammates for their use or for use in plotmaker.
this is another of those functions that works perfectly in a solo project, but goes bottom-up in the teamwork environment! the way we work around this is have a virtual teammate signed in continuously as teamleader. if anybody needs to create, manage or edit viewsets they simply open up that particular teamwork draft to make the changes - this ensures that the views are always owned by the same 'person'. if a normal teammate leaves the project, their viewsets won't be lost from editing, etc.
(btw - this virtual teamleader also manages the attributes and dwg x-ref management: see my topic here)
another thing to note: if a solo project is shared to a teamwork file with viewsets already present, the views will still appear to be owned by nobody in the teamwork file: you see the little teamwork heads icon if it's not in your 'workspace'.
confused? so are we all!
i think that there has been a wish somewhere along the line for GS to sort out viewset management...HTH
~/archiben
amanda
okay - a bit more detail:
see the attached screenshot image - it shows all of the viewset management controls from the drop-down box at the top of the 'View Editor'.
you can see all of the viewsets available at the bottom. the ones with the little head icons are viewsets owned by another team member that are 'shared' to the team for viewing. at the bottom is a set that i've created for my own use in navigating the project - i've shared it for others to use if they wish. it's denoted by the hand icon - this means that i own it and have shared it. the final viewset in the list is owned by me, but not shared.
other teammates can also create and use their own viewsets, and unless they've shared them they won't show up in my list.
(by the way - don't set your viewsets up like this. it's a system that we have in place for a variety of reasons, but it's not the most efficient or 'best practice': look at the defaults in a 'new and reset' document to see how GS intend them to be used! )
let's say that you have a project with various team members: "Ben Frost", "Amanda Mason" and "Djordje Grujic". each of the teammates here can sign into a project as team leader if nobody else already has this status. so "Amanda Mason" signs in as team leader and creates a viewset for all general arrangement drawings. "Amanda Mason" then shares this viewset and all other teammates now see this viewset in their view editor,
this viewset is owned by "Amanda Mason" not the team leader - even though "Amanda Mason" was team leader when she created the viewset. only somebody signed into the project as "Amanda Mason" can edit, add to, delete, etc anything associated with these views.
and this is where the virtual team leader comes in:
when the very first person signs into a team project type in a generic name at the very first dialogue screen, rather than your own. we use "File Manager", but it could equally be "Team Leader" or "Project Architect" or "Mickey Mouse". at the same time choose the 'team leader' status.
(aside - if you are using x-ref management also sign into all stories and all layers already associated with x-ref drawings at this point. see the link in my post up there)
so when you're finished, save this teamwork draft file on the server (or somewhere the team has access to) as "ProjectManagement.plc" or similar, and then repeat the sign-in process with your own name and everything that you need to work on.
any project management should then be done through this team leader draft on the server - you can limit who can and can't open it by carefully distributing the team leader password. all new viewsets and view editting should be done by opening this draft and sending changes. all attribute management can also be done in this file (layers, composites, etc, etc) without the need for continuous signing in and out of teammates to modify small settings.
it ensures that anybody (with teamleader password) can manage the viewsets without having to pester the person who first created the viewset, etc.
another thing to note, viewsets are stored (along with most of the project) with ID numbers and not names - it's this number that allows plotmaker to keep track of the view if you modify naming conventions, etc.
hope that this makes sense and you'll find it useful. it's essentially a workaround for the poor project management abilities in the teamwork environment and something i really hope graphisoft are working to rectify!
~/archiben
okay - a bit more detail:
see the attached screenshot image - it shows all of the viewset management controls from the drop-down box at the top of the 'View Editor'.
you can see all of the viewsets available at the bottom. the ones with the little head icons are viewsets owned by another team member that are 'shared' to the team for viewing. at the bottom is a set that i've created for my own use in navigating the project - i've shared it for others to use if they wish. it's denoted by the hand icon - this means that i own it and have shared it. the final viewset in the list is owned by me, but not shared.
other teammates can also create and use their own viewsets, and unless they've shared them they won't show up in my list.
(by the way - don't set your viewsets up like this. it's a system that we have in place for a variety of reasons, but it's not the most efficient or 'best practice': look at the defaults in a 'new and reset' document to see how GS intend them to be used!
)let's say that you have a project with various team members: "Ben Frost", "Amanda Mason" and "Djordje Grujic". each of the teammates here can sign into a project as team leader if nobody else already has this status. so "Amanda Mason" signs in as team leader and creates a viewset for all general arrangement drawings. "Amanda Mason" then shares this viewset and all other teammates now see this viewset in their view editor,
this viewset is owned by "Amanda Mason" not the team leader - even though "Amanda Mason" was team leader when she created the viewset. only somebody signed into the project as "Amanda Mason" can edit, add to, delete, etc anything associated with these views.
and this is where the virtual team leader comes in:
when the very first person signs into a team project type in a generic name at the very first dialogue screen, rather than your own. we use "File Manager", but it could equally be "Team Leader" or "Project Architect" or "Mickey Mouse". at the same time choose the 'team leader' status.
(aside - if you are using x-ref management also sign into all stories and all layers already associated with x-ref drawings at this point. see the link in my post up there)
so when you're finished, save this teamwork draft file on the server (or somewhere the team has access to) as "ProjectManagement.plc" or similar, and then repeat the sign-in process with your own name and everything that you need to work on.
any project management should then be done through this team leader draft on the server - you can limit who can and can't open it by carefully distributing the team leader password. all new viewsets and view editting should be done by opening this draft and sending changes. all attribute management can also be done in this file (layers, composites, etc, etc) without the need for continuous signing in and out of teammates to modify small settings.
it ensures that anybody (with teamleader password) can manage the viewsets without having to pester the person who first created the viewset, etc.
another thing to note, viewsets are stored (along with most of the project) with ID numbers and not names - it's this number that allows plotmaker to keep track of the view if you modify naming conventions, etc.
hope that this makes sense and you'll find it useful. it's essentially a workaround for the poor project management abilities in the teamwork environment and something i really hope graphisoft are working to rectify!
~/archiben
Still looking?
