Skip to content

Enable native Excel output, additional input parameters, and choose input file, build executable version
Compare
Choose a tag to compare
@DavidUnderdown DavidUnderdown released this 24 Feb 13:33
· 7 commits to master since this release
v2.0
d73d0b3

This includes all Issues under the v2.0 Milestone.

The location of the input file is no longer fixed, on running the script (or executable) you will be asked for the location of input CSV. Hitting enter without giving one with default to the looking for discovery_api_SearchRecords_input_params.csv in the current working directory.

Input parameters now also include specification of output file location, text encoding, and native Excel output if the output file is given a .xls or .xlsx extension, plus the ability to specify which Discovery fields should be included in the output.

A Windows 64 bit executable is included, this can run without Python being installed (or without all required libraries being installed). This was built with PyInstaller 3.3.1. As running the executable has to build a complete virtual Python environment it takes quite a while to start, and is quite a large binary.

In addition to the executable the sample CSV file is provided along with the CSV Schema file (which uses the CSV Schema Language 1.1 develop by The National Archives. This can be used to check the structure of your own CSV input file using the CSV Validator.

Hashes for discovery_api_SearchRecords.exe are:

  • SHA256 679827e158b1b9cc5f4f922d4eb115ff3f4b1bdc56a4c3b9ecfed81e0471f913
  • MD5 caa0403d5f1d647e8a54dac736a12577
Assets 5
Loading