Hi Sawsan,

For our migration from CONTENTdm to Islandora, we developed the Move To 
Islandora Kit<https://github.com/MarcusBarnes/mik>, which can crawl a CONTENTdm 
collection and write it out to disk in a format ready to ingest into an 
Islandora repository. MIK is structured to be extensible, so it would be fairly 
easy to make it write out DSpace import packages instead of Islandora import 
packages. Doing so would require a little development effort, but all of the 
code for crawling CONTENTdm is already in place. Let me know if you are 
interested in knowing more.


Mark


________________________________
From: [email protected] <[email protected]> on 
behalf of Bram Luyten <[email protected]>
Sent: Wednesday, November 14, 2018 1:19 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [dspace-community] migrating from CONTENTdm to DSpace

Dear Sawsan,

we have recently done this again for one of our clients.
As far as we know, there is no way in ContentDM to "package up" the files 
together with the metadata.

So the method we resorted to is:
- ensuring the metadata XML exports contain a reference to a uniquely named file
- have the client deliver us all the uniquely named files in a big zip (or 
several zips)

And then on our end, we wrote custom code to resolve & import the file based on 
the match between the filename in the XML metadata, and the presence of a file 
with that name in the provided ZIP.

In your specific situation, where the metadata import into DSpace is already 
finished, the question would be whether your DSpace metadata, right now, 
contains a reference to the filename? If that's the case, you could leverage 
this with custom scripts, iterate over these items and try to resolve these 
names against a directory where you have gathered the files with those names.

with kindest regards,

Bram

[logo]  Bram Luyten
250-B Lucius Gordon Drive, Suite 3A, West Henrietta, NY 14586
Gaston Geenslaan 14, 3001 Leuven, Belgium
atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>


On Wed, 14 Nov 2018 at 09:55, Sawsan Habre 
<[email protected]<mailto:[email protected]>> wrote:
Hello

The decision in our library was taken to remove CONTENTdm and to import all the 
metadata and objects to our LAU repository (LAUR) 
(http://libraries.lau.edu.lb/research/laur (DSpace software)

Did any library had to do the same export/import procedure? How to export 
together the metadata and the object attached to it. We had been able to export 
the metadata to CSV files and importing them to DSpace but we couldn’t been 
able to export in the time the objects attached to the metadata. We have to 
upload the objects one by one to their corresponding metadata.
ANY suggestions, please, to do the migration from CONTENTdm to DSpace in a 
simplest way?



Sawsan Habre
Head of University Archives & Special Collections
Library, Beirut Campus
Office: +961 1 786456 ext. 1345
Fax: +961  1 786098



[Lebanese American 
University]<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018>
Beirut<http://www.lau.edu.lb/about/contact/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018>
 | 
Byblos<http://www.lau.edu.lb/about/contact/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018>
 | New 
York<http://www.lau.edu.lb/locations/nyc/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018>
f<https://www.facebook.com/LebaneseAmericanUniversity>

in<https://www.linkedin.com/edu/school?id=14810>

t<https://twitter.com/lebamuniv>

ig<https://instagram.com/lebamericanuni>


________________________________


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To post to this group, send email to 
[email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To post to this group, send email to 
[email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to