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

When mirroring framework, make "Internal associations" link #1479

Open
jmarks opened this issue Jun 2, 2021 · 1 comment
Open

When mirroring framework, make "Internal associations" link #1479

jmarks opened this issue Jun 2, 2021 · 1 comment

Comments

@jmarks
Copy link
Member

jmarks commented Jun 2, 2021

When mirroring case.smarterbalanced.net, there are internal associations between the framework (e.g. the content spec links to the item specs at the target level). Also there are association from the source to items that are resident. In both cases the associations on the left column are not linked. They should be.

see and example here: https://opensalt.net/cftree/item/1127804

image

@jmarks jmarks assigned jmarks and roverwolf and unassigned jmarks Jun 2, 2021
@jmarks jmarks added this to the OpenSALT 3.1 milestone Jun 2, 2021
@jmarks jmarks changed the title WHen mirroring framework, make "Internal associations" link When mirroring framework, make "Internal associations" link Jun 2, 2021
@roverwolf
Copy link
Member

roverwolf commented Jun 2, 2021

The listed associations in question do not have "linkable" destinations.

This is actually caused by technically invalid data from the framework being mirrored.

https://case.smarterbalanced.org/cftree/item/118333 shows that those associations are to URNs which are not CASE CFItems nor CFDocuments (they are tags to AIR and DOK identifiers).

Selection_20210602T091733

The solution going forward is not obvious:

  • I'm assuming that throwing an error during mirroring (and not mirroring) is not wanted
  • Fetching the framework from OpenSALT.net currently returns those associations, but to filter them out would mean changing the data from what is being mirrored (so breaking the "mirror")
  • The UI does not break, but could possibly be made to look nicer for these non-valid URNs (but is it worth the effort for something that is not valid data)

@roverwolf roverwolf added Area - UI Priority 3 - Low Low priority and removed Priority 2 - Normal Normal priority labels Aug 31, 2021
@roverwolf roverwolf modified the milestones: OpenSALT 3.1, Backlog Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants