STANDARDIZED SKILL CREATION AND PUBLISHING

Transmitting digital definitions of skills at a computing system to allow the digital definitions skills to be interoperable with other computing systems. The method includes identifying a skill name for a skill. The method further includes contextualizing the skill name for a specific system or use case by creating and storing metadata associated with the skill name. The method further includes publishing the contextualized skill at a predetermined network location, in a standardized digital format allowing for interoperability with other computing systems, wherein publishing comprises providing an active network link to the contextualized skill.

BACKGROUND

Background and Relevant Art

Computers can be used to manage so called contextualized “skills”, where the skills have a descriptive name, and the descriptive skill name is contextualized by associating metadata with the skill name to create a definition of the skill in context to a specific organization or use case. The contextualized skill can be compared to contextualized skills for other organizations or use cases. Note that as used herein, unless otherwise indicated, a skill is a contextualized skill having a skill name and contextualization metadata.

For example, Skills Architects may work with thousands of records in a library of skills in the form of a spreadsheet. Spreadsheets are cumbersome and fragile for Skills Architects to use and, as the library expands, spreadsheets will soon prove inadequate to the task of managing the library. As used herein, a skills library, or library is a collection of RSDs.

The Skills Architects deliver collections of relevant skills to the teams that design programs and curricula at an institution. They currently do so by selecting skills and exporting them as a subset of the spreadsheet. This is a cumbersome manual process of searching and copying and introduces the likelihood that a program team will not be working with the very latest relevant skills as their collection is potentially obsolete the moment it is delivered.

The Skills Architects work with outside personnel to research, craft, and improve skills according to the needs of institution program design teams. The process of putting sets of new skills into the library is manual and subject to error. These skills are not useful to the program team without information about relevant industry and job keywords, relationships to relevant certifications and standards, a well-crafted contextualized skill statement, etc. The process of putting this additional data in place is similarly manual and error prone.

The growing skills library can be used for linking an institution's educational products to the needs of industry employers and the students they will employ. Thus, there is a desire to share skills outside of institutions, and to create relationships between skills, competencies, assessments, achievements, pathways, etc. The current method of managing skills affords none of this.

Sharing data is currently extremely difficult, and open-source skills management tools that meet these aims do not seem to exist.

BRIEF SUMMARY

One embodiment illustrated herein includes a method that includes acts for transmitting digital definitions of skills at a computing system to allow the digital definitions skills to be interoperable with other computing systems. The method includes identifying a skill name for a skill. The method further includes contextualizing the skill name for a specific system or use case by creating and storing metadata associated with the skill name. The method further includes publishing the contextualized skill at a predetermined network location, in a standardized digital format allowing for interoperability with other computing systems, wherein publishing comprises providing an active network link to the contextualized skill.

DETAILED DESCRIPTION

Embodiments may be included in a system to author and manage Rich Skill Definitions (RSDS) (sometimes referred to herein as contextualized skills) and facilitate publishing in common standard formats. An RSD is a contextualized skill statement and associated metadata that enables interoperability of skills. Some skill statements have three elements, including a subject, predicate, and object. For example, for the skill statement may be “The individual evaluates chemical processes to identify ways to optimize performance.” In this example, “the individual” is the subject, “evaluates” is the predicate, and “chemical processes to identify ways to optimize performance” is the object. The metadata for an RSD may be organized according to a predetermined schema. For example, the following illustrates an example schema:

PropertyTypeComments/ExampleUUID*URIhttp://ngp.wgu.edu/skills/000001Skill Name*StringShort name or label for Skill, i.e. “VerbalContextualizedStringSkills description written in standard syntaxSkill Statement*Skill CategoryArrayKey term to categorically organize skillsProfessionalArrayField for associating skills to professional standardsStandard(i.e., NICE Framework)ToolsArrayHardware or software typically associated with a skillCertificationsArrayField for associating external certifications to RSDsOccupation DataArrayWe need to develop a context object, which indicatesCategoriesskill alignment to relevant job roles/occupations.(collapsed fields)BLS SOC: Major group, Industry, Occupation, JobFunctionO*Net: Job RoleRelationshipsArrayEach relationship needs a Relationship type and GUIDof the linked data. Kinds of relationships may include:Belongs toDepends onSpecific EmployerArrayField to relate RSDs to specific employersSpecific Employer:ArrayField to relate job titles specific to RSDs for anJob TitleemployerIntelligent SourceArraySource data to connect RSDs to intelligent job marketDatadata and underlying unique identifiers (i.e., Emsi;Creator*StringEx: WGU

