348:"The more metadata experience we have, the more it becomes clear that metadata perfection is not attainable, and anyone who attempts it will be sorely disappointed. When metadata is crosswalked between two or more unrelated sources, there will be data elements that cannot be reconciled in an ideal manner. The key to a successful metadata crosswalk is intelligent flexibility. It is essential to focus on the important goals and be willing to compromise to reach a practical conclusion to projects."
109:(TEI), and other metadata schemes. For example, an archive has a MARC record in its catalog describing a manuscript. Suppose the archive makes a digital copy of that manuscript and wants to display it on the web along with the information from the catalog. In that case, it will have to translate the data from the MARC catalog record into a different format, such as
217:
Simple Dublin Core only has one "Title" element, so all of the different types of MARC titles get lumped together without further distinctions. This is called "many-to-one" mapping. This is also why once you've translated these titles into Simple Dublin Core, you can't translate them back into MARC.
133:
One of the biggest challenges for crosswalks is that no two metadata schemes are 100% equivalent. One scheme may have a field that doesn't exist in another scheme or a field that is split into two different fields in another scheme; this is why you often lose data when mapping from a complex scheme
124:
Crosswalks also have several technical capabilities. They help databases using different metadata schemes to share information. They help metadata harvesters create union catalogs. They enable search engines to search multiple databases simultaneously with a single query.
113:, that is viewable on a webpage. Because MARC has various fields than MODS, decisions must be made about where to put the data into MODS. This type of "translating" from one format to another is often called "metadata mapping" or "field mapping," and is related to "
218:
Once they're Simple Dublin Core, you've lost the MARC information about what types of titles they are, so when you map from Simple Dublin Core back to MARC, all the data in the "Title" element maps to the basic MARC 245 Title
Statement field.
104:
Crosswalks show people where to put the data from one scheme into a different scheme. They are often used by libraries, archives, museums, and other cultural institutions to translate data to or from MARC standards, Dublin Core,
301:
This is why crosswalks are said to be "lateral" (one-way) mappings from one scheme to another. Separate crosswalks would be required to map from scheme A to scheme B and from scheme B to scheme A.
313:
One scheme has one element that needs to be split up with different parts of it placed in multiple other elements in the second scheme ("one-to-many" mapping)
490:
316:
One scheme allows an element to be repeated more than once while another only allows that element to appear once with multiple terms in it
134:
to a simpler one. For example, when mapping from MARC to Simple Dublin Core, you lose the distinction between types of titles:
433:"Metadata in Practice" Diane I. Hillmann and Elaine L. Westbrooks, eds., American Library Association, Chicago, 2004, p. 91.
110:
458:
485:
500:
415:
446:
480:
106:
36:
407:
401:
330:
An element in one scheme is indexed, but the equivalent element in the other scheme is not
8:
28:
495:
411:
464:
452:
118:
21:
465:"Metadata Interoperability and Standardization - A Study of Methodology Part I"
47:
31:, especially when multiple systems are interfaced or when the system includes
474:
32:
24:. It maps the elements in one schema to the equivalent elements in another.
358:
114:
342:
Crosswalking
Citation Metadata: The University of California's Experience,
51:
20:
is a table that shows equivalent elements (or "fields") in more than one
387:
368:
363:
43:
390:
Network
Development and MARC Standards Office, Library of Congress
35:
data. In the context of
Interfaces, they function as an internal
340:
Some of these problems are not fixable. As Karen Coyle says in "
27:
Crosswalk tables are often employed within or in parallel to
406:. Chicago: American Library Association. pp.
333:Schemes may use different controlled vocabularies
70:$ 260c (Date of publication, distribution, etc.)
472:
447:"Metadata Crosswalk Depository" (SchemaTrans)
128:
459:"Crosswalks the Path to Universal Access?"
319:Schemes have different data formats (e.g.
304:
403:Metadata fundamentals for all librarians
336:Schemes change their standards over time
473:
399:
491:Library cataloging and classification
309:Other mapping problems arise when:
13:
453:"Mapping Between Metadata Formats"
111:Metadata Object Description Schema
14:
512:
440:
388:"Dublin Core to MARC Crosswalk,"
81:522 (Geographic Coverage Note)
424:
393:
381:
92:$ 300a (Physical Description)
1:
374:
7:
352:
10:
517:
400:Caplan, Priscilla (2003).
129:Challenges for crosswalks
486:Knowledge representation
107:Text Encoding Initiative
37:extract, transform, load
501:Technical communication
305:Difficulties in mapping
42:For example, this is a
350:
150:210 Abbreviated Title
346:
183:242 Translated Title
295:245 Title Statement
284:245 Title Statement
273:245 Title Statement
262:245 Title Statement
251:245 Title Statement
240:245 Title Statement
224:Dublin Core element
194:245 Title Statement
145:Dublin Core element
65:Dublin Core element
205:246 Variant Title
172:240 Uniform Title
29:enterprise systems
299:
298:
215:
214:
102:
101:
87:Coverage.Spatial
39:(ETL) mechanism.
508:
434:
428:
422:
421:
397:
391:
385:
221:
220:
137:
136:
119:semantic mapping
57:
56:
18:schema crosswalk
516:
515:
511:
510:
509:
507:
506:
505:
481:Data management
471:
470:
443:
438:
437:
429:
425:
418:
398:
394:
386:
382:
377:
355:
307:
131:
46:crosswalk from
22:database schema
12:
11:
5:
514:
504:
503:
498:
493:
488:
483:
469:
468:
462:
456:
450:
442:
441:External links
439:
436:
435:
423:
416:
392:
379:
378:
376:
373:
372:
371:
366:
361:
354:
351:
338:
337:
334:
331:
328:
317:
314:
306:
303:
297:
296:
293:
290:
286:
285:
282:
279:
275:
274:
271:
268:
264:
263:
260:
257:
253:
252:
249:
246:
242:
241:
238:
235:
231:
230:
227:
225:
213:
212:
209:
206:
202:
201:
198:
195:
191:
190:
187:
184:
180:
179:
176:
173:
169:
168:
165:
162:
161:222 Key Title
158:
157:
154:
151:
147:
146:
143:
141:
130:
127:
100:
99:
98:Format.Extent
96:
93:
89:
88:
85:
82:
78:
77:
74:
71:
67:
66:
63:
61:
48:MARC standards
9:
6:
4:
3:
2:
513:
502:
499:
497:
494:
492:
489:
487:
484:
482:
479:
478:
476:
466:
463:
460:
457:
454:
451:
448:
445:
444:
432:
427:
419:
413:
409:
405:
404:
396:
389:
384:
380:
370:
367:
365:
362:
360:
357:
356:
349:
345:
343:
335:
332:
329:
326:
322:
318:
315:
312:
311:
310:
302:
294:
291:
288:
287:
283:
280:
277:
276:
272:
269:
266:
265:
261:
258:
255:
254:
250:
247:
244:
243:
239:
236:
233:
232:
228:
226:
223:
222:
219:
210:
207:
204:
203:
199:
196:
193:
192:
188:
185:
182:
181:
177:
174:
171:
170:
166:
163:
160:
159:
155:
152:
149:
148:
144:
142:
139:
138:
135:
126:
122:
120:
116:
112:
108:
97:
94:
91:
90:
86:
83:
80:
79:
76:Date.Created
75:
72:
69:
68:
64:
62:
59:
58:
55:
53:
49:
45:
40:
38:
34:
33:legacy system
30:
25:
23:
19:
430:
426:
402:
395:
383:
359:Meta element
347:
341:
339:
324:
320:
308:
300:
216:
132:
123:
115:data mapping
103:
41:
26:
17:
15:
229:MARC field
140:MARC field
60:MARC field
52:Dublin Core
475:Categories
417:0838908470
375:References
325:Doe, John
496:Metadata
369:Database
364:Metadata
353:See also
321:John Doe
117:", and "
44:metadata
467:(D-Lib)
461:(Getty)
455:(UKOLN)
449:(OCLC)
414:
289:Title
278:Title
267:Title
256:Title
245:Title
234:Title
211:Title
200:Title
189:Title
178:Title
167:Title
156:Title
412:ISBN
323:or
121:".
50:to
477::
431:in
410:.
408:39
344:"
292:→
281:→
270:→
259:→
248:→
237:→
208:→
197:→
186:→
175:→
164:→
153:→
95:→
84:→
73:→
54::
16:A
420:.
327:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.