Skip to main content

Managing Analytics Catalog and Projects

This guide explains how to use Coginiti's Analytics Catalog to organize, version, share, and publish your data analysis projects. The Analytics Catalog provides a comprehensive project management system with three distinct workspaces and a complete collaboration workflow similar to modern version control systems.

Overview​

Coginiti's Analytics Catalog is a centralized repository for managing data analysis projects, queries, and related assets. It provides version control, collaboration features, and publishing workflows that enable teams to work together effectively while maintaining project integrity and access control.

Key Features​

Three Workspace System:

  • Personal - Individual workspace for private projects and development
  • Shared - Collaborative workspace for team projects and shared access
  • Project Hub - Central repository for published, versioned projects

Version Control:

  • All catalog assets are automatically versioned
  • Complete history tracking for all changes
  • Version comparison and diff capabilities
  • Semantic versioning for published projects

Project Management:

  • Projects as fundamental organizing units
  • Nested folder and file organization
  • Project sharing with role-based access control
  • Publishing workflow with review process

Collaboration Features:

  • Project sharing with multiple access levels
  • Review process with line-by-line comments
  • Notification system for project changes
  • Team-based publishing with approval workflows

Analytics Catalog Workspaces​

Personal Workspace​

The Personal workspace serves as your individual development environment where you can create, modify, and test projects before sharing or publishing them.

Characteristics​

  • Private by default - Only you can access projects in your personal workspace
  • Development environment - Ideal for experimenting and initial project creation
  • Version controlled - All changes are tracked and versioned
  • Publishing source - Projects can be published from personal to Project Hub

Use Cases​

  • Initial project development and testing
  • Personal queries and analysis work
  • Experimental features and concepts
  • Staging area before sharing with team

Shared Workspace​

The Shared workspace facilitates collaboration by providing a space where team members can work together on projects with controlled access levels.

Characteristics​

  • Collaborative environment - Multiple users can access and modify projects
  • Role-based access - Different permission levels (Viewer, Editor, Co-owner)
  • Notification system - Users receive notifications for project changes
  • Comment system - Team members can leave comments on files and lines

Access Levels​

Co-owner:

  • Full control over the project
  • Can manage and share the project with others
  • Can modify project settings and permissions

Editor:

  • Can make changes to project content
  • Cannot share the project with others
  • Can participate in review processes

Viewer:

  • Read-only access to project content
  • Can view project history and comments
  • Cannot modify project files or settings

Use Cases​

  • Team collaboration on analysis projects
  • Code review and feedback processes
  • Shared resources and common queries
  • Cross-functional project development

Project Hub​

The Project Hub serves as the central repository for finalized, published projects that are ready for broader organizational use.

Characteristics​

  • Centralized repository - Organization-wide access to published projects
  • Semantic versioning - Published projects follow version numbering conventions
  • Admin-controlled - Administrators manage structure and access permissions
  • Immutable versions - Published versions cannot be directly modified

Admin Responsibilities​

  • Setting up repository structure and organization
  • Defining access levels and user permissions
  • Managing folder hierarchy and organization
  • Assigning Publisher roles to team members

Use Cases​

  • Finalized analysis projects for organizational use
  • Reusable code libraries and templates
  • Best practices and standardized procedures
  • Historical record of completed projects

Project Management​

Creating Projects​

Projects are the fundamental organizing unit in the Analytics Catalog, containing folders, files, and related assets for specific analysis initiatives.

Create a New Project​

Step 1: Access Project Creation

  1. Navigate to the Catalog in the left sidebar
  2. Right-click on any existing Catalog asset to open the context menu
  3. Choose "New Project" to create a new project entity

Step 2: Configure Project Details

  1. Project Name: Enter the project name
    • Must start with a letter (a-z, A-Z), digit (0-9), or underscore (_)
    • Choose descriptive, meaningful names
  2. Project Description (optional): Provide a brief project overview
  3. Project Location: Use the dropdown to select the project path
    • Default location is where you initiated project creation
    • Can be modified to organize projects logically

Step 3: Create Project

  1. Click "Create" to finalize the project creation
  2. The project appears in the selected workspace location
  3. Begin adding folders and files to organize project content
Project Nesting Restriction

A project cannot include another project within it. Projects must be created at the appropriate hierarchy level.

Create Project from Existing Folder​

Transform existing folder structures into organized projects:

Step 1: Convert Folder

  1. Right-click on existing Catalog folder to access context menu
  2. Choose "Convert to Project" to transform the folder

Step 2: Configure Conversion

  1. Project Name: Rename if necessary (defaults to folder name)
  2. Project Description (optional): Add project overview
  3. Project Location: Modify path if needed (defaults to current location)

Step 3: Complete Conversion

  1. Click "Create" to convert folder to project
  2. Existing folder contents are preserved and organized
  3. Project gains version control and collaboration features

Project Organization Best Practices​

Folder Structure​

Create logical folder hierarchies that mirror your workflow:

Project Name/
├── data/
│   ├── raw/
│   ├── processed/
│   └── reference/
├── queries/
│   ├── exploratory/
│   ├── production/
│   └── archived/
├── reports/
│   ├── monthly/
│   ├── quarterly/
│   └── annual/
├── documentation/
│   ├── requirements/
│   ├── specifications/
│   └── user-guides/
└── utilities/
    ├── common-functions/
    └── templates/

Naming Conventions​

  • Use descriptive names that clearly indicate purpose
  • Follow consistent patterns across similar projects
  • Include version indicators when appropriate
  • Avoid special characters that might cause issues

Content Organization​

  • Group related files in appropriate folders
  • Separate development from production assets
  • Maintain clear documentation for project purposes
  • Use consistent file naming within projects

Project Search and Discovery​

Coginiti provides efficient search capabilities for finding projects and assets:

Search Functionality:

  • Search box at the top of the Catalog panel
  • Finds all assets containing search terms in their names
  • Hover over results to view full path information
  • Quick navigation to located assets

Search Tips:

  • Use specific terms for targeted results
  • Search across all workspaces simultaneously
  • Combine search with folder navigation for efficiency
  • Bookmark frequently accessed projects

Version Control and History​

Automatic Versioning​

All catalog assets are automatically versioned, providing complete change tracking and history management.

Version Tracking Features​

  • Automatic snapshots of all changes
  • Timestamp recording for each modification
  • User attribution for change tracking
  • Complete change history preservation

Accessing Version History​

Step 1: Open History View

  1. Right-click on catalog item to open context menu
  2. Select "View History" from the options
  3. History window opens showing all versions

Step 2: Review Version Information

  • Version numbers and timestamps
  • User information for each change
  • Change descriptions and comments
  • File modification details

Version Comparison​

Compare different versions to understand changes and evolution:

Compare Process​

Step 1: Access Comparison

  1. Open the History window for the desired item
  2. Click the "Compare" button in the interface
  3. Select versions to compare from available options

Step 2: Review Differences

  • Side-by-side comparison of selected versions
  • Highlighted changes showing additions and deletions
  • Line-by-line differences for detailed analysis
  • Context preservation for understanding changes

Comparison Use Cases​

  • Code review processes to understand modifications
  • Debugging assistance to identify problematic changes
  • Documentation updates to track content evolution
  • Compliance auditing for change verification

Version Management Benefits​

Change Tracking​

  • Complete audit trail of all modifications
  • User accountability for change management
  • Time-based analysis of project evolution
  • Rollback capabilities for error recovery

Collaboration Support​

  • Conflict resolution through version comparison
  • Change attribution for team coordination
  • Review processes supported by version history
  • Documentation of decision rationale

Project Sharing and Collaboration​

Sharing Projects​

Project sharing enables team collaboration while maintaining appropriate access controls and security.

Share a Project​

