# Import Scan

{% hint style="warning" %}
Please be aware that some information in this article may be inaccurate or out of date as we work to update it to be in line with our tools' latest functionality. Thank you for your patience as we update our documentation portal.
{% endhint %}

## Import Scan Tool <a href="#h_01he6qan7arbshq6zfkf887qw3" id="h_01he6qan7arbshq6zfkf887qw3"></a>

\[RE]DESIGN's Import Scans app brings relevant editorial information about your scans into ShotGrid, which can then be used to request pulls compiling the footage to be pulled in the edit, export out an EDL (or tab-delimited text file) and drag this into the app to create Versions in scans.

{% hint style="info" %}
The information that follows assumes you are using an Avid editing system. Much of it will be the same for other systems, but contact \[RE]DESIGN if you have any questions.
{% endhint %}

## Preparing and Exporting Editing Data <a href="#preparing-and-exporting-editing-data" id="preparing-and-exporting-editing-data"></a>

The Import Scans app provides two options for bringing in data from an editing system: either via EDL with locators, or via a tab-delimited

**Note**: *Which option you use will likely be due to personal preference. The tab-delimited text file route allows for importing more editorial information into ShotGrid, but if you’re going to be using locators anyway then generating EDLs will be a much quicker approach.*

### Option 1 — Export EDL with Locators <a href="#option-1-export-edl-with-locators" id="option-1-export-edl-with-locators"></a>

With this approach, you create a Sequence with everything you want to scan for a particular pull request, using locators to indicate which EDL, along with a set of thumbnails, to be used with the Import Scans app.

First, create (or copy) a new Sequence. The Import Scans app will use the Sequence name to generate a Playlist name (for subsequent give the Sequence the same name you intend to use for the request.

In the Sequence itself, include just the footage you intend to scan, so that each clip corresponds to a single pull and that the start and end footage needing to be pulled (inclusive of any handles).

{% hint style="info" %}
By default, the Import Scans app assumes 0-frame handles. Handle frame lengths can be specified in ShotGrid after the import.
{% endhint %}

Ensure that each clip contains a single locator (the locator color does not matter), which has the desired name of the scan (this will be us you’re ready, export the Sequence as an EDL to a folder of your choice.

<figure><img src="/files/dH6e28Mqjs5qq3sh2tA3" alt=""><figcaption></figcaption></figure>

Next, export the Sequence locators as JPEGs to the same folder, and in the settings, ensure that “Sequential Files” and “Markers Only”

<figure><img src="/files/4DA1kuXJZ2hi7TJeqCkQ" alt=""><figcaption></figcaption></figure>

### Option 2 — Export Tab-delimited Text File <a href="#option-2-export-tab-delimited-text-file" id="option-2-export-tab-delimited-text-file"></a>

With this approach, you create a bin with individual clips for everything you want to scan for a particular pull request, including columns fo tab-delimited file, along with a set of thumbnails, to be used with the Import Scans app.

First, create a new bin. The Import Scans app will use the bin’s name to generate a Playlist name (for subsequent use with the Request S name as you intend to use for the request. Make sure the bin displays columns for all the information you wish to export.

The following columns are required by this process and must be included in the bin:

* “Name” (or “Version Name”)
* “Clip” (or “Source Clip”)
* “Tape”
* “Start” (as a timecode)
* “End” (as a timecode)

Here, “Name” represents what the scan should be called (which will be shown as the “Version Name” in ShotGrid), and “Clip” should be th The following columns are not required but will be used if provided:

* “Head” (or “Head Duration”) “Tail” (or “Tail Duration”) “First Frame”
* “ASC\_SAT”
* “ASC\_SOP”
* “Slate”
* “Format”
* “Comments” (or “VFX Comments”)

{% hint style="info" %}
The app can be configured to use default values for many of the optional columns.
{% endhint %}

Any other columns will be ignored. To avoid potential conflicts it’s best to not include any unnecessary columns.

{% hint style="success" %}
The Import Scans app can be configured to either assume handles are included within the start and end timecodes, or that they will be added based on the head and tail values provided.
{% endhint %}

Add all the clips (or subclips) you want to include in the bin, and verify that the information listed for each is correct. Then when you’re rea folder of your choice.

Next, you’ll want to save the thumbnails for each of the clips in the bin, making sure that each is named the same as the corresponding clip in the tab file.

## Import to ShotGrid <a href="#import-to-shotgun" id="import-to-shotgun"></a>

Once you have created a folder with the exported data, you’re ready to use the Import Scans app to create Versions in ShotGrid to track a To launch the app, either:

* Open the ShotGrid Desktop app, browse to your project, and click the Import Scans icon, or
* In your browser, from any ShotGrid page in your project, choose Project Actions > Import Scans.

<figure><img src="/files/cMgNANBB3JmIriBEXE8P" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You must have the ShotGrid Desktop app installed. For more information about the ShotGrid Desktop app, Getting started with ShotGrid Desktop.
{% endhint %}

The Import Scans window will be shown.

<figure><img src="/files/pwFTHsirLvteOAFlVoMH" alt=""><figcaption></figcaption></figure>

To import the data, drag the folder with the exported data onto the app.

{% hint style="info" %}
Make sure you drag the folder itself, and not just the EDL or tab-delimited text file, or else the import will complete without including the thumbnails.
{% endhint %}

<figure><img src="/files/5zyqkHwVCgpTtcOEI1Jq" alt=""><figcaption></figcaption></figure>

Once complete, you can click “Jump to ShotGrid” to be taken to the newly created Playlist with the clips needing to be pulled. From here y the request, via the “Request Scan” app.

<figure><img src="/files/NEQAr4UKDDwARPsgqbwv" alt=""><figcaption></figcaption></figure>

### Controlling Import Scans’ Behavior <a href="#controlling-import-scans-behavior" id="controlling-import-scans-behavior"></a>

The Import Scans app has a number of different aspects that can be configured to accommodate different workflows.&#x20;

### Link Fields <a href="#link-fields" id="link-fields"></a>

The app will automatically try to fill in the Link field for each scan based on the Version Name. For example, if the scan is named “042\_CE existing Shot called “042\_CE\_0490”. Depending on your naming conventions, this link may be left blank when you use the app.

{% hint style="info" %}
**Note**: *By default, the app expects shots to be named in the form 001\_AA\_0010 and scans to be 001\_AA\_0010\_el01\_v01.*
{% endhint %}

## Automatic Shot Creation <a href="#automatic-shot-creation" id="automatic-shot-creation"></a>

The app will automatically create a new Shot if it can’t find an existing one to fill in the Link field, unless the scan doesn’t match the expec importing lens grids).

### Appendix: Field Calculations <a href="#appendix-field-calculations" id="appendix-field-calculations"></a>

These are the fields processed by our tools during Import Scan:

First Frame is the default from the configuration or imported with the TXT file

Length is Timecode Out - Timecode In

Last Frame is First Frame + Length - 1

Head Duration is provided in the TXT file, but will default to a value in the configuration if not filled in

Tail Duration is provided in the TXT file, but will default to a value in the configuration if not filled in

Cut In is First Frame + Head Duration

Cut Out is First Frame - Tail Duration

Cut Length is Cut Out - Cut In

Work In is Cut In - Work Head Duration

Work Out is Cut Out - Work Tail Duration

Work Length is Work Out - Work In + 1

&#x20;


---

# 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://artist-anywhere.gitbook.io/artist-anywhere/editorial-workflows/import-scan.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.