The document discusses how a library shares development and maintenance of technical and public services. It describes how the library maintains databases, ebooks, print books, and websites. Content developed on template guides can be mapped to FAQ posts on multiple platforms for discoverability. Newspaper boxes created on a template guide were copied and pasted into corresponding FAQ posts to dynamically map the content. Link assets were then mapped from the template guide to a newspapers guide to centrally manage all newspaper content from a single page.

1. RB

2. RB

3. RB

4. JM
Technical and
Public Services
share development
and maintenance.
Catalog
widgets
.
Reference
books.
Discover
widgets.
Video
widgets.

5. JM
Database assets
provide greater
control over access,
description,
filtering, mapping,
and presentation.

6. FAQ posts streamline support and
can be deployed anywhere.
JM

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. 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. 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. RB

11. We added subject and
resource-type filtered
A-Z List widgets to
each Reference
Resources guide.

12. JM
We added a link to
the FAQ in the
database asset’s
description field.

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. JM
Once each newspaper
box was ready, we copied
the embed code for the
box via the “Edit Box”
tab.

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. JM
Now the content of
the newspaper box is
dynamically mapped
to the FAQ post.
Updates are handled
centrally from the
TEMPLATE guide.

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. 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. 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. RB