Step 1: Initiate Sharing

  1. Navigate to Personal section of the Catalog
  2. Find the target project in your personal workspace
  3. Right-click on the project to access context menu
  4. Select "Share" to begin the sharing process

Step 2: Select Recipients

  1. Choose sharing target: Individual users or groups
  2. Use search function to filter users by typing names
  3. Select multiple recipients as needed for project scope
  4. Group sharing provides access to all group members
Group Sharing Benefits

When sharing with a group, all direct and inherited members gain access automatically, simplifying management for large teams.

Step 3: Set Access Levels Choose appropriate permission levels based on collaboration needs:

Co-owner Access:

  • Full control over the project
  • Can modify all project content
  • Can share the project with additional users
  • Can change project settings and permissions

Editor Access:

  • Can make changes to project content
  • Can add, modify, and delete files
  • Cannot share the project with others
  • Can participate in review and comment processes

Viewer Access:

  • Read-only access to project content
  • Can view all files and project history
  • Cannot modify files or project settings
  • Can leave comments (if commenting is enabled)

Step 4: Complete Sharing

  1. Review selected users and permissions
  2. Click "Share" to finalize the process
  3. Project appears in recipients' Shared workspace
  4. Notifications sent to all new collaborators

Collaboration Features​

Notification System​

New Project Access:

  • Users receive notifications when granted project access
  • Notifications include direct links to the shared project
  • Projects appear automatically in recipients' Shared workspace
  • Quick access enables immediate collaboration

Change Notifications:

  • Project owners receive notifications of modifications
  • Notifications include links to modified assets
  • Change details help maintain project awareness
  • Version history accessible from notification links

Comment System​

File-Level Comments:

  • Leave comments on specific files within projects
  • Comment threads for ongoing discussions
  • User attribution and timestamp tracking
  • Comment resolution and follow-up capabilities

Line-Level Comments:

  • Detailed comments on specific code or content lines
  • Precise feedback for code review processes
  • Context-aware discussions about specific implementations
  • Integration with version control for change tracking

Collaborative Workflows​

Review Processes:

  • Structured review workflows for project changes
  • Reviewer assignment and notification system
  • Comment resolution tracking and status management
  • Approval processes for project progression

Team Development:

  • Multiple editors working on different project aspects
  • Coordination through shared workspace visibility
  • Change tracking for team coordination
  • Conflict resolution through version management

Project Hub Administration​

Setting Up Project Hub Structure​

Administrators are responsible for creating and maintaining the Project Hub organization to support company workflows and access requirements.

Repository Structure Planning​

Organizational Alignment:

  • Structure reflects company organization and workflows
  • Department-based folder hierarchies
  • Project type classifications (Analytics, Reporting, Research)
  • Access level groupings for security management

Example Structure:

Project Hub/
├── Analytics/
│   ├── Customer-Analytics/
│   ├── Financial-Analytics/
│   └── Operational-Analytics/
├── Reporting/
│   ├── Executive-Dashboards/
│   ├── Departmental-Reports/
│   └── Regulatory-Reports/
├── Research/
│   ├── Market-Research/
│   ├── Product-Research/
│   └── Technical-Research/
└── Templates/
    ├── Query-Templates/
    ├── Report-Templates/
    └── Analysis-Templates/

Creating Project Hub Structure​

Step 1: Access Project Hub

  1. Navigate to "Project Hub" section in the Catalog sidebar
  2. Right-click in the Project Hub space to open context menu
  3. Select "New Folder" to create organizational structure

Step 2: Create Folder Hierarchy

  1. Create top-level folders for major organizational divisions
  2. Add sub-folders for specific project categories
  3. Organize by function, department, or project type
  4. Maintain consistent naming conventions

Step 3: Configure Folder Access

  1. Right-click on target folder to open context menu
  2. Choose "Share" to begin access configuration
  3. Select users or groups for folder access
  4. Set appropriate access levels for each recipient

Access Control Management​

Access Levels in Project Hub​

