Competency and Skills Service -- Competency Framework Editor
Create, edit, modify CASS frameworks and competencies using an easy to use, embeddable iframe.
The (unbranded) experimental new version of cass-editor is available for use at https://cassproject.github.io/cass-editor/ and is found on the master branch. References to 1.3 in this README refer to this branch.
To try the previous, stable version of the editor, check out branch 1.2.
Integrate the cass-editor into your website by nesting it into an iframe on your website.
<iframe id="iframe" width="100%" height="800" frameborder="0"></iframe>
<script>
document.getElementsByTagName("iframe")[0].setAttribute("src", "https://cassproject.github.io/cass-editor/");
</script>
The cass-editor attempts to read the stylesheets of the parent page and import them into the website if they have inherit="true"
as an attribute. It may not be able to do this without your help.
An error message when headers are not set:
...Styles/Webfonts/Gibson/Gibson-Regular-webfont.woff2' from origin 'https://cassproject.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://cassproject.github.io' is therefore not allowed access. The response had HTTP status code 404.
To remedy this, your web server needs to allow cross-origin requests to the cassproject github.io site, or you can clone this repository and host it locally.
Access-Control-Allow-Origin: https://cassproject.github.io
Finally, to import a CSS file using a URL parameter, use css=<url>
.
The cass-editor has many modes and options that can be enabled or disabled based on desired functionality. These options are passed as URL parameters.
By default, the cass-editor operates on the dev.cassproject.org CASS instance. This should instead be your server. To do this, use server=protocol://cass.yourserver.com
.
ex:
https://cassproject.github.io/cass-editor/?server=https://sandbox.cassproject.org
By default, the cass-editor provides a framework browser to select and edit frameworks. To instead be restricted to only viewing frameworks, use view=true
.
ex:
https://cassproject.github.io/cass-editor/?view=true
By default, the cass-editor prior to version 1.3 edits competency frameworks. To instead edit concept schemes, use concepts=true
. Starting in version 1.3, you can select Concepts from the menu in the sidebar to edit concept schemes. If you want to bypass the welcome page and link directly to the list of concept schemes, this parameter can be used in conjunction with frameworksPage=true
.
ex:
https://cassproject.github.io/cass-editor/?concepts=true
If your app needs the ability to select competencies from a framework, use select=label
where 'label' is the tag you want the select button to have. ex: Add, Select, Import. Best used with view=true
. Clicking the select button will send a post message with the selected items to the parent application.
ex:
https://cassproject.github.io/cass-editor/?select=Add
If your app needs to have the entire competency or relation returned as part of the selection, or the framework that the competencies were selected from use selectVerbose=true
.
ex:
https://cassproject.github.io/cass-editor/?select=Add&selectVerbose=true
If your app needs to receive CTDL-ASN fields in the postMessage when selecting competencies to add or link to, use selectExport=ctdlasn
.
ex:
https://cassproject.github.io/cass-editor/?selectExport=ctdlasn
If your app needs the ability to select a single competency from a framework, use singleSelect=label
where 'label' is the tag you want the select button to have. ex: Add, Select, Import. Best used with view=true
.
ex:
https://cassproject.github.io/cass-editor/?singleSelect=Select
If your app needs the ability to select a single competency and the relations associated, use selectRelations=true
along with select
.
ex:
https://cassproject.github.io/cass-editor/?select=Add&selectRelations=true
If your app needs the ability trigger the select action from outside of the cass-editor iframe, send the iframe the postMessage {"message":"select"}
. Additionally, if you wish to hide the select button and use one on your page instead, use select=
without a value.
ex:
https://cassproject.github.io/cass-editor/?select=
By default, the cass-editor provides a framework browser to select and edit frameworks. To start with a workflow of creating a framework, use action=add
. This will expose the framework creation and import pages (1.2) or take you to a newly created framework (1.3).
ex:
https://cassproject.github.io/cass-editor/?action=add
To jump directly to the import option of the above add menu, use action=import
. This will expose the import page.
ex:
https://cassproject.github.io/cass-editor/?action=import
If you have a specific framework you are directing your users to edit or view, you can force the cass-editor to only show that framework by using frameworkId=<url identifier of framework>
ex:
https://cassproject.github.io/cass-editor/?frameworkId=https://dev.cassproject.org/api/data/schema.cassproject.org.0.3.Framework/e17ad428-e27e-4265-b2ec-782fe7cd81e1
If you have a specific competency you are directing your users to edit or view, you can force the cass-editor to select that competency using competencyId=<url identifier of competency>
. Must be used in conjunction with frameworkId=<url identifier of framework>
ex:
https://cassproject.github.io/cass-editor/?frameworkId=https://dev.cassproject.org/api/custom/data/schema.cassproject.org.0.2.Framework/76ffff33-bd15-4bf3-a007-4ce247d2216d&competencyId=https://dev.cassproject.org/api/custom/data/schema.cassproject.org.0.2.Competency/onet:1.A.1.a.1
If you wish to highlight one or more competencies, you can force the cass-editor to highlight that competency using a postMessage. It is suggested this be used in conjunction with frameworkId=<url identifier of framework>
document.getElementById("iframe").contentWindow.postMessage({
"message": "highlightedCompetencies",
"competencies": ["@id of competency", "@id of competency", "@id of competency"]
}, window.location.origin);
or ex:
https://cassproject.github.io/cass-editor/?frameworkId=https://sandbox.credentialengineregistry.org/resources/ce-b454a3b4-ae5f-4e41-9ce1-f4b4f1776a79&highlightCompetency=https://army.mil/task/081-833-0197&highlightCompetency=https://army.mil/task/081-835-3010&server=https://dev.cassproject.org/api/
If your users need the URLs for each framework or resource they are editing, you can enable link-showing by using link=true
ex:
https://cassproject.github.io/cass-editor/?frameworkId=https://dev.cassproject.org/api/data/schema.cassproject.org.0.3.Framework/fd9dbdae-6b10-46da-8256-1458b448bfab&link=true
If you are limiting users to seeing only a set of frameworks that can be described by a search query, you can add an additional search query to the initial framework search by using filter=<search query>
.
ex:
https://cassproject.github.io/cass-editor/?filter=@id:case.georgiastandards.org
CASS can create and manage a local user that owns the frameworks and competencies they create. The user credentials will be stored in HTML5 LocalStorage and unique per individual. To enable this functionality, use user=self
.
Note: This method is risky, as a user that clears their localstorage will lose access to their frameworks and competencies.
CASS can operate using credentials provided by the parent site. These credentials are passed into the iframe via a message, in order to avoid transmitting them over HTTP. Use user=wait
, and pass a RSA-OAEP 2048 bit PEM private key in via:
document.getElementById("iframe").contentWindow.postMessage(
JSON.stringify({action:"identity",identity:privateKey}),
window.location.origin
);
The cass-editor can be populated with templates that set initial properties of new competencies and frameworks. These templates are passed into the iframe via a message. To specify:
document.getElementById("iframe").contentWindow.postMessage(
JSON.stringify({
action: "template",
competency: {
"http://bogus/property": "woo"
},
framework: {
"http://bogus/property": "woo"
},
conceptScheme: {
"http://bogus/property": "woo"
},
concept: {
"http://bogus/property": "woo"
}
}),
window.location.origin
);
Along with user credentials, the cass-editor can be configured to not show others' frameworks. This functionality can be enabled by the URL parameters show=mine
or ownedByMe=true
.
When linking a concept to a competency, the cass-editor can be configured to not show others' concept schemes. This functionality can be enabled by the URL parameter conceptShow=mine
.
Users can make a framework or concept scheme private by clicking the checkbox in the edit pane (1.2) or clicking the user management button within a framework (1.3). This checkbox can be selected by default with the URL parameter private=true
. Note that this will not change existing frameworks and concept schemes but will apply to newly created ones.
When linking a concept to a competency or another concept, the cass-editor can be configured to allow the user to edit concepts or concept schemes. This functionality can be enabled by the URL parameter editIframe=true
.
CASS supports the storage of objects where the @id parameter does not refer to the object in CASS.
cass-editor can be configured via the newObjectEndpoint
to create and edit objects with @id
URIs or objects located outside of CASS.
As an example, if newObjectEndpoint=http://not.here/
and a new framework is created, the @id
of the framework will be http://not.here/<generated UUID>
.
Additionally:
The base URL for version 1.3 takes the user to a welcome page. If you wish to bypass this page and have the framework list be the first thing your users see, use the URL parameter frameworksPage=true
. If you want to go directly to the concept scheme list, this parameter can be used in conjunction with concepts=true
.
The cass-editor can orient towards either a basic CASS schema or a Credential Engine CTDL-ASN schema.
ceasnDataFields=true
enables and renames fields to accompany the CTDL-ASN fields. Many of these fields map to schema.org properties, but some map only to CTDL-ASN properties. In 1.3, this parameter also hides some components from view, such as configuration management and user/group management.The cass-editor can be configured to hide the assertion management functionality if it is not needed.
disableAssertions=true
will hide the assertion timeline, assertion sharing, and assertion creation/edititing features.The cass-editor can be overridden to assist in cross domain, iframe, and web socket connection issues.
editorRoot=<relative or absolute path>
helps any recursive iframes locate the root of the cass-editor. Examples include '/cass-editor/' or 'https://cassproject.github.io/cass-editor/'webSocketOverride
helps the cass-editor connect to the websocket of CASS in case a reverse proxy is misbehaving when handling websockets (Looking at you, IIS.)The cass-editor can send events when various operations occur.
To bind the cass-editor from the parent page, use the following code:
window.addEventListener('message', iframeMessage, false);
function iframeMessage(event) {
//check the origin, to make sure it comes from a trusted source.
if (false && event.origin !== window.location.origin)
return;
alert("I got " + event.data.selected.length + " selected items from the iframe");
}
To ensure the iframe is passing the correct origin, pass the origin into the iframe using a URL parameter, origin=originUrl
.
select=Add
):event.data.message == "selected"
event.data.selected == [uri,uri,uri]
or, if selectVerbose is on, event.data.selected == [{Competency},{Competency},{Competency}] and event.data.selectedFramework == {Framework}
Changes when frameworks or competencies are clicked, changed, or the internal editor view changes are passed to the parent page. The message types are `viewChanged`, `frameworkChanged`, `frameworkClicked`, `competencyChanged`, `competencyClicked`. See the console for additional fields that are passed.
To export, send the iframe a message to export using a particular format.
$("iframe")[0].contentWindow.postMessage({action:"export",schema:"ceasn"},window.location.origin);
You will receive in the parent page an event:
message.data ~= {
action: "response",
message: "export",
schema: "<schema>",
format: "<format mimetype>",
data: "<data in JSON if JSON-compatible, string if not JSON compatible."
}
Acceptable schemas are: "cass","cassn4","cass","cassrdfjson","cassrdfxml","cassturtle","ctdlasn","asn","case".
To set some data in an object:
$("iframe")[0].contentWindow.postMessage(
{
action:"set",
id:"https://id of the object to set",
key1:value1,
key2:value2
}
,window.location.origin);
A response event will be sent: "setOk","setFail" after the save is attempted.
Most fields are not validated beyond the input type assigned to them. URLs, drop downs, datetimes and selectors all have inbuilt validation. The datetime format being used is ISO 8601. The user is prevented from saving invalid date. To change the behavior to warn the user if they are saving invalid data, set allowValidationBypass=true
.
Validation can be accomplished through the configuration manager. Here you can set which fields are required, the type of value accepted, whether the field is limited to one value or can have multiple values, etc.
Clone cass-editor to local repository.
Install dependencies and submodule.
cd cass-editor
git submodule init
git submodule update
npm install
Enable HTTPS using the ca.pem file. With Windows/Chrome:
Create an .env.local file in the project root directory. Its contents should be:
VUE_APP_SELECTEDSERVER=https://dev.api.cassproject.org/api/
Start cass-editor.
npm run serve
Connect.
npm install cassproject
npm audit --production
and address any dependencies with vulnerabilitiesnpm run test:unit
After github finishes deploying to the gh-pages branch, the cass-editor pointer can be updated in the CaSS repository.