project: MoodleNet
summary: Users should be able to add a licence to resources they add to collections
description: Users should be able to add a licence to resources they add to collections. We should look to Wikimedia Commons as an example: Also see

1.summary: Complete missing screens to create clickable prototype for testing of new UI
description: Weve got some great screens so far to show the new, more conversational MoodleNet UI. What were missing are just a couple of tweaks so that we can turn it into a clickable prototype. ------ Heres what were missing: ------ User flow (-completed screens-) -Login page- -Login page with user name and password entered- -Discover page- -Community page (with Collections tab shown)- -Collections page (showing Add a link and Upload a file)- -Collections page (enter a URL - empty box)- -Collections page (enter a URL - completed)- -Collections page (resource previewed and tag box empty)- -Collections page (resource previewed and tag box completed)- Collections page (newly-added resource shown in resources stream) -Profile (showing newly-added resource in Activities)- -Profile (showing Joined communities tab)- -Profile (showing Followed collections tab)- -Profile (showing Likes)- -Add Create a new community to relevant pages-
2.summary: Decide on interplay between Communities and Collections in UI 2.1
description: Ensuring users understand whats happening when they go from a Community into a Collection (and back again) is key to MoodleNets success. Lets think about options here. Currently UI 2.1 prototypes:

Below is an instruction that describes a task, paired with an input that provides an epic with this format: 
"project": "Name of the project" 
"summary": "Summary of the epic user story" 
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Users should be able to add a licence to resources they add to collections
description: Users should be able to add a licence to resources they add to collections. We should look to Wikimedia Commons as an example: Also see

### Response:
1.summary: Complete missing screens to create clickable prototype for testing of new UI
description: Weve got some great screens so far to show the new, more conversational MoodleNet UI. What were missing are just a couple of tweaks so that we can turn it into a clickable prototype. ------ Heres what were missing: ------ User flow (-completed screens-) -Login page- -Login page with user name and password entered- -Discover page- -Community page (with Collections tab shown)- -Collections page (showing Add a link and Upload a file)- -Collections page (enter a URL - empty box)- -Collections page (enter a URL - completed)- -Collections page (resource previewed and tag box empty)- -Collections page (resource previewed and tag box completed)- Collections page (newly-added resource shown in resources stream) -Profile (showing newly-added resource in Activities)- -Profile (showing Joined communities tab)- -Profile (showing Followed collections tab)- -Profile (showing Likes)- -Add Create a new community to relevant pages-
2.summary: Decide on interplay between Communities and Collections in UI 2.1
description: Ensuring users understand whats happening when they go from a Community into a Collection (and back again) is key to MoodleNets success. Lets think about options here. Currently UI 2.1 prototypes:
