Importing Plain Text (pdf, txt, etc…)

Last modified on January 31st, 2017.


This section contains outlined instructions for importing Plain Text (.pdf, .txt, etc...) into Innoslate.

  1. Within 'Import Analyzer', ensure the 'Plain Text (.pdf, .txt, etc...)' tab is selected, if not, click on the tab to switch to it.

    Select the Plain Text Tab

  2. Type in a name for your new Artifact entity which will be created and used to store a backup of the pasted in text.

    Set Artifact Name

  3. Select from the dropdown which schema-based class of entities should be created from importing the text. Search or scroll within the dropdown to find your desired class if need be.

    Select Class from Dropdown

    Note: By default, the schema-based class Requirement is selected, however, the overall process is the same regardless of the selected class. This example will continue to use the Requirement class moving forward.

  4. Select which outline format which most closely matches your source document by clicking on its picture. For more information about the available outline formats see Supported List Formats.

    Select Outline Format

  5. Click on the 'Next >' button to continue to the next step in the process.

    Select Next

  6. Open your DOCX source document in Microsoft Word, highlight the text you would like to import and copy (Ctrl+c) it.

  7. Paste (Ctrl+p) your text into the rich text editor and modify the text as needed.

    Paste Text In

  8. Click on the 'Next >' button to preview what will be imported.

    Click the Next Button

  9. Verify the preview of the import is what you were expecting. To finish the import process and save the entities to your current project's database, click on the 'Save' button. To go back, modify your text and try importing again, click on the '< Prev' button to return to the previous step in the process.

    Click the Save Button

 
Please Note:

Importing Plain Text (pdf, txt, etc…)

Last modified on January 31st, 2017. 


This section contains outlined instructions for importing Plain Text (.pdf, .txt, etc…) into Innoslate.

  1. Within ‘Import Analyzer’, ensure the ‘Plain Text (.pdf, .txt, etc…)’ tab is selected, if not, click on the tab to switch to it.

    Select the Plain Text Tab

  2. Type in a name for your new Artifact entity which will be created and used to store a backup of the pasted in text.

    Set Artifact Name

  3. Select from the dropdown which schema-based class of entities should be created from importing the text. Search or scroll within the dropdown to find your desired class if need be.

    Select Class from Dropdown

    Note: By default, the schema-based class Requirement is selected, however, the overall process is the same regardless of the selected class. This example will continue to use the Requirement class moving forward.

  4. Select which outline format which most closely matches your source document by clicking on its picture. For more information about the available outline formats see Supported List Formats.

    Select Outline Format

  5. Click on the ‘Next >’ button to continue to the next step in the process.

    Select Next

  6. Open your DOCX source document in Microsoft Word, highlight the text you would like to import and copy (Ctrl+c) it.

  7. Paste (Ctrl+p) your text into the rich text editor and modify the text as needed.

    Paste Text In

  8. Click on the ‘Next >’ button to preview what will be imported.

    Click the Next Button

  9. Verify the preview of the import is what you were expecting. To finish the import process and save the entities to your current project’s database, click on the ‘Save’ button. To go back, modify your text and try importing again, click on the ‘< Prev’ button to return to the previous step in the process.

    Click the Save Button

 

Please Note:
  • Numbered sections of the imported document are each parsed for a name, number and description.
  • If only Statement and/or Requirement entities or any subclass of Statement entities are imported, you will be navigated to Requirements View upon successful import.
  • If any other class of entites are present in the import, you will be navigated to Database View upon successful import.
  • Tab characters are parsed and treated as space characters.