These are the things that need to be added to the SkillsBase system.
Here are the things being added to the next version
- Add a location tree and facilities for people to say where they live, where they are willing to work, and where they are entitled to work. This would be similar to the Skills Tree, but instead of skills, this would be a taxonomy of locations. At the top of the tree would be "all" then within that we could have Global, then countries regions, cities etc. The location tree would be a folksonomy and so would grow in response to actual need and would reflect local conditions and political boundaries. For example, the Sydney CBD might be in the tree as /all/Global/Australia/NSW/Greater Sydney/CBD. Walnut Creek could be /all/Global/US/CA/Bay Area/East Bay/Walnut Creek. The point is that the people who live/work in these places could describe them. We could also have links to things like Google Maps to show where these places are geographically, which might be fun.
- There should be some consistency between the contact, location and summary sections. In the opinion of this user, all should be set up like the summary: show the text the user has entered, and give them an Edit button to take them to an edit page.
- Search results are listed in order of Member / Subscriber / Guest (and the account status is shown) and within that the ordering is the most recently updated resume first. This is in response to the suggestion that the search mechanism should take into account experience and location etc.
Here are things for future versions
Please add things you would like to see to this list.
- Engagement start and end dates should be validated on the client (using ECMAScript if possible).
- Dates imported from HR-XML in YYYY-MM format (as opposed to YYYY-MM-DD) should be accepted by the SkillsBase. At present, these get imported as the current day at the time of import. Ideally we would support the input of both types of date, but if all dates are to be converted to YYYY-MM-DD format, the SkillsBase should follow a convention, e.g. YYYY-MM => YYYY-MM-01, such that totals for skills make sense. Ideally, when these yyyy-mm dats are exported again, they should be represented at yyyy-mm, and not yyyy-mm-01.
- The skills tree should be displayed in a way which allows expanding and collapsing branches of the tree and searching within the tree (even in the collapsed branches). The elements of the tree should be in a sensible initial order.
- Tables should be sortable (without having to inccur the cost of a round-trip to the server). Tables should be initially presented in a reasonable order.
- Perhaps the availability information should be using calendars. Then we can take advantage of existing free/busy capabilities. It such be possible to use calendar information to express availabiliy in a way that can be searched.
- Members should be able to specify that their entries default to public rather than private when created.
- A commendation facility, where one member can commend another.
- Smarter export of HRXML Competency elements if multiple skills share the same root.
- Members should be able to allow searchers to download a PDF and/or HR-XML version of their public details from their public resume page.
- Enable searching by employer
- Have the exported HR-XML record what skills and engagement are public/private and have the import re-establish these settings.
- Model the migration of one skill into one or more other skills by remembering the lineage of a skill, i.e. if it came out of another skill, or if it was replaced by a set of more specific skills ... then, in searching make it clear to searchers that a skill has been superseded, also make this notice work for a while, and then expire.
- Provide a skill-centric view of My Resume. In this view I see one skill, and all the engagements the skill has been used in. I can modify the notes and experience levels for the engagements skills.
- Allow searchers to create job specifications. These would be essentially saved search specifications, but may include text describing a position. Such saved searches could be used by searchers to repeat searches easily, or even to advertise jobs.
- Add support for certifications (e.g. LPI or a BSc from a university). Certifications will be held in a tree (probably). The certificates tree may only be added to by the system admin, and each certification in the tree must have a defined way of confirming the certification. The method will vary among the certifying organisations. People will be able to claim any certification, but the certification will only appear in the tree if confirmed by the certifying authority.
- Members should be able to have one external link show on their public home page. For example, this could be to their personal www home page, or to the home page of their business or even their employer.