Update CASE frameworks using the Date Modified similar to the O*Net frameworks

[sedula27]

@gloverkari
similar to how we handle the ingest of the DOL competency frameworks to automatically re-import a CASE framework if it’s updated based on the date modified.

[gloverkari]

1EdTech has changed hosting procedures.
Use case: Client is no longer going to use the data existing on the old system and would like to move the data to the Credential Registry.

The purpose of the script from this ticket would be for updating existing (known) frameworks based on URIs.

[gloverkari]

How would the system know that the framework is from OpenSALT? Should it automatically be updated?

[gloverkari]

Example framework imported from OpenSALT.

https://cassproject.github.io/cass-editor/#/framework?frameworkId=https://opensalt.net/uri/c5fb0812-d7cb-11e8-824f-0242ac160002

[gloverkari]

More Details from Meeting Notes 1/10/2024:

Script is ready - checks on frameworks that have already been imported. Need to know where to get them. It’s using the date modified. Run with a nightly service to look for data modified.
Can either look for frameworks from a specific location or an OpenSalt endpoint, for example https://opensalt.net/ims/case/v1p0/CFDocuments/?limit=5.
The system would need to know when a CASE / OpenSalt URI is being imported to CaSS and CaSS would have to retain the URI from the import. This does not exist! Bottom line question? How would CaSS know the framework was imported from OpenSalt and has a CASE URI.
Workflow? Does the customer want it to be current?

Use Case - I need to transfer frameworks from CASE/Open Salt to Credential Registry. I will no longer maintain those frameworks in CASE/OpenSalt.
The CASE/OpenSalt policy will maintain the framework URIs.
The CASE/OpenSalt repo will NOT maintain URIs.

[winonadeb]

Is this still a blocker if it has been removed from Active Development?