With respect to common standard formats, embodiment may receive and output data, for example, according to CASE data specification, CTDL-ASN data specification, Open Badges 2.x, etc.

Referring now toFIG. 1, some embodiments may be a computer implemented system100configured to manage, process, and provide universal access through standardized data formats and universal resource locators (URLs) on computer networks, to large swaths of data and will help an institution contribute to an ecosystem of interoperability where one or more of the following may be implemented:achievements are understood in terms of the skills they recognizelearners, educators, and employers can define stackable pathways through learning programsverifiable learner records facilitate the efforts of candidates searching for jobs and employers vetting candidates for those jobscomputer interfaces are configured to make it is easy to see the landscape of skills in a particular domain and increase the use of common definitions that make achievements actionableopen standards ensure that many institutions and vendors may participate and use available data

By publishing the contextualized skills110from a data store120(such as a database, web server, or other storage) using URLs pointing to the data store120, embodiments have a number of advantages. First, users are able to ensure that the skills are up to date for any user who wishes to access the contextualized skills, rather than simply having whatever context was provided when a particular contextualized skill was cut and pasted from a document or spreadsheet and sent to the user. Second, the user can browse and access skills from virtually any system or location. Third, users can add the URL's in their own creation of conceptualized skills to provide for linking between different skills for different organizations or use cases. Other advantages, illustrated herein exist as well. Thus, embodiments implement a technologically rooted solution to an Internet-centric problem.

A Note about Users

This document considers only three users of the system: the Skills Architect102, who is the primary operator of the system; the program team members104, who consume the work of the Skills Architect in the system by reviewing collections of skills; and external users106viewing skills and collections at public URLs pointing to a publicly available, network connected datastore120, provided by the system. Note that these users accomplish these tasks by using respective computer systems112,114, and116.

Core Capabilities

Some embodiments include the following capabilities:

Work with Skills

To serve the program team and other consumers of skills, a Skills Architect is able to create, edit, and search for skills; add them to collections; view them; archive and unarchive them; and make them available to others.

In some embodiments, the work of the Skills Architect with subject matter experts (SMEs) is done outside the system, and the first time this data appears in the system will be when a Skills Architect begins entering skills manually, via batch import, or via other appropriate entry method.

1. A Skills Architect102is able to use the user interface (which may be displayed at the computer system112) to create a skill so that they may later use or improve it.» New skills start in “draft” status2. A Skills Architect102is able to use the user interface to clone a skill so that they may create a derivative skill that is separate from the original.

3. A Skills Architect102is able to use the user interface to view the complete list of skills so that they can find something they are looking for.4. A Skills Architect102is able to use the user interface to search the library for skill(s) so that they can determine which skill(s) to operate on next.» Any combination of parameters is fair game—draft or not, name, contextualized skill statement, keywords, job codes, standards, certifications, etc.5. A Skills Architect102is able to use the user interface to search within a collection for skill(s) so that they can determine which skill(s) to operate on next.6. A Skills Architect102is able to use the user interface to select a skill to view from a list and view it so that they can determine if it merits inclusion in a collection, needs further editing, etc.7. A Skills Architect102is able to use the user interface to access a skill in the system by URL and view its details so that they can determine if it merits inclusion in a collection or needs further editing.8. A non-Skills Architect (e.g., a team member104or external user106) user is able to use another user interface (which may be displayed at computer system114or116respectively) to view a public view of a skill by URL so that they can use it in their work.» Note: only published skills may be viewed unauthenticated

9. A Skills Architect102is able to use the user interface to edit a skill so that they can correct errors, add SOC codes, add or change keywords, etc.

Archive Skill

10. A Skills Architect102is able to use the user interface to archive a skill so it can no longer be put into collections.11. A Skills Architect102is able to use the user interface to unarchive a skill so it can be put into collections again.

Make a Skill Available to the Public (See FIG.4)

12. A Skills Architect102is able to use the user interface to publish a skill, promoting it from “draft” status, so it can be viewed publicly and used in collections.13. A Skills Architect102is able to use the user interface to be warned when attempting to take a skill out of “draft” that lacks useful data, such as SOC codes, so that they do not confuse the program team.

Understand a Skill (See FIG.4)

14. A Skills Architect102is able to use the user interface to know, when viewing a skill, which collections it is a part of so that they can understand the impact of potential edits.15. A Skills Architect102is able to use the user interface to know, when viewing a skill, which other skills in the library have a similar skill statement so that they can consider consolidating these skills.16. A Skills Architect102is able to use the user interface to see the history of changes to a skill so that they can determine where problems originated.17. A Skills Architect102is able to use the user interface to see if a skill has a “draft” status or is published so that they can identify which skills require attention to finalize and publish.

CONVENIENCES AROUND BLS SOC AND O*NET JOB CODES (See FIG.4)

18. A Skills Architect102is able to use the user interface to recognize a job code they enter into a skill, and automatically associate higher-order job codes with that skill, so that they can complete their work quickly and without error.19. A Skills Architect102is able to use the user interface to be able to search for skills not only by job code but by the short name associated with a BLS SOC or O*NET job code so that they can find relevant skills more easily.20. A program team member104may wish for the expression of a collection they are using to contain job codes and the short names associated with those job codes, where available in the system, so that they can readily understand the contents of the collection.21. A non-Skills Architect or public viewer (e.g., external user106) of a skill may be able to use a user interface to see the job code and name for each job code associated with the skill.

Import Skills

22. A Skills Architect102is able to use the user interface to batch import complete or partial skills into the system via CSV so that they can use or improve them later.» This creates new skills (in some embodiments); new skills start in “draft” status23. A Skills Architect102is able to use the user interface to see (during import) skills that have potentially duplicate descriptions so that they can be led to produce fewer and better-aligned skills.
Work with Collections (SeeFIGS. 5, 6, and 7)

To serve the program team and other consumers of skills, a Skills Architect102is able to create collections, add skills to and remove skills from them, search for and view them, archive and unarchive them, and make them available to others.

24. A Skills Architect102is able to use the user interface to create a collection so that they can gather skills for use by a product team.

25. A Skills Architect102is able to use the user interface to view the list of collections so that they can select one to operate on.26. A Skills Architect102is able to use the user interface to search for a collection so that they can select one to operate on.27. A Skills Architect102is able to use the user interface to search within a collection so that they can select a skill to inspect or edit.28. A Skills Architect102is able to use the user interface to view the skills included in a collection so that they can understand its readiness for consumption.29. A Skills Architect102is able to use the user interface to view a collection in the system via URL so that they can determine if it needs further editing or is ready to share.30. A non-Skills Architect user is able to use a user interface to view the public view of a collection via URL so that they can make use of its contents.31. A non-Skills Architect user is able to use a user interface to retrieve the contents of the public view of a collection in CSV format so that they can use its contents to do other work.32. A non-Skills Architect user is able to use a user interface to retrieve the contents of the public view of a collection via URL in JSON-LD format so that they can use it in a system that operates on Credential Engine's CTDL-ASN standardized representation of skill data.

Update Collection

33. A Skills Architect102is able to use the user interface to select one or more skills from a list, then include them in a collection, so they can be used in the work of the program team.34. A Skills Architect102is able to use the user interface to include the skill they are viewing in a collection so it can be used in the program team's work.35. A Skills Architect102is able to use the user interface to remove a skill from a collection, via the individual skill, so it will not interfere with the program team's work.36. A Skills Architect102is able to use the user interface to remove a skill from a collection, via the list of skills included in the collection, so it will not interfere with the program team's work.37. A Skills Architect102is able to use the user interface to be warned when they attempt to add a draft skill to a published collection so that they do not confuse the program team.

Archive Collection

38. A Skills Architect102is able to use the user interface to archive a collection so no one uses it mistakenly.39. A Skills Architect102is able to use the user interface to unarchive a collection so it may be used again.

Make a Collection Available to the Public (See FIGS.5and6)

40. A Skills Architect102is able to use the user interface to make a collection available to the program team/public (by removing its “draft” status) so they can use it to inform their work.41. A Skills Architect102is able to use the user interface to be warned when attempting to take a collection out of “draft” status if it has draft skills, so that they do not confuse the program team.42. A Skills Architect102is able to use the user interface to be warned when attempting to take a collection out of “draft” status if it contains no skills, so that they do not confuse the program team.

Understand a Collection (See FIG.5)

