Planet Cataloging

January 19, 2017

OCLC Next

Share your library space pictures!

spotlight banner 2

Since last October, libraries have been sharing pictures of their spaces with us for us to pass along on Twitter and Facebook. We’ve gotten some great pictures—many thanks to everyone who has been contributing. We’ve seen folks in the community sharing and liking these so we wanted to put them in one place for you to see.


Beautiful pictures of libraries! Do you have a #LibrarySpaces photo to share?
Click To Tweet


If you’d like to add your picture to our collection and maybe see it featured in the future, send a photo (minimum size 1920 x 1080; JPG, please) to photos@oclc.org. Please also include a brief caption with the name of the library, city and country. By submitting photos this way, you confirm that you own the image rights and agree to OCLC’s use of them in digital and print marketing and communications.

So many great library spaces, so many great pictures. Thanks again, and we look forward to seeing yours!

 

14_ntu

Koo Chen-Fu Memorial Library at NTU College of Social Sciences in Taipei, Taiwan

01_defiance

Pilgrim Library at Defiance College in Defiance, Ohio, USA

 

02_amistad

Amistad Research Center at Tulane University in New Orleans, Louisiana, USA

 

03_jacksonville

Houston Cole Library at Jacksonville State University in Jacksonville, Alabama, USA

 

04_deakin

Deakin University Library in Geelong Waurn Ponds, Australia

 

05_krupp

Douglas and Judith Krupp Library at Bryant University in Smithfield, Rhode Island, USA

 

06_moraine

Moraine Valley Community College Library in Palos Hills, Illinois, USA

 

15_sheffield

University of Sheffield Library in Sheffield, England, UK

 

07_birmingham

Birmingham Public Library in Birmingham, Alabama, USA

 

08_bowling green

Bowling Green State University Libraries in Bowling Green, Ohio, USA

 

09_clarion

Rena M. Carlson Library at Clarion University in Clarion, Pennsylvania, USA

 

10_dayton

Roesch Library at the University of Dayton, Dayton, Ohio, USA

 

11_howell

Howell Carnegie District Library in Howell, Michigan, USA

 

12_mt-holyoke

Mount Holyoke College Reading Room in South Hadley, Massachusetts, USA

 

13_oregon

Oregon State Library in Salem, Oregon, USA

The post Share your library space pictures! appeared first on OCLC Next.

by Andy Havens at January 19, 2017 09:14 PM

January 17, 2017

025.431: The Dewey blog

Roses, garlic, and cherries: Angiosperms outside botany

Previous blog posts have described the extensive revision of 583-584 Angiosperms, most recently the post entitled "New and improved."

What about treatment of angiosperms outside botany—are there ripple effects?  Yes, wherever a number is built using numbers from 583-584. Let’s consider roses, garlic, and cherries as examples.

At 583.644 Rosa is the history note (displayed in WebDewey in the History box):

Rosa (roses) formerly located in 583.734

2016-11-16, Edition 23

A quick check in the Relative Index shows other numbers ending with the same last digits as 583.644:

Roses 635.933644

Roses—arts T3C—3643644

Roses—botany 583.644

Roses—floriculture 635.933644

That is a clue that the other numbers with the same last digits were built by adding numbers from 583.644 to a base number—in this case the base numbers being T3C—364 and 635.93.

When we check in Table 3C, we find an add note that says to add numbers from 582-588 to base number T3C—364:

T3C—364 Plants

Add to base number T3C—364 the numbers following 58 in 582-588, e.g., trees T3C—364216, roses T3C—3643644

When we check the floriculture schedule, under 635.9 Flowers and ornamental plants, we find a span for taxonomic groupings with an add note that says to add numbers from 583-588 to base number 635.93:

635.933-635.938 Taxonomic groupings

Add to base number 635.93 the numbers following 58 in 583-588, e.g., cacti 635.933885, roses 635.933644, orchids 635.93472; however, for everlastings, see 635.973 for comprehensive works on dicotyledons, see 635.9 for taxonomic groupings of trees, see 635.9773-635.9775

Will we find the same pattern for garlic? Garlic is named in the second including note at 584.78 Amaryllidaceae:

Including African lilies, atamasco lilies, chives, daffodils, garlic, jonquils, leeks, narcissus, onions, shallots, spider lilies

Garlic is also named in the second history note (displayed in WebDewey in the History box):

Allioideae; African lilies, chives, garlics, leeks, onions, shallots all formerly located in 584.33

2016-11-16, Edition 23

A quick check in the Relative Index, however, shows only one built number ending with the same last digits as 584.78:

Garlic 641.3526

Garlic—botany 584.78

Garlic—cooking 641.6526

Garlic—food 641.3526

Garlic—garden crop 635.26

Garlic—pharmacology 615.32478

When we check the pharmacology schedule, under 615.3 Organic drugs, we find a span with an add note that says to add numbers from 583-587 to base number 615.32:

615.323-615.327 Drugs derived from specific plants

Add to base number 615.32 the numbers following 58 in 583-587, e.g., belladonna 615.3239593

Hence the pharmacology number for garlic has been changed because of the change to the botany schedule.

But what about the other numbers? Several end with the same digits 526, and the shortest is 635.26; maybe the other numbers ending with 526 were built with numbers from 635.26? In the garden crop schedule, under 635.2 Edible tubers and bulbs, is a non-built number with garlic in the including note:

635.26 Alliaceous plants

Including chives, garlic, leeks, shallots

Because 635.26 is not built with numbers from the botany schedule, it is not affected by changes to the botany schedule.

Two other numbers end with the same last digits as 635.26, a clue that they are built by adding digits from 635.26 to a base number:

Garlic—cooking 641.6526

Garlic—food 641.3526

When we check in the cooking schedule, under 641.6 Cooking specific materials, we find a span with an add note that says to add numbers from 633-637 to base number 641.6:

641.63-641.67 Cooking food derived from plant crops and domesticated animals

Add to base number 641.6 the numbers following 63 in 633-637, e.g., legumes 641.6565 (not 641.633), garden legumes 641.6565, meat 641.66, chicken meat 641.665; however, for ices, sherbet, sorbet, see 641.863

Similarly, when we check under 641.3 Food, we find a span with an add note that says to add numbers from 633-635 to base number 641.3:

641.33-641.35 Specific food from plant crops

Add to base number 641.3 the numbers following 63 in 633-635, e.g., field legumes 641.3565

Hence the numbers for cooking garlic and for garlic as a food are unaffected by changes to the botany schedule.  

In general, it is hard to predict what will be changed and what will stay the same; you should always check.  However, in the 630s there is a general pattern: numbers for specific plants as a food are not built with botany numbers and thus are not changed, while numbers for ornamentals (635.9) are built with botany numbers and are affected by changes to the botany schedule.  Cherries can illustrate this point. Cherries are named in the second including note at 583.642 Rosaceae:

Including almonds, apples, apricots, blackberries, cane fruits, cherries, chokeberries, cinquefoils, dewberries, drupaceous fruits, fire thorns, hawthorns, juneberries, loquats, medlars, mountain ashes, peaches, pears, plums, pomaceous fruits, pyracanthas, quinces, raspberries, rowan trees, serviceberries, spireas, stone fruits, strawberries

Cherries are also named in the history note (displayed in WebDewey in the History box):

Rosaceae (rose family), Rubus; almonds, apples, apricots, blackberries, cane fruits, cherries, chokeberries, cinquefoils, dewberries, hawthorns, loquat, medlar, mountain ashes, peaches, pears, plums, pomaceous fruits, pyracanthas (fire thorns), quince, raspberries, serviceberries, spireas, stone fruits (drupaceous fruits), strawberries all formerly located in 583.73

2016-11-16, Edition 23

A quick check in the Relative Index shows only one built number ending with the same last digits as 583.642:

Cherries 641.3423

Cherries—agricultural economics 338.17423

Cherries—botany 583.642

Cherries—commercial processing 664.80423

Cherries—cooking 641.6423

Cherries—food 641.3423

Cherries—orchard crop 634.23

Cherries—ornamental arboriculture 635.9773642

