another serial number collision; two with SG-0517BBBK1111

[jbrzusto]

One is Niles' Seaview Harbour, with e.g. these files on Aug. 18:

   changeMe-0517BBBK1111-000879-2017-08-18T11-42-13.9300Z-all.txt.gz
   changeMe-0517BBBK1111-000939-2017-08-18T17-14-48.2090P-all.txt.gz
   changeMe-0517BBBK1111-000880-2017-08-18T11-45-27.9490P-all.txt.gz
   ...

and the other is Motus Bookton:

   Bookton-0517BBBK1111-000006-2017-08-18T00-19-52.4450T-all.txt.gz
   Bookton-0517BBBK1111-000006-2017-08-18T01-19-52.5130T-all.txt.gz
   Bookton-0517BBBK1111-000006-2017-08-18T02-19-52.5630T-all.txt.gz
   ...

The collision will be resolved like so:

• Bookton: SG-0517BBBK1111
• Seaview Harbour (NJ): SG-0517BBBK1111_1

The fix requires:

• [x] register a new receiver with serno SG-0517BBBK1111_1
• [x] motus.org: change deployment record for Seaview Harbour to use the new (_1) serno - [ ] rename all raw files for Seaview Harbour to include the '_1' Don't do this; we will preserve names on disk; parseFilenames() will deal with serial number disambiguation.
• [x] add (another) special case to motusServer::parseFilenames() so incoming files are routed appropriately; done: in 4a3e1e9176b6cbcdc6208d22405524d13f663cd8
• [x] rerun both of these receivers

[zcrysler]

I've changed the receiver serial number for Seaview in project 47 to SG-0517BBBK1111_1, so that takes care of the first two items on the list

[zcrysler]

A recent upload of raw files for Seaview in project 47 was placed in the hourly plot folder for project 1 - will this affect future processing of that detection data being linked to the correct project?

[zcrysler]

Project 47 uploaded a file for Seaview on Oct 30 (job id 726896), but all data was placed in project 1. Is there anything more I need to do on the website end so that this duplicated receiver data gets put with the correct project?