I just imported my collection from DVD Profiler. Roughly half of the 5019 titles are missing cover images and Edition Release Date. What am I doing wrong?
Hello. I also had the issue with converting from DVD Profiler several month ago. Unfortunately the import of XML file with movie connect does NOT consider the front/back covers from your import files. If you look closly, the covers you are seeing all come from CLZ core Data. I only learned this after a few weeks as I was amazed about all the back covers I was missing after the import. Movie Collector however imports the covers correctly BUT a lot of other important fields are missing when importing with Movie Collector. CLZ knows about this, as I adressed several messages here in the Forum. My conclusion: you need to import using Movies Connect and upload your covers by hand if you like to stick to your images from DVD Profiler. I would also strongly advise NOT trying to import Data with Movies collector as there are to many bugs in that import.
I managed to install Movie Collector 23.3.5, but it won’t let me buy a license. I guess I’ll stick to DVD Profiler a while longer.
I now use the CLZ movie package: mobile App & Connect on the Web. It‘s as least as good as DVD Profiler (which I used for 20 years). And the Team behing the software is EXTREMLY responsif.
@oberkorn
If you wish to use Movie Collector as just an import tool (so the covers come with), and then send everything to CLZ Movies Web, I’m sure I can give you a temporary Movie Collector license to do that. Please contact me through help.clz.com and include a link to this topic and we will see if we can make that work with you (if you want that, that is)
Just to clarify what I wrote above, if you import your DVD Profiler XML with Movies COLLECTOR (the desktop version), here are my concerns with regard to that import. I think you better verify these after you import your file:
- my TAG fields were all empty ( which was a Showstopper for me)
- The EDITION fields were all empty
- The FORMAT field did not always contain the correct value
If I remember correctly, I also copied all the cover images from DVD Profiler Images Folder to the Movies Collector Images Folder BEFORE performing the import of the xml file. This allowed them to be linked to the movies entries.
We did a lot of fixes to the DVD Profiler import on CLZ Movies Web that never made it to the Windows version.
But the the Web version has no way to grab the file path from the XML and grab the covers from your computer (would be kinda weird if that worked too I’m guessing with a web-app).
So if the desktop version has problems with importing certain fields, than that would be an “either or” story.
I‘m not a developper, but here is an Idea for a ‚mass‘ upload: the DVDProfiler User would prepare a ZIP file which contains the IMAGES folder of DVD Profiler where all front and back images are named after their EAN combined with Country number (data available in the xml). So when a User starts this this new fancy Maintenance-mass-upload function, your web applications ask for a file and uploads this ZIP file and processes it in your back-end. Basically it would perform exactly what the user needs to do by hand today which is uploading an image in the respectif movie detail.
@CLZ_AJ
Will Movie Collector also import disc release date into Edition Release Date fields? Is it possible to do bulk data updates via some other mechanism?
I submitted a Contact Us form.
@Allardl Based on the UI, I believe collection.xml is being uploaded to the web server which then parses the data locally. For comparison, my collection.xml file is 105 MB and my full backup file is 1.25 GB.
Yes, that seems like an easy enough idea, but for most users who import it seems that they are happy with the Core front/back they’re getting for their barcodes, so that saves a lot of uploading/downloading time, without the images - plus, it saves a lot of data on the server (cover images are coming from Core, so not everyone has their own “same cover” - unless the user specifically changes one. So I’m hesitant to put this on a to-do list.
I believe it will. But I will double check that when we start importing.