EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

140
eXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO

Transcript of EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Page 1: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

eXtensible Catalog

Software PortfolioBen Anderson, Software Engineer, XCO

Page 2: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

eXtensible Catalog is…

2

eXtensible Catalog (XC) is open source, user-centered, next generation software for libraries.

XC provides a discovery interface and a set of tools for libraries to manage metadata and build applications.

Page 3: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Software Overview

• User Interface: – Faceted, FRBRized, customizable search interface– Web application framework for libraries

• Metadata Tools: – Automated metadata processing: Enable libraries to aggregate metadata and run services on it

• XC Schema– New XML schema with Dublin Core terms, RDA elements and roles, MARC vocabularies, and XC elements– FRBR levels +: Work, Expression, Manifestation, Holdings, Item

• Connectivity Tools: – Harvest and synchronize metadata with OAI-PMH– Circulation and authentication with NCIP

3

XC Metadata Services Toolkit

XC Metadata Services Toolkit

Metadata Tools

Drupal CMS Drupal CMS

XC Drupal Toolkit

User Interface

ILSILS

XC OAI ToolkitXC OAI Toolkit

XC NCIP Toolkit

XC NCIP Toolkit

Connectivity Tools

Metadata Application

Profile

Metadata Application

Profile

XC Schema

Page 4: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Partners and Contributors

• University of Rochester• The Andrew W. Mellon Foundation• Consortium of Academic and Research Libraries in Illinois (CARLI)• University of Notre Dame • Rochester Institute of Technology• Kyushu University working with NTT-Data• University of North Carolina at Charlotte• Serials Solutions• OCLC• University at Buffalo• Cornell University• Yale University• Ohio State University• Nylink

4

Page 5: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Partners and Contributors

5

Page 6: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Note from Takanori HAYASHIHi, folks,

As all know, great earthquake and tsunami attack East Japan Area (Alsomy library).Many libraries has earthquake destruct.Now, Code4Lib Japan members and other librarians manage and distributeof destruct information about any libraries.http://www45.atwiki.jp/savelibrary/pages/1.html

NHK is broadcasting Japanese information by Ustreamhttp://www.ustream.tv/channel/nhk-world-tvGoogle provide Crisis response service, if your friend in Japan statusis unknown, I recommend use Person Finder and Disaster message boardsprovide by telephone careers.http://www.google.co.jp/intl/en/crisisresponse/japanquake2011.html

And send response to Japanese librarian by twitter, using hachtag #jishinlib

Thank you for very kindness message from all member of c4l by twitteror other, and sending rescue team form USA and other countries.

Please don't worry, hacker is never die :-)

--Takanori HAYASHIAgriculture, Forestry and Fisheries Research Information Technology Center

6

Page 7: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

eXtensible Catalog

User InterfaceXC Drupal Toolkit

Page 8: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Drupal Toolkit

• Discovery interface and library web application platform in one

• Faceted, FRBRized search of XC Schema metadata• Extensive, easy customization• Established open source community• Data-driven web applicatons with web forms

8

Drupal CMS Drupal CMS

XC Drupal Toolkit

User Interface

Page 9: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

9

Page 10: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

10

Page 11: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

11

Page 12: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

12

Page 13: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

13

Page 14: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

14

Page 15: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

15

Page 16: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

16

The XC Schema combines metadata fields from multiple standard schemas (RDA and DC) plus adds new XC schema elements.

Page 17: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

17

Page 18: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Schema Fields

• New XML metadata schema– Dublin Core terms– RDA - 22 elements and 11 roles

designators– XC elements (contain MARC

vocabularies, linking fields, etc)• Subset of RDA chosen to retain the

granularity in current MARC data:– Frequency– Numbering of Serials– Coordinates of Cartographic Content– Plate number (music)

18

DCMI

RDA

XC

Page 19: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Schema Record Types

• FRBR Group 1 Entities +– Work– Expression– Manifestation– Holdings– Item

19

Page 20: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Creating XC Schema data from MARC

20

MARCXMLBibliographic

XCWork

XCExpression

XC Manifestation

XC Holdings

• Parse MARCXML records into linked FRBR-based records

• MARC Holdings records produce XC Holdings records (to preserve MARC granularity)

