Skip to content

(WIP) Randomized selection from content libraries - Do not merge, for internal review - #2

Closed
bradenmacdonald wants to merge 5 commits into
studio-library-viewfrom
studio-library-randomization
Closed

(WIP) Randomized selection from content libraries - Do not merge, for internal review#2
bradenmacdonald wants to merge 5 commits into
studio-library-viewfrom
studio-library-randomization

Conversation

@bradenmacdonald

Copy link
Copy Markdown
Member

This is a continuation of the prototype found in #1, extended to implement SOL-18 "As a content author, I am able to select a number of random content blocks that would be displayed in a LibraryContent block."

Testing instructions:

  1. Check out this branch on a vanilla devstack (not solutions), and do paver install_python_prereqs and paver update_db
  2. As 'edxapp' user, edit ~/cms.env.json and add "ENABLE_CONTENT_LIBRARIES": true to the FEATURES object.
  3. Edit ~/cms.auth.json. Go to MODULESTORE > default > OPTIONS > stores - it should contain two or three entries. Re-order the entries so that the store with "NAME": "split", comes first in the stores list. (This makes split the default modulestore for any new courses.)
  4. Start paver devstack studio and go to localhost:8001 in your browser.
  5. Log in as staff, and create a new course.
  6. Edit the new course in studio. Go to Content > Content Library. Click the link to create the library, then go back and refresh the page to see the new library.
  7. Add some content to the library. (Graded problems not tested at this point - stick to content like HTML blocks rather than problems).
  8. Go to Settings > Advanced Settings and add "library_content" to advanced_modules.
  9. Go to Content > Outline. Create a new section and subsection, then edit it. Click "Advanced" and add a new "library_content" block.
  10. Once the block is added, click "Edit" to edit its settings. Most are explained on the settings editor. For the "Library" setting, you must click "Add", then paste the CourseLocator of your library. This looks like course-v1:ProblemX+PR0B+2014+branch@library. (It's in the URL when you go to Content > Content Library, though the URL may not show the +branch@library part, so make sure to add that). Hit Save.
  11. Click "Update now with latest components from the library".
  12. Optional: Click "View >" to preview all the blocks found in the library.
  13. Hit "Publish", then start up the LMS and go to localhost:8000. Browse into the course, and you should see that the block is replaced by random blocks from the library. To test the randomization, click the lowest "STAFF DEBUG INFO" link underneath the module, then click "Delete Student State", then refresh the page.

@Kelketek

Copy link
Copy Markdown
Member

This checks out. I was able to get it running per the instructions and it works as advertised.

I did notice an oddity that isn't mentioned in the instructions-- When first visiting the Content Library link, I get a very basic unstyled response with a statement saying there is no content library, and giving me a link to create one. When I click the link, the result is JSON that loads in the browser. Is that expected?

The code itself doesn't raise any particular red flags for me. I'm good with this, if that previous note is expected and shall be resolved down the line as part of the project at large.

@bradenmacdonald

Copy link
Copy Markdown
Member Author

@Kelketek Ah, right. I forgot to mention that in the instructions. Yes, that is the expected behaviour. It's unstyled and simple because this is just a proof of concept prototype. Once we have an approved design, and a UX plan, we will clean all those things up.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just a prototype so very minor at this point, but it could be worth moving the code selecting the blocks to its own method.

@bradenmacdonald

Copy link
Copy Markdown
Member Author

Superseded by #5.

@bradenmacdonald
bradenmacdonald deleted the studio-library-randomization branch October 29, 2014 02:37
e-kolpakov pushed a commit that referenced this pull request Jan 12, 2015
…2.0-v2

Upgrade: Font Awesome 4.2.0 - Take #2
bradenmacdonald added a commit that referenced this pull request Oct 8, 2015
itsjeyd pushed a commit that referenced this pull request Dec 23, 2015
itsjeyd pushed a commit that referenced this pull request Dec 23, 2015
…dback-update-2

Hash Update #2: Diagnostic-Feedback
omarkhan pushed a commit that referenced this pull request Mar 25, 2016
Create the security fix #2 for the RC 2016-03-22
pomegranited pushed a commit that referenced this pull request Jul 25, 2018
pkulkark pushed a commit that referenced this pull request Jun 26, 2019
Syncing fork to the original repository
lgp171188 pushed a commit that referenced this pull request Sep 7, 2019
� This is the 1st commit message:

BOM-149
python3 tests failures.

� This is the commit message #2:

BOM-149
python3 tests failures.
pomegranited pushed a commit that referenced this pull request Oct 30, 2019
bradenmacdonald pushed a commit that referenced this pull request Feb 28, 2020
…guration_siteconfiguration_values_2.1

Rename values in SiteConfiguration (2/3) attempt #2
bradenmacdonald pushed a commit that referenced this pull request Feb 28, 2020
…me_site_configuration_siteconfiguration_values_2.1

Revert "Rename values in SiteConfiguration (2/3) attempt #2"
tartansandal pushed a commit that referenced this pull request Mar 6, 2020
This reverts commit e6f58b6.

This is our third (3rd!) attempt to deploy stage 2 of this column rename.
tartansandal pushed a commit that referenced this pull request Mar 6, 2020
…te_configuration_siteconfiguration_values_2.3

Revert "Revert "Rename values in SiteConfiguration (2/3) attempt #2""  (attempt #3)
Agrendalath added a commit that referenced this pull request Jun 9, 2020
xitij2000 added a commit that referenced this pull request Nov 10, 2020
Fix for setting provider to none
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.

3 participants