Salt Lake City
How about this idea to address the Not Matched status issue:
Message Posted: Jan 10, 2014 1:37:05 PM
“Linked” instead of “Matched”
“Unlinked” instead of “Unmatched”
When a user adds a station to their FSL, it gets LINKED to the MSL by station ID (behind the scenes) instead of getting MATCHED by station NAME.
Likewise, when a user reports a price, it updates the MSL by station ID (behind the scenes) instead of by station NAME.
For the developers of this system, is this possible??
I'm no developer yet my CS degree taught me a long time ago that text fields are BAD BAD BAD as a unique key identifier.