**Source URL:** https://safety.veevavault.help/en/lr/01238/index.md

# Import Literature References from Database Files

SafetyDocs can import literature references in bulk from third-party databases, significantly decreasing the potential for errors and speeding up your literature review process. Literature database files include reference information for all of the articles that show up as search results when you query a database using a specific search term. 

To import literature references from a database file:

1. Create a <a href="/en/lr/01239/#create-a-literature-review">_Literature Review_</a> and any <a href="/en/lr/01239/#search-terms">_Literature Search Terms_</a> required to capture details of your literature search.
2. [Upload][4] the RIS, JAPIC ZIP, or IMIC database file to your _Library_.
3. [Import references][5] from the file.

For each article reference in the imported file, Vault creates a <a href="/en/lr/01239/#create-literature-articles">_Literature Article_</a> and populates its fields using article data from the file. If your database file includes references from non-English literature articles, Vault can <a href="/en/lr/01443/">send any available abstracts for translation</a>.

Once complete, you can proceed with your <a href="/en/lr/01239/#literature-review-process">literature review</a>.

## Prerequisites

To use this feature to import RIS or IMIC files, your Admin must enable:

* <a href="/en/lr/01318/">Literature Review Process Management</a>
* <a href="/en/lr/01303/">Importing Literature References from Databases</a>

To use this feature to import JAPIC files, your Admin must additionally enable <a href="/en/lr/726861/">JAPIC Literature Intake</a>.

## Upload a Database File {#upload}

To upload an RIS, IMIC, or JAPIC ZIP database file:

1. Navigate to the <a href="/en/lr/01239/#search-terms">_Literature Search Term_</a> that corresponds to the term used to search the database and expand the **Documents** section.
2. Select **Add** and <a href="/en/lr/15085/#upload">upload the file</a> using the **Database Export** <a href="/en/lr/01239/#working-with-literature-documents">document classification</a>.

## Import Literature References {#import-literature-references}

To import literature references from a database file:

1. From the [uploaded document][4], select the **Literature Search Term** value.
2. From the **All Actions** menu, select **Import Articles from File**<sup><a href ="#import-action">1</a></sup>.

Upon starting the import process, Vault moves the database file document and the _Literature Search Term_ to the _Importing_ state. Then, for each reference within the file, Vault creates a _Literature Article_ on the _Literature Review_ related to the document and [maps data from the file to the fields on the _Literature Article_][6]. Vault handles [duplicate references][7] and [matching search expression numbers][3] as required. 

For JAPIC ZIP files, Vault creates a document in your _Library_ for every article document contained in the ZIP file. Vault associates each document with a _Literature Article_ by matching the document number in its name with the _Document Number_ field on the _Literature Article_.

<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>: For JAPIC ZIP files, Vault uses the D-SDI.txt file within the ZIP file for literature reference information.</p>
    </div>
  </div>
</div>



Once the import process is complete, Vault moves the document and the _Literature Search Term_ to the _Imported_ state.

### Considerations When 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 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 source field exceeds the character limit of the Vault object field to which it is being mapped, Vault truncates the value to that object field's maximum character length. Vault also adds the value to the _Additional Info_ section as a new record. For information on truncated fields, see the _Article Review Notes_ field of the _Literature Article_.
* If any or all articles fail to be imported, Vault sends a notification.
* <a id="import-action"></a>The _Import Articles from File_ action can import files in the following formats only. Any other file format will cause the import to fail and Vault will move both the _Literature Search Term_ and the uploaded document to the _Error_ state. If needed, verify the file format and try again:
    * RIS files, including EMA MLM RIS files
    * JAPIC-formatted ZIP files
    * IMIC-formatted TXT files

### Duplicate Handling {#duplicate-handling}

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

* Creates an initial _Literature Article_
* For each duplicate reference, creates a _Duplicate_-state _Literature Article_ and populates its _Duplicate Literature Review_ and _Duplicate Literature Article_ fields with the initial _Literature Review_ and _Literature Article_
* For documents associated with these duplicate records, populates the _Literature Article_ field with the initial _Literature Article_ 

### Search Expression Number Matching {#search-expression-number-matching}

When you import literature articles using a JAPIC ZIP or IMIC file, Vault runs a search to determine whether each article's _Search Expression Number_ or _Search Query Number_<sup><a href ="#search-query-number">1</a></sup> value matches the value of this field in an existing <a href="/en/lr/01239/#search-terms">_Literature Search Term_</a> or <a href="/en/lr/726859/">_Literature Standard Search Term_</a>. Based on this search, Vault does the following:

