-
Notifications
You must be signed in to change notification settings - Fork 34
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
Keep track of when public modules are copied. #2005
Comments
FrenjaminBanklin
added a commit
to FrenjaminBanklin/Obojobo
that referenced
this issue
Apr 6, 2023
…ons before rendering copy/preview buttons in a module's public page. Adds 'normal' and 'read-only' copy options to a module's public page. Replaces 'edit' button with 'synchronize' button in module dashboard for read-only modules. Adds a new dialog and relevant backend logic to automatically synchronize a read-only copied module with its original if any changes have been made.
FrenjaminBanklin
added a commit
to FrenjaminBanklin/Obojobo
that referenced
this issue
Apr 27, 2023
FrenjaminBanklin
added a commit
to FrenjaminBanklin/Obojobo
that referenced
this issue
Jul 21, 2023
FrenjaminBanklin
added a commit
to FrenjaminBanklin/Obojobo
that referenced
this issue
Aug 2, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there's no real way of knowing when somebody makes a copy of a module in the community collection. This may be useful to keep track of, and potentially down the road add a feature to potentially make it possible to overwrite a copy if updates are made to the community collection version of a module.Possible extra/alternate ending - make it so that copies of community collection modules are read-only. This would enable instructors to embed a copy of a community module that they haven't changed but will allow them to check assessment stats.It turns out metadata has been generated any time a module is copied that enables tracking down copies of modules, though this data isn't exposed anywhere outside of the database. I don't think it's super important to do so, but the ability to make read-only copies of modules that can be synced with the original at will might still be useful.
The text was updated successfully, but these errors were encountered: