Hi Lisa,
I'm working on a project that sounds extremely similar to what you describe (using an OAI harvester to grab metadata from our eTD server for transformation into MARC and then loading the records into our catalog).
As Terry said, since Dublin Core is a much less precise schema than MARC/AACR2/RDA, the first hurdle is mapping the vagaries of Dublin Core onto the precision of MARC. For example, the data elements available to us on our eTD site include "Graduate Program" and "Keywords." Both are currently mapped to DC element subject, which means the "out of the box" MarcEdit XSLT (OAIDCtoMARCXML.xsl) will transform both elements to MARC field 690. Our practice in the past has been to distinguish between Keywords (which we manually input as 653 fields) and Graduate Program data (which we input as 699 fields). One "solution" would be to change the mapping of the Graduate Program eTD element to a DC element not used elsewhere in our data (e.g. coverage) and then edit the xsl file to have DC element coverage output as MARC 699 (and "subject" as 653 instead of the default 690).
A similar conundrum exists for eTD data elements currently not mapped to DC; in our case, we have "Degree" unmapped to DC. Of course we would like it to end up in a MARC field 502. The only option seems, as above, to map Degree to some unused (and frankly, inappropriate) DC element, e.g. relation (which we happen not to be using for any other eTD data), and then edit the xsl file to map DC relation to MARC 502.
Finally, there's the sticky wicket of all that other MARC data completely absent from the eTD data and handled only very vaguely (if at all) by Dublin Core: 008, 006, 007, 040, etc. Much of this we can add after the fact using MarcEdit as more or less constant data. But how much do we add and how much do we give up on?
Thanks,
Jeff
----- Original Message -----
From: "Lisa Bodenheimer" <[log in to unmask]>
To: [log in to unmask]
Sent: Thursday, February 27, 2014 1:50:24 PM
Subject: [MARCEDIT-L] OAI harvester question
Hi, Terry,
I have a question about the OAI harvester function. I have been testing
MarcEdit as a way to pull OAI metadata for ETDs from our IR, which is
Digital Commons, and convert it to MARC records for our catalog.
In my testing, I’ve noticed that using Dublin Core as the metadata type (and
its corresponding crosswalk) gets me only some of the metadata that I want.
Specifically, I want to include the thesis advisor (or contributor) in my
MARC records. According to what I know (which isn’t a lot—I’m new at this),
the contributor name is part of qualified Dublin Core.
Assuming that what we get is governed by the crosswalk, is it possible to
create either:
a crosswalk that allows both unqualified and qualified Dublin Core to be
pulled from the IR and converted;
or, a function within the harvester that allows for retrieval of all Dublin
Core metadata associated with an item?
If this is possible, I would like to suggest that as an enhancement for
MarcEdit.
Thanks very much for considering this.
Lisa Bodenheimer
Team Leader, Standards Management and Assessment
Technical Services & Collection Management
R.M. Cooper Library
Clemson University
Clemson, SC 29634-3001
864-656-1769 (voice)
864-656-0758 (fax)
[log in to unmask]
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask] To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask] To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]
|