Publisher Access:

  • Can publish new projects to the folder
  • Can publish new versions of existing projects
  • Full project management capabilities within assigned folders
  • Cannot modify access permissions (admin-only)

Viewer Access:

  • Can view all folder contents and projects
  • Can access project files and version history
  • Cannot publish or modify projects
  • Read-only access to all project materials

Folder-Level Permissions​

Inheritance Model:

  • Access levels apply to folder and all contents
  • Sub-folders inherit parent folder permissions
  • Cannot grant higher access than parent folder allows
  • Consistent access control across folder hierarchies

Permission Management:

  1. Identify folder requiring access control
  2. Right-click folder to access context menu
  3. Select "Share" to configure permissions
  4. Choose between individual users or groups
  5. Set appropriate access level (Publisher or Viewer)
  6. Click "Share" to apply permissions
Access Level Inheritance

When assigning access levels to folders, the same level applies to everything inside the folder, including all sub-folders and projects.

Best Practices for Project Hub​

Organizational Structure​

  • Align with business structure for intuitive navigation
  • Use clear, descriptive folder names for easy identification
  • Maintain consistent hierarchy depths across similar areas
  • Plan for growth and future organizational changes

Access Management​

  • Use groups instead of individuals when possible for easier management
  • Regular access reviews to ensure appropriate permissions
  • Document access rationale for compliance and auditing
  • Coordinate with HR for organizational change impacts

Publishing Workflow​

Publishing Overview​

The publishing process in Coginiti provides a structured approach to moving projects from development to production, ensuring quality control and version management.

Publishing Benefits​

Content Integrity:

  • Only authorized Publishers can publish projects
  • Prevents unauthorized changes to published content
  • Maintains stability of production assets
  • Ensures consistent project versions

Version Preservation:

  • Earlier versions remain accessible and unchanged
  • Dependent projects continue functioning with previous versions
  • Historical record of project evolution
  • Rollback capabilities for issue resolution

Collaboration Enhancement:

  • Published projects accessible to authorized users
  • Streamlined sharing within authorized groups
  • Centralized access to approved content
  • Reduced duplication and improved reuse

Quality Assurance:

  • Review processes before publication
  • Testing opportunities with working copies
  • Controlled modification processes
  • Consistent versioning standards

Publishing New Projects​

Transform personal or shared projects into published, versioned assets available in the Project Hub.

Publish from Personal Workspace​

Step 1: Prepare for Publishing

  1. Review project content thoroughly for completeness
  2. Test all queries and functionality to ensure reliability
  3. Organize files and folders logically within the project
  4. Document project purpose and usage instructions

Step 2: Initiate Publishing

  1. Navigate to Personal section of the Catalog
  2. Find the project you wish to publish
  3. Right-click on the project to open context menu
  4. Select "Publish" to start the publishing process

Step 3: Configure Publication

  1. Project Name: Enter the name for the published version
  2. Version Number: Set initial version (e.g., 1.0.0, v1.0)
  3. Publication Location: Choose destination folder in Project Hub
  4. Description: Provide overview of project and major features
  5. Click "Publish" to complete the process
Version Numbering

Use the same versioning system your team typically employs for consistency and easy change tracking. Common approaches include semantic versioning (1.0.0) or simple incremental versioning (v1, v2).

Step 4: Verify Publication

  1. Check Project Hub for newly published project
  2. Verify access permissions are correctly applied
  3. Test project functionality in published environment
  4. Notify team members of new published project

Publishing Updated Versions​

Modify existing published projects through a controlled workflow that preserves previous versions while introducing new functionality.

Create Working Copy​

Step 1: Access Published Project

  1. Navigate to Project Hub section of the Catalog
  2. Locate the project you want to modify
  3. Right-click on the project to access context menu
  4. Choose "Create Working Copy" to make editable version

Step 2: Configure Working Copy

  1. Project Name: Rename if needed (defaults to original name)
  2. Project Description: Update description for working copy purpose
  3. Project Location: Select location in Personal workspace
  4. Click "Create" to generate working copy

