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

[STEMED] Revised Course Asset Duplicate Accessibility for 2.2.22 #1729

Open
wants to merge 8 commits into
base: 2.2.22
Choose a base branch
from

Conversation

jessewoo
Copy link
Contributor

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

image
image
image
image
image
image

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

@jessewoo jessewoo self-assigned this Jul 31, 2024
@nkissebe
Copy link
Contributor

We need this against the dev branch

@jessewoo
Copy link
Contributor Author

even though STEMED is on 2.2.22? Sure I'll do that. I'll work on it next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants