Well that make sense! Is there folks out there that have converted from CONTENTdm to other systems? (Dspace?, others?...) How did you get the structure info from the cpd files to populate the new system?
From: Code for Libraries <[log in to unmask]> On Behalf Of Brian Meuse
Sent: Monday, September 13, 2021 11:31 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Do we have any OAI programmers here? I have questions.
[You don't often get email from [log in to unmask] Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
WARNING: This email originated from a non-WCU email account. Do not click links or open attachments unless you are confident the content is safe.
For what it's worth, OAI is usually meant to harvest descriptive metadata, not structural. DPLA doesn't host content, AFAIK, they just link back to the host site.
On Mon, Sep 13, 2021 at 11:00 AM Jill Ellern <[log in to unmask]> wrote:
> Code4lib folks,
> Thanks to everyone for help on this...It has kept me up last night
> thinking about... It certainly seemed like it from the documentation
> So I was hoping that the data structure info was in either the OAI and
> then it occurred to me that it might also be in the XML data. (it
> looks like it from the brief info in the documentation) So I had a
> long conversation with OCLC/ContentDm.
> I was disappointed to I found out that the "structure" of the compound
> images (also called the containers for those in Contentdm) that might
> have multiple children files is in files called #.cpd. Those files
> are kept in the images folder. The data looks like this <?xml
> version="1.0" encoding="utf-8"?> <cpd>
> <pagetitle>Page 1</pagetitle>
> <pagetitle>Pages 2 & 3</pagetitle>
> <pagetitle>Page 4</pagetitle>
> I'm wondering how places like OCLC and DLA actually harvest the data
> from CONTENTdm OAI without these files.
> > On Sep 13, 2021, at 4:07 AM, Jill Ellern <[log in to unmask]> wrote:
> > Code4lib folks,
> > I have perhaps some stupid OAI questions. We are moving off
> > Contentdm
> and onto a platform with programmers that I’m pretty sure don't know
> OAI and harvesting at all. We have been thinking that it would be
> simple to convert our output of metadata that comes in a text format.
> However, we see now that it drops the set structure (front and back of
> an image for
> example) especially since we have some collections that have different
> titles for the container (root description) and the images attached.
> We do see a line with cpd but with different titles, it look like we
> might have to identify sets in Excel. That sounds like a big job and
> a pain. I'm thinking there is a better way with OAI but I don't know much about it.
> > My thinking is that we can use OAI to move this data instead of text
> files. I'm sure it has the structure built in...doesn't it? Is there
> a easy tutorial on OAI? I’m not finding much for the layperson. And
> our new vendor is pretty new to library land (they are in museum land)
> and we doubt if they know OAI and I don't see easy ways to teach them.
> Do you have suggestions?
> > Jill Ellern
Brian Meuse, MSLIS
Digital Initiatives Librarian
Brandeis University Library
*Proud member of SEIU Local 888*