When we check under 635.977 Trees (a subdivision of 635.97 Other groupings of ornamental plants), we find a span for taxonomic groupings with an add note that says to add numbers from 583-585 to base number 635.977:

635.9773-635.9775 Taxonomic groupings

Add to base number 635.977 the numbers following 58 in 583-585, e.g., elms 635.9773648; however, for comprehensive works on dicotyledonous trees, see 635.977

But what about the other numbers? In the orchard crop schedule, under 634.2 Stone fruits, is a non-built number for cherries:

634.23 Cherries

Because 634.23 is not built with numbers from the botany schedule, it is not affected by changes to the botany schedule.  When we check under 338.1 Agriculture to see how the agricultural economics number for cherries (338.17423) is built, we find a span with an add note that says to add numbers from 633-636 to base number 338.17:

338.173-338.176 Products of culture of plants, of domestic mammals, of domestic birds

Add to base number 338.17 the numbers following 63 in 633-636, e.g., rice or seed rice 338.17318, forestry 338.1749, forest products 338.17498; however, for supply of timber in nature, see 333.7511; for demand for timber, see 333.7512

When we check under 664 Food technology to see how the commercial processing number for cherries (664.80423) is built, we find an add note that says to add numbers from 634.1-634.8 to base number 664.804:

664.804 Specific fruits and groups of fruits

Add to base number 664.804 the numbers following 634 in 634.1-634.8, e.g., citrus fruits 664.804304, nuts 664.8045

The cooking number (641.6423) and food number (641.3423) for cherries are built according to the same add notes as the cooking and food numbers for garlic, but adding numbers from 634.23.

When you look at a built-number record where the number has been changed because of a change to the botany number, you don’t find a history note giving the previous number.  You can, however, figure out what the old built number would have been by checking in the botany record to find the old botany number that would have been used to build it.

Discipline Old DDC for roses New DDC for roses
Botany 583.734 583.644
Floriculture 635.933734 635.933644

 

Discipline Old DDC for garlic New DDC for garlic
Botany     584.33 584.78
Pharmacology 615.32433 615.32478

 

Discipline Old DDC for cherries  New DDC for cherries
Botany 583.73 583.642
Ornamental arboriculture 635.977373 635.9773642

by Juli at January 17, 2017 08:58 PM

Terry's Worklog

MarcEdit’s new Logging Features

Over the years, I’ve periodically gotten requests for a much more robust logger in MarcEdit.  Currently, when the tool performs a global change, it reports the number of changes made to the user.  However, a handful of folks have been wanting much more.  Ideally, they’d like to have a log of every change the application makes, which is hard because the program isn’t built that way.  I provided the following explanation to the MarcEdit list last week.

**************************************

The question that has come up a number of times since posting notes about the logger is questions about granularity.  There has been a desire to have the tool provide additional information (about the records), more information around change context, and also wondering if this will lead to a preview mode.  I think other folks wondered why this process has taken so long to develop.  Well, it stems from decisions I make around the development.  MarcEdit’s application structure can be summed up by the picture below:

img-110105911-0001

In developing MarcEdit, I have made a number of very deliberate decisions, and one of those is that no one component knows what the other one does.  As you can see in this picture, the application parts of MarcEdit don’t actually talk directly to the system components.  They are referenced through a messenger, which handles all interactions between the application and the system objects.  However, the same is true of communication between the system objects themselves.  The editing library, for example, knows nothing about MARC, validation, etc. – it only knows how to parse MarcEdit’s internal file format.  Likewise, the MARC library doesn’t know anything about validation, MARC21, or linked data.  Those parts live elsewhere.  The benefit of this approach is that I can develop each component independent of the other, and avoid breaking changes because all communication runs through the messenger.  This gives me a lot of flexibility and helps to enforce MarcEdit’s agnostic view of library data.  It’s also how I’ve been able to start including support for linked data components – as far as the tool is concerned, it’s just another format to be messaged.

