Peer review is heavily encouraged - it helps prevent mistakes before they happen. And yeah, lol, Access.
Sure things in this thread are all over the place, but it's not as if this structure, as is, is entirely optimum for such uses. Over time I see this as something that can, and will improve. I'm not sure about a "MVP" but there's certainly previous planning as to the required outcome. IMHO nowhere near somewhere sensible to start programing yet, still identifying variables. But when it does, hopefully there will be collaborational tools on tap and between us we can sketch out functions then begin to wrap them into entire services. As to agreement this would be correct, input into the process of identifying variables hasn't been overly productive. After opening a thread in each ministry to capture the widest range, most got deleted. Think 2 remain. Of them one had some input, the other just seemed to be a thread to talk about what a great idea it'd be. I've kinda built that tree solo(and near the limits of my ken - so further expansion appreciated. I should possibly of put some effort into the other trees by now, but I'm lazy).
As for "business use" - there isn't one. It's reason for existence, however, is to facilitate the ease of matching required skillsets in order to easily assemble teams within our number in order to maximise success of initatives. The intent is not to actually access it, really, but instead a search engine which will pass appropriate details, which will include how to initiate contact(eventually we will have uniform facilities in place). As to security concerns, there's no personally identifyable information being collected. Just lists of qualifications, skills etc. Things like contact name(as not to expose the real name, where users have elected for not publicly displaying it) the search engine will simply retrieve this from the existing citizen database - same with geographic location, but this should be "fuzzed" ... reduced in precision. The two indexed together - possibly by ID number, as this wouldn't require adjusting the current copy of the citizen database. Then presumably this would be protected alongside the existing citizen database, encompassed by whatever methods have been deployed to protect this(likely, none by other examples. It's already publicly skimable with ease.) We're kept in the dark largely about this, even after expressly requesting details. Not a good sign, overall.
Previous positions held is a nice one, wish that'd of been thought of sooner. Aspirations and achievements are not poor suggestions within themselves but I find it difficult to model some sort of tree or structure that could contain such. Simple text input feilds would yeild a large number of options that would then require much more linking and tomfoolery with making the engine locate particular things input with different terminologies. Skills do indeed change/evolve/increase over time. My intent was to leave the input open constantly. Once we have educational facilities then courses passed in this can autonomously upgrade the database.
I could put a dollar figure on my time. You couldn't afford it. However, this isn't what motivates me. Just in the time taken to compose this post I'm out of pocket, technically. I'm quite simply prepared to do what needs done because it needs doing. To make sure it gets done. It's not to make friends, it's not to become famous, it's not to make an efficient revenue stream - it's to get it done. It's the end product of this particular initative that keeps me driven towards it's conclusion. This is just the first iteration, V2 will start getting complex. Ultimately, the output of this initative is the engine. Or the contents searched by, I don't imagine the engine itself to be anything special. The ease of connecting tasks to skills, across a wide population base. It's difficult to put a dollar figure on that. It is unquestionably worthy of persuit. The benefits are intrinsic to how it is used. BTW to clock up time spent on this, to ignore the textwall rants and focus on actual design time and data input, less than two hours.
Concerning the three seperate ways to look at a single activity, this should be a function of the engine to encompass. The user specifies what they after and the results delivered. As to the long term maintainence of the list - The community. That's how crowdsourcing works. Over time many individuals see something that needs doing and do it. When you come to put a skill in that you have and it doesn't exist in the DB yet, then you pull up the applicable file and add it yourself if you have to. Put in a pull request and wait for updates to propigate. Concerning the actual storage of this data, simply to compliment the existing DB I was thinking SQL. Kind of an industry standard, really. Quite easilly processed by machines. The tree exists in it's current gimboid form largely for humans. The rest of it is about making it trivial to feed it into awk and have that spit out some valid PHP form, and then similar for the DB queries. That sort of thing only needs specifying once and every option iterates itself. Lazy.
PS: Tyvm for that link, that's helped pad it out to 1k+ lines(and still more to go) before hr 3.