I'm going to spend the rest of the week rebuilding DIMEdb into something that's a little bit more easy to deploy and maintain.

A recurring issue right now is that user account management is becoming a bit of an issue to deal with. The reality of the situation is that it was only ever implemented as a means of keeping track of tables, but this is a feature that's rarely used.

The 300 or so tables that are currently created are all private, and 80% of them contain < 10 metabolites each. I've already sent an email to those who do use it, and the feedback was that they wouldn't miss it as they primarily use the API.

So alas, it shall go.

https://dimedb.ibers.aber.ac.uk/tables/api/DDBT2/get_metabolites?_=1510163016444

Error regarding token id being parsed through jQuery:
https://github.com/KeironO/DIMEdb/blob/master/dimedb/app/mod_tables/controllers.py#L54-L64

DIMEdb Roadmap November 2017

A summary of our plans and goals.

• Version 1.0 of the database to be finalised.
• JCAMP and TSV export of data from metabolite page
• JCAMP dumps of the entire database, readily available for download.
• Over-representation analysis of KEGG pathways for a given Metabolite Table.
• Possible reintroduction of the MetaboliteClipboard.
• Solidifying of the front end, providing Metabolite views through server-side.
• Conversion from JavaScript to AngularJS.
• Simpler API access, needs consideration.