Vectice Docs
API Reference (Latest)Vectice WebsiteStart Free Trial
Latest
Latest
  • 🏠Introduction
    • Vectice overview
      • Autolog
      • Next-Gen Autolog [BETA]
      • AskAI
      • Vectice for financial services
  • 🏁Quickstart
    • Getting started
    • Quickstart project
    • Tutorial project
    • FAQ
  • ▶️Demo Center
    • Feature videos
  • 📊Manage AI/ML projects
    • Organize workspaces
      • Create a workspace
      • Workspace Dashboard
    • Organize projects
      • Create a project
      • Project templates best practices
    • Invite colleagues
    • Define phase requirements
    • Collaborate with your team
  • 🚀Log and Manage Assets with Vectice API
    • API cheatsheets
      • Vectice Python API cheatsheet
      • Vectice R API cheatsheet
    • Connect to API
    • Log assets to Vectice
      • Autolog your assets
      • Log datasets
      • Log models
      • Log attachments and notes
      • Log code
      • Log a custom data source
      • Log assets using Vectice IDs
      • Log dataset structure and statistics
      • Log custom metadata in a table format
      • Log MLFLow runs
    • Retrieve assets from app
    • Manage your assets
    • Manage your iteration
    • Preserve your code and asset lineage
  • 🤝Create Model documentation and reports
    • Create model documentation with Vectice Reports
    • Streamline documentation with Macros
    • Auto-document Models and Datasets with AskAI Prompts
    • Document phase outcomes
  • 🗂️Admin Guides
    • Organization management
    • Workspace management
    • Teams management
    • User management
      • User roles and permissions
      • Update a user role in your organization
      • Activate and deactivate users
      • Reset a user's password
    • Manage report templates
  • 🔗Integrations
    • Integrations Overview
    • Integrate Vectice with your data platform
  • 💻IT & Security
    • IT & Security Overview
    • Secure Evaluation Environment Overview
    • Deployment
      • SaaS offering (Multi-Tenant SaaS)
      • Kubernetes self-hosted offering
        • General Architecture & Infrastructure
        • Kubernetes on GCP
          • Appendices
        • Kubernetes on AWS
          • Appendices
        • Kubernetes on Azure
          • Appendices
        • GCP Marketplace deployment
        • On premise
        • Configuration
      • Bring Your Own LLM Guide
    • Data privacy
    • User management
    • SSO management
      • Generic SAML integration
      • Okta SSO integration
    • Security
      • Data storage security
      • Network Security
        • HTTPS communication
        • Reverse proxy
        • CORS/CSRF
        • VPC segregation
      • Sessions
      • Secrets and certificates
      • Audit logs
      • SOC2
      • Security updates
      • Best practices
      • Business continuity
    • Monitoring
      • Installation guide
      • Customizing the deployments
    • Maintenance & upgrades
    • Integrating Vectice Securely
  • ⭐Glossary
    • Concepts
      • Workspaces
      • Projects
        • Setup a project
      • Phases
      • Iterations
        • Iterative development
      • Datasets
        • Dataset resources
        • Dataset properties
        • Dataset lineage and versions
      • Models
      • Reports
  • 🎯Release notes
    • Release notes
  • ↗️References
    • Vectice Python API Reference
    • Vectice R API Cheatsheet
    • Notebooks and code samples
    • Vectice website
Powered by GitBook
On this page
  • How to preserve code and lineage
  • How to Find Your Code and Model Lineage in Vectice

Was this helpful?

  1. Log and Manage Assets with Vectice API

Preserve your code and asset lineage

PreviousManage your iterationNextCreate model documentation with Vectice Reports

Last updated 8 months ago

Was this helpful?

Vectice captures, tracks, and visualizes the relationships between your data science assets—code, datasets, models, and artifacts—from origin to deployment. This ensures full transparency and traceability for better validation and collaboration.

With automatic code capture from your Notebook via the Vectice API, you can preserve both version-controlled and local files. This simplifies model management and saves time by ensuring your code is documented from the start.

How to preserve code and lineage

  1. Capture Code Automatically

    • Use the Vectice API to automatically capture code directly from your Notebook.

    • Utilize the code capture variable for version-controlled files (e.g., Git or Databricks).

    • For local files, use the code file capture variable to track those as well.

  2. Maintain Code Traceability

    • Your local files and Git repository can coexist in Vectice, ensuring complete traceability of your code.

    • This guarantees that the correct version of your code is always associated with your models.

  3. Document Code and Lineage

    • While Vectice allows you to update code later within the app, automating the code capture process from the start saves time and effort.

    • Capturing both the source code and input lineage is crucial for documenting your models and building trust in your data science workflows.

How to Find Your Code and Model Lineage in Vectice

To access your code and model lineage:

  1. Go to your project and select the Datasets or Models tab

  2. Select the desired asset and its version to view the corresponding lineage

  3. Under Lineage, you can view the code and assets used for the asset

  4. To edit the lineage in-app, select the Edit Lineage button and make changes

🚀