Skip to end of banner
Go to start of banner

Data Import UI and CLI experiences

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Okay

MARC record test loads through the data import ui and cli as of early June 2019. At this point, the cli is available in release 2.1; the ability to use the data import UI to do test loads is available via https://folio-testing.aws.indexdata.com/

Data Import UI

Instructions and explanations for using the data import UI to test loading of MARC records can be found in the Data Import Temporary MARC Bib Load Button powerpoint presentation created by Ann-Marie Breaux, the data import product owner. If you wish to test loading MARC bib records through the UI, follow these steps:

Click on the data import icon in the top menu bar

  • Follow the instructions in the righthand pane to drag and drop a file of MARC records or select them the file using the 'or choose files' button. The file MUST have a .mrc or .marc extension
  • Click the caret (^) next to the word Files in the upper lefthand corner and click the resulting label "Load MARC bibliographic records".

At this point, you should review the Data Import Temporary MARC Bib Load Button powerpoint for explanations and next steps.

Data Import Command Line Interface (cli)

The instructions for using the cli to the data import tool can be found at: https://github.com/folio-org/mod-source-record-manager. The relevant section begins on that page at Data Import Workflow

Some points to be aware of when using the cli:

  • The cli will accept 3 types of input: RAW MARC, MARC XML, and MARC JSON. The interface expects that all record input will consist of properly-escaped json. The Free Online JSON Escape / Unescape Tool can be used to escape input records.
  • Multiple records must be enclosed in quotes (") and the closing quote must be followed by a comma (,) except following the last record, in order to serialize the records as an array of JSON strings

Here are some sample files to show what the formatted records should look like:


  • No labels