Step 3: Invite Collaborators (if needed)

  • Share working copy with team members for collaboration
  • Assign appropriate access levels based on involvement
  • Include Publishers if you lack publishing permissions
  • Coordinate review process before publication

Modify and Test Working Copy​

Development Process:

  1. Make necessary modifications to project content
  2. Test all changes thoroughly in working copy environment
  3. Document significant changes for version description
  4. Review with team members if collaborative project

Quality Assurance:

  • Validate all queries execute correctly
  • Check data integrity and result accuracy
  • Test integration points with other systems
  • Ensure documentation is current and accurate

Publish Updated Version​

Step 1: Prepare for Publication

  1. Complete all modifications and testing
  2. Finalize documentation and change descriptions
  3. Coordinate with team for publication timing
  4. Ensure working copy is ready for production use

Step 2: Publish Working Copy

  1. Right-click on working copy to open context menu
  2. Select "Publish" to begin publication process
  3. Configure publication settings:
    • Version Number: Increment appropriately (e.g., 1.1.0, v2.0)
    • Location: Choose destination (usually same as original)
    • Description: Highlight major changes and improvements
  4. Click "Publish" to create new version
Location Changes

If you change the publication location, it creates a separate, independent project rather than a new version of the original. Use "Publish as new Project" if creating a derivative work.

Step 3: Verify New Version

  1. Confirm new version appears in Project Hub
  2. Test published version functionality
  3. Verify access permissions are correctly inherited
  4. Update documentation or announcements as needed

Review and Approval Workflow​

Projects can incorporate formal review processes before publication, similar to code review workflows in software development.

Request Project Review​

Step 1: Initiate Review

  1. Navigate to shared project requiring review
  2. Right-click on project to access context menu
  3. Select "Request Review" to begin review process
  4. Configure review parameters

Step 2: Add Reviewers

  1. Select reviewers from available team members
  2. Include users with Publisher permissions if required for publication
  3. Add subject matter experts relevant to project content
  4. Specify review deadline if time-sensitive

Step 3: Submit Review Request

  1. Add review description explaining changes and context
  2. Specify review focus areas or particular concerns
  3. Submit request to notify selected reviewers
  4. Track review status through notification system

Review Process​

Reviewer Responsibilities:

  1. Receive review notification with project access
  2. Thoroughly examine project content and changes
  3. Leave comments on files and specific lines as needed
  4. Provide constructive feedback for improvement
  5. Approve or request changes based on review findings

Comment Types:

  • File-level comments for general feedback
  • Line-level comments for specific code or content issues
  • Suggestion comments for improvement recommendations
  • Approval comments indicating satisfaction with changes

Review Resolution:

  1. Address reviewer comments and feedback
  2. Make necessary modifications based on input
  3. Respond to comments with explanations or confirmations
  4. Request re-review if significant changes made
  5. Obtain final approval from all required reviewers

Publication After Review​

Step 1: Complete Review Process

  1. Ensure all comments are addressed or resolved
  2. Obtain necessary approvals from reviewers
  3. Verify Publisher approval if required for publication
  4. Document final changes made during review

Step 2: Publish Reviewed Project

  1. Follow standard publication process for approved project
  2. Include review outcomes in version description
  3. Credit reviewers in publication notes if appropriate
  4. Notify stakeholders of successful publication

Publishing Best Practices​

Pre-Publication Checklist​

  • Comprehensive testing of all project components
  • Documentation review and updates
  • Version numbering consistency with team standards
  • Access permission verification for target location
  • Change description completeness and accuracy

Version Management​

  • Semantic versioning for clear change communication
  • Consistent numbering across related projects
  • Change documentation for each version increment
  • Backward compatibility consideration for dependent projects

Collaboration Optimization​

  • Early reviewer involvement for complex projects
  • Clear communication of review expectations
  • Timely response to review feedback
  • Documentation of review outcomes and decisions

