With Aginity Team™, your team of SQL analysts will be able to collaborate through sharing SQL scripts and snippets with one another in a single team catalog; using those catalog items to build new, more powerful SQL scripts; and encapsulating complex SQL expressions into powerful, reusable code that can be incorporated throughout your future SQL.
Setting Up the Team
After installing Aginity Team™, as an administrator, you have the ability to add team members into the collaborative environment. Your license permits a certain number of team members. You can add a team member by selecting “Manage Users” from the “Administration” menu within Aginity Team™ and completing the form.
Setting Up Your Active Catalog
Once you’ve set up the members of your team as users within Aginity Team™, it’s time to set up your active catalog. When you first install Team™, your catalog is empty. You can access it by clicking on the “Catalog” tab on the left side of the screen.
We recommend starting by creating a folder for every member of your team. Press the (+) button next to the Catalog header and enter a name for your first user. When you’re done, click OK. Repeat the process for all the users in your team.
It’s also useful to set up at least one additional folder that can contain catalog items for your whole team. You can call it “Shared Items”, for example, or “Common Area”. Whatever makes sense for your team.
Another thing you can do to enhance the way your team collaborates is to create some subfolders inside the Shared Items folder: one for “Approved” items and one for “Draft” items. This separation helps to provide a visual cue to the team as to whether an item has been tested or is trusted.
Importing Catalog Items from Aginity Pro™
You and your team members may have worked previously in Aginity Pro™ and created catalog items in that tool. Aginity can help you to easily and quickly migrate those catalog items into the shared catalog inside Aginity Team™. We’ll provide you a script that your team members can run on their machines to export their own catalogs to a file, which you as an administrator can then import into Aginity Team™.
The Aginity script will allow you to specify the path into which you wish to import items. We suggest that each user’s catalog items be imported into their home directory. This has two important effects: first, it makes it clear which items were originally created by which users, and secondly, it avoids the potential for naming collisions.
Working within Aginity Team™
A great way to start working in Aginity Team™ is for a team member to build in their own home folder at first – in addition, team members can create subfolders to help organize their catalog items. Once a user has a SQL script or snippet that he or she wants to share, we recommend saving that catalog item into the Draft subfolder of the Shared Items or Common Area folder. There, it is a signal to others that they can use it and provide feedback. Once it’s accepted as a useful and correct script, move it to the Approved subfolder instead. These items can now be used with confidence by all team members.
This is a Beta!
Aginity Team™ will help your team collaborate toward improved analytic outcomes, and there are many features to come. One of those features is the ability to control entitlement to folders, which will allow users to mark their own folders private and to work individually without inadvertently making scripts available that perhaps aren’t yet ready for sharing. Until that feature arrives, it is possible for any team member to edit or delete any catalog item, and for items to be created in any folder – even one without your name on it. We’ll look forward to your feedback on how the Active Catalog works for you and how we can improve it.