The Instructure Product Team is working on implementing a better solution to collect your feedback. Read Shiren's blog for more information.
Don't get me wrong: I love Commons! But imagine my surprise when I learned that linked pages weren't being included when sharing pages or modules to Commons.
Here's the scenario: I created a module consisting of pages that I share across different courses. Several of these pages contain links to sub-pages. The sub-pages do not appear anywhere else--just as a link in the primary page. For example, I create a page and in that page, I link to another course page--a sub-page. Why? The primary page provides context and direction for using the linked sub-pages.
When I share this module to Commons, however, only the primary pages are being copied into Commons. None of the linked sub-pages are copied.
When I include a linked PDF file in the primary page, however, the PDF file is part of the copy to Commons; no problem. But pages are more accessible than PDF documents, so I use pages.
So why are linked pages handled differently than linked PDF files?
If I use the Copy To feature on the module instead of sharing it to Commons, the module primary pages and sub-pages are copied to the destination course. No problem. But this means I need to repeat this step for each course, whereas if Commons worked as expected, I could copy the content into multiple courses at once. And using Copy To, I miss the central library feature that Commons is wonderful for.
So here's my idea: Please make sharing pages with linked pages to Commons work the same as sharing pages with linked PDF documents. I believe all linked or embedded content that is being shared at the top level should be part of the copy to Commons.
Cheers,
Colleen
To participate in the Instructure Community, you need to sign up or log in:
Sign In