The document discusses improving displays of bibliographic data from MARC records. It provides examples of how MARC records are normally displayed versus improved displays that provide additional context and details. It also discusses using XSLT to transform MARCXML into HTML to produce more informative displays, and the benefits of libraries having tools to customize their displays.

1. Smart Interfaces through Domain
Knowledge: Facets, Metadata
Displays, Analysis, Algorithms, and
Paths to Knowledge
Sam Cook
Library Connection
Casey A. Mullin
Stanford University Libraries
Aaron Wood
Alexander Street Press
Charleston Conference 2013 “Too Much Is not
Enough”
Nov. 7, 2013
Francis Marion, Charleston, South Carolina

2. MARC Is Not Perfect,
But It Is No Excuse For
Lazy Displays
Improving Displays of Bibliographic Data
Sam Cook, Systems Librarian for Public Services
Library Connection, Inc.
Windsor, CT
Formerly Public Services Librarian
Allen Library, University of Hartford
West Hartford, CT
2

3. Improving Displays of Bibliographic Data
A Sample Item

4. Improving Displays of Bibliographic Data
How it is Cataloged
100 1 _aBeethoven, Ludwig van,
_d1770-1827
240 10 _aConcertos,
_mViolin, orchestra,
_nop. 61,
_rD major
700 12 _aBrahms, Johannes,
_d1833-1897
_tConcertos,
_mviolin, orchestra,
_nop. 77,
_rD major

5. Improving Displays of Bibliographic Data
How it is Normally Displayed

6. Improving Displays of Bibliographic Data
How it is Normally Displayed
6

7. Improving Displays of Bibliographic Data
How it is Normally Displayed
7

8. Improving Displays of Bibliographic Data
How it is Normally Displayed
8

9. Improving Displays of Bibliographic Data
How Koha Normally Displays It

10. Improving Displays of Bibliographic Data
University of Hartford’s OPAC Display

11. Improving Displays of Bibliographic Data
What is XSLT?
MARC
MARCXML
100 10 $aCopland, Aaron, $d1900-1990.
<datafield tag="100" ind1="1" ind2="0">
<subfield code="a">Copland, Aaron,</subfield>
<subfield code="d">1900-1990.</subfield>
</datafield>
XSLT
<h5 class="author">By Copland, Aaron, 1900-1990.</h5>
HTML

12. Improving Displays of Bibliographic Data
Title (245)
Changes made:
•Added 245 subfield c
•Put 245 subfields in order they are cataloged in, rather than in a
specified order
•Removed everything from subfield h for sound recordings except
for forward slash (/)

13. Improving Displays of Bibliographic Data
Controlled Names & Name/Titles (1XX/240, 7XX)
Changes made:
•Placed 1XX with 240
•Placed 1XX/240 with name/title 7XXs
•Line breaks between name/titles to make it easier to read
•Separated name-only 7XXs into their own list
•Included all subfields in proper order

14. Improving Displays of Bibliographic Data
Results Page Title/Author
Changes made:
•Included (nearly) complete 245 in title line
•Removed everything from subfield h except for forward slash (/)
•If item is a sound recording with a 245 $c, it no longer includes
“by” line
•Added 511 performer note instead of 7XXs

15. Improving Displays of Bibliographic Data
Results Page Author
Changes made:
•Consolidated author entries

16. Improving Displays of Bibliographic Data
Results Page Item Format
Changes made:
•Replaced generic “sound disc” format with more specific CD or LP
designation
•Modified icon to reflect proper format
•Removed “Literary form” from sound recordings

17. Improving Displays of Bibliographic Data
Why This Matters
1) This is not an attempt to promote Koha.
2) Our data is the most important part of our
catalog. We need to have the tools to modify
displays in creative ways based on our
familiarity with our own data.
3) If given the tools, we need to then actually use
them.

18. Music Discovery Beyond
MARC
Benefits and challenges of domain-driven
functionality outside the ―silo‖
Casey A. Mullin
Stanford University
Libraries

19. Music Discovery at Stanford

