VDCIntegration
From Pledge
Contents |
VDC Integration Metadata Processing
In order to prepare the contents of the Virtual Data Center for transmission to DSpace descriptive and administrative metadata needs to be translated out of the DDI schema and into MODS and PREMIS. This metadata will be either referenced or included in METS packages that will also be prepared from each VDC Item's DDI document.
These METS packages will conform to the DSpace METS Document Profile for Submission Information Packages (SIP).
VDC METS Submission Information Package Application Profile
A METS Application Profile is being prepared to describe METS Documents and Packages that are prepared by the VDC for transmission to DSpace. This profile will be a sub-profile of the DSpace METS Document Profile for Submission Information Packages (SIP).
DDI to MODS / DDI to PREMIS Crosswalk
Descriptive metadata for the VDC object that is to become a DSpace Item is drawn from the VDC object's DDI document and translated into MODS according to the crosswalk below.
| Item Metadata Field | MODS Element | DDI No. | DDI Element | Comments on Translation |
|---|---|---|---|---|
| dc.identifier | identifier | 1.1.1.5 | IDNo | @ type = “hdl” |
| dc.description.sponsorship | originInfo.publisher | 1.1.3.1 | producer.ExtLink | Could take from producer or distrbtr |
| dc.title | titleInfo.title | 2.1.1.1 | titl | |
| dc.creator | name.namePart | 2.1.2.1 | AuthEnty | @ type = “personal” ; Multiple names in AuthEnty separated by commas, each name in own name.namePart in MODS |
| dc.publisher | 2.1.3.1 | producer | ||
| dc.date | originInfo.dateCreated | 2.1.3.3 | prodDate | @ encoding = “iso8601” |
| dc.description | abstract | 2.2.2 | abstract | |
| dc.format.extent | physicalDescription.extent | 3.1.4.1 | caseQnty | Have to append “cases” to end of value |
| dc.format.extent | physicalDescription.extent | 3.1.4.2 | varQnty | Have to append “variables” to end of value |
Here is a sample, conforming MODS record.
<mods xmlns="http://www.loc.gov/mods/v3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-2.xsd">
<titleInfo>
<title>Computer Use in Redistricting</title>
</titleInfo>
<identifier type="hdl">hdl:1902.1/AMXGCNKCLU</identifier>
<name type="personal">
<namePart>Micah Altman</namePart>
</name>
<name type="personal">
<namePart>Karin Mac Donald</namePart>
</name>
<name type="personal">
<namePart>Michael P. McDonald</namePart>
</name>
<abstract><p>This is a replication dataset for:<br>
<br>
</p>
<blockquote>Micah Altman, Karin MacDonald, Michael McDonald, 2005.
"From Crayons to Computers: The Evolution of Computer Use in
Redistricting", <em>Social Science Computer Review</em>, Vol. 23,
No. 3, 334-346. DOI: <a href=
"http://dx.doi.org/10.1177/0894439305275855">10.1177/0894439305275855</a></blockquote>
<p>In order to study the use of computers in redistricting, in the
fall of 2004 we surveyed redistricting authorities in all fifty
states concerning their use of computers in the 1990 and 2000
rounds of redistricting. For some states, the information we sought
was provided entirely on a state's redistricting web page. Where
information was inaccessible, we contacted a state's redistricting
authority to locate a person or group of persons willing to respond
to our survey. We found that persons who had worked and retained
accurate information on the 1990 round of redistricting were
difficult to locate. For example, some respondents assured us that
they had used software in 1991 that was not developed until 1998.
We used due diligence in eliminating responses that were obviously
inaccurate and attempted, whenever possible, to conduct follow-up
surveys with additional sources.</p>
<p>This study comprises one dataset, with accompanying
codebook.</p></abstract>
<originInfo>
<publisher>Murray Research Archive</publisher>
<dateCreated encoding="iso8601">2005-09-01</dateCreated>
</originInfo>
<physicalDescription>
<extent>201 cases</extent>
<extent>19 variables</extent>
</physicalDescription>
</mods>
DDI to DSpace Bitstream Metadata via PREMIS Crosswalk
Technical/Administrative metadata for each Bitstream (or file) in the VDC object needs to be drawn from the DDI document and translated into PREMIS for inclusion in a METS SIP. The crosswalk below shows the field in the DSpace bitstream metadata table, its corresponding PREMIS term and the DDI element number and name from which the information is harvested. Files/bitstreams are recorded in diverse sections of the DDI document and so some information that will comprise the Bitstream Metadata may be drawn from either of two sources depending upon the nature of the file/bitstream being cataloged.
| Bitstream Metadata Field | method | PREMIS Term | DDI No. | DDI Element |
|---|---|---|---|---|
| dc.title | getName() | object.originalName | 3.1.1 | fileName |
| 5.1 | labl | |||
| dc.title.alternative | getSource() | object.creatingApplication.creatingApplicationName | 1.1.3.5 | software |
| dc.description | getDescription() | object.objectCharacteristics.significantProperties | 3.1.2 | fileCont |
| 5.2 | txt | |||
| dc.format | getUserFormatDescription() | |||
| dc.format.medium | getFormat().getShortDescription() | |||
| dc.format.mimetype | getFormat().getMIMEType() | object.format.formatDesignation.formatName | ||
| dc.format.supportlevel | getFormat().getSupportLevel() | |||
| dc.format.internal | getFormat().isinternal() | |||
| object.objectCharacteristics.fixity.messageDigest | 3.3 | notes | ||
| object.objectCharacteristics.size |
Here is a sample conforming PREMIS record.
<premis xmlns="http://www.loc.gov/standards/premis"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/standards/premis http://www.loc.gov/standards/premis/PREMIS-v1-0.xsd"> <object> <objectIdentifier> <objectIdentifierType>URL</objectIdentifierType> <objectIdentifierValue>http://vdc.hmdc.harvard.edu/VDC/Repository/0.1/Access/hdl:1902.1/AMXGCNKCLU/idysotihno</objectIdentifierValue> </objectIdentifier> <objectCategory>File</objectCategory> <objectCharacteristics> <fixity> <messageDigestAlgorithm>VDC:UNF</messageDigestAlgorithm> <messageDigest>UNF:3:J0PkMygLPfIyT1E/8xO/EA==</messageDigest> </fixity> <size>1</size> <format> <formatDesignation> <formatName>application/x-stata</formatName> </formatDesignation> </format> <significantProperties>replication data ( tab delimited format, statistics available)</significantProperties> </objectCharacteristics> <creatingApplication> <creatingApplicationName>Virtual Data Center</creatingApplicationName> </creatingApplication> <originalName>amm_replication_data</originalName> </object>
</premis>