Of course, the challenge with an approach like this then, is that most of MarcEdit’s functions don’t have a concept of a record.  Most functions, for reasons of performance, process data much like an XML sax processor.  Fields for edit raise events to denote areas of processing, as do errors, which then push the application into a rescue mode.  While this approach allows the tool to process data very quickly, and essentially remove size restrictions for data processing – it introduces issues if, for example, I want to expose a log of the underlying changes.  Logs exist – I use them in my debugging, but they exist on a component level, and they are not attached to any particular process.  I use messaging identifiers to determine what data I want to evaluate – but these logs are not meant to record a processing history, but rather, record component actions.  They can be muddled, but they give me exactly what I need when problems arise.  The challenge with developing logging for actual users, is that they would likely want actions associated with records.  So, to do that, I’ve added an event handler in the messaging layer.  This handles all interaction with the logging subsystem and essentially tracks the internal messaging identifier and assembles data.  This means that the logger still doesn’t have a good concept of what a record is, but the messenger does, and can act as a translator.

Anyway – this is how I’ll be providing logging.  It will also let me slowly expand the logging beyond the core editing functions if there is interest.  It is also how I’ll be able to build services around the log file – to provide parsing and log enhancement, for users that want to add record specific information to a log file, that goes beyond the simple record number identifier that will be used to track changes.  This would make log files more permanent (if for example the log was enhanced with a local identifier), but due to the way MarcEdit is designed, and the general lack of a standard control number across all MARC formats (in merging for example, merging on the 001 trips checks of 9 other fields that all could store associated control data), it is my belief that providing ways to enhance the log file after run, while an extra step, will allow me the most flexibility to potentially make greater user of the processing log in the future.  It also enables me to continue to keep MARCisms out of the processing library – and focus only on handling data edits.

**********************************************

So that’s pretty much the work in a nut shell.  So what do you get.  Well, once you turn it on, you get lots of stuff and a few new tools.  So, let’s walk through them.

Turning on Logging:

Since Logging only captures changes made within the MarcEditor, you find the logging settings in the MarcEditor Preferences Tab:

image

Once enabled, the tool will generate a new session in the Log folder each time the Editor starts a new Session.  With the logs, come log management.  From within the MarcEditor or the Main window, you find the following:

Main Window:

image

From the MarcEditor, you’ll find in Reports:

image

Functionally, both areas provide the same functionality, but the MarcEditor reports entry is scoped to the current session logfile and current record file loaded into the Editor (if one is loaded).  To manage old sessions, use the entry on the Main Window.

Advanced Log Management

To of the use cases that were laid out for me were the need to be able to enhance logs and the ability to extract only the modified records from a large file.  So, I’ve included an Advanced Management tool for just these kinds of queries:

image

This is an example run from within the MarcEditor. 

 

Anyway – this is a quick write-up.  I’ll be recording a couple sessions tomorrow.  I’ll also be working to make a new plugin available.

Best,

–tr

by reeset at January 17, 2017 06:29 AM

MarcEdit update

I’ve posted a new update for all versions of MarcEdit, and it’s a large one.  It might not look like it from the outside, but it represents close to 3 1/2 months of work.  The big change is related to the inclusion of a more detailed change log.  Users can turn on logging and see, at a low level, the actual changes made to specific data elements.  I’ve also added some additional logging enhancement features to allow users to extract just changed records, or enhance the log files with additional data.  For more information, see my next post on the new logging process.

The full change log:

6.2.447
* Enhancement: Z39.50: Sync’ng changes made to support Z39.50 servers that are sending records missing proper encoding guidelines.  I’m seeing a lot of these from Voyager…I fixed this in one context in the last update.  This should correct it everywhere.
* Enhancement: MARCEngine: 008 processing was included when processing MARCXML records in MARC21 to update the 008, particularly the element to note when a record has been truncated.  This is causing problems when working with holdings records in MARCXML – so I’ve added code to further distinguish when this byte change is needed.
* Enhancement: MarcEdit About Page: Added copy markers to simplify capturing of the Build and Version numbers.
* Enhancement: Build New Field: The tool will only create one field per record (regardless of existing field numbers) unless the replace existing value is selected. 
* Enhancement: Swap Field Function: new option to limit swap operations if not all defined subfields are present.
* Bug Fix: MARCValidator: Potential duplicates were being flagged when records had blank fields (or empty fields) in the elements being checked. 
* Update: MarcEditor: UI responsiveness updates
* New Feature: Logging.  Logging has been added to the MarcEditor and supports all global functions currently available via the task manager. 
* New Feature:  MarcEditor – Log Manager: View and delete log files.
* New Feature:  MarcEditor – Log Manager: Advanced Toolset. Ability to enhance logs (add additional marc data) or use the logs to extract just changed records.

You can download the update directly from the website at: http://marcedit.reeset.net/downloads or you can use the automated downloader in the program.

One last note, on the downloads page, I’ve added a directly listing that will provide access to the most previous 6.2 builds.  I’m doing this partly because some of these changes are so significant, that there may be behavior changes that crop up.  If something comes up that is preventing your work – uninstall the application and pull the previous version from the archive and then let me know what isn’t working. 

Best,

–tr

by reeset at January 17, 2017 06:16 AM

January 12, 2017

OCLC Cataloging and Metadata News

How to optimize your library sales with OCLC's complete MARC record solution

Of course libraries need bibliographic records, but how do you ensure they have the best records to increase the sales, discoverability and usage of your content?

January 12, 2017 03:30 PM

January 11, 2017

OCLC Next

The long tail of library discovery

long-tail

One of our first OCLC symposium speakers was Chris Anderson, the technology writer and former editor of Wired. He spoke for us at ALA Annual back in 2005 on the subject of his famous Wired article and soon-to-be published best-seller, The Long Tail. Like many others in our profession, I found the subject to be both interesting and appropriate to libraries, as did others whom we quoted in a NextSpace article at the time.

Libraries have been collecting, preserving and promoting “long tail materials” for centuries, of course. That’s the long tail of content. But we’ve also found that, when it comes to WorldCat, there’s a long tail for discovery.

A brief history of WorldCat traffic

For the first year or so after we released WorldCat.org in 2006, most of the traffic came through the “front door”—from what we call “organic page views.” That’s where you visit the site itself, do a search, look at the results and then find materials in a nearby library.

Today organic page views account for around 12% of our traffic.

The next largest source of page views is from “signed partners.” Call this the “warehouse door,” used for large deliveries. These are organizations that work directly with OCLC in order to get programmatic, large-scale access to library metadata. As you might expect, Google is the leader in this category.

Other large “signed partners” include Goodreads, BibMe, Citavi, CiteFast and EasyBib. These are important partnerships because they make sure that library materials are found within the online services people use the most. But what might surprise you is that even taken all together, these partnerships no longer account for even half of the site’s usage. What accounts for the rest?

The long tail of discovery.

A thousand side doors into your library

WorldCat Page Views pie chartWe refer to the last category of sites sending traffic to WorldCat as “volunteer partners.” These are websites that choose on their own to link to libraries through WorldCat.org by taking advantage of the various tools we make available for this purpose, including APIs, Linked Data sets, widgets and the like.

Volunteer partners include some large and well-known sites. For example, because of how WorldCat centralizes library data, it is much easier for search engines to find. Bing, for example, sent 9.6 million views last year, along with Yahoo (7.8 million), HathiTrust (1.3 million), Wikipedia (1.1 million) and others.

But the story doesn’t end with large web services. Because OCLC makes it easy to link to libraries through WorldCat.org, many smaller organizations can provide discovery access to libraries, too. For OCLC, these sites represent the “long tail” of library discovery.

Knit one, purl two-hundred-thousand

At an OCLC Member Forum in Boston last year, I shared the fact that the knitting site, Ravelry.com, is one of the most active examples of our third category of referrers: volunteer partners. Last year Ravelry users viewed library materials on WorldCat.org around 200,000 times. That’s 200,000 opportunities for members of this tight-knit community (sorry, couldn’t help myself) to share knowledge and connect to local libraries and other fans.


More than half of all WorldCat.org page views come from volunteer partners.
Click To Tweet


The reaction from librarians at the forum was very positive. Many had heard of or even used or recommended Ravelry. They were also pleased that an online community like this was able to easily send traffic to library materials through WorldCat. Some other interesting partners in this category include:

