Top Banner
Implementation scenarios, encoding structures and display Rob Walls Director Database Services Libraries Australia
26

Implementation scenarios, encoding structures and display

Jan 02, 2016

Download

Documents

kermit-slater

Implementation scenarios, encoding structures and display. Rob Walls Director Database Services Libraries Australia. Introduction. Database Implementation Scenarios Record display - ISBD MARC 21 Dublin Core Bibliographic system changes Libraries Australia implementation. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Implementation scenarios, encoding structures and display

Implementation scenarios, encoding structures and display

Rob WallsDirector

Database ServicesLibraries Australia

Page 2: Implementation scenarios, encoding structures and display

Introduction

• Database Implementation Scenarios

• Record display - ISBD

• MARC 21

• Dublin Core

• Bibliographic system changes

• Libraries Australia implementation

Page 3: Implementation scenarios, encoding structures and display

RDA Database Implementation Scenarios

• RDA is a content standard

• RDA is not a display or encoding standard

• RDA is not prescriptive as to the data structures that are used to create, exchange, store or access the metadata

Page 4: Implementation scenarios, encoding structures and display

Flat file database structure

Bibliographic record

Holdings/Item record

Name-TitleAuthority record

NameAuthority record

Page 5: Implementation scenarios, encoding structures and display

Linked Bibliographic and Authority Records

Bibliographic record

Holdings/Item record

Name-TitleAuthority record

NameAuthority record

Page 6: Implementation scenarios, encoding structures and display

Relational / object-orientated database structure

Work

Holdings/Item

Manifestation

Expression

Access Point Control Record

Page 7: Implementation scenarios, encoding structures and display

RDA Database Implementation Scenarios

• New database structures needed to realise the full potential of RDA

• Improve efficiency of cataloguing

• Improve searching and browsing for users

Page 8: Implementation scenarios, encoding structures and display

Record Display

• Unlike AACR, RDA doesn’t specify record display format – it will include examples of RDA data in various display formats

• This reflects the real world in which display formats are determined by library managers, system designers and system capability

• Guidelines on ISBD presentation

Page 9: Implementation scenarios, encoding structures and display

ISBD punctuation example

ISBD Area / Element Punctuation RDA Element

1. Title and statement of responsibility area

1.1. Title proper 2.3.1 Title proper

1.2. General material designation [ ] 3.2 Media type

6.10 Content type

1.3. Parallel title = 2.3.2 Parallel title

1.4. Other title information : 2.3.3 Other title information

1.5. Statements of responsibility

First statement / 2.4.1 Statement of responsibility relating to title

Subsequent statement ; 2.4.1 Statement of responsibility relating to title

Page 10: Implementation scenarios, encoding structures and display

RDA/MARC Working Group

• MARC21 should be neutral regarding FRBR entities and database design

• The proposals can be found at: http://www.loc.gov/marc/marbi/list-p.html#2008

• The discussion papers can be found at: http://www.loc.gov/marc/marbi/list-dp.html#2008

Page 11: Implementation scenarios, encoding structures and display

MARC 21 changes

• More information about MARC 21 changes early in 2009

• Relatively minor changes need to support the initial implementation of RDA

• Mappings of RDA data elements to ISBD, MARC21 and Dublin Core will be included in RDA

Page 12: Implementation scenarios, encoding structures and display

MARC 21 changes

• New subfields for 502 (Dissertation note)– $b Degree type– $c Name of granting institution– $d Year degree granted– $o Dissertation identifier– $g Miscellaneous information

Page 13: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• New field (tag 011) in the Bibliographic and Authority formats to identify which of the FRBR entities is represented by the record

• 011 ## $aexpression $2rda

Page 14: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• A new field in the Bibliographic and Authority formats for Content Type, Carrier type and Media type– 336 $aContent $b Media $cCarrier

• Or separate fields for each– 336 Content type– 337 Media type– 338 Carrier type

• 336 ## $aperformed music $baudio $caudio disc $2rda

Page 15: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• New subfields for 340 (Physical medium)– $j Generation– $k Layout– $l Color– $m Foliation– $n Font size– $o Polarity– $p Reduction ratio– $q Digital file encoding format– $r Presentation format for motion picture– $2 Source of controlled terms

Page 16: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• New subfield for 500 (General note)– $i Display text– 500 ## $iMount:$aMounted on starched linen– 500 ## $iSource of title proper:$aCaption title

Page 17: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• Controlled lists of terms and coded data– Additional codes for types of Non-projected graphics (007/01)– Additional codes for format of Music (008/20)– Additional codes for primary support materials for Maps, Globes

and Non-projected graphics (007/04)– Additional character position for Text (007/02), Notated Music

(007/02), Non-projected graphic (007/06) and Tactile materials (007/10)

– Additional character position for Videorecordings (007/09)– Additional code for surround sound in Motion picture (007/08),

Videorecording (007/08) and Sound recording (007/04)

Page 18: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• New fields in the Authority format to record additional information:– 046 Special coded dates– 621 Additional places– 622 Address– 623 Field of activity– 624 Affiliation– 625 Occupation– 626 Gender– 627 Additional information about a family– 628 Associated language

Page 19: Implementation scenarios, encoding structures and display

MARC 21 possible changes

• Possible expansion of the MARC relator list to include additional roles identified in RDA

• Support URIs for relator data

• Addition of subfield $4 (Relator code) to the Authority format

Page 20: Implementation scenarios, encoding structures and display

Dublin Core

• DCMI/RDA Task Group• RDA Element Vocabulary

– RDA metadata entities (elements, attributes)• E.g. “Title”, “Content type”

– RDA value vocabularies (terms)• E.g. “spoken word”, “microform” (media type)

• Enable RDA entities to be used in Semantic Web applications/by computers as well as people

• DC Application Profile for RDA

Page 21: Implementation scenarios, encoding structures and display

Bibliographic system changes

• Implement support for new/changed MARC 21 data elements:– Cataloguing interface– Record displays– Index definitions

Page 22: Implementation scenarios, encoding structures and display

OCLC WorldCat

• Ex-officio member of ALA Committee on Cataloguing

• JSC RDA Examples Groups

• RDA/MARC Working Group

• ALA RDA Implementation Task Force

Page 23: Implementation scenarios, encoding structures and display

Libraries Australia

• Will support the creation and exchange of RDA data from the agreed Australian implementation date

• Continued support for exchange of AACR2 data

• Cataloguing policy will allow AACR records to be upgraded to RDA

Page 24: Implementation scenarios, encoding structures and display

Libraries Australia

• Global change programs to convert AACR records to RDA

• Provide users with as much notice as possible of the changes to the data format and cataloguing policy

• Changes will be reflected in training courses and system documentation

• We aim to provide a training system that supports RDA well in advance of the formal Australian RDA implementation date

Page 25: Implementation scenarios, encoding structures and display

Questions?

Page 26: Implementation scenarios, encoding structures and display

Links• RDA Database Implementation scenarios

http://www.collectionscanada.gc.ca/jsc/docs/5editor2.pdf

• Encoding RDA datahttp://www.collectionscanada.gc.ca/jsc/docs/5editor2.pdf

• RDA, FRBR/FRAD, and Implementation Scenarioshttp://www.collectionscanada.gc.ca/jsc/docs/5editor4.pdf

• MARC Development web sitehttp://www.loc.gov/marc/development.html

• DCMI/RDA Task Group wiki http://dublincore.org/dcmirdataskgroup