Adrien, When I was doing my master's in accounting we built up a set of books for an imaginary business entity as we learned various aspects of financial and business accounting. Entering various example data and importing data as necessary from CSV files. The final exercises and exam were done in a completed correct data set incorporating new data which we could download in CSV ( this was supplied by the textbook publisher) and import into whatever program we were using. I actually used GnuCash at that time, ~2009.
I think flywire is proposing something similar for the examples used in the documentation having them in a single file or files that can be imported. That approach was certainly useful in learning aspects of accounting practice. Maybe not as useful for the reference Manual but may be useful in the Concepts and tutorial Guide. On Fri, 2026-10-16 at 23:02 -0500, Adrien Monteleone wrote: > I am now even more confused. > > At no point did I understand there to be a 'default test data set' > ever > available. Have you just now created one? (usually, such things are > generated on the fly to test specific cases and specific code points > to > make sure things are working as intended, not so much as examples, > though certainly that is a useful function.) > > And what does this 'default test data set' have to do with the > existing > documentation or is this limited to exhibiting the new report you are > proposing? > > Regards, > Adrien > > On 10/16/26 10:37 PM, flywire wrote: > > On Sat, 17 Oct 2026 at 13:59, David T. <[email protected]> wrote: > > > > > I'm still not clear what changes you're proposing here or where > > > they are > > > intended to be placed. While I fully understand that you've > > > created a new > > > report that you want added to GnuCash that you feel meets the > > > needs for > > > analytical accounting, I don't understand your use of the word > > > "data" here; > > > the Guide doesn't really have data. It provides some examples in > > > the course > > > of explaining how to use GnuCash, but it isn't really a source of > > > data, per > > > se. > > > > > > > David, > > > > Thanks for the feedback regarding the misunderstanding about what I > > have > > built. > > > > I am not proposing any text changes to the Guide in this thread, > > nor am I > > bypassing Git/Bugzilla or suggesting I wouldn't support an update > > of the > > guide. > > > > When I say "data," I mean that I have manually extracted the > > disjointed > > transactional examples scattered throughout the text of the Guide > > and > > compiled them into a structured, unified CSV dataset. > > > > My goal is simple: provide a ready-to-use, standardised sample book > > file so > > the community can easily test and demonstrate GnuCash features, > > like > > multidimensional reporting, without starting from scratch. > > > > I hope that clarifies the scope. > > _______________________________________________ > gnucash-user mailing list > [email protected] > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
