Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 CS/INFO 430 Information Retrieval Lecture 16 Metadata 3.

Similar presentations


Presentation on theme: "1 CS/INFO 430 Information Retrieval Lecture 16 Metadata 3."— Presentation transcript:

1 1 CS/INFO 430 Information Retrieval Lecture 16 Metadata 3

2 2 Course Administration Assignment 2 and Midterm Examinations Grades were sent out by email yesterday. Assignment 3 Will be posted tomorrow.

3 3 Theoretical Problems in Metadata: What to Catalog The IFLA Model Work A work is the underlying abstraction, e.g., The Iliad The Computer Science departmental web site Beethoven's Fifth Symphony Unix operating system The 1996 U.S. census This is roughly equivalent to the concept of "literary work" used in copyright law.

4 4 IFLA Model Expression. A work is realized through an expression, e.g., The Illiad has oral expressions and written expressions A musical work has score and performance(s). Software has source code and machine code Many works have only a single expression, e.g. a Web page, or a book.

5 5 IFLA Model Manifestation. A expression is given form in one or more manifestations, e.g., The text of The Iliad has been manifest in numerous manuscripts and printed books. A musical performance can be distributed on CD, or broadcast on television. Software is manifest as files, which may be stored or transmitted in any digital medium.

6 6 IFLA Model Item. When many copies are made of a manifestation, each is a separate item, e.g., a specific copy of a book computer file [Works, expressions, manifestations and items are explored in CS 431, Architecture of Web Information Systems.]

7 7 Theoretical Problems in Metadata: : Events Version 1 New material Version 2 Should Version 2 have its own record or should extra information be added to the Version 2 record? How are these represented in Dublin Core or MARC?

8 8 Theoretical Problems in Metadata: : Complex Objects Complex objects Article within a journal Page within a Web site A thumbnail of another image The March 28 final edition of a newspaper Complete object Sub-objects Metadata records

9 9 Theoretical Problems in Metadata: Packaging Rules When an object consists of various parts, how should their interaction be described? Example: An object on the Web may consist of several html pages with images, applets, etc. Metadata Object Description Schema (MODS) http://www.loc.gov/standards/mods/ MPEG 21 http://www.chiariglione.org/mpeg/standards/mpeg-21/mpeg-21.htm

10 10 MPEG 21

11 11 Theoretical Problems in Metadata: Flat v. linked records Flat record All information about an item is held in a single record (e.g., a Dublin Core record), including information about related items convenient for access and preservation information is repeated -- maintenance problem Linked record Related information is held in separate records with a link from the item record less convenient for access and preservation information is stored once Compare with normal forms in relational databases

12 12

13 13 Representations of Dublin Core: XML (with qualifiers) Digital Libraries and the Problem of Purpose David M. Levy Corporation for National Research Initiatives January 2000 article 10.1045/january2000-levy http://www.dlib.org/dlib/january00/01levy.html English Copyright (c) David M. Levy to be continued

14 14 Dublin Core with flat record extension Continuation of D-Lib Magazine record D-Lib Magazine 1082-9873 6 1

15 15 Theoretical Problems in Metadata: Many Languages See: Thomas Baker, Languages for Dublin Core, D-Lib Magazine December 1998, http://www.dlib.org/dlib/december98/12baker.html

16 16 Automatic extraction of catalog data Strategies Manual by trained cataloguers - high quality records, but expensive and time consuming Entirely automatic - fast, almost zero cost, but poor quality Automatic followed by human editing - cost and quality depend on the amount of editing Manual collection level record, automatic item level record - moderate quality, moderate cost

17 17 DC-dot DC-dot is a Dublin Core metadata editor for Web pages, created by Andy Powell at UKOLN http://www.ukoln.ac.uk/metadata/dcdot/ DC-dot has two parts: (a) A skeleton Dublin Core record is created automatically from clues in the web page (b) A user interface is provided for cataloguers to edit the record

18 18

19 19 Automatic record for CS 430 home page DC-dot applied to http://www.cs.cornell.edu/courses/cs430/2001sp/ continued on next slide

20 20 Automatic record for CS 430 home page (continued) DC-dot applied to http://www.cs.cornell.edu/courses/cs430/2001sp/

21 21 Observations on DC-dot applied to CS430 home page DC.Title is a copy of the html field DC.Publisher is the owner of the IP address where the page was stored DC.Subject is a list of headings and noun phrases presented for editing DC.Date is taken from the Last-Modified field in the http header DC.Type and DC.Format are taken from the MIME type of the http response DC.Identifier was supplied by the user as input

22 22

23 23 Observations on DC-dot applied to George W. Bush home page The home page has several meta tags: [The page has no html ] <META NAME="KEYWORDS" CONTENT="George W. Bush, Bush, George Bush, President, republican, 2000 election and more

24 24 DC-dot applied to http://www.georgewbush.com/ continued on next slide Automatic record for George W. Bush home page

25 25 DC-dot applied to http://www.georgewbush.com/ Automatic record for George W. Bush home page (continued)

26 26 Collection-level metadata Several of the most difficult fields to extract automatically are the same across all pages in a web site. Therefore create a collection record manually and combine it with automatic extraction of other fields at item level. See: Jenkins and Inman

27 27 Collection-level metadata Compare: (a) Metadata extracted automatically by DC-dot (b) Collection-level record (c) Combined item-level record (DC-dot plus collection-level) (d) Manual record

28 28

29 29 Metadata extracted automatically by DC-dot D.C. Field Qualifier Content title Digital Libraries and the Problem of Purpose subject not included in this slide publisher Corporation for National Research Initiatives date W3CDTF 2000-05-11 type DCMIType Text format text/html format 27718 bytes identifier http://www.dlib.org/dlib/january00/01levy.html

30 30 Collection-level record D.C. Field Qualifier Content publisher Corporation for National Research Initiatives type article type resource work relation rel-type InSerial relation serial-name D-Lib Magazine relation issn 1082-9873 language English rights Permission is hereby given for the material in D-Lib Magazine to be used for...

31 31 Combined item-level record (DC-dot plus collection-level) D.C. Field Qualifier Content title Digital Libraries and the Problem of Purpose publisher (*) Corporation for National Research Initiatives date W3CDTF 2000-05-11 type (*) article type resource (*) work type DCMIType Text format text/html format 27718 bytes (*) indicates collection-level metadata continued on next slide

32 32 Combined item-level record (DC-dot plus collection-level) D.C. Field Qualifier Content relation rel-type (*) InSerial relation serial-name (*) D-Lib Magazine relation issn (*) 1082-9873 language (*) English rights (*) Permission is hereby given for the material in D-Lib Magazine to be used for... identifier http://www.dlib.org/dlib/january00/01levy.html (*) indicates collection-level metadata

33 33 Manually created record D.C. Field Qualifier Content title Digital Libraries and the Problem of Purpose creator (+) David M. Levy publisher Corporation for National Research Initiatives date publication January 2000 type article type resource work (+) entry that is not in the automatically generated records continued on next slide

34 34 Manually created record D.C. Field Qualifier Content relation rel-type InSerial relation serial-name D-Lib Magazine relation issn 1082-9873 relation volume (+) 6 relation issue (+) 1 identifier DOI (+) 10.1045/january2000-levy identifier URL http://www.dlib.org/dlib/january00/01levy.html language English rights (+) Copyright (c) David M. Levy (+) entry that is not in the automatically generated records

35 35 Search Engine Spam D-Lib Magazine Web pages created for user, with good quality control and no attempt to impress search engines. (The editor originally trained as a librarian.) The site lends itself to automatic indexing. Political Web Sites (Bush and Gore) Web pages created for marketing, with little consistency, designed to impress search engines. (The editors are specialists in public relations.) The sites are difficult to index automatically.

36 36 Metatest Metatest is a research project led by Liz Liddy at Syracuse with participation from the Human Computer Interaction group at Cornell. The aim is to compare the effectiveness as perceived by the user of indexing based on: (a) Manually created Dublin Core (b) Automatically created Dublin Core (higher quality than DC-dot) (c) Full text indexing Preliminary results suggest remarkably little difference in effectiveness.

37 37 Why is Dublin Core not used to Index and Search the Web? Technology: The methods used in early Infoseek, Lycos and Altavista have been greatly enhanced. (Note that these methods provide quite good precision at the expense of low recall.) Users: The typical user who searches the Web has limited training and does not understand catalogs. Economics: The size of the Web makes human indexing of every important site impossible. The rate of change requires frequent re-indexing.

38 38 Why is Dublin Core not used to Index and Search the Web? For Web pages, information retrieval by automatic indexing works of full text works at least as well as metadata based methods, and is much, much cheaper. However, we will see later an effective example of automated extraction of metadata from video sequences (Informedia).


Download ppt "1 CS/INFO 430 Information Retrieval Lecture 16 Metadata 3."

Similar presentations


Ads by Google