SearchWorks
◦ Canonical catalog since September 2010
◦ Blacklight implementation
◦ Feature rollouts to date largely domainneutral
◦ ―Music view‖ in preliminary development
19

20. Music Discovery at Stanford

Features that benefit all domains, but were
prompted by music-specific use cases
◦ Name-title searching
Source: http://searchworks.stanford.edu
20

21. Music Discovery at Stanford

Features that benefit all domains, but
were prompted by music-specific use
cases
◦ Better 7xx labeling (based on 2nd indicator)
 ―Related work‖ vs. ―Included work‖
Source: http://searchworks.stanford.edu
21

22. Music Discovery at Stanford

Features that benefit all domains, but
were prompted by music-specific use
cases
◦ Date slider and enhanced date display
(i.e., not just ―Date1‖)
22

23. Music Discovery at Stanford

Emerging metadata ecosystem no longer
limited to MARC
◦ Metadata for digital objects and collections ―flows
in‖ through a separate pipeline
 Mapping decisions
 Item vs. collection-level access
 Harmonization with MARC metadata
 Conversion to MODS (for storage)
 Remediation
 Conversion to SOLR indexes
◦ MARC-based domain-driven functionality
complicated by the presence of native nonMARC metadata
 Not really a new problem
 Doesn’t mean MARC should (continue to) be glossed
over
23

24. Alternative Paths to
Knowledge

Not just beyond MARC, but beyond the
―catalog‖ (as we know it)
◦ Locally stored and maintained metadata an
obsolescent notion
 Shared ILSes
 OCLC Worldshare Management Services (―the
cloud‖)
◦ Pie-in-the-sky vision: Catalog (discovery
layer) no longer merely a (slick, sexy)
inventory of a library’s holdings (whether
owned or licensed), but a true knowledge tool
◦ How do we realize this?
24

25. Alternative Paths to
Knowledge

Linked Data
◦ Links can be leveraged in both directions
 In: enhanced metadata, displayed in context
 Out: links to external sites for further exploration of
a person, place, topic…
 Can (must) be applied judiciously!
◦ Risk: the larger the web of data, the fewer
assumptions can be made about a results
set, and thus the less confidently algorithms
can be applied
◦ But, links and external content can be
activated using similar algorithms to those
that activate special display rules, facets, etc.
25

26. Linked Data—Music use
cases
◦ MusicBrainz
 Enhanced track-level metadata (for popular
music, especially)
 Robust relationships between works, recordings
26

27. Source:
27

28. Linked Data—Music use
cases
◦ Opening Night! Opera & Oratorio
Premieres
 Rich data on the works themselves (e.g., date and location
of premiere), with live links to SearchWorks
28

29. Source: http://operadata.stanford.edu/
29

30. Source: http://searchworks.stanford.edu
30

31. Linked Data—Music use
cases
◦ Linked Jazz
 Relationships between performers (collaborators, mentors)
 Could prompt a user to expand a results set based on a
performers personal network (―More like this…‖)
31

32. Source: http://linkedjazz.org
32

33. Domain-Specific Facets
University of Virginia:
http://search.lib.virginia.edu/music
University of Music and Theatre "Felix Mendelssohn
Bartholdy" Leipzig:
https://katalog.hmt-leipzig.de/
Alexander Street Press:
http://search.alexanderstreet.com

34. University of Virginia Libraries’ VIRGO Music Search

35. Hochschule für Musik und Theater Felix Mendelssohn
Bartholdy Leipzig

37. Alexander Street Press – search.alexanderstreet.com

38. Questions?
Casey A. Mullin
Sam Cook
Head, Data Control Unit
Systems Librarian for Public Services
Metadata Department
Library Connection, Inc.
Stanford University Libraries
Email: scook315@yahoo.com
Phone: 650-736-0849
Email: cmullin@stanford.edu
http://www.caseymullin.com
Aaron Wood
Vice President, Systems & Data Architecture
Alexander Street Press
Phone: 800-889-5937 ext. 122
Email: awood@astreetpress.com
http://search.alexanderstreet.com