[X] I agree to follow this project's Contributing Guidelines.
Description
I have been getting a lot of requests lately to allow people to download spectra and metadata in the Open Specy app. This has been a challenge because I have to point them to the R code for installing the library and have to assume that they know how to do that. I think it would be more streamlined if we supported a csv format is a fully flattened version of the Open Specy objects. I am thinking that this format could have each row as a spectrum where columns are the wavenumbers (formatted as just numbers for the column header) we use that to identify where the spectra is in the csv. Then the other columns are assumed to be metadata. One row per spectrum. This could be created by write_OpenSpecy() and read by either read_OpenSpecy or read_csv.
Problem
downloads in the app not currently sufficient.
Proposed Solution
New download format with flat csv of the full Open Specy object.
Alternatives Considered
perhaps giving people json or yaml but these aren't intuitive to most of the app users.
wincowgerDEV
commented
7 months ago
Guidelines
Description
I have been getting a lot of requests lately to allow people to download spectra and metadata in the Open Specy app. This has been a challenge because I have to point them to the R code for installing the library and have to assume that they know how to do that. I think it would be more streamlined if we supported a csv format is a fully flattened version of the Open Specy objects. I am thinking that this format could have each row as a spectrum where columns are the wavenumbers (formatted as just numbers for the column header) we use that to identify where the spectra is in the csv. Then the other columns are assumed to be metadata. One row per spectrum. This could be created by
write_OpenSpecy()and read by eitherread_OpenSpecyorread_csv.Problem
downloads in the app not currently sufficient.
Proposed Solution
New download format with flat csv of the full Open Specy object.
Alternatives Considered
perhaps giving people json or yaml but these aren't intuitive to most of the app users.