Hi Helen,
Thanks for being in touch and carrying on the bot, glad you enjoyed #FlashHacks, feel free to join us again.
I think the current version of turbot is ‘turbot-gem/0.1.9 (x86_64-linux) ruby/1.9.3’ so I expect that is why the manifest was a little light, I don’t think it will cause a problem other than that but here’s what Seb said about versions when I asked him about updating:
“””
Seb
It depends how they installed it in the first place. This is not a question I was looking forward to being asked! (But it's inevitable...) Going forward, we would want people to use the packaged installers, but historically this has not been the case - and in some cases, people will still want to use the gem. If they used the packaged installer, then we need to release a new package which they would then install. I could do that this week but not now. If they used a gem-based install process, they can do "gem update turbot"
“””
So if you let me know how you installed originally then I can follow up about upgrading, or if you installed via the gem then you can update yourself, by the sound of it.
There’s a bit of a glitch in the simple licence docs regarding required fields - licence_jurisdiction is actually optional. company_jurisdiction is the country where the company is registered, licence_jurisdiction is where a company is licensed to operate - so for the MTB financial missions one might come across a licensed foreign branch where the licence_jurisdiction would be the current jurisdiction whereas company_jurisdiction would be the home country of that company.
You’re right in saying that the simple licence is quite restricted in what it can capture, we’re working on a rich licence which will be able to capture addresses and such, but for now a lot of jurisdictions will only be capturing basic fields like company_name, regulator, jurisdiction, and jurisdiction_classification. This is one of the main reasons why we output primary data as well as transformed data, so that we can easily add rich licences further down the line.
All the best and thanks again for the work you’re putting into the bot,
Peter