Bengkel Metadata, RDA & Hyperlink PUiTM 2010 Anjuran : BPBPT PTAR Tarikh : 5 April 2010 Tempat : Bilik Seminar PTAR 1 Penceramah : Pn.Hamidah Abdul Rahman Jawatan: Senior Lecturer

1. METADATA: AN INTRODUCTION Presented by: Hamidahbt. HJ. A. Rahman Senior Lecturer Faculty of Information Management UiTMPuncakPerdana Campus 40150 Shah Alam SELANGOR DARUL EHSAN 4/5/2010 1

2. Metadata is structured data which describes the characteristics of a resource. It shares many similar characteristics to the cataloguing that takes place in libraries, museums and archives. The term "meta" derives from the Greek word denoting a nature of a higher order or more fundamental kind. A metadata record consists of a number of pre-defined elements representing specific attributes of a resource, and each element can have one or more values. 4/5/2010 2 What is metadata?

3. What is metadata? Structured data about resources Library catalogues Abstracting and indexing services Archival finding aids Museum documentation Community information Carriers: MARC, HTML, SGML, XML 4/5/2010 3

4. Types of metadata Descriptive Metadata Administrative Metadata Structural Metadata 4/5/2010 4

5. Types of metadata Descriptive Metadata Administrative Metadata Structural Metadata 4/5/2010 5

6. Types of metadata Descriptive Metadata: to serve the purposes of discovery (how one finds a resource), identification (how a resource can be distinguished from other, similar resources), and selection (how to determine that a resource fills a particular need, for example, for the DVD version of a video recording) 4/5/2010 6

7. Types of metadata Administrative Metadata: is information intended to facilitate the management of resources. It can include such information as when and how an object was created,who is responsible for controlling access to or archiving the content, what control or processing activities have been performed in relation to it, and what restrictions on access or use apply. 4/5/2010 7

8. Types of metadata Structural Metadata (SM): can be thought of as the glue that holds compound digital objects together. A book, for example, may have many chapters, each consisting of a set of pages, each page represented by a separate digital file. Structural metadata (SM) is required to record the relationships between physical files and pages, between pages and chapters, and between chapters and the book as a whole. Presentation software uses SM to display Tables of contents and to deliver such functions as going directly to a requested chapter, or to turn pages forward or backward in order. 4/5/2010 8

9. Why use metadata? Metadata provides the essential link between the information creator and the information user. 4/5/2010 9

11. security

12. personal information

13. management information

14. content rating

15. rights management

16. preservation4/5/2010 10

17. Metadata may be deployed in a number of ways: Embedding the metadata in the Web page by the creator or their agent using META tags in the HTML coding of the page As a separate HTML document linked to the resource it describes In a database linked to the resource. The records may either have been directly created within the database or extracted from another source, such as Web pages. 4/5/2010 11

19. AACR2 (Anglo-American Cataloging Rules)

20. GILS (Government Information Locator Service)

21. EAD (Encoded Archives Description) IMS (IMS Global Learning Consortium) AGLS (Australian Government Locator Service) 4/5/2010 12

22. The data will be unusable, unless the encoding scheme understands the semantics of the metadata schema. The encoding allows the metadata to be processed by a computer program. Important schemes include: HTML(Hyper-Text Markup Language) SGML (Standard Generalised Markup Language) XML (eXtensible Markup Language) RDF (Resource Description Framework) MARC (MAchine Readable Cataloging) MIME (Multipurpose Internet Mail Extensions) 4/5/2010 13

23. Markup languages SGML- Standard Generalised Markup Language - controls document formatting for publication XML- Extensible Markup Language - “next generation” SGML HTML- Hyper Text Markup Language - SGML subset, controls display of web pages Tags (usually paired) structure text into elements e.g. headings, paragraphs, lists, etc. <title> </title> <p> </p> <li> </li> 4/5/2010 14

25. Numeric and alpha tags

26. Fixed fields

27. Leader, 001-008, 010-099

28. Variable fields4/5/2010 15

29. MARC – elements 1XX Main entry 2XX Title, SR, edition, publication 3XX Physical description 4XX Series 5XX Notes 6XX Subject access 7XX Added entries 8XX Added entries for series 9XX References and local fields 4/5/2010 16

31. Primary use

32. publishers to Internet booksellers

34. current version Release 2.0 (2001)

35. Elements – XML reference name and tag4/5/2010 17

38. ONIX record <ISBN> 0123456789 </ISBN> <DistinctiveTitle> Alice in Wonderland </Distinctive Title> <Contributor> <ContributorRole> Author </ContributorRole> <PersonNameInverted> Carroll, Lewis </PersonNameInverted> </Contributor> <PublisherName> Collins </PublisherName> <PublicationDate> 2000 </Publication Date> 4/5/2010 19

39. Dublin Core - structure Simple resource discovery DCMES – Dublin Core Metadata Element Set HTML the most common ‘carrier’ Comprises 15 elements with element qualifiers element encoding schemes optional/mandatory elements Application profiles 4/5/2010 20

40. Dublin Core - elements Title Creator Subject Description Publisher Contributor Date Resource Type Format Resource Identifier Source Language Relation Coverage Rights 4/5/2010 21

41. Dublin Core - record <Title> Alice in Wonderland </Title> <Creator> Lewis Carroll </Creator> <Subject> <LCSH> Fiction </LCSH> </Subject> <Publisher> Project Gutenberg </Publisher> <Date> 2000 </Date> <Format> ASCII file via FTP </Format> <Identifier> http://promo.net/pg/….. </Identifier> 4/5/2010 22

44. EAD - structure <ead> <eadheader> </eadheader> <frontmatter> [optional] </frontmatter> <archdesc> <did> </did> </archdesc> </ead> 4/5/2010 24

45. EAD - elements <eadheader> [id + bibliographic inf. for finding aid] <archdesc> [data on a body of archival materials] <did> [container, physical description, physical location, repository, date and title of unit] <admininfo> [biography, scope, access, arrangement] <controlaccess> [name, place, genre, subject, title] </archdesc> 4/5/2010 25

46. EAD record - <header> <ead> <eadheader> <eadid> LKX-3042 </eadid <filedesc> <titlestmt> <titleproper> Pitman Shorthand Collection Catalogue </titleproper> <author> Ann Chapman </author> </titlestmt> <publicationstmt> <date> 1990 </date> <publisher> Bath University Library </publisher> </publicationstmt> </filedesc> </eadheader> 4/5/2010 26

47. EAD record - <archdesc> <archdesc> collection <did> <abstract> A collection of materials in and about shorthand collected by Sir Isaac Pitman and James Pitman</abstract> </did> <controlaccess> <subject encodinganalog=“MARC650”> Shorthand </subject> </controlaccess> </archdesc> </ead> 4/5/2010 27

48. Collection Description Schema developed May 2000 Access version for RSLP – summer 2001 Web version for Reveal – spring 2002 General attributes Subject Dates Associated agents External relationships 4/5/2010 28

49. Coll.Desc. - elements General: title, identifier, description, strength, physical characteristics, language, type, access control, accrual status, legal status, custodial history, note, location Subject: concept, object, name, place, time Dates: accumulation, contents Agents: creator, owner Relationships: sub/super collections, catalogues and descriptions, associated collections and publications 4/5/2010 29

50. Coll. Desc. - record Title: Pitman Collection Strength: Shorthand – national collection Phys. Desc: Printed texts and manuscripts Lang: English, Spanish, Esperanto, …… Access: Written request to the Librarian, Bath Univ. Accrual: passive, deposit Location: The Library, Bath University, Bath Subject: Shorthand, Sir Isaac Pitman Owner: Pitman Publishing Co. Catalogue: Bath University OPAC 4/5/2010 30

51. M21 Community Information Same principles as MARC Bibliographic Leader individual/organization/program/event/other Fixed fields 001-008, 010-099 fixed fields 007 disability facilities 008 special aspects Variable fields 4/5/2010 31

52. M21 Comm. Inf. - elements 1XX Name 2XX Title and Address 3XX Physical description 4XX Series (for events) 5XX Notes 6XX Subject access 7XX Added entries8XX Other variable fields 4/5/2010 32

53. M21 Comm. Inf. - record 110 $a CILIP 245 $a CILIP HQ 247 $a LA HQ $f 19?? - 2002 270 $a 7 Ridgmount St, London, WC1E 7AE $k 020 7255 0505 $m info@cilip.org.uk $r 9am to 6pm 311 $a Ewart Room $d seats 50 $g £100 per day 312 $a Overhead projector $f £10 per day 581 $a Library + Information Update 856 $a http://www.cilip.org.uk 4/5/2010 33

55. ONIX

56. Dublin Core

57. EAD

58. Collection description

59. M21 Community Information4/5/2010 34

60. How does one create metadata? DC-dot - http://www.ukoln.ac.uk/metadata/dcdot/. This service will retrieve a Web page and automatically generate Dublin Core metadata, either as HTML tags or as RDF/XML, suitable for embedding in the section of the page. DCmeta - http://www.dstc.edu.au/RDU/MetaWeb/generic_tool.html. Developed by Tasmania Online. It is based on SuperNoteTab text-editor and can be customised. HotMeta - http://www.dstc.edu.au/Research/Projects/hotmeta/. A package of software, including metadata editor, repository and search engine. 4/5/2010 35

61. ANY QUESTIONS THANK YOU 4/5/2010 36