Notifications and Communication​

Notification Types​

Coginiti's notification system keeps all project stakeholders informed of relevant changes and activities.

Access Notifications​

New Project Access:

  • Triggered when users are granted access to projects
  • Includes direct link to the shared project
  • Provides access level information
  • Enables immediate project engagement

Permission Changes:

  • Notifications for access level modifications
  • Alerts for added or removed permissions
  • Information about scope of access changes
  • Contact information for permission grantor

Change Notifications​

Project Modifications:

  • Owners notified of changes to their projects
  • Specific asset modification details
  • Direct links to modified content
  • Contributor identification and timestamp

Version Updates:

  • Notifications for new published versions
  • Version number and change summary
  • Links to updated projects in Project Hub
  • Migration guidance if necessary

Review Notifications​

Review Requests:

  • Reviewers notified of pending reviews
  • Project context and review requirements
  • Direct access to review interface
  • Deadline information if specified

Review Status Updates:

  • Project owners notified of review progress
  • Comment additions and resolutions
  • Approval status changes
  • Final review outcomes

Notification Management​

Notification Preferences​

  • Customize notification types received
  • Set frequency preferences for non-urgent updates
  • Configure delivery methods (in-app, email)
  • Manage notification grouping for related projects

Notification Actions​

Quick Access:

  • Direct links to relevant projects and assets
  • Context-sensitive navigation to specific content
  • Immediate access to review interfaces
  • Streamlined workflow continuation

Information Integration:

  • Version history access from notifications
  • Change comparison capabilities
  • User activity context and attribution
  • Project timeline and evolution tracking

Best Practices and Tips​

Project Organization​

Structure Planning​

  • Mirror workflow patterns in project organization
  • Use consistent folder hierarchies across similar projects
  • Plan for scalability and future growth
  • Document organizational standards for team consistency

Naming Conventions​

  • Choose descriptive, meaningful names for all projects and assets
  • Follow consistent patterns across the organization
  • Include version indicators when appropriate
  • Avoid special characters that might cause technical issues

Content Management​

  • Separate development from production assets clearly
  • Maintain comprehensive documentation for all projects
  • Use templates and standards for consistency
  • Regular cleanup of obsolete or duplicate content

Collaboration Optimization​

Access Control​

  • Grant minimum necessary permissions for security
  • Use groups for permission management when possible
  • Regular access reviews to maintain appropriate permissions
  • Document access rationale for compliance and auditing

Communication​

  • Use comment systems effectively for feedback
  • Provide context in all communications and changes
  • Respond promptly to review requests and comments
  • Document decisions and rationale for future reference

Review Processes​

  • Establish clear review criteria and expectations
  • Include appropriate stakeholders in review processes
  • Provide constructive, actionable feedback
  • Follow up on review outcomes and implementations

Version Control Strategy​

Versioning Standards​

  • Establish consistent numbering schemes across projects
  • Document versioning policies for team adherence
  • Plan version migration strategies for breaking changes
  • Maintain backward compatibility when possible

Change Management​

  • Document all significant changes in version descriptions
  • Test thoroughly before publishing new versions
  • Coordinate releases with dependent projects and stakeholders
  • Plan rollback procedures for critical issues

Summary​

You have successfully learned to manage Coginiti's Analytics Catalog and Projects! Key achievements:

✅ Workspace Understanding: Mastery of Personal, Shared, and Project Hub workspaces ✅ Project Management: Creation, organization, and lifecycle management of analysis projects ✅ Version Control: Complete change tracking, history management, and version comparison ✅ Collaboration: Project sharing, access control, and team coordination ✅ Publishing Workflow: Structured process for moving projects from development to production ✅ Review Process: Formal review and approval workflows with comment systems ✅ Administration: Project Hub setup, access control, and organizational structure management

Your team now has a comprehensive project management and collaboration system that supports the complete analytics development lifecycle from initial exploration through production deployment and ongoing maintenance.