CTDL-ASN import succeeds but competencies don't link to framework (shows "0 competencies ready to edit")

[nphoenix]

Problem

CTDL-ASN files import without error but competencies are not linked to the framework. Import shows "Import success, 0 competencies ready to edit" regardless of how many competencies are in the file.

Prerequisites

• Requires fix from CTDL-ASN files fail detection with context arrays #1408 (detection must work first)
• Related to long-standing CTDL-ASN import issues

Steps to Reproduce

1. Import CTDL-ASN file (see attached test files)
2. Detection works: "1 Framework and X Competencies Detected" ✅
3. Click "Process Files" to import
4. Import succeeds: "Import success, 0 competencies ready to edit" ⚠️
5. Check framework in Frameworks list
6. Framework shows "Items: 0" ❌

Expected Behavior

• Framework should show correct competency count
• Competencies should be linked and visible in framework
• Opening framework should display all competencies

Actual Behavior

• Import completes without error ✅
• Framework is created ✅
• But shows "Items: 0" ❌
• Opening framework shows empty (no competencies) ❌
• All competencies are missing despite successful import

Affected File Sizes

Tested with multiple file sizes - bug affects ALL imports:

• ✅ 2 competencies: Imports, 0 shown
• ✅ 20 competencies: Imports, 0 shown
• ✅ 50 competencies: Imports, 0 shown

Root Cause (Suspected)

Import execution may be:

1. Not creating competency records in database
2. Not creating framework ↔ competency relationships
3. Creating competencies but not linking them via isPartOf/hasTopChild
4. Silently failing during competency processing

Test Cases

File 1: SAMPLE-IMPORT-BUG-DEMO.jsonld (2 competencies)

• Minimal test case
• All HTTP URLs, standard structure
• Result: ✅ Imports, ❌ 0 competencies shown

File 2: SAMPLE-20-COMPETENCIES.jsonld (20 competencies)

• Medium-sized framework
• All HTTP URLs, standard structure
• Result: ✅ Imports, ❌ 0 competencies shown

File 3: SAMPLE-50-COMPETENCIES.jsonld (50 competencies)

• Larger framework
• All HTTP URLs, standard structure
• Result: ✅ Imports, ❌ 0 competencies shown

All files demonstrate the same issue: import succeeds but competencies are lost.

Impact

• CRITICAL: Makes CTDL-ASN import completely non-functional
• Even with detection fix (CTDL-ASN files fail detection with context arrays #1408), import produces empty frameworks
• Prevents any CTDL-ASN interoperability
• Affects all framework sizes (2 to 50+ competencies tested)

Suggested Investigation

1. Find import execution function (likely importCtdlAsnJsonLd() or similar in backend)
2. Add logging to see if competencies are being processed
3. Check if competency records are created in database
4. Verify framework-competency relationships are established
5. Check for silent errors during competency import

---

Note: This is separate from #1408 (detection). Detection works, but import execution loses all competencies.

Additional Note: Files with 74+ competencies fail with a different error ("URL does not begin with http") - that will be reported separately.

[SAMPLE-IMPORT-BUG-DEMO.jsonld.txt](https://github.com/user-attachments/files/24340575/SAMPLE-IMPORT-BUG-DEMO.jsonld.txt)
[SAMPLE-50-COMPETENCIES.jsonld.txt](https://github.com/user-attachments/files/24340574/SAMPLE-50-COMPETENCIES.jsonld.txt)
[SAMPLE-20-COMPETENCIES.jsonld.txt](https://github.com/user-attachments/files/24340573/SAMPLE-20-COMPETENCIES.jsonld.txt)

[jeannekitchens]

@nphoenix Credential Engine engineering team is hoping to get more information about your local CaSS instance. Also @sedula27 is going to try to replicate both issues. Tagging @Lomilar and @miledivovic here in case they can provide some helpful information here and on #1408

[nphoenix]

ICICLE_Learning_Engineering_Competency_Framework_CTDL-ASN_2025-12-26.zip I am iterating on a Sharable Competency Definition (SCD) tool and believe my export to CTDL-ASN format is valid. Before the submitted edits i was not able to import this file.

[sedula27]

@nphoenix I reviewed your file and it will need a few corrections for the import to succeed

1. @context must be a string, not an array/collection.

2. @id values must be Credential Registry URIs, This applies both at the top-level @id and for each object inside @graph.

   • https://credentialengineregistry.org/resources/ce-guid

3. use ceasn namespace for ASN properties, The framework and competency objects should use the ceasn: namespace, including: @type (e.g., ceasn:CompetencyFramework, ceasn:Competency) and common fields like name, description, dateCreated, dateModified, etc.

4. A few properties are invalid in this context

   • ceterms:version: use ceterms:versionCode
   • schema:keywords: not supported
   • ceterms:proficiencyLevel: not supported
   • ceterms:lifecycle: not supported
   • ceterms:contextTag: not supported
   • ceterms:status: not supported
   • ceasn:source : This should be at the framework level and needs to be an URI

5. Required properties:

   • ceasn:Publisher: The framework should include ceasn:publisher set to the publisher’s Credential Registry URI.
   • Add ceasn:isPartOf on each competency pointing to the framework @id (Credential Registry URI).
   • For ceasn:hasTopChild, the list should contain the Credential Registry URIs of the top-level competencies.

6. ceterms:publicationStatus should be an URI not a string

Reference links:

Minimum Data Policy: https://credreg.net/registry/policy#competencyframework_competency

CompetencyFramework terms: https://credreg.net/ctdlasn/terms/publisher#CompetencyFramework

Competency terms: https://credreg.net/ctdlasn/terms/Competency#Competency

ExampleJsonFile.json

[nphoenix]

Update: Issue Resolved on My End

@sedula27 Thank you so much for the detailed feedback! It was incredibly helpful.

What I learned:
Your review identified that my TLA Toolbox (tlatoolbox.com) CTDL-ASN export had compliance issues. While the @context array format appeared spec-compliant to me, your feedback about the other issues (namespace, missing properties, invalid properties) was spot-on.

What I did:
I updated TLA Toolbox's CTDL-ASN export to address all the compliance issues you identified:

✅ Changed @context to single string
✅ Switched from ceterms: to ceasn: namespace
✅ Added ceasn:publisher to framework
✅ Added ceasn:isPartOf to each competency
✅ Fixed publicationStatus to URI format
✅ Removed unsupported properties
✅ Switched to @graph structure

Result:
The updated export now imports successfully into CASS (tested on original version without PR #1409). The compliance fixes resolved my immediate issue.

About PR #1409:
I'll leave it to your team to decide whether to merge PR #1409. It may still be valuable for handling legacy or non-compliant CTDL-ASN files from other tools, but my specific use case is now resolved with compliant exports.

Thanks again for taking the time to review the file and provide such clear guidance! 🙏

EDITABLE_-_ICICLE_Learning_Engineering_Competency_Framework_CTDL-ASN_2026-02-09.zip

[mparsons-ce]

@miledivovic @sedula27
Only remaining action is determine if the above PR will be merged into CaSS