* If a _Literature Search Term_ with a matching _Search Expression Number_ or _Search Query Number_ exists in your Vault, Vault creates:
    * A _Literature Article_ and links it to the matching _Literature Search Term_
    * A <a href="/en/lr/01239/#lit-art-prod">_Literature Article Product_</a> on the _Literature Article_ for each _Product_ or _Product Family_ on the existing _Literature Search Term_
* If a _Literature Standard Search Term_ with a matching _Search Expression Number_ or _Search Query Number_ exists in your Vault, Vault creates:
    * A _Literature Search Term_ and maps the _Search Expression Number_ or _Search Query Number_, _Product_, and _Product Family_ values from the matched _Literature Standard Search Term_
    * A _Literature Article_ and links it to the new matching _Literature Search Term_
* If no _Literature Search Term_ or _Literature Standard Search Term_ with a matching _Search Expression Number_ or _Search Query Number_ exists in your Vault, Vault creates:
    * A _Literature Search Term_ and populates the _Search Expression Number_ or _Search Query Number_ with the current _Search Expression Number_ or _Search Query Number_
    * A _Literature Article_ and links it to the new _Literature Search Term_

<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>: <a id="search-query-number"></a>1. When conducting search number matching for IMIC files, if a <em>Literature Article</em> contains more than one value in the <em>Search Query Number</em> field, as indicated by a forward slash (/) between two values, Vault treats the entire <em>Search Query Number</em> as a single value.</p>
    </div>
  </div>
</div>



## Field Mapping from Database Files {#field-mapping}

When importing literature reference information from a database file, Vault creates a <a href="/en/lr/01239/#create-literature-articles">_Literature Article_</a> for each article included within it and maps information from the file to the _Literature Article_ based on the database file format:

* [Standard RIS][8]
* [EMA MLM RIS][9]
* [JAPIC ZIP][10]
* [IMIC][11]

<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>: For blank field values in the imported file, Vault leaves the associated <em>Literature Article</em> field blank.</p>
    </div>
  </div>
</div>



### Field Mapping from Standard RIS Files {#field-mapping-ris}

