Re: [CODE4LIB] repository migration
We migrated from DSpace to Fedora a couple of years ago, using basically the process that Edwin outlines. One issue to consider is identifiers and permalinks: we were using handles in DSpace, and had to make sure that all the old handles continued to work against Fedora and that we could mint new ones properly. Apart from that, it was a fairly straight-forward scripting job, using the Fedora API. Peter Peter Binkley Digital Initiatives Technology Librarian Information Technology Services peter.bink...@ualberta.ca 2-10K Cameron Library University of Alberta Edmonton, Alberta Canada T6G 2J8 phone 780-492-3743 fax 780-492-9243 On Mon, May 13, 2013 at 10:18 PM, Edwin Shin wrote: > Kelsey, > > I can't speak to the ePrints side of things, but on the Fedora side, there > are nominally two options to consider: > > 1) create your records programmatically, via the REST API > 2) create FOXML serializations of your ePrints records and then ingest > those into Fedora > > There are a number of variations on either approach, depending on the > number/size of records involved to optimize ingest times. My general > preference would be for #1. > > Some best practices (not specific to migration) to consider in your Fedora > repository: > i) use (M)anaged datastreams rather than Inline (X)ML datastreams where > possible > ii) use Akubra and not the legacy low-level store > iii) unless you have a fairly small repository, update the > HashIdPathMapper config (in akubra-llstore.xml) to have a deeper hierarchy > (e.g. "#/##" or "##/##) rather than just "##". > > I'd recommend joining the Fedora users mailing list for any > Fedora-specific follow-on. > > -Eddie > > On May 9, 2013, at 12:16 AM, "Williamson, Kelsey CTR NUWC NWPT" < > kelsey.williamson@navy.mil> wrote: > > > Good afternoon, > > > > I was hoping someone might be willing to talk about migration projects. > I am getting ready to migrate records from an ePrints repository into a > fedora repository- but I've never done anything like this before. I have an > abstract plan, but I think hearing other people's experiences would be very > helpful; particularly any lessons learned? > > > > Best regards, > > > > Kelsey > >
Re: [CODE4LIB] repository migration
Kelsey, I can't speak to the ePrints side of things, but on the Fedora side, there are nominally two options to consider: 1) create your records programmatically, via the REST API 2) create FOXML serializations of your ePrints records and then ingest those into Fedora There are a number of variations on either approach, depending on the number/size of records involved to optimize ingest times. My general preference would be for #1. Some best practices (not specific to migration) to consider in your Fedora repository: i) use (M)anaged datastreams rather than Inline (X)ML datastreams where possible ii) use Akubra and not the legacy low-level store iii) unless you have a fairly small repository, update the HashIdPathMapper config (in akubra-llstore.xml) to have a deeper hierarchy (e.g. "#/##" or "##/##) rather than just "##". I'd recommend joining the Fedora users mailing list for any Fedora-specific follow-on. -Eddie On May 9, 2013, at 12:16 AM, "Williamson, Kelsey CTR NUWC NWPT" wrote: > Good afternoon, > > I was hoping someone might be willing to talk about migration projects. I am > getting ready to migrate records from an ePrints repository into a fedora > repository- but I've never done anything like this before. I have an abstract > plan, but I think hearing other people's experiences would be very helpful; > particularly any lessons learned? > > Best regards, > > Kelsey
Re: [CODE4LIB] repository migration
At the recent Archiving 2013 conference (www.imaging.org/ist/) a presentation by colleagues from Portugal at KEEP SOLUTIONS and the Dept. of Informatics, Univ. of Minho discussed guidelines for legacy repository migration. I recommend their paper and guidelines / suggestions for anyone planning a large migration - their approach takes into account not only the technical export/import issues but also over programmatic issues and concerns, opportunities based on their years of work with migrating systems. Their guidelines are based on a combination of 13 existing methodologies that have been surveyed and unified into a comprehensive multistep methodology. See: http://www.keep.pt/servicos/migracao-de-dados/?lang=en Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ -Original Message- From: Code for Libraries [mailto:CODE4LIB@listserv.nd.edu] On Behalf Of Williamson, Kelsey CTR NUWC NWPT Sent: Wednesday, May 08, 2013 12:17 PM To: CODE4LIB@listserv.nd.edu Subject: [CODE4LIB] repository migration Good afternoon, I was hoping someone might be willing to talk about migration projects. I am getting ready to migrate records from an ePrints repository into a fedora repository- but I've never done anything like this before. I have an abstract plan, but I think hearing other people's experiences would be very helpful; particularly any lessons learned? Best regards, Kelsey
[CODE4LIB] repository migration
Good afternoon, I was hoping someone might be willing to talk about migration projects. I am getting ready to migrate records from an ePrints repository into a fedora repository- but I've never done anything like this before. I have an abstract plan, but I think hearing other people's experiences would be very helpful; particularly any lessons learned? Best regards, Kelsey smime.p7s Description: S/MIME cryptographic signature
