I've now done a bit more research and the recipe software suggested above is definitely not for me. I have started building a relational DB with multiple tables, the two big ones being recipes and ingredients.
My challenge is 'keywording' to use an Adobe Lightroom metaphor. I need to create sub-categories e.g. vegetable/tuber/potatoes/salad potatoes/charlotte with relevant input fields. I also need all the 'keywords' above to be populated so if I enter 'charlotte', then all the keywords above are also selected. In addition when I describe a recipe, I want to be able to specify potatoes, salad potatoes or charlotte at will.
On the recipe side, it is a bit of the same but with the ability to move 'sideways' So you may have 'meat main courses'/beef/raw beef/steak tartare but as a small portion this is often also offered as a starter. Maybe it's a case of two separate tables, one with multiple choices
Another table would be cooking methods and you could use main method + other methods. The steak tartare with fries above would be 'raw' + 'deep frying'
Ultimately I would want to enter a query such as 'starter containing spinach and involving deep frying' and it would come up with 'courgette flower stuffed with ricotta and spinach'
Ideally, it needs to be future proof i.e. exportable as an SQL database should the supplier stop updating the programme.
So far I've been testing Ninox
, which is reasonably straightforward to use but is giving problems with some of the keywording described above.
Any follow-up thoughts appreciated!
Bop 'til you drop
MB Pro 13 | i5 | 16 Gigs of shiny DDR RAM | 1TB SSD - we have arrived...
iMac 27 i5 16Gig 1TB
iPad Air 64Gig
Time Capsule 1TB | 4TB connected HD
iPhone 6: "Too big, but bloody fast..." & a bunch of ill fitting ear buds
Canon 7D proper camera with nice L glass and Lightroom 6