The following sections provide a breakdown of this mapping when standard 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/lr/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 {#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>

#### Additional Info Section {#additional-info-ris}

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 {#vancouver-citation-ris}

If the RIS file has a TY ([Type of Reference][12]) value of JOUR, Vault uses field values from the _Literature Article_ to generate a Vancouver citation using the following format:

{Comma-separated list of _Raw_ values from all _Literature Authors_}.{_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 {#field-mapping-ema-mlm-ris}

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/lr/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/lr/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 {#field-mapping-japic-zip}

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 {#vancouver-citation-japic}

If the JAPIC ZIP file has a value in the 学会名 (Conference Name) column, Vault uses field values from the _Literature Article_ to generate a Vancouver citation using the following format:

{Comma-separated list of _Raw_ values from all _Literature Authors_}.{_Title of Article_}.{_Conference_}.{_Date of Publication_}

Otherwise, Vault generates a Vancouver citation in the following format:

{Comma-separated list of _Raw_ values from all _Literature Authors_}.{_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 IMIC Files {#field-mapping-imic}

When importing data from an IMIC file, Vault maps data to generated _Literature Articles_ as follows:

<table>
    <thead>
        <tr>
            <th><strong>Literature Article Section</strong></th>
            <th><strong>Column in IMIC File</strong></th>
            <th><strong>Populated Field</strong></th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td rowspan="2" style="vertical-align: middle;"><a href="/en/lr/01239/#literature-article-fields"><em>Article Details</em></a></td>
            <td>標題 (Title)</td>
            <td><em>Title of Article</em></td>
        </tr>
        <tr>
            <td>検索回 (Search Cycle)</td>
            <td><em>Access Date</em></td>
        </tr>
        <tr>
            <td rowspan="19" style="vertical-align: middle;"><a href="/en/lr/01239/#reference-information-section"><em>Reference Information</em></a></td>
            <td>参照文献 (References)</td>
            <td><em>References</em></td>
        </tr>
        <tr>
            <td>雑誌名 (Journal Name)</td>
            <td><em>Abbreviated Title of Journal</em></td>
        </tr>
        <tr>
            <td>副題 (Subtitle)</td>
            <td><em>Subtitle</em></td>
        </tr>
        <tr>
            <td>原著 (Original Article)</td>
            <td><em>Original Article</em></td>
        </tr>
        <tr>
            <td>学会名 (Conference Name)</td>
            <td><em>Conference</em></td>
        </tr>
        <tr>
            <td>学会開催年月日 (Conference Date)</td>
            <td><em>Conference Date</em></td>
        </tr>
        <tr>
            <td>雑誌コード (Journal Code)</td>
            <td><em>Accession Number</em></td>
        </tr>
        <tr>
            <td>ISSN</td>
            <td><em>ISBN/ISSN</em></td>
        </tr>
        <tr>
            <td>巻 (Volume)</td>
            <td><em>Volume</em></td>
        </tr>
        <tr>
            <td>号 (Issue)</td>
            <td><em>Issue Number</em></td>
        </tr>
        <tr>
            <td>頁 (Pages)</td>
            <td><em>Start Page</em> and <em>End Page</em></td>
        </tr>
        <tr>
            <td>文書番号 (Document Number)</td>
            <td><em>Document Number</em></td>
        </tr>
        <tr>
            <td>検索式番号 (Search Query Number)</td>
            <td><a href="/en/lr/01238/#search-expression-number-matching"><em>Search Expression Number</em></a></td>
        </tr>
        <tr>
            <td>発送日 (Dispatch Date)</td>
            <td><em>Dispatch Date</em></td>
        </tr>
        <tr>
            <td>発行年月日 (Publication Date)</td>
            <td><em>Publication Date</em></td>
        </tr>
        <tr>
            <td>所属機関 (Article Type)</td>
            <td><em>Article Type</em></td>
        </tr>
        <tr>
            <td>情報区分 (Information Type)</td>
            <td><em>Information Type</em></td>
        </tr>
        <tr>
            <td>プログラム (Program)</td>
            <td><em>Program</em></td>
        </tr>
        <tr>
            <td>DR詳細 (DR Details)</td>
            <td><em>DR Details</em></td>
        </tr>
        <tr>
            <td rowspan="2" style="vertical-align: middle;"><a href="/en/lr/01239/#keywords-section"><em>Keywords</em></a></td>
            <td>AEキーワード (AE Keyword)</td>
            <td><em>Keywords</em><sup>1</sup></td>
        </tr>
        <tr>
            <td>DRキーワード (DR Keyword)</td>
            <td><em>Keywords</em><sup>1</sup></td>
        </tr>
        <tr>
            <td style="vertical-align: middle;"><a href="/en/lr/01239/#literature-author-section"><em>Authors</em></a></td>
            <td>著者名 (Author Name)</td>
            <td>
                Vault generates a <em>Literature Author</em> and populates its fields as follows:
                <ul>
                    <li><strong>Author Type</strong>: <em>Primary</em></li>
                    <li><strong>Raw</strong>: Entire author name</li>
                    <li><strong>First Name</strong>: The author's first name</li>
                    <li><strong>Last Name</strong>: The author's last name</li>
                </ul>
            </td>
        </tr>
        <tr>
            <td style="vertical-align: middle;"><a id ="vancouver-citation-imic"></a><a href="/en/lr/01239/#vancouver-citation-section"><em>Vancouver Citation</em></a></td>
            <td>N/A</td>
            <td>
                <p>If the IMIC file has a value in the 学会名 (Conference Name) column, Vault uses field values from the <em>Literature Article</em> to generate a Vancouver citation in the following format:</p>
                <p>{Comma-separated list of <em>Raw</em> values from all <em>Literature Authors</em>}.{<em>Title of Article</em>}.{<em>Conference</em>}.{<em>Publication Date</em>}</p>
                <p>Otherwise, Vault generates a Vancouver citation in the following format:</p>
                <p>{Comma-separated list of <em>Raw</em> values from all <em>Literature Authors</em>}.{<em>Title of Article</em>}.{<em>Abbreviated Title of Journal</em>}.{<em>Publication Date</em>} [cited {<em>Access Date</em>}]; {<em>Volume</em>}({<em>Issue Number</em>}): {<em>Start Page</em>}-{<em>End Page</em>}. Available from {<em>Database Name</em>} DOI:{<em>DOI</em>}</p>
            </td>
        </tr>
        <tr>
            <td colspan="3">
                1. If an article contains both AEキーワード (AE Keyword) and DRキーワード (DR Keyword) values, Vault displays both values in a comma-separated list in the <em>Keywords</em> field.
            </td>
        </tr>
    </tbody>
</table>

[1]: #field-mapping-from-ema-mlm-ris-files
[2]: #field-mapping-from-ris-files
[3]: #search-expression-number-matching
[4]: #upload
[5]: #import-literature-references
[6]: #field-mapping
[7]: #duplicate-handling
[8]: #field-mapping-ris
[9]: #field-mapping-ema-mlm-ris
[10]: #field-mapping-japic-zip
[11]: #field-mapping-imic
[12]: #reference-type-mapping