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
Support passing a list of files for ingestion. Files should be relative to sourceFolder.
This is required for the SwissFel usecase. They would like to replace calling datasetIngestor metadata.json fileListing.txt with a REST call to the PSI Ingestor service.
POST /dataset currently takes body {metadata: string}.
I have a question about this: the sourceFolder in the metadata is an obligatory field as far as I know, and it normally marks the source folder of the dataset that should contain all files. Should I verify that all of the files in the given file list is within that folder (normal or symlinked path contains sourceFolder basically) or should I just ignore it? @sbliven
Also, it's not clear for me if you want this feature to be presented in the front-end. If that's the case, then a new file picker has to be implemented in the front-end, and a way for the back-end to let the front-end explore the filesystem (additional endpoint[s]).
Support passing a list of files for ingestion. Files should be relative to
sourceFolder
.This is required for the SwissFel usecase. They would like to replace calling
datasetIngestor metadata.json fileListing.txt
with a REST call to the PSI Ingestor service.POST /dataset
currently takes body{metadata: string}
.I suggest this change to something like
(or whatever this path stabilizes to)
The text was updated successfully, but these errors were encountered: