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
"One of the things I’ve been puzzling about this project is how to present what I’ve developed. The idea is that this script is a toolkit – a basis to build upon. It is meant to handle the big barriers to manipulating CIN Census files by handling the conversion between XML and blades for you. A person who wants to use it to get the validation errors will take a very different approach to someone who wants to transform their CIN submission before they upload it.
What I’ve done in this first version is split the code into sections, each of which does one of those things. Then I’ve commented out the latter two sections – the idea being the end user can pick up what they want from it, and maybe customise them as they do it (more important if you’re using it for transformations as it doesn’t come with any out-of-the-box). Not sure how sustainable that approach would be if we add more and more options to the toolbox. Suggestions welcomed!"
The text was updated successfully, but these errors were encountered:
"One of the things I’ve been puzzling about this project is how to present what I’ve developed. The idea is that this script is a toolkit – a basis to build upon. It is meant to handle the big barriers to manipulating CIN Census files by handling the conversion between XML and blades for you. A person who wants to use it to get the validation errors will take a very different approach to someone who wants to transform their CIN submission before they upload it.
What I’ve done in this first version is split the code into sections, each of which does one of those things. Then I’ve commented out the latter two sections – the idea being the end user can pick up what they want from it, and maybe customise them as they do it (more important if you’re using it for transformations as it doesn’t come with any out-of-the-box). Not sure how sustainable that approach would be if we add more and more options to the toolbox. Suggestions welcomed!"
The text was updated successfully, but these errors were encountered: