A bit about the process of developing a framework for resource development and re-use at UBC's Office of Learning Technology. Part of a presentation for ETUG 2010 in Victoria, BC.
2. Great content but not easy to find. Re-inventing instead of re-using. Sometimes need a taste not the whole enchilada. Parts not easily re-mixable. The Problem
3. Take apart the big pieces. Create sub-pages: tasters. Re-assemble subpages for different purposes using transclusion. Embed for presentation. The Plan
4. Content management: authoring/presentation. Dynamic page list: keeps track of the bits/subpages. Transclusion code: to pull the bits together. Embed code/page level re-publishing The Parts content management connectors content content
5. Trade-offs: imposed structure improves re-use but does it constrict editing? Opening up to serendipitous use - our structure may work for us but does it invite others in? Open editing vs. control over content - some may like the idea of new content being added and fed out to multiple sites - others not so much. Tensions/Questions?