All together? From mighty search engines to knitters, volunteer partners now account for 58% of our page views on WorldCat.

Regardless of the size of the partner, the point is that easy tools and a variety of opportunities help OCLC democratize discovery and access to library materials. Meaning that the long tail now helps get people into libraries as well as give them content options once they’re there.

Visit the OCLC Developer Network to learn more about how you can incorporate WorldCat data into your applications and services.

The post The long tail of library discovery appeared first on OCLC Next.

by Chip Nilges at January 11, 2017 06:09 PM

January 06, 2017

Thingology (LibraryThing's ideas blog)

Introducing Syndetics Unbound

oa_logo_425w

Short Version

Today we’re going public with a new product for libraries, jointly developed by LibraryThing and ProQuest. It’s called Syndetics Unbound, and it makes library catalogs better, with catalog enrichments that provide information about each item, and jumping-off points for exploring the catalog.

To see it in action, check out the Hartford Public Library in Hartford, CT. Here are some sample links:

We’ve also got a press release and a nifty marketing site.

UPDATE: Webinars Every Week!

We’re now having weekly webinars, in which you can learn all about Syndetics Unbound, and ask us questions. Visit ProQuest’s WebEx portal to see the schedule and sign up!

Long Version

oa_sample2

The Basic Idea

Syndetics Unbound aims to make patrons happier and increase circulation. It works by enhancing discovery within your OPAC, giving patrons useful information about books, movies, music, and video games, and helping them find other things they like. This means adding elements like cover images, summaries, recommendations, series, tags, and both professional and user reviews.

In one sense, Syndetics Unbound combines products—the ProQuest product Syndetics Plus and the LibraryThing products LibraryThing for Libraries and Book Display Widgets. In a more important sense, however, it leaps forward from these products to something new, simple, and powerful. New elements were invented. Static elements have become newly dynamic. Buttons provide deep-dives into your library’s collection. And—we think—everything looks better than anything Syndetics or LibraryThing have done before! (That’s one of only two exclamation points in this blog post, so we mean it.)

Simplicity

Syndetics Unbound is a complete and unified solution, not a menu of options spread across one or even multiple vendors.

This simplicity starts with the design, which is made to look good out of the box, already configured for your OPAC and look.

The installation requirements for Syndetics Unbound are minimal. If you already have Syndetics Plus or LibraryThing for Libraries, you’re all set. If you’ve never been a customer, you only need to add a line of HTML to your OPAC, and to upload your holdings.

Although it’s simple, we didn’t neglect options. Libraries can reorder elements, or drop them entirely. We expect libraries will pick and choose, and evaluate elements according to patron needs, or feedback from our detailed usage stats. Libraries can also tweak the look and feel with custom CSS stylesheets.

And simplicity is cheap. To assemble a not-quite-equivalent bundle from ProQuest’s and LibraryThing’s separate offerings would cost far more. We want everyone who has Syndetics Unbound to have it in its full glory.

Comprehensiveness and Enrichments

Syndetics Unbound enriches your catalog with some sixteen enrichments, but the number is less important than the options they encompass. These include both professional and user-generated content, information about the item you’re looking at, and jumping-off points to explore similar items.

Quick descriptions of the enrichments:

enrichment-screenshots_0000_1-cover-images
Boilterplate covers for items without covers.

Premium Cover Service. Syndetics offers the most comprehensive cover database in existence for libraries—over 25 million full-color cover images for books, videos, DVDs, and CDs, with thousands of new covers added every week.

For Syndetics Unbound, we added boilerplate covers for items that don’t have a cover, which include the title, author, and media type.

Summaries. Over 18 million essential summaries and annotations, so patrons know what the book’s about.

About the Author. This section includes the author biography and a small shelf of other items by the author. The section is also adorned by a small author photo—a first in the catalog, although familiar elsewhere on the web.

Look Inside. Includes three previous Syndetics enrichments—first chapters or excerpts, table of contents and large-size covers—newly presented as a “peek inside the book” feature.

Series. Shows a book’s series, including reading order. If the library is missing part of the series, those covers are shown but grayed out.

You May Also Like. Provides sharp, on-the-spot readers advisory in your catalog, with the option to browse a larger world of suggestions, drawn from LibraryThing members and big-data algorithms. In this and other enrichments, Syndetics Unbound only recommends items that your library owns.

The Syndetics Unbound recommendations cover far more of your collection than any similar service. For example, statistics from the Hartford Public Library show this feature on 88% of items viewed.

Professional Reviews includes more than 5.4 million reviews from Library Journal, School Library Journal, New York Times, The Guardian, The Horn Book, BookList, BookSeller + Publisher Magazine, Choice, Publisher’s Weekly, and Kirkus. A la carte review sources include Voice of Youth Advocates: VOYA, Doody’s Medical Reviews and Quill and Quire.

Reader Reviews includes more than 1.5 million vetted, reader reviews from LibraryThing members. It also allows patrons and librarians to add their own ratings and reviews, right in your catalog, and then showcase them on a library’s home page and social media.

Also Available As helps patrons find other available formats and versions of a title in your collection, including paper, audio, ebook, and translations.

enrichment-screenshots_0010_10-tags
Exploring the tag system

Tags rethinks LibraryThing’s celebrated tag clouds—redesigning them toward simplicity and consistency, and away from the “ransom note” look of most clouds. As data, tags are based on over 131 million tags created by LibraryThing members, and hand-vetted by our staff librarians for quality. A new exploration interface allows patrons to explore what LibraryThing calls “tag mashes”—finding books by combinations of tags—in a simple faceted way.

I’m going to be blogging about the redesign of tag clouds in the near future. Considering dozens of designs, we decided on a clean break with the past. (I expect it will get some reactions.)

Book Profile is a newly dynamic version of what Bowker has done for years—analyzing thousands of new works of fiction, short-story collections, biographies, autobiographies, and memoirs annually. Now every term is clickable, and patrons can search and browse over one million profiles.

enrichment-screenshots_0012_12-reading-level
Explore Reading Levels

Reading Level is a newly dynamic way to see and explore other books in the same age and grade range. Reading Level also includes Metametrics Lexile® Framework for Reading. Click the “more” button to get a new, super-powered reading-level explorer. This is one my favorite features! (Second and last exclamation point.)

Awards highlights the awards a title has won, and helps patrons find highly-awarded books in your collection. Includes biggies like the National Book Award and the Booker Prize, but also smaller awards like the Bram Stoker Award and Oklahoma’s Sequoyah Book Award.

Browse Shelf gives your patrons the context and serendipity of browsing a physical shelf, using your call numbers. Includes a mini shelf-browser that sits on your detail pages, and a full-screen version, launched from the detail page.

Video and Music adds summaries and other information for more than four million video and music titles including annotations, performers, track listings, release dates, genres, keywords, and themes.

Video Games provides game descriptions, ESRB ratings, star ratings, system requirements, and even screenshots.

Book Display Widgets. Finally, Syndetics Unbound isn’t limited to the catalog, but includes the LibraryThing product Book Display Widgets—virtual book displays that go on your library’s homepage, blog, LibGuides, Facebook, Twitter, Pinterest, or even in email newsletters. Display Widgets can be filled with preset content, such as popular titles, new titles, DVDs, journals, series, awards, tags, and more. Or you point them at a web page, RSS feed, or list of ISBNs, UPCs, or ISSNs. If your data is dynamic, the widget updates automatically.

Here’s a page of Book Display Widget examples.

Find out More

Made it this far? You really need to see Syndetics Unbound in action.

Check it Out. Again, here are some sample links of Syndetics Unbound at Hartford Public Library in Hartford, CT: The Raven Boys by Maggie Stiefvater, Alexander Hamilton by Ron Chernow, Faithful Place by Tana French.

Webinars. We hold webinars every Tuesday and walk you through the different elements and answer questions. To sign up for a webinar, visit this Webex page and search for “Syndetics Unbound.”

Interested in Syndetics Unbound at your library? Go here to contact a representative at ProQuest. Or read more about at the Syndetics Unbound website. Or email us at ltflsupport@librarything.com and we’ll help you find the right person or resource.

by Tim at January 06, 2017 07:22 PM