43. A Skills Architect102is able to use the user interface to see the “draft” status of a collection so that they can have my attention brought to work in progress.

Access

44. A Skills Architect102is able to use the user interface to be able to log into the system using the institution identity and access system, which can control who has access to authenticated use of the system, so that they can complete work in the system.

Additional Details

Some embodiments will support the following general capabilities.

Search for Skills

It is common for Skills Architects using the current skills spreadsheet to filter by one or more columns (keywords, job codes, etc.), then search for useful skills based on text fragments in skill statements and other strings. The search feature is able to accept and make use of all these data types.

Publish Skills

A skill goes from unpublished to published merely by removing its “draft” status.

“Draft” status is purely a human decision (in some embodiments) but is intended to ensure that a skill is not merely complete in its strictly required parts but also complete enough to be useful to others.

When a skill is in “draft” status, it is not visible to the outside world at its canonical URL. When a skill's “draft” status is removed, the system makes it immediately available to the public.

The skill's canonical URL is subject to content negotiation. User agents (UAs) requesting HTML will receive a nicely formatted, human-readable HTML expression of the skill. UAs requesting JSON or JSON-LD will receive a standards-compliant JSON representation of the skill suitable for use in systems that understand CTDL-ASN.

Publish Collections

A collection goes from unpublished to published merely by removing its “draft” status. Removing “draft” status is purely a human decision (in some embodiments) but is intended to denote that a collection is ready for others to use.

When a collection is in “draft” status, it is not visible to the outside world at its canonical URL. When a collection's “draft” status is removed, the system makes it immediately available to the public.

The collection's canonical URL is subject to content negotiation. UAs requesting HTML will receive a nicely formatted, human-readable HTML expression of all skills in the collection. UAs requesting JSON or JSON-LD will receive a standards-compliant JSON representation of the collection suitable for use in systems that understand CTDL-ASN.

The HTML representation of the collection also contains a control that allows the UA to obtain a CSV file containing the data for each skill in the collection.

Allow Internal and External Access by Url

The system is available to authenticated users at a URL internal to the institution.

Skills and collections that have been made public are available to unauthenticated users at their canonical external URLs.

Skills and collections that have not yet been made public are available only to authenticated users at their canonical external URLs.

Skills and collections are also available to authenticated users within the system via specific internal URLs related to their canonical external URLs for convenience of directing system user attention to a specific skill or collection.

Prevent Premature Publication of a Collection

A collection is useful when it contains a set of fully qualified, useful, related skills. Therefore, it is recommended that a collection not be made public (have its “draft” status removed) if it contains skills in “draft” status.

A user who attempts to remove “draft” status from a collection containing one or more skills with “draft” status can be warned—in some embodiments with the option to publish anyway, thereby removing the draft status from the indicated skills as well.

A user who attempts to add a draft skill to an already public collection may be warned—in some embodiments with the option to do so anyway, thereby removing the draft status from the indicated skill.

Prevent Duplicates

Helping avoid duplicate (highly similar) contextualized skill statements is important during batch import of skills and nice to have during authoring of a skill. To a human a skill statement is possibly a duplicate, when to a computer it is merely similar. Thus, some embodiments implement a similarity (and/or distance) search that returns skills with the most similar skill statements, within some predetermined similarity threshold. In some embodiments, a similarity threshold may be set via trial.

Track Changes

Some embodiments may explicitly version skills or collection. In other embodiments, the system does not explicitly version skills or collections. In such embodiments, however, it does keep an audit log of changes to a skill or a collection and expose it to internal users. This intends to allow users to recover from mistakes and unintended consequences, review edits, etc. It is up to the Skills Architect whether to create a new skill or collection when a substantive change is necessary.

Keyword Association

Keywords will be used to group skills, rather than single categories. A keyword may be a word or a phrase (and can contain a space). Zero keywords may be associated with a skill, but a skill isn't easy to find and understand without at least one.

Help with Job Codes

Entering and segmenting BLS SOC and O*NET job codes in the current skills spreadsheet is arduous and error prone. The system understands these codes well enough to infer the higher-order codes when a more granular code is entered, so these codes can be available for searches. In some embodiments, the system displays job code short names in useful places for Skills Architects and program team members, as well as allow searches to make use of their text.

The system allows Skills Architects to enter other strings as job codes, so other job code systems might be captured in skills in a basic way.

