Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resources export SQL #5030

Closed
EnzyanBiocatalysis opened this issue Apr 4, 2024 · 1 comment
Closed

Resources export SQL #5030

EnzyanBiocatalysis opened this issue Apr 4, 2024 · 1 comment

Comments

@EnzyanBiocatalysis
Copy link

Describe your feature request precisely

Dear Elab team,

We want to export our "resources" (e,g, chemicals, methods, plasmid) into our MySQL database. However, currently, the reformatting is very tedious. The most common way we store information in the "resources" is to generate a table in the Main Text Box where the information gets filled in. When the "resources" data gets exported this information is stored into the "body" column of the CSV file with line breaks. This is challenging to handle with larger data sets, any improvement on that would be great. Also, suggestions how a large information set in the "resources" folder can be handled more efficiently would also be highly appreciated.

Cheers

Pro Support

No response

@NicolasCARPi
Copy link
Contributor

Hello,

Do you mean you have something like this:

A single resource entry called "Plasmids", which contains a table with the plasmids listed in the main text?

What you should have is something similar to this:

2024-04-04-151652_441x724_scrot (see demo)

where each entry is a plasmid. And exporting that to CSV will be much easier to deal with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants