# Import Literature References from Database Files

Learn how to intake literature reference information from external databases.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Depending on your Admin’s configuration, object, field, and section labels, lifecycle states, and workflows may differ from the general information on this page. Refer to your organization’s business processes for guidance.</p>
    </div>
  </div>
</div>



## About Importing Literature References

SafetyDocs can import literature references in bulk from third-party databases.

When you <a href="/en/gr/01239/#search-terms">create a search term</a> in your Vault as part of a literature review, you can select an action to import articles from a database in the following formats:

* Research Information Systems (RIS) files, including European Medicines Agency Medical Literature Monitoring (EMA MLM) RIS files
* ZIP files, when importing from the Japan Pharmaceutical Information Center (JAPIC). Vault uses the D-SDI.txt file within these ZIP files for literature reference information.

These files include reference information for all the articles that show up as search results when you query databases using that specific search term. 

Vault then creates a _Literature Article_ record for each article included in the imported database file and maps all relevant information from the file to these records. Once your _Literature Article_ records are created and all fields are populated, you can proceed with your literature review as usual.

Automating the literature intake process reduces the need for manual data entry, significantly decreasing the potential for errors and speeding up your literature review process. 

 <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: SafetyDocs can also <a href="/en/gr/01239/#test-the-pubmed-database-connection">integrate with PubMed</a> to support automated literature searches and article intake.</p>
    </div>
  </div>
</div>



### Prerequisites

Your Admin must configure the following features in your Vault:

* <a href="/en/gr/01318/">Literature Review Process Management</a>
* <a href="/en/gr/01303/">Importing Literature References from Databases</a>
* <a href="/en/gr/726861/">JAPIC Literature Intake</a>

## Upload a Database File

To <a href="/en/gr/15085/">upload an RIS or JAPIC ZIP file</a> to your Vault, use the **Database Export** document classification.

To link an uploaded file to the related _Search Term_, populate the **Literature Search Term** field with the search term used to find the articles included in the RIS file.

To learn about other subtypes and classifications of literature documents, see <a href="/en/gr/01239/#working-with-literature-documents">Working with Literature Documents</a>.

## Import Literature References

Once you have uploaded the database file to your Vault, complete the following steps to start importing your literature references:

1. Navigate to **Literature > Literature Reviews**.
2. Select the **Literature Review** that contains the _Search Term_ record associated with your file.
3. In the _Search Terms_ section, select the associated **Search Term**.
4. From the **All Actions** menu, select **Import Articles from File**.

**Result**

The following results take place:

* The file is imported and for each reference within it, _Literature Article_ records are created under the selected _Literature Review_.
* For JAPIC ZIP files, Vault can also create a document in your Library for every article document contained in the ZIP file. Vault associates each document with a _Literature Article_ record by matching the document number in its name with the _Document Number_ field on the _Literature Article_ record.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: This action can import files in the following formats only:</p>
<ul>
  <li>RIS files, including EMA MLM RIS files</li>
  <li>ZIP files (if the <em>Literature Database</em> field on the <em>Search Term</em> record is set to <em>JAPIC</em>)
<br /></li>
</ul>

<p>Any other file format will cause the import to fail and both the <em>Search Term</em> record and the uploaded file will enter the <em>Error</em> state. You will receive a notification indicating that the import has failed. If needed, verify the file format and try again.</p>
    </div>
  </div>
</div>



### Duplicate Handling 

Vault identifies duplicate references using the _DOI_ field for RIS files and the _Document Number_ field for JAPIC ZIP files. Once duplicates have been identified, Vault does the following:

* Creates an initial _Literature Article_ record.
* Creates _Literature Article_ records for the duplicate references and sets their _Duplicate Literature Review_ and _Duplicate Literature Article_ fields to point to the initial record.
* For documents associated with these duplicate records, sets the _Literature Article_ field to point to the initial record. 

### Search Expression Number Matching

