This is an issue in the UI not the export.
When competencies are linked as "Skills Embodied" to competencies that were deleted from a another Collection or Competency Framework, the CaSS UI does not remove them from the UI, rather the UI shows the Competency Label and the property selectors shows the full URI. When a user goes to publish, they'll get errors and have to figure out which Skills Embodied to delete.
The CaSS UI needs to include the full URI for each of the Skill Embodied to help users identify what has to be deleted. The showing of only a Competency Label is a clue but it should be be used to make delete decisions. This will help people not to have to go back to the original spreadsheet and figure it out.
This scenario is applicable to any situation where the CaSS UI provides information about competencies, concepts or progression levels that are linked.
This is an issue in the UI not the export.
When competencies are linked as "Skills Embodied" to competencies that were deleted from a another Collection or Competency Framework, the CaSS UI does not remove them from the UI, rather the UI shows the Competency Label and the property selectors shows the full URI. When a user goes to publish, they'll get errors and have to figure out which Skills Embodied to delete.
The CaSS UI needs to include the full URI for each of the Skill Embodied to help users identify what has to be deleted. The showing of only a Competency Label is a clue but it should be be used to make delete decisions. This will help people not to have to go back to the original spreadsheet and figure it out.
This scenario is applicable to any situation where the CaSS UI provides information about competencies, concepts or progression levels that are linked.