Game plan, thoughts and discussions about lycophron HOT 1 CLOSED

• Lycophron should have a separate module to handle the Zenodo communication;

Something more of a Zenodo "client", where one can do e.g.:

client = ZenodoClient(token='<your-api-token>')

record = client.records.get('12345')
record['title']
# 'My record title'

deposit = client.deposits.create()
deposit.metadata.update({'title': 'some title', ... })  # updates the metadat
deposit.files.add(path='/path/to/figure.png')  # uploads a file
deposit.publish()  # publishes the deposit

• It should load/export data using Pandas Dataframes;

A lighter alternative to Pandas (since we're not doing any strictly computational work) is also openpyxl... Not sure if there are major speed/ease-of-use differences.

• It should use .env (python-dotenv) to keep sensible information and other eventual parameters of the tool;

Another helpful option for globally storing CLI application config is appdirs (which is also cross-platform).

• It should be to auto-match provided columns with Zenodo fields, asking, if not an absolute match, if the user agrees before doing any API call;

There's also the Zenodo Deposit JSON Schema we can cross-check against using the jsonschema library before submitting things.

from lycophron.