Credential Engine would like to enable the use of an external identifier

[mparsons-ce]

When importing a framework, the requirement for CTID can be a burden for a user. Instead would like to enable the use of an external identifier.

The external identifier for a framework would have to be unique for the owning organization.
If a CTID is present, it would take precedence over the external identifier
OR should the latter be an error? That is one or the other must be provided.
On import the external id would be used to reference the proper existing framework.
On import a CTID would be generated (for a new framework).
The competencies would also use an external identifier, which just needs to be unique to the framework.
On upload of an existing framework, the existing competencies would have to be matched to the uploaded ones - as they could be aligned to other entities.

Related (#912 ) will be the ability to reference a related concept by an external identifier. OR actually as long as a CTID can be use, may be enough.

[woodkri]

Currently the user can use an id (URL) or a CTID in the CSV import.
Potential solution with external identifiers - generate UUID based on (organization + 'framework' + identifier + 'competency' + identifier) so they are unique and can be updated using the same external identifiers. Need to differentiate between the object types as we'll need to do something similar for concepts.

[Lomilar]

Two routes here:

1. CE has a "help me with GUIDs button" that fixes the import spreadsheet in various ways. (generates CTIDs from integer IDs, etc)
2. CaSS, when it notices there's no ID column that makes sense, uses the organization ID to build CTIDs.

[Lomilar]

@siuc-nate Please comment on the direction you'd prefer.

[siuc-nate]

Here are the two options I had in mind. I don't have a strong preference between them: