1. NEEO Technical Workshop 2
DIDL/MODS implementation
Sciences Po, Paris
January 15th, 2009
Benoit PAUWELS
Université Libre de Bruxelles (ULB)
Brussels

2. Plan Problem description Implementation at ULB (DSpace)
Round table discussion
Q&A

4. Publication is described as a complex (compound) object
DIDL[1]
Item[1]
Descriptor/Identifier (persistent identifier)
Item[1..∞] (of type descriptiveMetadata)
Descriptor/type (« descriptiveMetadata »)
Component/Resource -- representation by value (XML)
Item[0..∞] (of type objectFile)
Component/Resource -- representation by ref. (URL)
Descriptor/modified
Descriptor/type (« objectFile »)
Item[0..1] (of type humanStartPage)
Descriptor/type (« humanStartPage »)
Data model
Publication is described as a complex (compound) object
persistent identifier
descriptiveMetadata (MODS)
objectFiles
humanStartPage
Extensible
additional items can be stored within the complex object
will be used when implementing metadata enrichment, usage metadata
MODS
contains Digital Author Identifier (DAI) of EO author

5. Mapping an article (DSpace)
Wiley InterScience:
DOI: /j x
Postprint version of this article is present in ULB DSpace

6. Mapping an article (DSpace)
Internal record structure of DSpace == Qualified Dublin Core
title: Intra-firm wage dispersion and firm performance: evidence from linked
employer-employee data
contributor.author: Rycx, François [ ]
contributor.author: Lallemand, Thierry
contributor.author: Plasman, Robert
date.issued: 2004
identifier.citation:  Kyklos (2004), v57 (4), (ISSN: )
identifier.uri: 
DIDL/MODS formatted record available over OAI:

7. Mapping an article (DSpace)
identifier.citation:  Kyklos (2004), v57 (4), (ISSN: )
<mods:relatedItem type="host">
<mods:titleInfo>
<mods:title>Kyklos</mods:title>
</mods:titleInfo>
<mods:identifier type="uri">urn:issn: </mods:identifier>
<mods:part>
<mods:detail type="volume">
<mods:number>57</mods:number>
</mods:detail>
<mods:detail type="issue">
<mods:number>4</mods:number>
<mods:extent unit="pages">
<mods:start>533</mods:start>
<mods:end>558</mods:end>
</mods:extent>
</mods:part>
</mods:relatedItem>

8. Mapping an article (DSpace)
identifier.citation:  Kyklos (2004), v57 (4), (ISSN: )
identifier.citation:  Kyklos (2004), 57, 4, (ISSN: )
identifier.citation:  Kyklos (2004), 57 (4), (ISSN: )
identifier.citation:  Kyklos (2004), vol.57 iss.4, pp (ISSN: )
identifier.citation:  Kyklos (2004), 57, 4 (ISSN: )
Volume Issue 4?
Volume 57 – page 4?
Issue 57 – page 4?
How do you map this to MODS?
IR should hold granular semantically well-defined metadata

9. Implementation at ULB (DSpace)
config/oaicat.properties
Crosswalks.didl=org.dspace.app.oai.DIDLCrosswalk
org.dspace.app.oai.DIDLCrosswalk.java
org.dspace.app.oai.OAIUtil.java
add line to config
copy ULB classes and compile as a start-off
first try DIDLCrosswalk.java with call to MODS routine commented out; and check result through a web browser
correct/adapt above two classes so that it reflects your internal record structure

10. Joseph Greene Re. crosswalks I would be interested in:
-a basic step by step for creating/installing/customizing crosswalks. Locations of config files, crosswalk classes, plugin classes. Been going through this in the DSpace documentation but it would be good to see how you are doing this.
-DSpace 1.4.x includes customizable crosswalks. Could DIDL information stored in tables other than metadatavalue (such as direct link to full-text from the bitstream table) be accessed through these? Where are the classes that read these config files (eg /dspace/config/crosswalks/mods.properties).
-I’m considering storing NEEO authors in a new table to keep family name/given name and DAI separate (DAI is primary key, already stored in individual MD records). What do I modify to get these values into MODS output?

11. Gabriele Horan
Will the normal OAI harvest continue to work if I install the java files (OAIDCCorsswalk, DIDLCrosswalk) etc.? Or
Is the DC-MODS crosswalk that you have written designed to sit along side of the standard OAI harvest without interfering?
I understand well your idea of using the DC fields to encode MODS using the pipe to delimited and letters to identify the MODs metadata.
Technically speaking, in the file OAIUtil.java (which is a totally new file, I believe), where I see for example:
dcvalue.getSubfield("b").value
is this part of the java.util.HashMap?
In theory, if I rewrote my DC metadata in DSPACE as you have described in the technical guidelines, should the crosswalk work on my site without any modifications?
What do you think of the idea of setting up a mirror on the database side of just the collections that we are interested in and setting up a second dspace-oai to look this up specifically for NEEO?
Could I use just one DC field (or one that I extend to my schema for example), and put all the MODS encoded stuff in there, and rewrite your crosswalk?
Do you have any other ideas about how a DSPACE site could implement NEEO when the DSPACE respository is high profile for the University?
Can I wait before doing the Statistics part?