Implementation scenarios, encoding structures and display

1. Implementation scenarios, encoding structures and display Rob Walls Director Database Services Libraries Australia

2. Introduction • Database Implementation Scenarios • Record display - ISBD • MARC 21 • Dublin Core • Bibliographic system changes • Libraries Australia implementation

3. 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

4. Flat file database structure Bibliographic record Name Authority record Name-Title Authority record Holdings/Item record

5. Linked Bibliographic and Authority Records Bibliographic record Name Authority record Name-Title Authority record Holdings/Item record

6. Relational / object-orientated database structure Manifestation Work Access Point Control Record Expression Holdings/Item

7. 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

8. 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

9. ISBD punctuation example

10. 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

11. 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

12. 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

13. 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

14. 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

15. 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

16. 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

17. 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)

18. 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

19. 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

20. 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

21. Bibliographic system changes • Implement support for new/changed MARC 21 data elements: • Cataloguing interface • Record displays • Index definitions

22. OCLC WorldCat • Ex-officio member of ALA Committee on Cataloguing • JSC RDA Examples Groups • RDA/MARC Working Group • ALA RDA Implementation Task Force

23. 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

24. 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

25. Questions?

26. Links • RDA Database Implementation scenarios http://www.collectionscanada.gc.ca/jsc/docs/5editor2.pdf • Encoding RDA data http://www.collectionscanada.gc.ca/jsc/docs/5editor2.pdf • RDA, FRBR/FRAD, and Implementation Scenarios http://www.collectionscanada.gc.ca/jsc/docs/5editor4.pdf • MARC Development web site http://www.loc.gov/marc/development.html • DCMI/RDA Task Group wiki http://dublincore.org/dcmirdataskgroup