STAFF_MASTER and PLAYER_MASTER CSV

[brigmcneil]

Can you please fix up the CSV exports for these two files? They are unusable as it stands due to some international character sets. Please share which encoding you are using OR change it to something that handles the characters. Right now it is throwing extra semi-colons (the delimiter), into fields and it makes it impossible to import.

[JeffR]

The ISO-8859-15 character set will load the special characters properly.

[tomkmb]

Originally Posted by JeffR

The ISO-8859-15 character set will load the special characters properly.

I'd wondered about this before...I had issues with the 2025 draft classing, I imported the CSV's using the encoding specified, however see the screenshots attached for the results on a certain players name:



I only noticed when I wrote the draftboard to a file viewable in excel, it just cut off the character at the beginning of the players surname all together

[brigmcneil]

I've tried that one but I still get some rows that fail because the field has something like Shikokuchūō in it which causes too many columns.

The big examples I see first are...

Player = Hidetora;Zaike

Staff = Tashiaki;Yagi

[brigmcneil]

Funny - they look fine here on the Forum (convert correctly)...

[JeffR]

Originally Posted by tomkmb

I'd wondered about this before...I had issues with the 2025 draft classing, I imported the CSV's using the encoding specified, however see the screenshots attached for the results on a certain players name:

What's the birthdate on that guy? I'm trying to narrow down whether it's some character that came into the database from an external source (i.e. he's a real player and there's ) or if it's something in our last name list that shouldn't be there.

[JeffR]

Originally Posted by brigmcneil

I've tried that one but I still get some rows that fail because the field has something like Shikokuchūō in it which causes too many columns.

The big examples I see first are...

Player = Hidetora;Zaike

Staff = Tashiaki;Yagi

I think I see the problem there. One of the researchers seems to have entered Japanese text in the nickname field for a large number of players, and the exporter is just rendering it as a mix of question marks and spaces. We're going to have to do something about that, but in the meantime the best solution I can think of is directly editing the csv's before using them for anything else: import the master files into Excel or another spreadsheet, sorting by the nickname field, then deleting everything in the Nick Name column with a ? anywhere in it (they all seem to have it as a leading character, so the sort should put them all together), then resave the csv with the bad data removed.

[tomkmb]

Originally Posted by JeffR

What's the birthdate on that guy? I'm trying to narrow down whether it's some character that came into the database from an external source (i.e. he's a real player and there's ) or if it's something in our last name list that shouldn't be there.

He's a real player - https://www.eliteprospects.com/playe...11/martin-svec




EDIT - I'm able to get this particular character to display when using the ANSI encoding to import - however not sure what effect that may have on other names just yet.