Stream: shorthand
Topic: sushi: input folder recurse
Patrick Werner (Feb 01 2021 at 14:09):
i just played with sushi and trying to include preexisting resources into input/resources
If i tested sushi correctly only the first level of this folder is read-in. Could this be switched to a recurse behaviour? This would enable a better overview of the input/ressources folder, as you can just c&p projects with existing subfolders into the input folder.
Chris Moesel (Feb 01 2021 at 14:29):
Hi @Patrick Werner -- We've usually seen folders split up directly under input/ rather than having nested sub-folders under input/resources, but as long as this is supported by the IG Publisher, then this seems like a reasonable ask. The fact that SUSHI doesn't do it now is probably more of an oversight (or not knowing it was a valid configuration) than an intentional decision.
Jose Costa Teixeira (Feb 02 2021 at 13:12):
This is configured in the template. There are "standard" folders next to resources, not under it
Patrick Werner (Feb 02 2021 at 14:32):
Jose Costa Teixeira said:
This is configured in the template. There are "standard" folders next to resources, not under it
i know. But what if these defined folders contain nested subfolders?
Jose Costa Teixeira (Feb 02 2021 at 15:13):
IIRC, subfolders are not included by default.
UNLESS (there's a thing in the publisher) the folder is called <ResourceName> and the files are called <id>.json
Jose Costa Teixeira (Feb 02 2021 at 15:14):
so, you can have
resources\Patient-patient1.json
OR
resources\Patient\patient1.json
Jose Costa Teixeira (Feb 02 2021 at 15:14):
This is just because the publisher looks in alternative paths
Last updated: Apr 12 2022 at 19:14 UTC
