Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add versionIdentifier, lastestVersion, nextVersion, previousVersion to CompetencyFramework, Collection, and Competency #1357

Open
mparsons-ce opened this issue May 7, 2024 · 9 comments

Comments

@mparsons-ce
Copy link

The following properties are being added in CTDL to CompetencyFramework, Collection, and Competency:

https://credreg.net/ctdl/terms#versionIdentifier
https://credreg.net/ctdl/terms/latestVersion
https://credreg.net/ctdl/terms/nextVersion
https://credreg.net/ctdl/terms#previousVersion

The latter three are URLs. VersionIdentifier has a domain of the class: IdentifierValue.

We would like these added to the CaSS editor.

Source: see CTDL github issue: CredentialEngine/Schema-Development#933

@jeannekitchens
Copy link

jeannekitchens commented May 8, 2024

@mparsons-ce @sedula27 Doesn't CaSS need to support the following:

versionIdentifier: https://credreg.net/ctdl/terms#versionIdentifier - This is a property that points to IdentifierValue. Thereby, CaSS needs to export versionIdentifier and the UI needs to include the properties with the IdentifierValue class:

  1. https://credreg.net/ctdl/terms/identifierType - string
  2. https://credreg.net/ctdl/terms/identifierTypeName - string
  3. https://credreg.net/ctdl/terms/identifierValueCode - string

Need to support multiples: There can be be multiple versionIdentifiers associated with any Competency Framework, Competency or Collection.

latest, next and previous version These require a valid CTID and are single values.

Impacted Classes: The Collection, Competency, and Competency Framework classes need the above listed property updates.

What else needs to be documented here?

@mparsons-ce
Copy link
Author

@jeannekitchens
I think technically latest, next and previous version can be any URI, they don't have to be a CTID/registry URI.

@mparsons-ce
Copy link
Author

@Lomilar Have you had an opportunity to review this request and determine the effort necessary?

@Lomilar
Copy link
Member

Lomilar commented May 29, 2024

IdentifierValue requires a unique editor interface to define these objects and the three properties in them (similar to educationalAlignment).

Adding a version field that has a range of strings is quite straightforward.

@miledivovic
Copy link
Contributor

@sedula27 latestVersion, nextVersion, and previousVersion should now be available with CASS 1.5.65 on sandbox

@sedula27
Copy link

sedula27 commented Sep 4, 2024

@miledivovic I was able to add versions manually and via import, but was not able to export them

@miledivovic
Copy link
Contributor

@sedula27 should the versions be exported as arrays or strings?

@sedula27
Copy link

@miledivovic latest, next and previous version These require a valid CTID and are single values.

@sedula27
Copy link

Was able to verify versions export, import and manual entry on Sandbox. Hold off on Adding version Identifiers until this github issue is resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

5 participants