• All XC records have globally unique identifiers, and a permanent host repository

• Uplinks created

MARCXMLHoldings

OO4 “Uplink”Manifestation Held

Expression Manifested

Work Expressed

Page 21: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

21

Page 22: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

22

Page 23: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

23

Page 24: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

24

Page 25: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

25

Page 26: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

26

Page 27: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

27

Page 28: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

28

Page 29: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

29

Page 30: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

30

Page 31: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

31

Page 32: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

32

Page 33: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

33

Page 34: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

34

Page 35: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

35

Page 36: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

36

Page 37: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

37

Page 38: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

38

Page 39: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

39

Page 40: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

40

Page 41: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

41

Page 42: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

42

Page 43: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

43

Page 44: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

44

Page 45: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

45

Page 46: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

46

Page 47: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

47

Page 48: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

48

Page 49: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

49

Page 50: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

50

Page 51: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

51

Page 52: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

52

Page 53: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

53

Page 54: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

54

Page 55: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

55

Page 56: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

56

Page 57: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

57

Page 58: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

58

Page 59: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

59

Page 60: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

60

Page 61: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

61

Page 62: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

62

Page 63: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

63

Page 64: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

64

Page 65: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

65

Page 66: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

66

Page 67: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

67

Page 68: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

68

Page 69: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

69

Page 70: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

70

Page 71: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

71

Page 72: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

72

Page 73: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

73

Page 74: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

74

Page 75: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

75

Page 76: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

76

Page 77: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

77

Page 78: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

78

Page 79: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

79

Page 80: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

80

Page 81: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

81

Page 82: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

82

Page 83: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

83

Page 84: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

84

Page 85: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

85

Page 86: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

86

Page 87: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

87

Page 88: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

88

Page 89: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

89

Page 90: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

90

Page 91: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

91

Page 92: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

92

Page 93: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

93

Page 94: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

94

Page 95: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

95

Page 96: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

96

Page 97: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

97

Page 98: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

New Default Theme

98

Page 99: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

99

Page 100: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

100

Page 101: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

101

Page 102: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Themes: Kyushu University Library

102

Page 103: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Kyushu - Search results in Japanese

Reasons why these items are shown

Query : America Japan

Translated : Faceted

navigation

103

Page 104: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Anyone in WNYLRC using Drupal?

104

Page 105: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

YES!

• Cattaraugus- Allegany-Erie-Wyoming BOCES, SLS

• Jamestown Community College (Jamestown)• Jamestown Community College (Olean)• Roswell Park Cancer Institute Corp.

+others that are cloaking or using drupal elsewhere besides the main web site

105

Page 106: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata

Metadata Issues and XC Metadata Management Tools

Page 107: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata Issues: Silos

• Users have many starting points for search because all the data is not available in a single system:– Integrated Library Systems– Institutional Repositories– Webpages– Subscription Databases

• Libraries don’t have good options for searching across all of these sources

Usability

Silo

Quality

Format

Silo

Page 108: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata Issues: Quality

• ILS MARC export issues• Cataloging errors and variant practices• End-user generated metadata• Lack of authority control• Libraries don’t have good options for

making use of data at a range of quality levels

Usability

Silo

Quality

Format

Quality

Page 109: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata Issues: Format

• MARC format is everywhere but does not support current metadata needs

• Multiple formats are useful to describe a range of resources, but difficult to search across consistently

• Libraries don’t have good options to try out new standards like RDA

Usability

Silo

Quality

FormatFormat

Page 110: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata Issues: Usability

• ILS OPAC interfaces are deficient in:– Ease of learning / ease of use– Precision and recall– Finding similar and related resources

Usability

Silo

Quality

Format

Usability

Page 111: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Other XCrecords

MMW

MME

MMM

5. Index4. Aggregate3. Transform

Following one MARC record through XC

Steps:1. Convert from raw MARC to MARCXML (minor cleanup)2. Normalize MARCXML (major cleanup)3. Transform from MARCXML to XC (FRBRize)4. Aggregate at each FRBR level (match and merge)5. Index records / create WEMs (one for each unique Manifestation)

111

MARC MARCXML(dirty)

MARCXML(clean)

W

E

M

XC

2. Normalize1. Convert

WEMWEM

Index

