I'm new to BabelDocs, and it's a nice bit of software. I've found it quite hard to work out how to get to running properly.
Here are some suggestions on how to make the project even better, and to make it more accessible:
- A full step-by-step worked example, similar to higgsbros (which is no longer there) that you can build, then modify for your own purposes. This helps because the structure of the file hierarchy is already set, and a new deployment is just copying that and changing config files.
- A FAQ with an explanation of the error-messages, and how to fix them.
- A bit more documentation on the GUI tools, and what they are for.
A suggestion for a feature in Flat2XML:
- Really blew me away when I realised what it could do, but I noticed one feature, which might be nice. What about extending it to deal with nested segmented data.
By that I mean data like:
" TAG1START d1 d2 d3 d4 TAG2START e1 e2 e3 TAG2END TAG3START f1 f2 f3 TAG3END TAG1END "
It strikes me that you could get somewhere with that by combining the CSV transform classes you already have with a DOM transform (treating the start and end markers as tags). I'm not that close to the code, so I don't know how difficult that would be to do.
Ed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm new to BabelDocs, and it's a nice bit of software. I've found it quite hard to work out how to get to running properly.
Here are some suggestions on how to make the project even better, and to make it more accessible:
- A full step-by-step worked example, similar to higgsbros (which is no longer there) that you can build, then modify for your own purposes. This helps because the structure of the file hierarchy is already set, and a new deployment is just copying that and changing config files.
- A FAQ with an explanation of the error-messages, and how to fix them.
- A bit more documentation on the GUI tools, and what they are for.
A suggestion for a feature in Flat2XML:
- Really blew me away when I realised what it could do, but I noticed one feature, which might be nice. What about extending it to deal with nested segmented data.
By that I mean data like:
" TAG1START d1 d2 d3 d4 TAG2START e1 e2 e3 TAG2END TAG3START f1 f2 f3 TAG3END TAG1END "
It strikes me that you could get somewhere with that by combining the CSV transform classes you already have with a DOM transform (treating the start and end markers as tags). I'm not that close to the code, so I don't know how difficult that would be to do.
Ed