Skip to content

Studio FAQ

Why can’t a Studio asset become a server or other repository asset?

Section titled “Why can’t a Studio asset become a server or other repository asset?”

Data quality. Think of Studio as a workshop outside your house: it’s where you can work freely and get messy, and you don’t bring dirty clothes and shoes inside. The asset repository is the house. vScope cleans the data, folds it, and only then lets it in, while everything raw stays in Studio. If custom data could be mixed in as it is, the repository would gradually lose trust and become obsolete.

Studio assets are therefore a separate asset type. You can use them in any content, but they are never merged with discovered assets.

Data from Studio can reach the house in two ways:

  1. Linking: link a Studio asset to the matching asset in the repository, so Studio data shows alongside it. See Studio.
  2. An official connector: if vScope builds an official connector for the data source, the assets enter the repository through their own entrance, with vScope handling collection and quality.

What does a CSV file need, and can I tag the assets?

Section titled “What does a CSV file need, and can I tag the assets?”

Only one column that uniquely identifies each row. Every other column is optional and can become a tag, with no requirements. A column with the same value on every row, such as fullimport = yes, tags all Studio assets from the file. See Studio File.

What happens when I remove a row from the file?

Section titled “What happens when I remove a row from the file?”

The Studio asset is removed directly on the next run.

Can I use a manually maintained file for networks where discovery can’t run?

Section titled “Can I use a manually maintained file for networks where discovery can’t run?”

Yes. Each row becomes a Studio asset, and the file is the source of truth, so someone needs to own it and update it routinely.

How should I document things I manage myself?

Section titled “How should I document things I manage myself?”

Use entities in Governance. See Creating and Managing Entities.

When vScope already has an official probe or connector for the source. vScope then handles collection and quality automatically. For one-time data, use tag import.