2. Survey of the Room
• How many catalogers are in the room?
• How many of you use metadata schema such
as…..
e.g Dublin Core, EAD, MODS, ?
3. Fulfillment of Service
• What comes across our desk
o Ex. Books, CDs, How to Guides, etc…
• More formally:
o A technical services librarian (is) primarily responsible for
preparing bibliographic records or metadata to represent the
resources in the collections of an information agency, including
description, subject analysis, access to information, authority
control, metadata application, quality control, and metadatarelated decision making.
4. Cataloger / Metadata
• Additional responsibilities include {data sharing,
consortia collaboration, project management,
standard}, policy, and workflow development. Also
refers to the librarian responsible for supervising a
cataloging or metadata department..
5.
6. The Great Exodus to The
New World
• Patrons aren’t using the library as their first research
source
• They have made the
internet their source
for “all” of their
information.
7. Technical Service Trends
Vendor processed resources
Will vendors control the distribution
of cataloging metadata for nonunique materials?
As budgets decrease demand for
various resources and information
increases at a cost.
9. In and Out = Change?
Functional Requirements for
Bibliographic Description (FRBR)
Resource Description and Access
(RDA)
Library Linked Data
10. Functional Requirements for Bibliographic Records
Entity-Relationship Model
User Tasks
•Find
•Identify
•Select
•Obtain
Entity = Work
Entity = Work
Attributes
Attributes
Title
Title
Creator
Creator
Value
Value
Value
Value
A Christmas Carol
A Christmas Carol
Charles Dickens
Charles Dickens
11. The Rules: AACR2 Vs. RDA
Schools of Thought:
Adopted RDA
maintain AACR2.
Those despite formal RDA training, still fighting the “good
fight.”
RDA as a set of rules will be the “final nail in the coffin” of
MARC.
BUT!!! WE Need to Googleize our OPACS
12. The Rules: AACR2 Vs. RDA
MARC was originally developed to print cards, not
for computerized searching or to supply machine
readable data. The library of Congress never
anticipated the imminent flexibility computers could
confer on bibliographic description to anticipate
many of the random or chaotic ways human
search catalogues. RDA is kind of like a politically
more control in the client in gathering subsets of
formats
- FRBR VTLS Users Group, access December 2013
13. The Rules: AACR2 Vs. RDA
The Anglo-American Cataloging Rules, 2nd edition
(AACR2) is a content standard published by the
American Library Association (ALA), Canadian
Library Association (CLA), and Chartered Institute of
Library and Information Professionals (CILIP).
14. The Rules: AACR2 Vs. RDA
RDA is organized by FRBR entities and
relationships
Not by ISBD (International Standard
Bibliographic Description) areas (AACR2)
RDA is focused on online resource
Not on print resource (AACR2)
15. The Rules: AACR2 Vs.
RDA
RDA is a Content Standard
Not a display (presentation) standard like AACR2
(largely a content and display standard)
Not an encoding schema (use whatever schema
is appropriate to record data elements: Dublin
Core, MODS, MARC, etc.)
18. Issues with RDA
Shared Cataloged implementation
Training catalogers and their staff
Devotion to AACR2
RDA still is not quite the answer or semantic web
or web friendly data
20. Linked Data: Is It Any
Good?
•
Not-library specific
o Detailed library data becomes part of the web
o Libraries can benefit from wider software, community, and expertise; less tied to specific
vendors
o Non-librarians can use data
•
Not catalogue-specific: e.g. if archives, repositories, and catalogues, and others can publish
linked data and share Uniform Resource Identifiers (URIs) then it can be mixed and re-used in
interesting ways
•
Can be linked with other schemes. E.g. authorities such as VIAF with Wikipedia, ORCID, and ISNI
•
Backbone of other big initiatives:
o Schema.org used by major search engines (Google, Bing, Yahoo)
o UK government open data: data.gov.uk
o Dbpedia
o BBC websites, e.g. wildlife finder (takes data from Wikipedia) and World Cup sites.
•
•
Based on very basic and flexible Entity Relationship Model (ERM), the same structure as e.g. FRBR
No standard way of presenting bibliographic information as linked data
- Thomas Meehan
29. Looking Back…..
RE-Cap
We are living in a time where libraries are competing
against the World Wide Web as the source for information.
Despite trying to reach a solution for users by attempting
to bring the web into the library, no uniform answers have
been found that satisfies everyone.
As new schemas, semantic web friendly metadata, as well
discovery systems are created, shared/co-op catalogs will
be harder to maintain or (in some cases) create.
30. References
•
Batoma, Atoma T. “Some General Features of RDA”. RDA Presentation Materials - 05/16/2012 & 05/23/2012.
University of Illinois- Urbana-Champaign, Accessed December 24, 2013.
http://www.library.illinois.edu/cms/cam/training/RDAatoma.pptx
•
“Cataloging or Metadata Librarianship.” Accessed December 22, 2013.
https://www.kent.edu/slis/programs/mlis/cataloging-or-metadata.cfm.
•
“Catalog_Desiree5.png Photo by LibraGoddess04 | Photobucket.” Accessed December 27, 2013.
http://smg.photobucket.com/user/LibraGoddess04/media/Catalog_Desiree5.png.html.
•
“FRBR_VTLS Users Group.pdf.” Accessed December 28, 2013. http://vug.vtls.com/presentations/2012/FRBR_VTLS
%20Users%20Group.pdf.
•
“Never Mind E-Books: Why Print Books Are Here to Stay - WSJ.com.” Accessed December 24, 2013.
http://online.wsj.com/news/articles/SB10001424127887323874204578219563353697002.
•
Thomas Meehan. “Beyond MARC: MARC, Linked Data, and Bibframe.” Education, 17:11:35 UTC.
http://www.slideshare.net/orangeaurochs/marcld2013.
•
•
“Transitioning from Cataloging to Creating Metadata | Association for Library Collections & Technical Services
(ALCTS).” Accessed December 26, 2013. http://www.ala.org/alcts/confevents/upcoming/webinar/022713.
“Twitter / Sophiewackles: #alamw13 #bibframe Hubba Hubba ...” Accessed January 2, 2014.
https://twitter.com/sophiewackles/status/296296921759350784.
Notes de l'éditeur
Just to get an idea of the room make-up how many catalogers are their in the room? How many people fairly familiar with technical services and that department’s work?
Currently, today, one of the major tenants of cataloging arguably still holds true ; Read Slide { }
Read Slide { } This is how life should be. But how is it “really” from the patron’s view?
Read Slide { } This is how life should be. But how is it “really” from the patron’s view?
On the patron end…..Students/Patrons are gravitated toward Google and anything other than the refined, manicured, catalog. They are drawn towards these sources because they are internet friendly and easier acclimate. So, we as the technical service staff have to go beyond providing the manicured bibliographic record. But, also services and workflows will change as services and types resources change. Flexibility, adaptability, and staying informed on emerging trends is paramount.
What does that mean in terms of change? Technical Services as a whole, has not changed for many libraries. Even as we increase our purchase of e-resources, we are still in the business of purchasing, organizing and making available resources that our patrons want. However, again, because students have, gravitated toward the user friendliness of the World Wide Web via search engines such as Google, the library as an organization must modify the content of its services to meet the needs of the 21st century patron.
So, what are we going to do and how is technical services going to accommodate these patrons in the 21st Century? We can’t exactly just go out and change people. But we can certainly do something about the system. We are the gate keepers.
Read From slide { } . The goal of both FUBUR and RDA is to make the local OPAC more internet friendly, hence more enticing to students. But many us including OCLC realize we have to go way beyond that. Instead just FUBURing our OPACS we probably should be saying that we need to Googleize our OPACS
Read Slide { }
Futhermore, people complain that MARC cannot be manipulated with general purpose editing tools. It is true that the MARC format is used only by a very narrow group of organizations and there are few tools for manipulating it directly. But we have MARCXML and it's easy enough to convert MARC to MARCXML and have access to all those XML tools, at least as long as you don't have bad MARC data.
-
- OCLC, 2013
Read Slide { }
-
- OCLC, 2013
Read Slide { }
- OCLC, 2013
Read Slide { }
- OCLC, 2013
From slide { } As with any new group of standards, rules, and regulations, there are always issues or growing pains that occur with implementation. While there are a lot of records that have upload to OCLC that are RDA ready, still we have an issues where the befits of Copy Cataloging in reference to to time can become an issue depending upon the standards of you technical services department. Many institutions have reverted to ordering Shelf Ready materials. RDA is also trying to follow the FRBR model and record relationships between different pieces of bibliographic information more effectively in a way that computers can use. Unfortunately, it's not easy to represent relationships and hierarchies in MARC.
linked data – everything has to have a link – so this has lead to linked data versions of all kinds of library knowledge – authority files, and subject headings. From Slide { }.
This is not the prettiest thing to see because it is for the System to read and understand.
Google's take on a linked data model, Knowledge Graphs, yields a more esthetically, but useful interface where search analytics are used to generate organized seta of data that is both text and visual connected. This results sways users from searching through other pages or conducting further search queries for answers to questions.
Here’s the BIBFRAME main page – source for current info about BIBFRAME experiments
In the summer of 2012, teh LoC hired Zepheira (http://zepheira.com/) to investigate the possibilistes of linked data as the carrier for library descriptive information. In November of 2012, Zepheira and LoC published a report, Bibliographic Framework as a Web of Data: Linked Data Model and Supporting Services
Not a record format – but an encoding scheme – Current BIBFRAME experiments getting data OUT of MARC records, into an XML format, and out onto the web, where it can be linked to and from (last slide – “These Information Resources can then be re-assembled into a coherent architecture that allows for cooperative cataloging at a far more granular level than before.
