# Cosmo Project File Index Action

{% hint style="warning" %}
**Change in Cosmo Project File Index Action V3 - v4.6.x+**\
\
With the release of the ***V3*** file index action it is now possible to ***assign*** the ***indexing either*** to the ***client or server*** depending on the host of the stream.\
\
With the previous V2 node, indexing was ***always executed*** by the Cosmo server\
\
Replacing the old one should consider to check the stream, eg an unlock project trigger should not call a client indexing as this could cause issues if the user is closing the website / helmut4 client connection.
{% endhint %}

With the help of the Project File Index Action, it is possible to index a project file (Premiere / After Effects). It is recommended to only do this when the project is closed. The indexing extracts all information from the project. These include:

* Folder structures and folder names
* Files and metadata
* Sequences

All changes that are detected during indexing compared to the status in Cosmo are changed in Cosmo. It is possible to define that the "indexed\_assets" trigger is triggered for newly found assets and the information on these assets is transferred.

In addition, the "unindexed\_assets" trigger is triggered for assets that have been removed from the project. Within a stream that is triggered by this trigger, it is possible to check whether these removed assets are still available in other projects or not. Every asset that is removed from a project and is no longer available in any other project is recorded in the database as an orphan clip, but is no longer accessible.

Within the node it is possible to define advanced indexing for the project file. If checked, the following information about sequences will also be extracted:

* Source and destination time code of all assets on the timeline
* Track that was used per asset
* Metadata of the assets

This information is not visualised in Cosmo but is available in the database.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/nodes/actions/cosmo/cosmo-project-file-index-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.