A refresher on FRBR (Functional Requirements for Bibliographic Records) theory, its implementation in VTLS Virtua, and RDA (Resource Description and Access), the cataloging code set to be implemented in early 2013.
Where is the Justice … League?: “Graphic novel” cataloging and classificationWilliam Fee
Presentation for PaLA Annual Conference 2012. Practical solutions to the problems of cataloging and classifying
graphica, with information on useful RDA changes and the upcoming
implementation of FRBR and its relationship to the format.
The document summarizes the State Library of Pennsylvania's efforts to crowdsource the transcription of materials related to the Civil War using the Scripto transcription software. It provides an overview of the library's history and digital projects. It then details the challenges faced in installing and implementing Scripto on a Windows server, including lack of documentation, dependency issues, and firewall restrictions. Screenshots of the Scripto interface for the main page, registration, images, and transcription are included.
The document summarizes the State Library of Pennsylvania's TableTop ScribeStation Program. It provides details on how local libraries and historical societies can apply to borrow the TableTop ScribeStation, a portable digitization scanner, to scan materials of significance. It outlines the requirements for participants, including making scanned materials publicly accessible online and taking responsibility for transportation. It also describes what is needed to set up and use the scanner and includes photos of the device and materials included.
Plays Well with Others: Getting Your Digital Collection Metadata Ready for th...William Fee
Presented at 2015 PaLA Annual Conference on November 6, 2015 by
Linda Ballinger, Penn State
Doreva Belfiore, Temple University
Bill Fee, State Library of Pennsylvania
Leanne Finnigan, Temple University
Kristen Yarmey, University of Scranton
FRBR and serials: implementation, problems and successesWilliam Fee
William Fee presented on the implementation, problems, and successes of digital collections and authority control at the State Library of Pennsylvania. He discussed his roles managing digital collections, authority control, and disaster response for the library's digital assets. The presentation addressed best practices for building and maintaining digital collections while navigating technical and organizational challenges.
A refresher on FRBR (Functional Requirements for Bibliographic Records) theory, its implementation in VTLS Virtua, and RDA (Resource Description and Access), the cataloging code set to be implemented in early 2013.
Where is the Justice … League?: “Graphic novel” cataloging and classificationWilliam Fee
Presentation for PaLA Annual Conference 2012. Practical solutions to the problems of cataloging and classifying
graphica, with information on useful RDA changes and the upcoming
implementation of FRBR and its relationship to the format.
The document summarizes the State Library of Pennsylvania's efforts to crowdsource the transcription of materials related to the Civil War using the Scripto transcription software. It provides an overview of the library's history and digital projects. It then details the challenges faced in installing and implementing Scripto on a Windows server, including lack of documentation, dependency issues, and firewall restrictions. Screenshots of the Scripto interface for the main page, registration, images, and transcription are included.
The document summarizes the State Library of Pennsylvania's TableTop ScribeStation Program. It provides details on how local libraries and historical societies can apply to borrow the TableTop ScribeStation, a portable digitization scanner, to scan materials of significance. It outlines the requirements for participants, including making scanned materials publicly accessible online and taking responsibility for transportation. It also describes what is needed to set up and use the scanner and includes photos of the device and materials included.
Plays Well with Others: Getting Your Digital Collection Metadata Ready for th...William Fee
Presented at 2015 PaLA Annual Conference on November 6, 2015 by
Linda Ballinger, Penn State
Doreva Belfiore, Temple University
Bill Fee, State Library of Pennsylvania
Leanne Finnigan, Temple University
Kristen Yarmey, University of Scranton
FRBR and serials: implementation, problems and successesWilliam Fee
William Fee presented on the implementation, problems, and successes of digital collections and authority control at the State Library of Pennsylvania. He discussed his roles managing digital collections, authority control, and disaster response for the library's digital assets. The presentation addressed best practices for building and maintaining digital collections while navigating technical and organizational challenges.
A presentation given at Choose your own journey, theMLA/DLA 2012 Joint Library Conference on Wednesday, May 09, 2012. Co-presentation by William TB Fee and Mary Spila. Presented with Beacher Wiggins, the Director for Acquisitions and Bibliographic Access at the Library of Congress.
This document provides an RDA authority record for William T. Fee (1969-), an American librarian and writer. It includes biographical information like places of residence and employment, education history, publications and unpublished works. Key details about Fee's career in libraries and areas of specialty in cataloging and FRBR theory are also provided.
Beyond MARC: MARC, linked data, and BibframeThomas Meehan
Beyond MARC summarizes the limitations of MARC and introduces linked data and Bibframe as potential replacements. It discusses how MARC was designed for storage and exchange of cataloging data but is inflexible, contains duplicate data, and does not represent relationships well. Linked data uses HTTP URIs and RDF to identify things and express relationships between related data to enable a global "web of data".
This document provides an overview and summary of key elements for cataloging serials according to RDA. It begins with definitions of what constitutes a serial and notes some of the new fields introduced in RDA for describing serials. It then discusses how to record various elements like title, publication information, frequency, numbering, notes, extent and carrier. It also covers identifying works and expressions for serials as well as when new records are required. The document concludes with examples of recording related works, expressions and manifestations for serials.
This document provides an overview of Machine Readable Cataloging (MARC) records. It defines MARC as the standard for encoding bibliographic data for computer processing. Key points include:
- MARC records use a common structure and format that allows libraries to share cataloging data and bibliographic resources.
- The structure includes a leader field, control fields, variable fields and subfields to store bibliographic information like titles, authors, subjects etc.
- Adhering to the MARC standard ensures cataloging data is compatible across different library systems.
- Examples of commonly used fields are provided, like title (245), author (100), subjects (650), and notes (500).
This document provides an overview of Machine Readable Cataloging (MARC) records. It defines MARC as the standard for encoding bibliographic data for computer processing. Key points include:
- MARC records use a common structure and format that allows libraries to share cataloging data and bibliographic resources.
- The structure includes a leader field, control fields, variable fields and subfields to store bibliographic information like titles, authors, subjects etc.
- Adhering to the MARC standard ensures cataloging data is compatible across different library systems.
- Examples of commonly used fields are provided, like title (245), author (100), subjects (650), and notes (500).
This document discusses MongoDB aggregation pipelines and their capabilities. It begins with an introduction to Tom Schreiber, who is a senior consulting engineer at MongoDB. It then provides examples of aggregation pipelines that find the two highest paid employees per department. It demonstrates how to do this in different ways using SQL queries and a Ruby implementation. It explains how aggregation pipelines allow data to be easily worked with and processed in series using composable stages like in other functional programming languages and libraries. Overall, the document shows how aggregation pipelines provide a powerful yet easy way to query and transform data in MongoDB.
MongoDB Europe 2016 - Advanced MongoDB Aggregation PipelinesMongoDB
We will do a deep dive into the powerful query capabilities of MongoDB's Aggregation Framework, and show you how you can use MongoDB's built-in features to inspect the execution and tune the performance of your queries. And, last but not least, we will also give you a brief outlook into MongoDB 3.4's awesome new Aggregation Framework additions.
MARC (Machine Readable Cataloging) is an international standard format for bibliographic data. It allows catalog records to be shared and processed by different library systems. The MARC standard ensures compatibility and enables efficient management of catalog records across libraries. Some key aspects include standardized field and tag definitions, a predictable record structure, and established formats like MARC21 that are used internationally. Common errors to avoid include incorrect field codes and indicators, typographical mistakes, failure to follow punctuation conventions, and not accounting for how one's library system handles specific MARC fields.
Bengkel Teknikal Pengkatalogan dan Pengkelasan PerpustakaanAffida Abu Bakar
This document provides an overview of key MARC 21 terms and definitions including delimiters, fields, tags, indicators, subfields, and subfield codes. It explains that bibliographic data is divided into fields and further subdivided into subfields. Tags identify each field and the data contained, while indicators act as signals to application software on how to treat the information. Subfield codes precede related pieces of data within fields.
This document describes how to create a simple web service using the Retro framework to expose Canadian province data over HTTP. It involves 5 steps:
1. Getting the province data from a CSV file and storing it in a list
2. Writing a ProvincesAPI class to access the data
3. Testing the API by printing out province details
4. Decorating methods with @expose to make them available via HTTP
5. Running the API on port 8000 and testing it with curl requests
The goal is to demonstrate how easily Retro allows exposing data as a web service without having to write any server code, by mapping Python methods to HTTP URLs. The example creates an API that can return a list
The document discusses different types of charts (bar charts, area charts, line charts, horizon graphs) and their use in visualizing data. It covers topics like reducing chart "junk", accessibility of charts for color blindness, and generating charts programmatically with code.
From: Linked Data: what cataloguers need to know. A CIG event. 25 November 2013, Birmingham. #cigld
http://www.cilip.org.uk/cataloguing-and-indexing-group/events/linked-data-what-cataloguers-need-know-cig-event
Accompanying write-up in Catalogue & Index 174: http://discovery.ucl.ac.uk/1449459/
The document provides information about changes from AACR2 cataloging rules to RDA, including: replacing the GMD with 336, 337, and 338 fields; removing abbreviations for marks of omission and abbreviations; not supplying other title information; recording the edition statement and publisher as they appear on the resource; handling reproductions; and no longer using abbreviations in field 362. Links are also provided to resources about RDA cataloging from the Library of Congress, JSC, and University of Chicago.
What is in All of Those SSTable Files Not Just the Data One but All the Rest ...DataStax
Have you ever wondered what is in all of those SSTable files and how it helps Cassandra find and manage your data? If you go to the Datastax website they will give you a high level explanation of what is in each file. In this talk we will go much deeper explaining each file and walking through a dump of its contents. We will also explore the differences between Cassandra 2.1 and 3.4.
About the Speaker
John Schulz Prinicipal Consultant, The Pythian Group
John has 40 of years experience working with data. Data in files and in Databases from flat files through ISAM to relational databases and most recently NoSQL. For the last 15 he's worked on a variety of Open source technologies including MySQL, PostgreSQL, Cassandra, Riak, Hadoop and Hbase. He has been working with Cassandra since 2010. For the last eighteen months he has been working for The Pythian Group to help their customers improve their existing databases and select new ones.
LIS 653, Session 4-A: Bibliographic Formats and MARC Dr. Starr Hoffman
This document provides an overview of bibliographic formats and MARC21 metadata standards. It discusses the purpose of library catalog records in facilitating user tasks like finding, identifying, selecting, and accessing information objects. The anatomy of a MARC21 record is described, including descriptive elements, labels, and how the record fits into systems with authority control, subject headings, and classification schemes. Common MARC21 fields are listed along with examples of how data appears at both the machine and human readable levels. The document also compares how different metadata standards like MARC21 and Dublin Core use common data elements to encode bibliographic descriptions within their defined structures and containers.
This document provides an introduction to Resource Description Framework (RDF) and RDF XML. It defines key RDF concepts like URI references, qualified names, basic RDF triples, RDF graphs, and RDF Schema. It also explains how to represent RDF models and descriptions in RDF XML format using elements like rdf:RDF, rdf:Description, and properties. Examples are provided to illustrate RDF triples and RDF XML representations.
Relational algebra is a collection of operations to manipulate or access tables. It includes set-oriented operations like selection, projection, join, division, as well as native relational operations like rename and assignment. Additional relational operators like aggregate functions, grouping, and outer joins were added to enhance its expressive power.
The document is an email exchange between William Perhach and Daniel Barry regarding a Freedom of Information Act (FOIA) request for records from the Council on Environmental Quality (CEQ) related to climate change. Barry provides Perhach with a proposed search definition, estimated cost of $1,970, and one day schedule to complete the search of CEQ email records from 2001-2002 for terms like "climate action report". Perhach approved the proposal.
More Related Content
Similar to Retirement Day has not yet Arrived:The Introduction to RDA, FRBR & the Associated Madness
A presentation given at Choose your own journey, theMLA/DLA 2012 Joint Library Conference on Wednesday, May 09, 2012. Co-presentation by William TB Fee and Mary Spila. Presented with Beacher Wiggins, the Director for Acquisitions and Bibliographic Access at the Library of Congress.
This document provides an RDA authority record for William T. Fee (1969-), an American librarian and writer. It includes biographical information like places of residence and employment, education history, publications and unpublished works. Key details about Fee's career in libraries and areas of specialty in cataloging and FRBR theory are also provided.
Beyond MARC: MARC, linked data, and BibframeThomas Meehan
Beyond MARC summarizes the limitations of MARC and introduces linked data and Bibframe as potential replacements. It discusses how MARC was designed for storage and exchange of cataloging data but is inflexible, contains duplicate data, and does not represent relationships well. Linked data uses HTTP URIs and RDF to identify things and express relationships between related data to enable a global "web of data".
This document provides an overview and summary of key elements for cataloging serials according to RDA. It begins with definitions of what constitutes a serial and notes some of the new fields introduced in RDA for describing serials. It then discusses how to record various elements like title, publication information, frequency, numbering, notes, extent and carrier. It also covers identifying works and expressions for serials as well as when new records are required. The document concludes with examples of recording related works, expressions and manifestations for serials.
This document provides an overview of Machine Readable Cataloging (MARC) records. It defines MARC as the standard for encoding bibliographic data for computer processing. Key points include:
- MARC records use a common structure and format that allows libraries to share cataloging data and bibliographic resources.
- The structure includes a leader field, control fields, variable fields and subfields to store bibliographic information like titles, authors, subjects etc.
- Adhering to the MARC standard ensures cataloging data is compatible across different library systems.
- Examples of commonly used fields are provided, like title (245), author (100), subjects (650), and notes (500).
This document provides an overview of Machine Readable Cataloging (MARC) records. It defines MARC as the standard for encoding bibliographic data for computer processing. Key points include:
- MARC records use a common structure and format that allows libraries to share cataloging data and bibliographic resources.
- The structure includes a leader field, control fields, variable fields and subfields to store bibliographic information like titles, authors, subjects etc.
- Adhering to the MARC standard ensures cataloging data is compatible across different library systems.
- Examples of commonly used fields are provided, like title (245), author (100), subjects (650), and notes (500).
This document discusses MongoDB aggregation pipelines and their capabilities. It begins with an introduction to Tom Schreiber, who is a senior consulting engineer at MongoDB. It then provides examples of aggregation pipelines that find the two highest paid employees per department. It demonstrates how to do this in different ways using SQL queries and a Ruby implementation. It explains how aggregation pipelines allow data to be easily worked with and processed in series using composable stages like in other functional programming languages and libraries. Overall, the document shows how aggregation pipelines provide a powerful yet easy way to query and transform data in MongoDB.
MongoDB Europe 2016 - Advanced MongoDB Aggregation PipelinesMongoDB
We will do a deep dive into the powerful query capabilities of MongoDB's Aggregation Framework, and show you how you can use MongoDB's built-in features to inspect the execution and tune the performance of your queries. And, last but not least, we will also give you a brief outlook into MongoDB 3.4's awesome new Aggregation Framework additions.
MARC (Machine Readable Cataloging) is an international standard format for bibliographic data. It allows catalog records to be shared and processed by different library systems. The MARC standard ensures compatibility and enables efficient management of catalog records across libraries. Some key aspects include standardized field and tag definitions, a predictable record structure, and established formats like MARC21 that are used internationally. Common errors to avoid include incorrect field codes and indicators, typographical mistakes, failure to follow punctuation conventions, and not accounting for how one's library system handles specific MARC fields.
Bengkel Teknikal Pengkatalogan dan Pengkelasan PerpustakaanAffida Abu Bakar
This document provides an overview of key MARC 21 terms and definitions including delimiters, fields, tags, indicators, subfields, and subfield codes. It explains that bibliographic data is divided into fields and further subdivided into subfields. Tags identify each field and the data contained, while indicators act as signals to application software on how to treat the information. Subfield codes precede related pieces of data within fields.
This document describes how to create a simple web service using the Retro framework to expose Canadian province data over HTTP. It involves 5 steps:
1. Getting the province data from a CSV file and storing it in a list
2. Writing a ProvincesAPI class to access the data
3. Testing the API by printing out province details
4. Decorating methods with @expose to make them available via HTTP
5. Running the API on port 8000 and testing it with curl requests
The goal is to demonstrate how easily Retro allows exposing data as a web service without having to write any server code, by mapping Python methods to HTTP URLs. The example creates an API that can return a list
The document discusses different types of charts (bar charts, area charts, line charts, horizon graphs) and their use in visualizing data. It covers topics like reducing chart "junk", accessibility of charts for color blindness, and generating charts programmatically with code.
From: Linked Data: what cataloguers need to know. A CIG event. 25 November 2013, Birmingham. #cigld
http://www.cilip.org.uk/cataloguing-and-indexing-group/events/linked-data-what-cataloguers-need-know-cig-event
Accompanying write-up in Catalogue & Index 174: http://discovery.ucl.ac.uk/1449459/
The document provides information about changes from AACR2 cataloging rules to RDA, including: replacing the GMD with 336, 337, and 338 fields; removing abbreviations for marks of omission and abbreviations; not supplying other title information; recording the edition statement and publisher as they appear on the resource; handling reproductions; and no longer using abbreviations in field 362. Links are also provided to resources about RDA cataloging from the Library of Congress, JSC, and University of Chicago.
What is in All of Those SSTable Files Not Just the Data One but All the Rest ...DataStax
Have you ever wondered what is in all of those SSTable files and how it helps Cassandra find and manage your data? If you go to the Datastax website they will give you a high level explanation of what is in each file. In this talk we will go much deeper explaining each file and walking through a dump of its contents. We will also explore the differences between Cassandra 2.1 and 3.4.
About the Speaker
John Schulz Prinicipal Consultant, The Pythian Group
John has 40 of years experience working with data. Data in files and in Databases from flat files through ISAM to relational databases and most recently NoSQL. For the last 15 he's worked on a variety of Open source technologies including MySQL, PostgreSQL, Cassandra, Riak, Hadoop and Hbase. He has been working with Cassandra since 2010. For the last eighteen months he has been working for The Pythian Group to help their customers improve their existing databases and select new ones.
LIS 653, Session 4-A: Bibliographic Formats and MARC Dr. Starr Hoffman
This document provides an overview of bibliographic formats and MARC21 metadata standards. It discusses the purpose of library catalog records in facilitating user tasks like finding, identifying, selecting, and accessing information objects. The anatomy of a MARC21 record is described, including descriptive elements, labels, and how the record fits into systems with authority control, subject headings, and classification schemes. Common MARC21 fields are listed along with examples of how data appears at both the machine and human readable levels. The document also compares how different metadata standards like MARC21 and Dublin Core use common data elements to encode bibliographic descriptions within their defined structures and containers.
This document provides an introduction to Resource Description Framework (RDF) and RDF XML. It defines key RDF concepts like URI references, qualified names, basic RDF triples, RDF graphs, and RDF Schema. It also explains how to represent RDF models and descriptions in RDF XML format using elements like rdf:RDF, rdf:Description, and properties. Examples are provided to illustrate RDF triples and RDF XML representations.
Relational algebra is a collection of operations to manipulate or access tables. It includes set-oriented operations like selection, projection, join, division, as well as native relational operations like rename and assignment. Additional relational operators like aggregate functions, grouping, and outer joins were added to enhance its expressive power.
The document is an email exchange between William Perhach and Daniel Barry regarding a Freedom of Information Act (FOIA) request for records from the Council on Environmental Quality (CEQ) related to climate change. Barry provides Perhach with a proposed search definition, estimated cost of $1,970, and one day schedule to complete the search of CEQ email records from 2001-2002 for terms like "climate action report". Perhach approved the proposal.
Similar to Retirement Day has not yet Arrived:The Introduction to RDA, FRBR & the Associated Madness (20)
Retirement Day has not yet Arrived:The Introduction to RDA, FRBR & the Associated Madness
1. RETIREMENT DAY
HAS NOT YET
ARRIVED:
THE INTRODUCTION TO RDA, FRBR & THE ASSOCIATED MADNESS
TUESDAY, JAN. 15, 2013
Bill Fee
Mary Spila
State Library of Pennsylvania
Cataloging Section
3. "But I don't want to go among mad people,” Alice
remarked.
“Oh, you can't help that,” said the Cat, “We're all mad
here. I'm mad. You're mad…”
4. FRBR:
Functional Requirements
for Bibliographic Records
MARC
FRAD: Dublin Core
Functional Requirements HTML/XML
for Authority Data
RDA ONIX
(Unknown
future
FRSAD: bibliographic
Functional Requirements encoding)
for Subject Authority Data
28. RDA
RESOURCE DESCRIPTION AND ACCESS
March 31, 2013 will be the implementation date of RDA at the Library of Congress.
At this time all records emanating from the Cataloging Section of the Library of
Congress will follow RDA Rules.
How does that effect the records that we are looking at on OCLC?
29. DIFFERENCES BETWEEN AACR2 AND RDA RECORDS
New fields:
In the 040 “$e RDA” is added.
In the 1XX and 7XX a relator term is added to the Authority Access Point using “$e”. A list of
relator terms can be found at the Library of Congress website.
http://www.loc.gov/marc/relators/relaterm.html
264 field replaces the 260 in RDA records. This allows for more information about
publication, manufacturing, and distribution of a title.
http://www.loc.gov/marc/bibliographic/bd264.html
33X fields are added to replace the “$h” in the 245 field. All of these fields are repeatable.
336 describes the content of the title (text, still image, recorded music…)
http://www.loc.gov/standards/valuelist/rdacontent.html
337 describes the type of access need to use the title (computer, audio, microform…)
http://www.loc.gov/standards/valuelist/rdamedia.html
338 describes the storage medium of the title.
http://www.loc.gov/standards/valuelist/rdacarrier.html
30. DIFFERENCES BETWEEN AACR2 AND RDA RECORDS
Changes and deletions in fields:
In the 245, the “$h” has been replaced by the 33X fields.
The 260 field has been replaced by the various iterations of the 264 field.
No more abbreviations. This includes the Latin abbreviations: et.al., n.d., s.l. …
“Take what you see” – If there is an error in the title, it is used in the 245 as is
with the correct version in a 246. [sic] is not longer used to show and error.
The “Rule of three” is gone. All contributors to the title can be in the 245 $c and
all have 7XX fields.
Can use sentence or title case for title in 245 $a.
Local policy trumps all.
If your ILS requires the “$h” then you should leave it in.
If you want to leave all of your 245 $a in sentence case; you can.
31. MAXWELL'S HANDBOOK FOR AACR2R
=LDR 01203mam a2200313 a 4500
=001 26378
=005 19991015152717.0
=008 970102s1997iluab0010eng
=010 $a 97001449
=020 $a 0838907040 (alk. paper)
=035 $a ocm36245980
=035 $a BBJ8611JS
=040 $a DLC $c DLC $d JUG
=049 $a JUGA
=050 00 $a Z694.15.A56 $b M393 1997
=082 00 $a 025.3/2$221
=099 9 $a A1 M
=100 1 $a Maxwell, Robert L., $d 1957-
=240 10 $a Handbook for AACR2R
=245 10 $a Maxwell's handbook for AACR2R : $b explaining and illustrating the Anglo-American cataloguing rules and the 1993 amendments / $c
Robert L. Maxwell with Margaret F. Maxwell.
=246 30 $a Handbook for AACR2R
=260 $a Chicago, IL : $b American Library Association, $c 1997.
=300 $a xii, 522 p. : $b ill. ; $c 26 cm.
=500 $a Rev. ed. of: Handbook for AACR2 / by Margaret Maxwell. 1989.
=504 $a Includes bibliographical references and index.
=630 00 $a Anglo-American cataloguing rules ; $v Handbooks, manuals, etc.
=650 0 $a Descriptive cataloging$xRules $v Handbooks, manuals, etc.
=700 1 $a Maxwell, Margaret F., $d 1927-
=700 1 $a Maxwell, Margaret F., $d 1927- $t Handbook for AACR2.
34. THE PENNSYLVANIA PUBLIC LIBRARY CODE
(2010)
(AACR2R)
=LDR 01648cam a2200313Ii 4500
=001 1430201
=005 20130108152017.0
=008 110112s2010paus0000engd
=035 $a (OCoLC)ocn696381940
=040 $a PHA $e rda $b eng $c PHA $d PHA
=035 $a (OCoLC)696381940
=037 $b Pennsylvania Joint State Government Commission, 108 Finance Building, Commonwealth Ave. & North St., Harrisburg, PA 17120
=043 $a n-us-pa
=086 $a PGA 88/54/2.2 P976c $2 padocs
=049 $a PHAS
=110 1 $a Pennsylvania. $b General Assembly. $b Joint State Government Commission, $e corporate author.
=245 14 $a The Pennsylvania Public Library Code : $b findings and recommendations / $c General Assembly of the Commonwealth of Pennsylvania, Joint State
Government Commission.
=264 1 $a Harrisburg, Pennsylvania : $b Pennsylvania, Joint State Government Commission, $c 2010.
=300 $a vi, 235 pages ; $c 28 cm
=336 $a text $2 rdacontent
=337 $a unmediated $2 rdamedia
=338 $a volume $2 rdacarrier
=500 $a "December 2010."
=530 $a Also available via the website of the Pennsylvania Joint State Government Commission $u
http://jsg.legis.state.pa.us/resources/documents/ftp/publications/2010-188-SR343%20Library%20Report%201-4-11%20(YH)%201042%20am.pdf
=650 0 $a Public libraries $z Pennsylvania.
=650 0 $a Library legislation $z Pennsylvania.
=650 0 $a Libraries and state $z Pennsylvania.
=856 41 $u http://jsg.legis.state.pa.us/resources/documents/ftp/publications/2010-188-SR343%20Library%20Report%201-4-11%20(YH)%201042%20am.pdf $z The
Pennsylvania Public Library Code : findings and recommendations.
=994 $a C0 $b PHA
35.
36. REPORT OF THE ADVISORY COMMITTEE ON THE CRIMINAL JUSTICE SYSTEM IN PHILADELPHIA
(2013)
(RDA)
=LDR 01810cam a2200325Ii 4500
=001 1505735
=005 20130108153046.0
=008 130108s2013paubs0000engd
=035 $a (OCoLC)ocn823646791
=040 $a PHA $e rda $b eng $c PHA
=035 $a (OCoLC)823646791
=037 $b Pennsylvania Joint State Government Commission, 108 Finance Building, Commonwealth Ave. & North St., Harrisburg,
PA 17120
=043 $a n-us-pa
=086 $a PGA 88.2 C929p $2 padocs
=049 $a PHAS
=110 1 $a Pennsylvania. $b General Assembly. $b Joint State Government Commission. $b Advisory Committee on the Criminal
Justice System in Philadelphia, $e corporate author.
=245 10 $a Report of the Advisory Committee on the Criminal Justice System in Philadelphia / $c General Assembly of the
Commonwealth of Pennsylvania, Joint State Government Commission
=264 1 $a Harrisburg, PA : $b Pennsylvania, Joint State Government Commission, $c 2013.
=300 $a ix, 105 pages ; $c 28 cm
=336 $a text $2 rdacontent
=337 $a unmediated $2 rdamedia
=338 $a volume $2 rdacarrier
=500 $a "January 2013" -- title page.
=504 $a Includes bibliographical references (pages 87-89).
=530 $a Also available via the website of the Pennsylvania Joint State Government Commission $u
http://jsg.legis.state.pa.us/resources/documents/ftp/publications/2013-287-SR%20344%20Report%20-%20Final.pdf
=650 0 $a Criminal justice, Administration of$zPennsylvania$zPhiladelphia.
=650 0 $a Criminal courts$zPennsylvania$zPhiladelphia.
=650 0 $a Court administration$zPennsylvania$zPhiladelphia.
=856 41 $u http://jsg.legis.state.pa.us/resources/documents/ftp/publications/2013-287-SR%20344%20Report%20-
%20Final.pdf $z Report of the Advisory Committee on the Criminal Justice System in Philadelphia.
=994 $a C0 $b PHA
37. THE QUARTER : $B NEWSLETTER OF THE PENNSYLVANIA DEPARTMENT OF BANKING
(2009-)
(RDA)
=LDR 01387nas a2200337Ii 4500
=001 1504914
=005 20121211144122.0
=008 121211c20099999pauqrs00engd
=035 $a (OCoLC)ocn820879061
=040 $a PHA $e rda $b eng $c PHA
=035 $a (OCoLC)820879061
=037 $b Pennsylvania Dept. of Banking and Securities, 17 North Second St., Suite 1300, Harrisburg, PA 17101
=043 $a n-us-pa
=086 $a PBS 1.18/9 $2 padocs
=049 $a PHAS
=110 1 $a Pennsylvania. $b Dept. of Banking, $e corporate author.
=245 14 $a The Quarter : $b newsletter of the Pennsylvania Department of Banking.
=264 1 $a [Harrisburg, Pennsylvania] : $b Pennsylvania Department of Banking, $c 2009-
=300 $a volumes : $b illustrations ; $c 28 cm
=336 $a text $2 rdacontent
=336 $a still image $2 rdacontent
=337 $a unmediated $2 rdamedia
=338 $a volume $2 rdacarrier
=362 1 $a Began with Vol.1, no.1 (October 2009).
=500 $a Description based on Vol.1, no.1 (October 2009); title from masthead.
=500 $a Most recent issue consulted: Vol.4, no.1 (November 2012).
=550 $a Vol. 4 to current published by the Pennsylvania Department of Banking and Securities.
=650 0 $a Banks and banking $z Pennsylvania $v Periodicals.
=650 0 $a Securities $z Pennsylvania $v Periodicals.
=710 1 $a Pennsylvania. $b Dept. of Banking and Securities.
=994 $a C0 $b PHA
38. WILLIAM T. FEE, 1969-
(AACR2 AUTHORITY RECORD)
LC Control Number: no2007117580
HEADING: Fee, William T., 1969-
000 00456cz a2200133n 450
001 7314450
005 20071011052004.0
008 071003n| acannaabn |n aaa c
010 __ |a no2007117580
035 __ |a (OcoLC)oca07541727
040 __ |a P |b eng |c P |d P
100 1_ |a Fee, William T., |d 1969-
670 __ |a Bonsowaaru Dracula-san the Easternization of the Western
vampire in anime, 2006: |b t.p. (William T. Fee)
670 __ |a Conversation with author, Oct. 3, 2007 |b (b. Aug. 13, 1969)
39. WILLIAM T. FEE, 1969-
(RDA AUTHORITY RECORD – SLIDE 1 OF 2)
=LDR 04023cz a2200421n 45 0
=001 oca07541727
=003 OCoLC
=005 20101018024953.0
=008 071003n|azannaabn|aaaac
=010 $a no2007117580
=040 $a P $b eng $c P $d P $e rda
=046 $f 19690813 $v Conversation with author, Oct. 3, 2007
=100 1 $a Fee, William T., $d 1969-
=370 $e Harrisburg (Pa.) $s 1995 $v input by author
=370 $e Halifax (Pa.) $s 1979 $t 1987
=370 $f Lemoyne (Pa.), $s 1995 $t 1996
=370 $f Harrisburg (Pa.) $s 1996 $t 2006
=370 $f Lykens (Pa.) $s 2006
=372 $a Writer (Library science/comic books), $s 2008
=372 $a Tutor (French/Theatre/Art History/Writing), $s 1992 $t 1994
=372 $a Trainer (Digitization), $s 2001
=372 $a Digital Collections and Authority Control Librarian $s 2009
=372 $a Graphical Materials Librarian, $s 2008
=372 $a Digital Collections Librarian, $s 2005 $t 2009
=372 $a Digital Technician, $s 2001 $t 2005
40. WILLIAM T. FEE, 1969-
(RDA AUTHORITY RECORD – SLIDE 2 OF 2)
=373 $a MLIS students, University of Pittsburgh (Pittsburgh, Pa.), $s 2006 $t 2008
=373 $a MA (Humanities) students, Pennsylvania State University (Middletown, Pa.), $s 1999 $t 2006
=373 $a BA (English) students, Mansfield University (Mansfield, Pa.), $s 1989 $t 1994
=373 $a BA (Art History- unfinished) students, Shippensburg University (Shippensburg, Pa.), $s 1988 $t 1989
=373 $a Halifax Area High School (Halifax, Pa.), $s 1983 $t 1987
=374 $a Librarian, $s 2005
=374 $a Library technician, $s 1995 $t 2005
=400 1 $a Fee, William TB, $d 1969-
=670 $a Bonsowaaru Dracula-san the Easternization of the Western vampire in anime, 2006: $b t.p. (William T. Fee)
=670 $a "Do You Have Any Ditko?: Comic Books, MARC, FRBR and Findability", 2008: $b Serials review vol. 34, no 3, first
page of article (William T. Fee, Digital Collections Librarian at the State Library of Pennsylvania)
=670 $a Conversation with author, Oct. 3, 2007 $b (b. Aug. 13, 1969)
=670 $a Input from author, Oct. 12, 2010 $b (Fee has written on a number of topics, especially literary cultural theory
and Japanese culture, and has a number of unpublished manuscripts, including "Hardboiled Cyberpunk & the End of
Magical Realism: A Look at Magical Realism & Cyberpunk Through Haruki Murakami's Hardboiled Wonderland," "Bikes,
'bots and Birmingham: A Subcultural Look at Masamune Shirow's Ghost in the Shell & the Japanese Speed tribes,"
"KAOS KERAUNOS CINEMATOS: A Chaoist Looks at Film and Film Theory," and "The French of Kate Chopin: A Study in
Hidden Message". His current work is in comic book cataloging and FRBR theory and implementation. Fee's specialties
and responsibilities at the State Library of Pennsylvania have included disaster response, digitization and metadata,
and oversight of image cataloging and delivery systems as well as those working within these systems).
=678 0 $a Fee graduated Mansfield University of Pennsylvania cum laude in 1994, where he concentrated in Radical
Literature, Creative Writing. He also completed 43 of 60 program credits in Theatre Management B.A. prior to his
change of major, and was a member of the Committee on Academic Freedom, the International Student Union, the
Flashlight staff, and was editor of Reseris vox, an underground newspaper, from 1993-1994. Fee began at the State
Library of Pennsylvania approximately 1.5 years after his graduation from Mansfield. As of Oct. 12, 2010, Fee lives in
Lykens, Pennsylvania with his wife and 3 children.
41. IT’S THE END OF THE SHOW AS WE KNOW
IT…
“The rabbit-hole went straight on like a tunnel for some way and then dipped
suddenly down, so suddenly that Alice had not a moment to think about
stopping herself before she found herself falling down what seemed to be a very
deep well.”
--Lewis Carroll. Alice’s Adventures in Wonderland (1916), p. 1.
Contact the presenters at:
William Fee – wfee@pa.gov
Mary Spila – mspila@pa.gov
http://www.portal.state.pa.us/portal/server.pt/community/bureau_of_state_library/8811
Presentation available at:
http://www.slideshare.net/WTBFee/
Editor's Notes
Simple 2 line record copied from OCLC record. Newspapers are one of the most promising problems to be solved with FRBR for Serials.
Merger note lives here, because it’s true of all Manifestations.
The meat of the record. Note that, for ease of the patron under MARC (may not be true under MARC replacement), the 580 is repeated here. Contains greyscale and color under 300.
Basket. Solves problem where linking fails because library does not own intervening title or not enough information for 780/785. Included 380 Super-work here (could be Metadata), to differentiate record. Public will likely never see this.
All results search. Would be modified for public consumption.
If this were a serial, it would be the MARC record we’re used to. 780s and 785s live here, as do numbering and merger notes.
Only 3 real lines. If translated versions were available would be more. Need to be really careful about what lives where.VTLS, at least in Sandbox, does not inherit down.
Starting with the simple.In FRBR, one is supposed to work from bottom up. In reality, it’s easier to move work down, then add super-work.Lines copied from OCLC record. Automated frbr-ization is… interesting…
The super-work, or a work of works. Better understood as a basket keeping publication history together.
The cause of my own fascination with FRBR for Serials- comic books. Horror title that became a partially reprinted superhero title that became a circus detective title. Contains the story Library of Horror! Note the Manifestation splits between publishers- this is due to changes in tone. Is, however, a handy grouping.
In this case, 785 lives on Expression because of black and white film that is different enough to be a new expression. Local adaptation.
Reprint volume- the public library “graphic novel”
Charlton as imprint. All are Charlton, but these are the only ones that say it in the indicia.
Pretty standard, but this is how items look in Virtua.
The basket. Shows all 3 titles. Note the 2 Blue Beetle- first 2 are reprints, second 2 originals.