When you import literature articles using a JAPIC ZIP file, Vault runs a search to identify if the value in each article's _Search Expression Number_ field matches the value of this field in an existing _Literature Search Term_ or _Literature Standard Search Term_ record. Based on this search, Vault does the following:

* If a _Literature Search Term_ record with a matching _Search Expression Number_ exists in your Vault, Vault creates a _Literature Article_ record and links it to the matching _Literature Search Term_ record.
* If a _Literature Standard Search Term_ record with a matching _Search Expression Number_ exists in your Vault, the following processes take place:
    * Vault creates a _Literature Search Term_ record and maps the _Search Expression Number_, _Product_ and _Product Family_ fields from the matched _Literature Standard Search Term_ record.
    * Then, Vault creates a _Literature Article_ record and links it to the new matching _Literature Search Term_ record.
* If no _Literature Search Term_ record or _Literature Standard Search Term_ record with a matching _Search Expression Number_ exists in your Vault, the following processes take place:
    * Vault creates a _Literature Search Term_ record and populates the _Search Expression Number_ field with the current Search Expression Number.
    * Then, Vault creates a _Literature Article_ record and links it to this new _Literature Search Term_ record.

## Field Mapping from Database Files

When Vault imports literature reference information from an RIS file or a D-SDI.txt file within a JAPIC ZIP file, it creates a _Literature Article_ record for each article included within it. All relevant information is mapped from the file to the fields in those _Literature Article_ records. 

### Field Mapping from RIS Files

The following sections provide a breakdown of this mapping when RIS files are imported.

 <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault <a href="/en/gr/01238/#field-mapping-from-ema-mlm-ris-files">maps EMA MLM RIS files differently</a> than standard RIS files.</p>
    </div>
  </div>
</div>



#### Literature Article Section

In this section, Vault maps general information about the article as it appears in the RIS file. The following table outlines how Vault maps this information from the file to fields in your Vault:

