Thank you Tim , Mark and Bram for your precious help, I will forward your responses to our IT men so they can be informed of the suggested solutions.
From: Tim Donohue [mailto:[email protected]] Sent: Wednesday, November 14, 2018 6:24 PM To: Mark Jordan <[email protected]> Cc: Bram Luyten <[email protected]>; Sawsan Habre <[email protected]>; [email protected] Subject: Re: [dspace-community] migrating from CONTENTdm to DSpace Hi Sawsan (and all), Another possible tool (that I just saw mentioned elsewhere) is the CDM Bridge tool out of the "Bridge2Hyku" IMLS project: https://bridge2hyku.github.io/toolkit/ This CDM Bridge tool looks to be a desktop application that allows you to pull data out of ContentDM (using the ContentDM API), clean it up a bit, and export it into a CSV. Unfortunately, however, there's very little documentation at this time. While I've never used this tool myself, it seems like it could be promising. I'd be interested in hearing someone try it out and report back. While the CSV out in this scenario is mentioned as a means to get data into Hyku, DSpace is also able to import content via CSVs, especially if you use the SAFBuilder to turn that CSV/Spreadsheet into Item Packages: https://github.com/DSpace-Labs/SAFBuilder So, it's another option to at least consider as it seems like a possible way to get data out of ContentDM into a generic format (CSV) that can then be imported into DSpace. Again, I've not tried this route myself, so mileage may vary. - Tim On Wed, Nov 14, 2018 at 8:58 AM Mark Jordan <[email protected]<mailto:[email protected]>> wrote: 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]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Bram Luyten <[email protected]<mailto:[email protected]>> Sent: Wednesday, November 14, 2018 1:19 AM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[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<https://maps.google.com/?q=Gaston+Geenslaan+14,+3001+Leuven,+Belgium&entry=gmail&source=g> 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<tel:+961%201%20786%20456> Fax: +961 1 786098<tel:+961%201%20786%20098> <http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> Beirut | Byblos | New York<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> f<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> in<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> t<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> ig<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> <http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> ________________________________ <http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> -- 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.<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> -- 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.<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> -- 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.<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> -- <http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org<http://www.lau.edu.lb/?utm_source=lau_email&utm_medium=email&utm_campaign=EmailSig2018> -- 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.