Link to Outside Data Sources

For some embodiments, it is sufficient for Skills Architects to record zero or more URLs, pointing to outside data sources, in an individual RSD. This is meant to be inexpensive and preserve optionality for later possible integrations with EMSI and other data sources.

Be Visually Similar to Other Institution Tools

The appearance of the system, in some embodiments, is consistent with other institution tools and makes use of patterns found there wherever helpful.

Open Source

In some embodiments, the system is shareable as an open source package. In some embodiments, this may be accomplished by providing:Source code for the back end and front end of the system tool, Kotlin/Spring/Angular, made public via GitHub.Deployment/infrastructure notes and details so open source users can deploy the tool and use it, made public via GitHub.Deployment/infrastructure work so the institution can deploy the tool to its existing production environments, proprietary.

Be White-Label Ready

A lightweight way to change the appearance of the tool (such as a configuration file containing colors, URLs of logo assets, etc.) may govern the branded appearance of the system. This will allow the system deployed at the institution to appear to be a sibling of other the institution tools while being deployable by others.

MV Views, Variants, and Modules

Following are system views that may be included in various embodiments, including their capabilities and related data.

Skills Lists

1. Library empty (skills list empty)» Local capabilitiesCreate skill (revealed in empty state)» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: empty state message and action» NotesIt should be a lightweight empty state as it won't be empty for long2. Library populated (skills list)» Local capabilitiesView skill from listMulti-select skills for association with a collection» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: skills as list itemsNotesLikely paginatedThis may be the “home” page for systemAny skills display, skills form, etc. will be informed by the RSD schema3. List of skills, search results (skills list)» Local capabilitiesRevise searchView skill from listMulti-select skills for collection» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: skills as list items» Success: list» Errors: empty list, what was wrong with the query» NotesLikely paginated4. collection, empty» Local capabilitiesArchive/unarchive this collectionEdit collection namePublish collection (remove “draft” status)» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» DataEmpty state for collection with no skills yet“Draft” statusArchived state (or not)Canonical URL» NotesPrevent publication of an empty collection (warn when removing “draft” status if collection is empty)Addressable via list in system and directly via URL5. collection, populated» Local capabilitiesRevise searchSearch within this collectionView a skill from the listMulti-select skills for removal from collectionRemove selected skills from a collectionArchive/unarchive this collectionEdit collection namePublish collection (remove “draft” status)» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» DataCollection nameSkills as list itemsDraft status (or not)Archived state (or not)Canonical URL» NotesPrevent publication of a collection containing draft skills (warn when removing “draft” status if draft skills are present in the collection)Prevent publication of an empty collection (warn when removing “draft” status if collection is empty)Likely paginatedAddressable via list in system and directly via URL

Single Skill

6. Skill» Local capabilitiesEditCloneRemove “draft” status (publish)Archive/unarchiveAdd to a collectionRemove from a collectionCheck for similar skill statements» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» DataEverything in a fully qualified skillEdit history—list of edits in reverse chronological order up to the current skill contentsCanonical URLDraft status (or not)Archived state (or not)Collections in which the skill is used» NotesCan be accessed via list in system, directly in system via system skill URL, and directly via public canonical URL if publishedIdeally, user can directly edit from here rather than having a separate edit viewNote: The exact manner of exposing and handling potential duplicates will be designed in a later phase7. New Skill Form» CapabilitiesSaveCancelCheck for similar skill statements» Data: empty, but pre-populate “Creator” and auto-generate “Skill ID/Canonical URL”» Success:Saved skill, with “draft” statusShow prior view with notice that skill was saved? Or show a new skill?» Errors: new skill form required fields not populated» Note: The exact manner of exposing and handling potential duplicates will be designed in a later phase

List of Collections

8. List of collections, empty» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: empty state message featuring create collection action9. List of collections, populated» Local capabilitiesSelect collectionView collectionArchive/unarchive collectionRemove “draft” status of collection» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: collections as list items, containingNameNumber of skillsArchived state“Draft” statusPossibly: frequent keywordsPossibly: publication date10. List of collections, search results (a form of collections list)» Local capabilitiesSelect collectionView collectionRemove “draft” status of collectionArchive/unarchive» Common capabilitiesCreate skillCreate collectionSearch for skills/collectionsView library of skills/collectionsBatch import skills via CSV» Data: collections as list items» Success: list of collections» Errors: empty list, what was wrong with the query11. New collection form» Capabilities: save, cancel» Data: none, pre-populate “Creator” and “Canonical URL” D SuccessSaved collectionShow collection empty state?» Errors: new collection form not populated enough to save; must have title

Public Views

12. Public view of skill» CapabilitiesContent negotiation—can get HTML or JSON-LDDownload as CSV» DataAll elements in the RSD schemaCanonical URLArchived stateDate archived“Draft” status (if authenticated)» ErrorsURL does not point to a skill (404)URL requires authentication to view (401?)13. Public view of collection» CapabilitiesContent negotiation—can get HTML or JSON-LDDownload as CSV» DataCollection nameCanonical URLArchived state“Draft” status (if authenticated)Stack of skills entries, including for each skill:All elements in the RSD schemaCanonical URLArchive statusDraft status (if authenticated)» ErrorsURL does not point to a collection (404)URL requires authentication to view (401?)

Special Views

Embodiments may incorporate the following user interface modules in various configurations:Skill display, skill form (ideal if one can be the other, editable in place)» Includes skill edit historyLists» List view of skillsSkill as a list item» List view of collectionsCollection as a list item» Single/multi-select of list itemsSearch controls for skills or collectionsConsistent location and appearance of universal capabilities (create skill, create collection, search for skills/collections, batch import skills via CSV)Confirmation dialogs for archive/unarchive or publish and warnings around sameStatus for archived/unarchived or draft/publishedPaginationKeyword suggestion (add similar items or select from a list)

ADDITIONAL EMBODIMENTS

Embodiments may implement one or more of the following features:

Conveniences for Improving a Skill

Embodiments may include guidance in a user interface for Skills Architects adding certifications to a skill so that one can be sure the correct ones are included.Embodiments may include guidance in a user interface for Skills Architects adding standards to a skill so that one can be sure the correct ones are included.Embodiments may include guidance in a user interface for Skills Architects adding a keyword to a skill so that one can be sure the correct one is used.Embodiments may include guidance in a user interface for Skills Architects finding skills that are missing pertinent information so that they can prepare them for use by others.
Conveniences for Working with a CollectionA Skills Architect102is able to use the user interface to begin establishing a new collection by first selecting one or more skills to include so that they can more conveniently start a collection from search results.A Skills Architect102is able to use the user interface to make a clone of a collection so that they can edit the collection.A Skills Architect102is able to use the user interface to give a collection a description to be more informative to the program team.A Skills Architect102is able to use the user interface to give a collection keywords to make finding collections easier.A Skills Architect102is able to use the user interface to view edit history for a collection so that they can determine where problems originated.

Batch Editing

is able to use the user interface to update the tagging or keywords of multiple selected skills at one time so that they can more rapidly and accurately associate the selected skills with the same job code, standard, etc.
Working with Keywords

To facilitate keyword management (merge them, rename them outside of skills, etc.) the keywords can be implemented as objects unto themselves.A Skills Architect102is able to use the user interface to create a new keyword so that they can better organize and segment the skills library and collections.A Skills Architect102is able to use the user interface to search the list of used keywords so that they can find one or more to operate on to improve skill findability.A Skills Architect102is able to use the user interface to see keywords used so that they can select keywords to edit.A Skills Architect102is able to use the user interface to edit a keyword so that they can correct an error or adapt to emerging vocational terminology.A Skills Architect102is able to use the user interface to assign multiple keywords to a skill so the skill has more context.

Versioning

Explicit versioning of skillsExplicit versioning of collections

Referring now toFIG. 8, a method800is illustrated. The method800includes acts for transmitting digital definitions of skills at a computing system to allow the digital definitions of skills to be interoperable with other computing systems. The method800includes identifying a skill name for a skill (802).

The method800further includes contextualizing the skill name for a specific system or use case by creating and storing metadata associated with the skill name (804).

The method800further includes publishing the contextualized skill at a predetermined network location, in a standardized digital format allowing for interoperability with other computing systems, wherein publishing comprises providing an active network link to the contextualized skill (806).

The method800further includes receiving a request for the contextualized skill by the other computing systems as a result of users at the other computer systems selecting the active network link (808).

The method800further includes as a result of the request, causing the contextualized skill to be automatically transmitted to the other computing systems (810).