[STEMED] Revised Course Asset Duplicate Accessibility for 2.2.22 #1729
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Source JIRA card(s) and hubzero ticket(s)
https://sdx-sdsc.atlassian.net/browse/STEMED-21
https://stemedhub.org/support/ticket/1051
Brief summary of the issue
Inside a course offering asset group, you can duplicate an asset. This is working fine, but you can only access this asset inside the same course offering unit it resides in. It seems like it should be accessible to add to another course offering unit by it's asset ID, but it's not. This feature will give an admin the ability to duplicate an asset group into any other course offering.
Brief summary of the fix
Had to create an entirely new form, new API with javascript to grab updated course data, and had to create new methods to duplicate assets. This new feature was created from branching off of 2.2.22, which is currently the old CMS version that stemedhub is running.
Screenshots showing the featured solution
Brief summary of your testing
Tried it on https://stage.stemedhub.org/. Will ask client to test on stage when it is ready. We want the client to try it out on stage before it is released.
Do the change needs to be hotfixed to any production hubs before a normal core rollout
No, not at this moment. But we can ask client whether she wants it out sooner than later.
Double check someone is assigned to review the ticket
Yes - Nick and David