<table>
    <thead>
        <tr>
            <th class="uk-width-1-5">RIS Tag</th>
            <th class="uk-width-1-5">Description</th>
            <th class="uk-width-3-5">Populated Field</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>TY</td>
            <td>Type of Reference</td>
            <td><strong>Reference Type</strong>
                <br>See <a href="#reference-type-mapping">Reference Type Mapping</a> for a list of RIS abbreviations for the value of the TY tag and how Vault interprets them to populate this field.</td>
        </tr>
        <tr>
            <td>AB</td>
            <td>Abstract</td>
            <td><strong>Abstract</strong></td>
        </tr>
        <tr>
            <td>AN</td>
            <td>Accession Number</td>
            <td><strong>Accession Number</strong></td>
        </tr>
        <tr>
            <td>CN</td>
            <td>Call Number</td>
            <td><strong>Call Number</strong></td>
        </tr>
        <tr>
            <td>DA</td>
            <td>Date</td>
            <td><strong>Date of Publication</strong>
                <br>If the file does not contain a DA value, Vault maps:
                    <ul>
                        <li>the Y1 value to the Day and Month components of this field</li>
                        <li>the PY value to the Year component of this field</li>
                    </ul>
                If the file does not contain a Y1 value either, Vault sets the Day and Month to "1 January".</td>
        </tr>
        <tr>
            <td>CY</td>
            <td>Place of Publication</td>
            <td><strong>Place of Publication</strong></td>
        </tr>
        <tr>
            <td>CP</td>
            <td>City/Place of Publication</td>
            <td><strong>Place of Publication</strong>
                <br>If the value of CP conflicts with the CY tag, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>DB</td>
            <td>Name of Database</td>
            <td><strong>Database Name</strong>
                <br>If the file does not contain a DB value, Vault populates this field with the value in the <strong>Literature Database</strong> field on the associated <strong>Search Term</strong> record.</td>
        </tr>
        <tr>
            <td>DO</td>
            <td>DOI</td>
            <td><strong>DOI</strong></td>
        </tr>
        <tr>
            <td>DP</td>
            <td>Database Provider</td>
            <td><strong>Database Provider</strong></td>
        </tr>
        <tr>
            <td>EP</td>
            <td>End Page</td>
            <td><strong>End Page</strong></td>
        </tr>
        <tr>
            <td>ET</td>
            <td>Edition</td>
            <td><strong>Edition</strong></td>
        </tr>
        <tr>
            <td>ID</td>
            <td>Reference ID</td>
            <td><strong>Reference ID</strong></td>
        </tr>
        <tr>
            <td>IS</td>
            <td>Issue Number</td>
            <td><strong>Issue Number</strong></td>
        </tr>
        <tr>
            <td>J1</td>
            <td>Periodical Name - User Abbreviation 1</td>
            <td><strong>Abbreviated Title of Journal</strong></td>
        </tr>
        <tr>
            <td>JA</td>
            <td>Periodical Name - Standard Abbreviation 1</td>
            <td><strong>Abbreviated Title of Journal</strong>
                <br>If the value of JA conflicts with the JF, J1, or T2 tags, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>JF</td>
            <td>Journal or Periodical Name - Full Format</td>
            <td><strong>Abbreviated Title of Journal</strong>
                <br>If the value of JF conflicts with the J1 or T2 tags, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>JO</td>
            <td>Journal or Periodical Name - Full Format</td>
            <td><strong>Abbreviated Title of Journal</strong>
                <br>If the value of JO conflicts with the JF, J1, or T2 tags, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>KW</td>
            <td>Keywords</td>
            <td><strong>Keywords</strong>
                <br>In case of multiple keywords, Vault maps them all to this field and separates them with commas.</td>
        </tr>
        <tr>
            <td>L1</td>
            <td>Link to PDF of the article</td>
            <td><strong>URL (PDF)</strong></td>
        </tr>
        <tr>
            <td>L2</td>
            <td>Link to full text of the article</td>
            <td><strong>URL (Full Text)</strong></td>
        </tr>
        <tr>
            <td>LA</td>
            <td>Language</td>
            <td><strong>Language</strong></td>
        </tr>
        <tr>
            <td>N1</td>
            <td>Notes</td>
            <td><strong>Article Notes</strong></td>
        </tr>
        <tr>
            <td>N2</td>
            <td>Abstract</td>
            <td><strong>Abstract</strong>
                <br>If the value of N2 conflicts with the AB tag, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>PB</td>
            <td>Publisher</td>
            <td><strong>Publisher</strong></td>
        </tr>
        <tr>
            <td>SE</td>
            <td>Section</td>
            <td><strong>Section</strong></td>
        </tr>
        <tr>
            <td>SN</td>
            <td>ISBN/ISSN</td>
            <td><strong>ISBN/ISSN</strong></td>
        </tr>
        <tr>
            <td>SP</td>
            <td>Start Page</td>
            <td><strong>Start Page</strong></td>
        </tr>
        <tr>
            <td>ST</td>
            <td>Short Title</td>
            <td><strong>Title of Article</strong>
            <br>If the value of ST conflicts with the T1 or TI tags, Vault maps it to the <strong>Literature Additional Information</strong> section.</td>
        </tr>
        <tr>
            <td>T2</td>
            <td>Secondary Title</td>
            <td><strong>Abbreviated Title of Journal</strong>
            <br><ul>
                        <li>If the value of T2 conflicts with the JF or J1 tags, Vault maps it to the <strong>Literature Additional Information</strong> section.</li>
                        <li>This tag contains the Secondary Title value for all reference types except Whole Book (BOOK) and Unpublished Work (UNPB). Secondary Titles for these reference types are mapped to the BT tag in the <strong>Literature Additional Information</strong> section.</li>
                </ul></td>
        </tr>
        <tr>
            <td>TI</td>
            <td>Title</td>
            <td><strong>Title of Article</strong>
            <br>If the file does not contain a TI value, Vault maps the T1 value to this field.</td>
        </tr>
        <tr>
            <td>TT</td>
            <td>Translated Title</td>
            <td><strong>Title (English)</strong></td>
        </tr>
        <tr>
            <td>UR</td>
            <td>URL</td>
            <td><strong>Link</strong>
            <br>If the file does not contain a UR value, Vault maps the value of the LK tag to this field.</td>
        </tr>
        <tr>
            <td>VL</td>
            <td>Volume Number</td>
            <td><strong>Volume</strong></td>
        </tr>
        <tr>
            <td>Y2</td>
            <td>Access Date</td>
            <td><strong>Access Date</strong></td>
        </tr>
    </tbody>
</table>

#### Reference Type Mapping

The following table outlines how Vault interprets Reference Type abbreviations from RIS files to set the value in the _Reference Type_ field:

| Abbreviation | Vault Mapping |
| --- | --- |
| ABST | Abstract |
| ADVS | Audiovisual Material |
| AGGR | Aggregated Database |
| ANCIENT | Ancient Text |
| ART | Art Work |
| BILL | Bill |
| BLOG | Blog |
| BOOK | Whole book |
| CASE | Case |
| CHAP | Book chapter |
| CHART | Chart |
| CLSWK | Classical Work |
| COMP | Computer Program |
| CONF | Conference Proceeding |
| CPAPER | Conference Paper |
| CTLG | Catalog |
| DATA | Data File |
| DBASE | Online Database |
| DICT | Dictionary |
| EBOOK | Electronic Book |
| ECHAP | Electronic Book Section |
| EDBOOK | Edited Book |
| EJOUR | Electronic Article |
| WEB | Web Page |
| ENCYC | Encyclopedia |
| EQUA | Equation |
| FIGURE | Figure |
| GEN | Generic |
| GOVDOC | Government Document |
| GRANT | Grant |
| HEAR | Hearing |
| ICOMM | Internet Communication |
| INPR | In Press |
| JFULL | Journal (full) |
| JOUR | Journal |
| LEGAL | Legal Rule or Regulation |
| MANSCPT | Manuscript |
| MAP | Map |
| MGZN | Magazine Article |
| MPCT | Motion Picture |
| MULTI | Online Multimedia |
| MUSIC | Music Score |
| NEWS | Newspaper |
| PAMP | Pamphlet |
| PAT | Patent |
| PCOMM | Personal Communication |
| RPRT | Report |
| SER | Serial Publication |
| SLIDE | Slide |
| SOUND | Sound Recording |
| STAND | Standard |
| STAT | Statute |
| THES | Thesis/Dissertation |
| UNBILL | Unenacted Bill |
| UNPB | Unpublished Work |
| VIDEO | Video Recording |

#### Literature Author Section

In this section, Vault maps information about the article's authors as it appears in the RIS file. The following table outlines how Vault maps this information from the file to fields in your Vault:

<table>
    <thead>
        <tr>
            <th class="uk-width-1-5">RIS Tag</th>
            <th class="uk-width-1-5">Description</th>
            <th class="uk-width-3-5">Field Populated</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>A1</td>
            <td>Primary Authors</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Primary</strong>.
            </td>
        </tr>
        <tr>
            <td>A2</td>
            <td>Secondary Authors</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Non-Primary</strong>.
            </td>
        </tr>
        <tr>
            <td>A3</td>
            <td>Tertiary Authors</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Non-Primary</strong>.
            </td>
        </tr>
        <tr>
            <td>A4</td>
            <td>Subsidiary Authors</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Non-Primary</strong>.
            </td>
        </tr>
        <tr>
            <td>AU</td>
            <td>Author</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Primary</strong> only if:
                    <ul>
                        <li>There is no A1 tag in the file</li>
                        <li>This is the first instance of the AU tag</li>
                    </ul>
            </td>
        </tr>
        <tr>
            <td>ED</td>
            <td>Editor</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Editor</strong>.
            </td>
        </tr>
        <tr>
            <td>TA</td>
            <td>Translated Author</td>
            <td>The complete author reference is populated in the <strong>Value</strong> field.
                <br>The author's last name is populated in the <strong>Last Name</strong> field.
                <br>The author's first name is populated in the <strong>First Name</strong> field.
                <br>The <strong>Author Type</strong> field is set to <strong>Translator</strong>.
            </td>
        </tr>
    </tbody>
</table>

#### Literature Additional Information Section

In this section, Vault maps any additional information about the article as it appears in the RIS file that was not covered in the _Literature Article_ and _Literature Author_ sections. Vault creates a record for every section of additional information with its corresponding tag and value from the RIS file. The _Tag_ field is populated with the RIS tag, and the _Value_ field is populated with the corresponding information.

#### Vancouver Citation

When an article's type of reference is _Journal_, Vault generates a Vancouver Citation for it by mapping relevant field values to that _Literature Article_ record's _Vancouver Citation_ section. Vault generates this citation in the following format:

{List of all literature authors, separated by commas}. {Title of Article}. {Abbreviated Title of Journal}. {Date of Publication} [cited {Access Date}]; {Volume}({Issue Number}): {Start Page}-{End Page}. Available from {Database Name} DOI:{DOI}

### Field Mapping from EMA MLM RIS Files

When Vault imports literature reference information from an EMA MLM RIS file, a file with a _Literature Database_ field value of `EMA MLM`, it follows the [same mapping to the _Literature Article_ record as other RIS files][2], with the following additions. Like with other RIS files, for blank tags in the import file, Vault leaves the associated _Literature Article_ field blank.

<table>
    <thead>
        <tr>
            <th>RIS Tag</th>
            <th>Description</th>
            <th>Populated Field</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>SG</td>
            <td>Substance Group</td>
            <td>
                <p><strong>Product Family</strong></p>
                <p>Vault populates this field with the <em>Product Family</em> record with an <em>EMA Substance Group</em> field value that matches the file's SG tag value.</p>
                <p>If multiple matching <em>Product Family</em> records exist, Vault creates a <a href="/en/gr/01239/#literature-article-product"><em>Literature Article Product</em></a> record for each matching <em>Product Family</em> record to support multi-product articles.</p>
                <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault imports an EMA MLM RIS file only if its SG tag value matches an existing <em>Product Family</em> record’s <em>EMA Substance Group</em> field value. Other references in the file will be skipped.</p>
    </div>
  </div>
</div>


            </td>
        </tr>
        <tr>
            <td>LA</td>
            <td>Lead Author</td>
            <td>
                <p><strong>Primary Author</strong></p>
                <p>Vault populates this field with the file's LA tag value. This field value should match one of the literature authors defined in the <a href="/en/gr/01238/#literature-author-section"><em>Literature Author </em> section</a>.</p>
            </td>
        </tr>
        <tr>
            <td>IE</td>
            <td>Inclusion/Exclusion</td>
            <td>
                <p><strong>EMA Inclusion/Exclusion Criteria</strong></p>
                <p>Vault populates this field with the file's IE tag value.</p>
            </td>
        </tr>
        <tr>
            <td>CP</td>
            <td>Confirmed/Potential ICSRs</td>
            <td>
                <p><strong>ICSR Review Outcome</strong></p>
                <p>Vault populates this field value depending on the value of the CP tag in the file:</p>
                <ul>
                    <li>If the tag value is <code>C</code>, Vault sets this field value to <em>Confirmed ICSR(s)</em></li>
                    <li>If the tag value is <code>P</code>, Vault sets this field value to <em>More Information Needed</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td>SR</td>
            <td>Serious</td>
            <td>
                <p><strong>ICSR(s) Serious?</strong></p>
                <p>Vault populates this field value depending on the value of the SR tag in the file:</p>
                <ul>
                    <li>If the tag value is <code>Y</code>, Vault sets this field value to <em>Serious</em></li>
                    <li>If the tag value is <code>N</code>, Vault sets this field value to <em>Non-serious</em></li>
                </ul>
            </td>
        </tr>
    </tbody>
</table>

### Field Mapping from JAPIC ZIP Files

The following sections provide a breakdown of this mapping when ZIP files are imported from JAPIC:

#### Literature Article Section

In this section, Vault maps general information about the article as it appears in the JAPIC ZIP file. The following table outlines how Vault maps this information from the file to fields in your Vault:

| Column in JAPIC ZIP File | Populated Field |
| --- | --- |
| 検索式番号 (Search Expression Number) | **Search Expression Number**  <br>For more information about this field, see the [Search Expression Number Matching section][3]. |
| 文書番号 (Document Number) | **Document Number** |
| 標題 (Title) | **Title of Article** |
| 所属機関 (Institution) | **Institution** |
| 雑誌名 (Journal Title) | **Abbreviated Title of Journal** |
| ISSN | **ISSN/ISBN** |
| 学会名 (Conference Name) | **Conference** |
| 巻 (Volume) | **Volume** |
| 号 (Issue) | **Issue Number** |
| 頁 (Page) | **Start Page** and **End Page** |
| 発行年月日 (Date of Publication) | **Date of Publication** |
| 全キーワード詳細 (All Keyword Details) | **Keywords**  <br>In case of multiple keywords, Vault maps them all to this field and separates them with commas. |
| 文献URL (Literature URL) | **URL** |
| 発送日 (Sent Date) | **Access Date** |

#### Literature Author Section

In this section, Vault maps information about the article's authors as it appears in the JAPIC ZIP file. Vault maps values in the _Author Name_ column of the JAPIC ZIP file to the _Raw_ field on the article's _Literature Author_ section.

#### Vancouver Citation

Vault uses the same logic and process to generate a Vancouver Citation for JAPIC ZIP files as for RIS files. The only exception is when the _Conference Name_ column is populated in the imported JAPIC ZIP file. In this case, Vault generates the citation in the following format:

{list of literature_author__v.raw__v (comma separated)}. {title_of_article__v}. {conference_name__v}. {date_of_publication__v}

## Translate Imported Literature Abstracts

If your database file includes references from non-English literature articles, Vault can automatically send any available abstracts for translation. Auto-translation allows you to quickly determine if the associated articles contain any ICSRs or new safety information, and eliminates the need for external translation tools. 

### Prerequisites

To use this feature, your Admin must set up Literature Abstract Translations in your Vault. See the following pages for the steps to complete:

* Enable Literature Abstract Translation: <a href="/en/gr/01450/#enable-the-amazon-translate-connection">Enable the Amazon Translate Connection</a> 
* Enable Literature Abstract Translation: <a href="/en/gr/01450/#configure-layouts">Configure Layouts</a> 
* <a href="/en/gr/01445/">Configure Literature Abstract Translation Settings</a> 

Once the required configuration is complete and you import references into your Vault, any abstracts that are in a non-English language are automatically sent to Amazon Translate for translation into English. Vault maps translated abstracts to the _Abstract_ field of their respective _Literature Article_ record. 

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When the translated abstracts are sent back to SafetyDocs, they are simply imported as received. Vault does not perform quality checks on the content.</p>
    </div>
  </div>
</div>



To learn more, see <a href="/en/gr/01443/#considerations-for-abstract-translations">Considerations for Abstract Translations</a>.

## Considerations for Importing Literature References

When importing literature reference information from a database file, keep the following things in mind:

* If any articles within the file have duplicate DOIs or ISSN/ISBNs, Vault imports only one (1) to prevent duplicate records in your Vault. Vault sends a notification indicating that some articles have been skipped from import due to matching unique identifiers.
* If the value of any tag exceeds the character limit of the field to which it is being mapped, Vault truncates the value to that field's maximum character length. Vault also adds the value to the _Literature Additional Information_ section as a new record. For information on truncated fields, see the _Notes_ field of the _Literature Article_ record.
* If any or all articles fail to be imported, Vault sends a notification.


[1]: #field-mapping-from-ema-mlm-ris-files
[2]: #field-mapping-from-ris-files
[3]: #search-expression-number-matching