ROAR playing record importer

[asloser]

Can you send me your data in a text file and I'll see what's going on. If you can preserve the copy/paste text (so ideally don't put it into word,excel - just the plain text in an attachment would be great) - cheers.

sure will send an email....

 

[daveramsey]

sure will send an email....

Thanks - that's helped.

Please retry, and let me know. I found the problem. The scenarios that can't be imported are because either the side can't be found (I do a substring match, but there are definitely differences) and the scenario titles sometimes don't match (for example 'Totsugeki! (ATL3 redone)' or the apostrophes are different, etc..

 

[asloser]

Thanks - that's helped.

Please retry, and let me know. I found the problem. The scenarios that can't be imported are because either the side can't be found (I do a substring match, but there are definitely differences) and the scenario titles sometimes don't match (for example 'Totsugeki! (ATL3 redone)' or the apostrophes are different, etc..

Success! There are some things to check for instance the players with names including Nordic characters öäåø cause duplicates as the importer does not recognize them, ROAR not using those characters and people in Archive spelling their name correctly. And some, especially older, scenarios are named differently.

I will go through what is in but so far it seems to be very useful -you can get in most of the data in right (maybe ~80% is all right) and then you'll just have to correct or manually enter the rest.

 

[von Marwitz]

However I still suck in ASL.

I am calling you on Maskirowka!

von Marwitz

 

[asloser]

I am calling you on Maskirowka!

von Marwitz

Well there goes that Cunning Plan

 

[Michael R]

I will try the importer when I return home from traveling. Here is an idea that I will use. Import only one year at a time. I believe this will make it easier to check for errors and find them. A pattern of error might show up that can be corrected for subsequent imports.

 

[asloser]

I will try the importer when I return home from traveling. Here is an idea that I will use. Import only one year at a time. I believe this will make it easier to check for errors and find them. A pattern of error might show up that can be corrected for subsequent imports.

I wish you had this idea yesterday.

Signed, man with 1100 lines to check and correct.

 

[daveramsey]

The importer will show you rows that have failed (for the reasons mentioned above) - but you can edit the source file and re-upload without worrying about duplicates so in theory, it's straightforward to find the issues and correct them. If there are common errors that are easy to spot on the Archive's side, it's obviously possible for the titles/sides to be edited if they need fixing.

 

[asloser]

The importer will show you rows that have failed (for the reasons mentioned above) - but you can edit the source file and re-upload without worrying about duplicates so in theory, it's straightforward to find the issues and correct them. If there are common errors that are easy to spot on the Archive's side, it's obviously possible for the titles/sides to be edited if they need fixing.

One thing I noticed is that if a scenario is republished it will default to the original version. For exaple Best of Friends Scenrios will show as the original FrF being played. Still beats having to enter everything manually.

 

[daveramsey]

One thing I noticed is that if a scenario is republished it will default to the original version. For exaple Best of Friends Scenrios will show as the original FrF being played. Still beats having to enter everything manually.

Ok - I've updated it to now search on the scenario ID (ie, AP52) which matches as a case-insenstive, match removing all spaces from the search (to hit AP 52, ap52, etc) and title, then if this fails, just the title- so this might catch a few of them. I know that the archive and roar don't always use the same notation but this might help.

If you need me to wipe your playings so you can re-import, just let me know.

 

[Sparafucil3]

Ok - I've updated it to now search on the scenario ID (ie, AP52) which matches as a case-insenstive, match removing all spaces from the search (to hit AP 52, ap52, etc) and title, then if this fails, just the title- so this might catch a few of them. I know that the archive and roar don't always use the same notation but this might help.

If you need me to wipe your playings so you can re-import, just let me know.

Just a thought: why not lower case any user input that is part of a matching process? You can then add a to.lower() wrapper around your matching text and user input on either side no longer matters. -- jim

 

[daveramsey]

Just a thought: why not lower case any user input that is part of a matching process? You can then add a to.lower() wrapper around your matching text and user input on either side no longer matters. -- jim

This is exactly what the case-insensitive match does.

 

[asloser]

If you need me to wipe your playings so you can re-import, just let me know.

Please do. I think my games make for an interesting test case as there is quite many of them and it has already been done once.

 

[asloser]

Please do. I think my games make for an interesting test case as there is quite many of them and it has already been done once.

Ok, this was an improvement, now most of the games show correct version and hit rate improved by 10 scenarios.

 

[fenyan]

asloser is really an aslwinner by 37 games

 

[bendizoid]

Success! There are some things to check for instance the players with names including Nordic characters öäåø cause duplicates as the importer does not recognize them, ROAR not using those characters and people in Archive spelling their name correctly. And some, especially older, scenarios are named differently.

I will go through what is in but so far it seems to be very useful -you can get in most of the data in right (maybe ~80% is all right) and then you'll just have to correct or manually enter the rest.

View attachment 30115

What happened in 2007 and 2017 ? Too much drinking or not enough? I see you got the ASL bug in 1998, won your very first scenario then got beat up in 1999 to pay your dues. Followed by a nice winning streak for about 7 years only then the wheels come off about every 10 years. Very nice, Just say’in.

Oops, strayed off topic

 

[asloser]

What happened in 2007 and 2017 ? Too much drinking or not enough? I see you got the ASL bug in 1998, won your very first scenario then got beat up in 1999 to pay your dues. Followed by a nice winning streak for about 7 years only then the wheels come off about every 10 years. Very nice, Just say’in.

Oops, strayed off topic

Well, I actually first played ASL circa 1990-1991, then I dabbled with for a couple of years and started playing and learning more systematically in 1994/5.

The records I kept until 1998 have been lost with old PCs crashing, started using ROAR in dec 1998.

2004-2007 I played a lot of playtest games for Hakkaa Päälle! and I was suffering a mild burout with ASL by 2007.

Between 2010-2017 I was playing a lot less, other things in life became more important, and there were even long 7-8 month gaps without a single game. By 2017 I had become so rusty that it was no longer enjoyable. I've never been a masterclass player, but the games mostly ended in frustration when I lacked the routine to play while knowing I used to do a lot better. So by winter 2017-18 it was about either quitting or playing more regularly to get my chops back.

I decided to start playing more regularly, booked my trip to ASLOK 2018 and took up VASL for live and PBEM play. Last 6 years I've played more ASL than ever before.

so that is the story.

 

[asloser]

Now it is all there. I'll need to check some things but at least number of games and W/L records match.

@daveramsey I'll post a few ideas for improvement now when I have some data to play with.