You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe this is just an issue related to the difference between the API that the frontend needs and what an user might want to download via the download button, but I think we need to include the blacklisted SRA keys in the outputs. It should be easy to include these in the CSV, I think. The JSON is trickier because the frontend uses the sample groupings, which is dependent on the blacklisted keys. But you might be able to include these as additional lists in the JSON (i.e., for each blacklisted key, have a list of the values, which all lists being the same order, such that one could recreate the original raw metadata, if one needed to).
In the “Terms” result, can you report the “radius” used.
For reproducibility, it would be good to report the database version (and any other relevant parameters) in the JSON output.
The text was updated successfully, but these errors were encountered:
Maybe this is just an issue related to the difference between the API that the frontend needs and what an user might want to download via the download button, but I think we need to include the blacklisted SRA keys in the outputs. It should be easy to include these in the CSV, I think. The JSON is trickier because the frontend uses the sample groupings, which is dependent on the blacklisted keys. But you might be able to include these as additional lists in the JSON (i.e., for each blacklisted key, have a list of the values, which all lists being the same order, such that one could recreate the original raw metadata, if one needed to).
In the “Terms” result, can you report the “radius” used.
For reproducibility, it would be good to report the database version (and any other relevant parameters) in the JSON output.
The text was updated successfully, but these errors were encountered: