Description Discovery Disclosure Rachel Heery r heeryukoln ac

  • Slides: 39
Download presentation
Description, Discovery, Disclosure Rachel Heery <r. heery@ukoln. ac. uk> UKOLN University of Bath http:

Description, Discovery, Disclosure Rachel Heery <r. heery@ukoln. ac. uk> UKOLN University of Bath http: //www. ukoln. ac. uk/metadata/ UKOLN is funded by the British Library Research and Innovation Centre, the Joint Information Systems Committee of the Higher Education Funding Councils, as well as by project funding from the JISC’s Electronic Libraries Programme and the European Union. UKOLN also receives support from the University of Bath where it is based.

Outline Description definitions Discovery metadata typology Dublin Core metadata creation subject gateways Disclosure metadata

Outline Description definitions Discovery metadata typology Dublin Core metadata creation subject gateways Disclosure metadata registries

Definitions (1). . data about data. . structured, machine readable data. . data which

Definitions (1). . data about data. . structured, machine readable data. . data which supports operations carried out on information objects

Definitions (2) What does metadata describe? “… machine understandable information about web resources or

Definitions (2) What does metadata describe? “… machine understandable information about web resources or other things” - Tim Berners-Lee (World Wide Web Consortium) digital resources and physical resources?

Metadata supports. . . • resource discovery • authentication • data management • rights

Metadata supports. . . • resource discovery • authentication • data management • rights management • digital preservation • content rating services

Discovery. . 6

Discovery. . 6

Metadata for resource discovery Provides support for: • searching • location • retrieval (delivery)

Metadata for resource discovery Provides support for: • searching • location • retrieval (delivery) • description May enable: • Semantic interoperability • Interworking systems

Diversity of formats and protocols Metadata is structured according to standards: MARC, EAD, CIMI,

Diversity of formats and protocols Metadata is structured according to standards: MARC, EAD, CIMI, TEI …. Dublin Core XML, RDF Metadata is searched using protocols: Z 39. 50, whois++, LDAP Glossary available at http: //www. ukoln. ac. uk/metadata/glossary/

A metadata typology Simple Rich

A metadata typology Simple Rich

USMARC record Extract from USMARC record ……. 111 2$a. Seminar on Cataloging Digital Documents

USMARC record Extract from USMARC record ……. 111 2$a. Seminar on Cataloging Digital Documents $d(1994 : $c. University of Virginia Library and Library of Congress) 245 10$a. Proceedings of the Seminar on Cataloging Digital Documents, October 12 -14, 1994 $h{computer file} /$c. University of Virginia Library, Charlottesville, and the Library of Congress. 256 $a. Computer data and program. 260 $a{Washington, D. C. : $b. Library of Congress, $c 1994}. 538 $a. Access: Internet. Address: http: //lcweb. loc. gov/catdir/semdigdocs/seminar. html. 500 $a. Title from title screen. 500 $a"Sponsor: Sarah Thomas, director for cataloging, Library of Congress"--Home page. …………. Extract from: Guidelines for the Use of Field 856. Network Development and MARC Standards Office, Library of Congress. Revised March 1996

TEI header <TEIHEADER><FILEDESC> <TITLESTMT><TITLE>Liberty Lyrics (1895): a machine-readable transcription</TITLE> <AUTHOR>Bevington, Louisa Sarah (Guggenberger) (1845?

TEI header <TEIHEADER><FILEDESC> <TITLESTMT><TITLE>Liberty Lyrics (1895): a machine-readable transcription</TITLE> <AUTHOR>Bevington, Louisa Sarah (Guggenberger) (1845? )</AUTHOR> <RESPSTMT><RESP>Transcribed and encoded by </RESP> <NAME>Felix Jung</NAME></RESPSTMT> <RESPSTMT><RESP>Edited by </RESP> <NAME>Perry Willett</NAME></RESPSTMT></TITLESTMT> <EXTENT>TEI formatted filesize uncompressed&colon; 1426 bytes</EXTENT> <PUBLICATIONSTMT> <PUBLISHER>Library Electronic Text Resource Service (LETRS), Indiana University</PUBLISHER> <DATE>September 22, 1995</DATE> <AVAILABILITY><P>© 1995, The Trustees of Indiana University makes a claim of copyright only to original contributions

ROADS Template-Type: SERVICE Handle: 871473886 -23884 Title: Wellcome Unit for the History of Medicine

ROADS Template-Type: SERVICE Handle: 871473886 -23884 Title: Wellcome Unit for the History of Medicine URI-v 1: http: //units. ox. ac. uk/ Admin-Email-v 1: wuhmo@wuhmo. ox. ac. uk Publisher-Name-v 1: Wellcome Unit for the History of Medicine Publisher-Postal-v 1: 45 -47 Banbury Road, Oxford, OX 2 6 PE Publisher-City-v 1: Oxford Description: The home page of the Wellcome Unit for the History of Medicine this site provides information on the Unit, seminars, . . Keywords: History of Medicine; Medicine Language-v 1: English Subject-Descriptor-v 1: WZ 40 History of Medicine Subject-Descriptor-Scheme-v 1: NLM Record-Last-Modified-Date: Fri, 10 Oct 1997 19: 09: 16 +0000 Record-Created-Date: Fri, 10 Oct 1997 19: 09: 16 +0000

Dublin Core …. . An instance of resource discovery metadata 13

Dublin Core …. . An instance of resource discovery metadata 13

What is the Dublin Core? • widespread consensus • 15 element metadata set •

What is the Dublin Core? • widespread consensus • 15 element metadata set • simple set for untrained creators • base set for semantic interoperability • web-based document-like objects?

Dublin Core history • workshop series - DC-1 (1995) to DC-6 • email discussion

Dublin Core history • workshop series - DC-1 (1995) to DC-6 • email discussion lists (Mailbase) • RFC 2413 - DC core elements http: //src. doc. ic. ac. uk/computing/internet/rfc 2413. txt • submission to NISO (…ISO) • DC home page http: //purl. oclc. org/dc/

Dublin Core elements • 15 element core metadata set • • 16 Title Subject

Dublin Core elements • 15 element core metadata set • • 16 Title Subject Description Creator Publisher Contributor Date Type • • Format Identifier Source Language Relation Coverage Rights

Dublin Core Qualified • refine the meaning of elements using ‘type’: • Relation TYPE=Is.

Dublin Core Qualified • refine the meaning of elements using ‘type’: • Relation TYPE=Is. Part. Of • associate value with externally defined ‘scheme’: • Subject SCHEME=LCSH • Date SCHEME=ISO 8601 • indicate ‘language’ of value • Title LANGUAGE=en

DC in HTML <HTML><HEAD> <TITLE>UKOLN Home Page</TITLE> <META NAME="DC. Title” CONTENT="UKOLN: UK Office for

DC in HTML <HTML><HEAD> <TITLE>UKOLN Home Page</TITLE> <META NAME="DC. Title” CONTENT="UKOLN: UK Office for Library and Information Networking"> <META NAME="DC. Subject" CONTENT="national centre, network information support, library community, awareness, research, information services, public library networking, bibliographic management, distributed library systems, metadata, resource discovery, conferences, lectures, workshops"> <META NAME="DC. Description" CONTENT="UKOLN is a national centre for support in network information management in the library and information communities. It provides awareness, research and information services"> <META NAME="DC. Creator" CONTENT=”UKOLN Information Services Group"> </HEAD>. . .

RDF Resource Description Framework • Abstract data model • expressed in XML based syntax

RDF Resource Description Framework • Abstract data model • expressed in XML based syntax • Provides structure (resource, property, value) • Provides common syntax • Provides means to aggregate metadata modules http: //www. w 3. org/TR/REC-rdf-syntax/

DC in RDF http: //www. ukoln. ac. uk/metadata/ DC: Title The UKOLN Metadata Home

DC in RDF http: //www. ukoln. ac. uk/metadata/ DC: Title The UKOLN Metadata Home Page <? xml: namespace ns="http: //purl. org/dublin_core/schema/" prefix=”DC"? > <RDF: RDF> <RDF: Description RDF: HREF=”http: //www. ukoln. ac. uk/metadata/”> <DC: Title>The UKOLN Metadata Home Page</DC: Title> </RDF: Description> </RDF: RDF>

DC in XML-RDF <rdf: RDF xmlns: rdf="http: //www. w 3. org/TR/WD-rdf-syntax#” xmlns: dc="http: //purl.

DC in XML-RDF <rdf: RDF xmlns: rdf="http: //www. w 3. org/TR/WD-rdf-syntax#” xmlns: dc="http: //purl. org/dc/elements/1. 0/"> <rdf: Description about="http: //www. ukoln. ac. uk/metadata/" dc: Title="UKOLN metadata homepage” dc: Subject="metadata; BIBLINK; DESIRE; News. Agent; ROADS; PRIDE; Cedars; Dublin Core; DC; Z 39. 50; WHOIS++" dc: Publisher="UKOLN, University of Bath" dc: Type="Text" dc: Format="text/html - 4847 bytes" > <dc: Creator> <rdf: Bag rdf: _1="Michael Day” rdf: _2="Andy Powell" /> </dc: Creator> <dc: Identifier> <rdf: Bag rdf: _1="http: //purl. org/net/ukoln/metadata" rdf: _2="http: //purl. eu. org/net/ukoln/metadata" /> </dc: Identifier> </rdf: Description> </rdf: RDF>

Metadata creation. . 22

Metadata creation. . 22

Who creates metadata? Resource creators • author • webmaster • institution Service providers •

Who creates metadata? Resource creators • author • webmaster • institution Service providers • search services • third parties • commercial publishers • hand crafted • robot generated 23 11/28/2020

Metadata creation editors DC dot (UKOLN) http: //www. ukoln. ac. uk/metadata/dcdot/ Reggie (DSTC) http:

Metadata creation editors DC dot (UKOLN) http: //www. ukoln. ac. uk/metadata/dcdot/ Reggie (DSTC) http: //metadata. net Nordic Metadata Template (Nordic Web Index) http: //www. lub. lu. se/cgi-bin/nmdc. pl

Metadata creation robots Search engine robots AC/DC UK Academic Directory - Harvest http: //acdc.

Metadata creation robots Search engine robots AC/DC UK Academic Directory - Harvest http: //acdc. hensa. ac. uk/index. shtml Nordic Web Index - Combine metadata aware robot http: //nwi. ub 2. lu. se/

BIBLINK …. . An instance of a metadata creation system 26

BIBLINK …. . An instance of a metadata creation system 26

BIBLINK Aim Establish information flow between electronic publishers and National Bibliographic Agencies Achieved by

BIBLINK Aim Establish information flow between electronic publishers and National Bibliographic Agencies Achieved by Establishing workspace Management of database of records Searching and downloading of records http: //www. ukoln. ac. uk/metadata/BIBLINK/

BIBLINK Workspace Interfaces Email or HTTP (Web) user interface Input formats: • Dublin Core

BIBLINK Workspace Interfaces Email or HTTP (Web) user interface Input formats: • Dublin Core in HTML • two SGML DTDs Export views • Dublin Core in HTML • two SGML DTDs • MARC (various flavours) Administrator Web interface • user registration, access control, mapping tables, configuration, . . .

Description of BIBLINK Workspace Publishers Third parties BIBLINK Workspace A shared facility for storing

Description of BIBLINK Workspace Publishers Third parties BIBLINK Workspace A shared facility for storing and manipulating BIBLINK workspace records BIBLINK Workspace Administrator e. g. Identification agencies - ISBN, ISSN, etc. National Bibliographic Agencies

Search services. . 30

Search services. . 30

Search Service models Geographic coverage: global service regional service Domain coverage subject sector 31

Search Service models Geographic coverage: global service regional service Domain coverage subject sector 31 Business models: commercial institutional collaborative centralised Selection criteria: quality language target audience

Subject gateways. . . 32

Subject gateways. . . 32

ROADS Resource Organisation and Discovery in Subject-based Services Web based tools for Subject Services

ROADS Resource Organisation and Discovery in Subject-based Services Web based tools for Subject Services • SOSIG, ADAM, OMNI, … plus Manage and search Internet resource descriptions • ROADS templates (based on IAFA templates) • WHOIS++ directory service protocol http: //www. ukoln. ac. uk/roads/

Roads Template Types In original RFC: New types: SERVICE PROJECT EVENT DUBLIN CORE DOCUMENT

Roads Template Types In original RFC: New types: SERVICE PROJECT EVENT DUBLIN CORE DOCUMENT SOFTWARE DATASET MAILING LIST …. . . 34 COLLECTION (under development)

ROADS template Template-Type: SERVICE Handle: 871473886 -23884 Title: Wellcome Unit for the History of

ROADS template Template-Type: SERVICE Handle: 871473886 -23884 Title: Wellcome Unit for the History of Medicine URI-v 1: http: //units. ox. ac. uk/ Admin-Email-v 1: wuhmo@wuhmo. ox. ac. uk Publisher-Name-v 1: Wellcome Unit for the History of Medicine Publisher-Postal-v 1: 45 -47 Banbury Road, Oxford, OX 2 6 PE Publisher-City-v 1: Oxford Description: The home page of the Wellcome Unit for the History of Medicine this site provides information on the Unit, seminars, . . Keywords: History of Medicine; Medicine Language-v 1: English Subject-Descriptor-v 1: WZ 40 History of Medicine Subject-Descriptor-Scheme-v 1: NLM Record-Last-Modified-Date: Fri, 10 Oct 1997 19: 09: 16 +0000 Record-Created-Date: Fri, 10 Oct 1997 19: 09: 16 +0000

Disclosure: registries 36

Disclosure: registries 36

Metadata registries Objectives • Definitions • Mappings • Information Users • Human • Software

Metadata registries Objectives • Definitions • Mappings • Information Users • Human • Software Enable • Tool creation • Further automation

ROADS registry RECCI Template Registry • Cataloguing Guidelines • Definitive lists of template types

ROADS registry RECCI Template Registry • Cataloguing Guidelines • Definitive lists of template types and elements • Interoperability guidelines • Template usage statistics • Recommendations for collaborative cataloguing 38 • Rules for content (schemes) • Change control

Future Move from projects to services Wider deployment Resource discovery: integration into learning environments

Future Move from projects to services Wider deployment Resource discovery: integration into learning environments targeted, personalised services Core metadata sets for …. . Metadata complex digital objects