Extending log information when exporting to a file

[jdhenaos]

Taking inspiration from tidylog to have the option to save the log into a .txt file. However, I think that this provides the opportunity to allocate more information than the displayed in the console. Probably it is the opportunity to allocate information in a way to allows us to create a standard in the field.

[stemangiola]

Hola Juan,

I love the idea of creating a standard for genomic data tracking. Do you have something in mind for the "more information" already?

The current idea/implementation is to store the log within the SE object so it can be shipped with the object itself (metadata slot). We can save any information there, independently of the one we print. Providing the option to save to a text file could be beneficial.

What do you think a text file would provide that a SummarizedExperiment slot cannot?

[jdhenaos]

Hi!

So far, I have thought that having the option of allocating log information in a file provides the user with the possibility to work with options that make them feel more comfortable.

As an alternative, the log file could capture detailed information that could overcrowd the SE object, for example, showing the specific sample/variable names removed or modified, which could be in the order of hundreds or thousands, depending on the operation used.

Additionally, I got the idea of adding numeric information, such as basic stats like mean +- SD, to track how the data is affected in every decision.

I will focus my attention on increasing our repertoire of functions to have a solid shareable package that covers the basic tidy operations (at least). I will create a branch from your recent PR, which fixed some basis of the package.

[stemangiola]

This makes me think that it's probably the right time to ask to the community what do people care more about being recorded. There is a balance between too few and too many details, that as you said could require different implementation.