Large Scale Asset Migration from Existing DAM

[Bill Tickle]

Hi. I'm trying to do something in resourcespace that I've never done before: port over an entire DAM from another system. Does anyone have any experience of doing this?
I have currently exported the meta-data from the existing system as UTF-8 CSV file and I've done an RSync of the existing Library folders to capture them images / docs themselves to a drive. There are about 220000 assets and it uses about 3tb of space. 
What is the best way of doing this? Doing some research suggests 3 different approaches so far.
1) staticSync
2) Bulk upload then CSV Upload

3) remoteimport using XML 

Before I start doing some hardcore dev on this I'd really like to hear from someone who has gone through the pain of doing this and if there is any best practise way of doing this. 

Thanks in advance. 

[Allison M Stec]

If the directory structure has meaningful data in the folder structure consider using staticsync (ingest=true) with mapped folders.

Outside of that, it really depends on your comfort level with csv/xml and how much effort it's going to take you to get the data in your csv file formatted for either metadata ingest method.

If you mention the DAM you're migrating from, perhaps someone in the group has more specific information about the process.

--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.org
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
--
ResourceSpace Developer
Reseller of Colorhythm's Prismpoint Portal DAM

[Bill Tickle]

Hi Allison

Yes should have mentioned what system I was coming from...

It is a Xinet Webnative Venture db and its really badly configured so I can't use folder structure. And to answer your other question I'm pretty confident in both CSV and XML. 

This is how I think I'm going to do it:

1) StaticSync to ingest the assets. This I will do 2nd level folder at a time. 

2) Once the assets are in I will export the meta data from the ingested assets into CSV. 

3) I will then merge the ingested asset data with the meta-data exported from Xinet

4) Do a CSV Upload to update the meta-data of the ingested assets. 

I think this should work. I'm currently doing a test staticSync on a good sized test folder of about 50gb. That should give me a meaningful test. 

However if anyone knows a slicker way of doing this I'd be happy to hear. 

[Mike Smith]

Hi Bill - 

I have been a part of quite a few migrations, would be happy to chat with you about it off board. 

MS 

[Bill Tickle]

Hi Mike

I think its working fairly well at the moment. 

I've ingested about 10,000 assets using staticSync and exported the CSV. 

I'm now marrying up the csv files. If I get stuck I'll reach out. Thanks

Bill

[Robert Damrau]

Maybe you can compile detailed information about your workflow afterwards for the RS wiki so the knowledge is preserved? That would be great!

[Bill Tickle]

Yes - will do

[J. Manuel Velasco]

Where can I find this information?

It is my first time I need to do a migration. In my case I am migrating an old version of RS (3626) to the latest one.
The way the resources are categorized now is within smart-themes (collections) and in my new setup I am using nodes (category tree).
In the old version we have about 2TB now of videos stored in the filestore, which it is an external drive linked to the RS file structure.

I will appreciate help here from anyone experience. Thanks in advance.