Single text input field for project-level identifiers about fetchngs HOT 4 CLOSED

Maybe it would rather be a Tower feature request to be able to supply file contents as a text field?

Yes, that's the plan eventually. To extend the Datasets feature to create samplesheets directly in the UI.

from fetchngs.

I really like the idea of this but I wonder if it will cause more issues than it's worth. The input parameter is currently specified as being a file-path in the schema along with other corresponding settings like mimetype, pattern etc which wouldn't apply if we allow a comma-separated string of ids to be provided. The other option is to have another parameter specifically for these but that doesn't sit right either because --input is quite generic and should incorporate this.

from fetchngs.

Thanks- I'm mostly thinking about my Tower users in-house, and the extra steps needed to create and upload a file with the right extension etc just to supply that single identifier. Any suggestions as to a better workaround?

Maybe it would rather be a Tower feature request to be able to supply file contents as a text field?

from fetchngs.

Closing this as I think we will always need some sort of file input to the pipeline given we also want to use nf-validation to validate samples ids.

from fetchngs.