Data is ready for searchand faceted browse

XC

merge

W

E

M

match

?

?

?

5. Index4. Aggregate3. Transform2. Normalize1. Convert

Page 112: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Drupal CMS Drupal CMS

XC Metadata Services ToolkitXC Metadata Services Toolkit

XC Software Components

ILSILS

112

XC OAI ToolkitXC OAI Toolkit

5. Index4. Aggregate3. Transform2. Normalize1. Convert

MARCXMLNormalization

MARCXMLNormalization

MARCXML to XCTransformation

MARCXML to XCTransformation XC AggregationXC Aggregation

XC Drupal Toolkit

Usability

Silo

Quality

Format

Usability

Silo

Quality

Format

Usability

Silo

Quality

Format

Quality

Format

Usability

5. Index4. Aggregate3. Transform2. Normalize1. Convert

Format

Silo

Quality

Metadata Issue Handling

Usability

Silo

Page 113: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Software Components

ILSILS

113

1. Convert

Usability

Silo

Quality

Format

1. Convert

Format

Silo

Quality

XC OAI Toolkit

Expose ILS metadata to XC’s next generation catalog interface and metadata tools

Synchronize ongoing changes in ILS records with XC software automatically

Convert raw MARC into MARCXML

Address data and identifier issues

Compatible with most ILSs

XC OAI ToolkitXC OAI Toolkit

Page 114: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Metadata Services Toolkit

New type of staff client for processing large batches of metadata through an orchestrated set of services.

Harvest from multiple sources (silos) to address format and quality issues.

Aggregate and de-dupe metadata.

Automatic synchronization propagates changes in source metadata through services and on to discovery interface.

XC Metadata Services ToolkitXC Metadata Services Toolkit

XC Software Components

114

4. Aggregate3. Transform2. Normalize

MARCXMLNormalization

MARCXMLNormalization

MARCXML to XCTransformation

MARCXML to XCTransformation XC AggregationXC Aggregation

Page 115: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Metadata Services ToolkitXC Metadata Services Toolkit

XC Software Components

115

4. Aggregate3. Transform2. Normalize2. Normalize

MARCXMLNormalization

MARCXMLNormalization

Usability

Silo

Quality

Format

Usability

Quality

MARCXML Normalization Service

• Transform language codes to spelled-out languages: e.g. fre becomes French

• Normalize forms of OCLC numbers so that they are all the same

• Substitute vocabulary terms for format/type of material codes in the MARC record (Leader, 006, 007, 008) to enable building facet values

• Substitute codes for audience level (juvenile, etc.) and type of material (fiction, non-fiction; identifies dissertation/thesis)

• “Deconstructs” LC Subject headings so we can map parts of them to different facets: geographic, genre, topic, etc.

Page 116: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Metadata Services ToolkitXC Metadata Services Toolkit

XC Software Components

116

4. Aggregate3. Transform2. Normalize

MARCXML to XCTransformation

MARCXML to XCTransformation

Usability

Silo

Quality

FormatFormat

Usability

3. Transform

MARCXML to XC Transformation Service

•Parse flat MARC records to create linked FRBR-based records (work, expression, etc.) in XC Schema•One input record results in several output records•Manage relationships between records, including one to many relationships•Creates multiple work and expression records for analytics•Handles “bound-withs” (e.g. two books bound together)

Page 117: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Metadata Services ToolkitXC Metadata Services Toolkit

XC Software Components

117

4. Aggregate3. Transform2. Normalize

XC AggregationXC Aggregation

Usability

Silo

Quality

Format

Usability

4. Aggregate

XC Aggregation Service

•Aggregate records that represent the same resource at:

• Manifestation-level • Work-level (depends on

Authority service)•Manage relationships between records (FRBR entities, etc.)•Enable automated synchronization of updates for records at each FRBR level •Sets stage for future “non-MARC” RDA implementation

Page 118: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Metadata Services ToolkitXC Metadata Services ToolkitXC Metadata Services ToolkitXC Metadata Services ToolkitDrupal CMS Drupal CMS

eXtensible Metadata Services

ILSILS

118

XC OAI ToolkitXC OAI Toolkit

5. Index4. Aggregate3. Transform2. Normalize1. Convert

MARCXMLNormalization

