Quoting Mole:

Quote:
I installed Bulkedit V2.22 in DVDP V3.7.2. last night and now when I select certain profiles in the Collection List window I get a BE popup which says  "Not a legal OleAut date".

It doesn't happen with every profile but it is repeatable with the affected ones, so I'm assuming that it's the profiles themselves that are at fault.

I'd be grateful for any ideas!

Doesn't seem like a BE message that I am familiar with. How do you know it is a BE popup?

Kapow!

OK, so we know it is BE.

Let me do some testing. Thanks again for the excellent feedback.

BulkEdit V2.28 Available
(Please do not quote this post)

CSV Import has been restored. The following formats are supported:

- CSV Export Plugin (Mark Harrison) Column Format
- CSV Export Plugin (Mark Harrison) 2.4 Format
- DVD Spot Export Format
- Custom Format

Notes:

Any import data file that does not include either UPC or Profile ID, will cause Manual Profiles to be created.

If you want to import automically into custom categories, the categories must be defined ahead of time in the database

If you use Excel to create your input data, UPCs can be screwed up unless you force the column to be text. BulkEdit CSV Import will tolerate a leading single quote (') in front of the UPC, so that you can use Excel to create the column.

Information from imported profiles (including Manual and Disc ID profiles) will overlay an existing profile with the same profile ID. However, manual IDs created by BulkEdit will never overlay existing manual profiles, since BulkEdit checks first and starts at the next sequential number.

If a locality column is not present, and if not included in the profile ID, a locality will be guessed by using the Rating information, if present.

Screen Shot:



Here is some usage information:

Except for Custom format, CSV Import expects the column headers to be spelled exactly, with case-sensitivity, as those that are output from CSV Export and DVD Spot. The best way to ensure this is to obtain a sample output and steal the headers.

- Here is a link to detailed instructions for DVD Spot.

- Here is a link to a prior post in this thread that details the exact header names for CSV Export and DVD Spot.

I believe that so long as the header names are spelled exactly, just about any subset of the fields may be used, for any format.

Let's say you wanted to import a list of newly purchased DVDs, and purchase info. Then you would make an Excel spreadsheet and save to CSV that looks something like this:

Profile ID, Purchase Price, Purchase Place, Collection Type
"'012236044802", "$29.95",  Amazon, Owned
"'13023153790.17","$19.95", Amazon, Anime

  ... or ...

UPC, Purchase Price, Purchase Place, Collection Type, Locality
"'012236044802", "$29.95", Amazon, Owned, "United States"
"'13023153790","$19.95", Amazon, Anime, Japan

You can optionally enclose data fields within quotes (a good idea). The official manual profile and Disc ID styles of Profile IDs are supported. If you don't have locality, you can use UPC instead of Profile ID. You could also use a separate Locality column with UPC instead of combining into Profile ID. Except for Custom and DVD Spot, you should make sure that the headers and data format look exactly like what you get with CSV Export. Something else might work accidentally, but is not supported. If any CSV Export field does not import properly, I will fix it. Note that the Collection Type "Anime" was defined in the database ahead of time.

After the import is complete, of course you must do a profile refresh to download the remaining profile information from Invelos. The successfully imported profiles are flagged to make it convenient to do this immediately.

I would appreciate feedback on how this is thing is working (or not). Thanks. (Edit: quick bug fix - now V2.28)

Version V2.31 Available

- Additional Performance enhancements
- When "disc" is present in CSV Import, the correct disc information is updated. Default is still disc 1
- Numeric values in the Slot column can now incremented / decremented by any amount, en masse

Oh what a nice Xmas gift!!!

Can,t wait to dig in and nail those bugs.

Mithi thanks so much for helping me bring improvements.

As you might guess, the code has grown a bit complex. I often break as much as I add.

So my descriptions may refer to intended or prior functions that got trashed in the rework.

I will totally enjoy fixing these bugs (if possible). 

Quoting Rander:

Quote:
My logic dictates I should use Multi-Copy, but no matter what I try, it either throws an error at me, or it fills the columns with wrong data.

The problem seems to be that the field "Case Type" can only hold specific entries, selectable by the drop-down.
I could replace "THINpak" with "Slip Case", but I found no way to replace an empty field with anything.

That did work just fine for me in the past for e.g. "Location"

cya, Mithi

Quoting mediadogg:

Quote:
Well Rander, consider that it might well be a bug. Even expensive MS products have bugs now and then.

Trust me, I now most of them by heart - I work as an it-supporter for civil servants - most of them barely knows how to turn the damn thing on! 

I just didn't expect this to be a bug, as I thought it was the whole point of the plugin - and when I couldn't find anybody else saying it didn't work as expected, I thought that I was just doing it wrong! It wouldn't be the first time... 

And thanks for the explanation of the multi-copy - I couldn't for the life of me work out what I was doing wrong with that.

Progress report:

- I have found and fixed the empty CaseType bug, but you will still be restricted to official DVDP dropdown values
- Fixed another bug relating to column copy that was created accidentally on a previous update
- Found and fixed the bug that ignores Locality when included in CSV import

@Mithi, I am looking to see if I can improve the Locality guessing when Rating is available.

The examples you gave are truly tough ones, because, as you obviously know, most of the UPCs in your sample violate the GS1 Country Code rules. So, I will not be able to improve on Test 1, unless I do it by exception. But I should be able to improve on Case 2, using Rating. And now case 3 scores 100% as expected, since Locality is supplied in the data.

Do you know whether the exceptions you gave me in Test 1 are general, or a result of miscoding of Profiles in the DVDP database, or misapplication of UPCs by the movie distributor?