Founded in 2008. The Landscape Juice Network (LJN) is the largest and fastest growing professional landscaping and horticultural association in the United Kingdom.
LJN's professional business forum is unrivalled and open to anyone within within the UK landscape industry
LJN's Business Objectives Group (BOG) is for any Pro serious about building their business.
For the researching visitor there's a wealth of landscaping ideas, garden design ideas, lawn advice tips and advice about garden maintenance.
Replies
That's a database building task, chris. Sounds like a decent challenge in a worthwhile pursuit.
The question is not so much about writing the database but deciding which database management system to use and which language to run the queries on. For instance (I use open source) perl, php, python, ruby and so forth.
I may well take it on this winter with either MySQL or PostgreSQL as the management system if I can't find an existing open source app already available.
If there are enough takers I could probably host a multi-user (individual database, individual access, own data only) server too. Web hosted so if you can use a browser you can use the app. When it's done. There may even be scope for half a dozen or so to help test it and raise query ideas in return for an extended free usage period.
Thanks for the idea.
Nothing complicated to the human, chris, especially when using a human language such as English.
Unfortunately digital pulses work somewhat differently. So how I would be structuring the database, then writing the php or perl scripts to query it - that is to say add in any new information correctly or give it a command such as "tell me this month if it needs pruning this month, say nothing about pruning it this month if it does not need pruning this month" - will be none too logical to the casual reader.
But if I get your main point correctly then yes, it should be able to print out for you, whether on screen or printed copy (or both), a schedule of work or treatment for this month's/week's/whatever's visit specific to that site, provided you or your staff have taken the trouble to enter the data regarding that site in the first place.
Surely that exists on the RHS guides (example here) via smartphone or by software products such as 'Complete Gardens" (or its online version)?
OK, but if all you need is info on the plants on your client site, keep a list and refer to the RHS site or similar prior to each visit. That sort of information is already there in abundance on t'interweb.
I'm understanding your original post as being more demanding, like you tell your database what's in that particular garden and it helps you keep tabs on what needs doing and when, in a format which you can print off and give your staff as a "to do" list or similar.
It can only do that if you keep it up to date with what you pull out and what you plant that's new. To achieve that it has to be correctly written in an appropriate set of languages, including some dialect or other of SQL (structured query language, and no, M$ arrived long after SQL, they most certainly did NOT invent it) and for web use a scripting language capable of handling SQL queries in a way that a browser can present it to you.
You can do that by setting up your plant groups/lists and querying by month ?
Like this....
So, every time you come across a new plant in one of your gardens you add it to a list(s) online, then select the month when you're in the garden and hey presto..
chris said:
Gary's right, chris, going by what you're saying now.
If on the other hand you mean you want instructions to hand for your staff in time for a site visit, which is what I initially understood, you need a means of scraping relevant information about plants and how to tend them from other sites, throwing that into a database, querying the information by filtering for each site and displaying output as a set of instructions or guidelines for that visit.
It will be very hard work to do that on a plant by plant basis. Restructured to have a list of plants on each site and relating the queries to that specific list it could be made to work quite smoothly I think. Emphasis on the last two words deliberate.
-
1
-
2
of 2 Next