MARCXMLNormalization

MARCXML to XCTransformation

MARCXML to XCTransformation XC AggregationXC Aggregation

XC Drupal Toolkit

5. Index4. Aggregate3. Transform2. Normalize1. Convert

DC / Qualified DCNormalization

DC / Qualified DCNormalization

DC to XCTransformation

DC to XCTransformation

MARCXML / XC Authority

MARCXML / XC Authority

DSpaceDSpace

<other schema> Normalization

<other schema> Normalization

<other> to <other> Transformation

<other> to <other> Transformation

XC to RDF(Linked data out)

XC to RDF(Linked data out)

Page 119: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

XC Drupal Toolkit

•Adds support for library metadata into Drupal (DC and XC schemas)•Apache SOLR index of WEMs to enable faceted, FRBRized results navigation•Single search interface across:

– Library catalog– Digital repository– Website resources

•Extensive customization•Integration with ILS circulation system (via XC NCIP Toolkit)

Drupal CMS Drupal CMS

XC Software Components

119

5. Index

XC Drupal Toolkit

Usability

Silo

Quality

Format

Usability

5. Index

Page 120: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

eXtensible Catalog

Software PortfolioMetadata Services Toolkit

Page 121: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Metadata Services Toolkit (MST) Tasks

• Get metadata into the MST– Add Repositories– Schedule Harvests

• Tell MST what to do with metadata– Install metadata services– Add processing rules

• Verify results / troubleshoot processing– Browse records– View error logs

121

XC Metadata Services Toolkit

XC Metadata Services Toolkit

Metadata Tools

Page 122: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Add Repository

122

Telling the MST about a repository is easy. Assign a name of your choice and enter the URL.

Telling the MST about a repository is easy. Assign a name of your choice and enter the URL.

After adding a repository, the MST will automatically do a “handshake” with it and provide “Success” or “Error” messages for each step in the handshake.

After adding a repository, the MST will automatically do a “handshake” with it and provide “Success” or “Error” messages for each step in the handshake.

When successful, the MST reports on what formats and sets are available in the remote database.

The MST supports all XML schemas, but individual services are schema-specific.

When successful, the MST reports on what formats and sets are available in the remote database.

The MST supports all XML schemas, but individual services are schema-specific.

Page 123: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Schedule Harvest

123

The next step is to schedule the harvesting of metadata from the remote repository.

The next step is to schedule the harvesting of metadata from the remote repository.

Options- Set the schedule- Choose start and end dates- Select sets and formats

Options- Set the schedule- Choose start and end dates- Select sets and formats

Page 124: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Install A Service

124

The next step is to install a metadata service.

A service is a separate program, written in Java, that is managed by the MST.

Services can be downloaded from the XC website or you can write your own by following the developer’s manual.

The next step is to install a metadata service.

A service is a separate program, written in Java, that is managed by the MST.

Services can be downloaded from the XC website or you can write your own by following the developer’s manual.

In order to use a service, you place the downloaded file in a directory by following the MST manual.

This screen can then be used to install the service in the MST.

In order to use a service, you place the downloaded file in a directory by following the MST manual.

This screen can then be used to install the service in the MST.

Page 125: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Add A Processing Rule

125

This example shows two services already installed in this Metadata Services Toolkit (MST): MARC Normalization and MARC-to-XC-Transformation.

This example shows two services already installed in this Metadata Services Toolkit (MST): MARC Normalization and MARC-to-XC-Transformation.

Now we need to tell the MST which metadata records we want proccessed through which services, and in what order. This is called service orchestration.

We will now add a “Processing Rule”

Now we need to tell the MST which metadata records we want proccessed through which services, and in what order. This is called service orchestration.

We will now add a “Processing Rule”

Page 126: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Browse Records

126

“Browse Records” is a feature of the MST that includes faceted browse and full-text search.

The MST has a local copy of all harvested metadata and all metadata produced by each installed service.

“Browse Records” is a feature of the MST that includes faceted browse and full-text search.

The MST has a local copy of all harvested metadata and all metadata produced by each installed service.

Page 127: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Browse Records

127

Library staff use “Browse Records” to verify that services are functioning properly and to debug any issues.

Library staff use “Browse Records” to verify that services are functioning properly and to debug any issues.

