Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
RB
RB
RB
JM
Technical and
Public Services
share development
and maintenance.
Catalog
widgets
.
Reference
books.
Discover
widgets.
V...
JM
Database assets
provide greater
control over access,
description,
filtering, mapping,
and presentation.
FAQ posts streamline support and
can be deployed anywhere.
JM
JM
Technical Services
maintains databases and
ebooks, Public Services
maintains print books and
websites.
ebooks are curat...
Database descriptions are
support FAQ posts on
LibAnswers.
JM
Posts play double-duty as
descriptions and support articles
...
JM
Content developed on TEMPLATE
guide and mapped to FAQ post.
Content can be managed and re-
purposed from LibGuides, and...
RB
We added subject and
resource-type filtered
A-Z List widgets to
each Reference
Resources guide.
JM
We added a link to
the FAQ in the
database asset’s
description field.
JM
On the TEMPLATE guide,
we created one box for
each newspaper we
wanted to include on the
Newspapers guide.
In each box,...
JM
Once each newspaper
box was ready, we copied
the embed code for the
box via the “Edit Box”
tab.
JM
Next, we pasted the
widget code into the
“Source View” of a
corresponding FAQ post.
…/springshare.common.min.css
and fo...
JM
Now the content of
the newspaper box is
dynamically mapped
to the FAQ post.
Updates are handled
centrally from the
TEMP...
JM
Once all the newspaper
boxes were mapped to
the FAQ articles, we
created a link asset to
each FAQ article on the
same T...
JM
We then mapped these link
assets to the Newspaper guide.
Using mapped link assets pointing
to the FAQ posts allows us t...
JM
Map the box.
Map the
assets in the
box.
Map the link
assets to the
posts.
Link FAQ posts to
provide consistent
content ...
RB
Simple Springshare Mashups: Cross-Platform Strategies for Repurposing Digital Content for Multiple Audiences
Upcoming SlideShare
Loading in …5
×

Simple Springshare Mashups: Cross-Platform Strategies for Repurposing Digital Content for Multiple Audiences

256 views

Published on

Presenter(s): Ruth Baker, Jeffrey Mortimore.
Presenters offered simple strategies for content creation and management that maximize opportunities for repurposing content across delivery platforms while keeping maintenance to a minimum. Strategies for content creation include
naming, description, and chunking-that support repurposing of content for multiple audiences and support contexts. The presentation also covers strategies for dynamically mapping content across platforms that eliminates any need to monitor platform content separately. While this session will focus on LibGuides and LibAnswers, the content creation techniques discussed are applicable to any content management system that supports dynamic content mapping and/or external widget creation.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Simple Springshare Mashups: Cross-Platform Strategies for Repurposing Digital Content for Multiple Audiences

  1. 1. RB
  2. 2. RB
  3. 3. RB
  4. 4. JM Technical and Public Services share development and maintenance. Catalog widgets . Reference books. Discover widgets. Video widgets.
  5. 5. JM Database assets provide greater control over access, description, filtering, mapping, and presentation.
  6. 6. FAQ posts streamline support and can be deployed anywhere. JM
  7. 7. JM Technical Services maintains databases and ebooks, Public Services maintains print books and websites. ebooks are curated by Technical Services and can be mapped to any guide via shared TEMPLATE guide.
  8. 8. Database descriptions are support FAQ posts on LibAnswers. JM Posts play double-duty as descriptions and support articles that can be shared via email and chat reference.
  9. 9. JM Content developed on TEMPLATE guide and mapped to FAQ post. Content can be managed and re- purposed from LibGuides, and is discoverable on both platforms. Linking to “Quick Start Guides” allows for more title density with less clutter.
  10. 10. RB
  11. 11. We added subject and resource-type filtered A-Z List widgets to each Reference Resources guide.
  12. 12. JM We added a link to the FAQ in the database asset’s description field.
  13. 13. JM On the TEMPLATE guide, we created one box for each newspaper we wanted to include on the Newspapers guide. In each box, we included links to our print and electronic holdings, etc.
  14. 14. JM Once each newspaper box was ready, we copied the embed code for the box via the “Edit Box” tab.
  15. 15. JM Next, we pasted the widget code into the “Source View” of a corresponding FAQ post. …/springshare.common.min.css and following only to ensure proper display in the FAQ post.
  16. 16. JM Now the content of the newspaper box is dynamically mapped to the FAQ post. Updates are handled centrally from the TEMPLATE guide.
  17. 17. JM Once all the newspaper boxes were mapped to the FAQ articles, we created a link asset to each FAQ article on the same TEMPLATE page as the newspaper boxes.
  18. 18. JM We then mapped these link assets to the Newspaper guide. Using mapped link assets pointing to the FAQ posts allows us to manage all content on the Newspaper guide from the TEMPLATE guide.
  19. 19. JM Map the box. Map the assets in the box. Map the link assets to the posts. Link FAQ posts to provide consistent content in multiple contexts. All content maintained from a single page.
  20. 20. RB

×