Page 128: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Browse Records

128

Navigation to full record display (MST handles display of any XML schema)

Navigation to full record display (MST handles display of any XML schema)

Whenever a record is processed by a service, the original record is preserved and one or more new records may be produced. These records are called successors.

Navigation links take you to predecessor and successor records. In this case, links connect MARC records to their normalized successor. In another case, links connect a normalized MARC record to its successor Work, Expression and Manifestation records.

Whenever a record is processed by a service, the original record is preserved and one or more new records may be produced. These records are called successors.

Navigation links take you to predecessor and successor records. In this case, links connect MARC records to their normalized successor. In another case, links connect a normalized MARC record to its successor Work, Expression and Manifestation records.

Page 129: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: Browse Records

129

Each service can register error messages with the MST upon installation. In this example the MARC Normalization service has attached errors to specific records.

Each service can register error messages with the MST upon installation. In this example the MARC Normalization service has attached errors to specific records.

Errors are facets in the MST. Errors are facets in the MST.

The “i” icon links to a customizable webpage with instructions for staff to address the error.

The “i” icon links to a customizable webpage with instructions for staff to address the error.

Page 130: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: View Full Record

130

Full Record Display: MARC Holdings Record

Administrative metadata managed by the MST

Predecessor and successor links

XML viewer (supports any XML schema)

Full Record Display: MARC Holdings Record

Administrative metadata managed by the MST

Predecessor and successor links

XML viewer (supports any XML schema)

Page 131: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

MST: View Error Logs

131

Log file management system with navigation. Log file management system with navigation.

This page shows MST system log files. Each installed service as well as harvest-in and harvest-out logs are available.

This page shows MST system log files. Each installed service as well as harvest-in and harvest-out logs are available.

Page 132: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

eXtensible Catalog

What’s NextVision for Linked Data

Page 133: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Semantic Web and Linked Data

• The Semantic Web refers to a set of technologies that allow computers to understand the meaning of information on the web

• Linked data is a mechanism for exposing, sharing and connecting data on the web

133

Page 134: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Semantic Web and Linked Data

• If everything has a unique identifier, then information from one website can be related to information from another via a computer program

• Everything includes people, places, things, vocabularies, metadata elements, web documents, …

134

Page 135: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Semantic Web and Linked Data

• A Uniform Resource Identifier (URI) is a string of characters used to identify a name (URN) or an resource on the internet (URL).

• Two kinds of resources– information resources – traditional web things like

documents, images, etc. – non-information resources – these are real world

objects like people, physical products, places, concepts, proteins, etc

135

Page 136: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Turning information into Linked Data

136

Predicate (URI from a defined vocabulary)Subject (URI) Object (URI or literal)

RDF Triple defined:

Information that might be on a webpage, but cannot be readily understood by a computer: “David Lindahl is 40 years old.”

Example #1: Describe something…

foaf:ageDavid Lindahl 40

Step 1: Parse it into a Subject, Predicate, and Object:

http://xc.org/resource/dlindahl 40http://xmlns.com/foaf/spec/#term_age

Step 2: Convert to URI’s:

Page 137: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Turning information into Linked Data

137

Predicate (URI from a defined vocabulary)Subject (URI) Object (URI or literal)

RDF Triple defined:

Information that might be on a webpage, but cannot be readily understood by a computer: “David Lindahl knows Jennifer Bowen.”

Example #2: Define a relationship…

foaf:knowsDavid Lindahl Jennifer Bowen

Step 1: Parse it into a Subject, Predicate, and Object:

http://xc.org/resource/dlindahl http://xc.org/resource/jbowen

http://xmlns.com/foaf/spec/#term_knows

Step 2: Convert to URI’s:

Page 138: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Linking Open Data Cloud

138

Page 139: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Linked Data on XC

• XC Metadata Services Toolkit (MST):– Converts multiple formats into XC Schema• XC Schema is linked data ready• XC Schema uses defined vocabularies (rda, dcterms, xc)

– Persistent OAI-PMH (web services) data repository– Plug-in service architecture can be extended

support RDF technologies

139

Page 140: EXtensible Catalog Software Portfolio Ben Anderson, Software Engineer, XCO.

Download XC software at

eXtensibleCatalog.org