Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIN Field Issues #53

Open
djbusby opened this issue Dec 27, 2022 · 3 comments
Open

VIN Field Issues #53

djbusby opened this issue Dec 27, 2022 · 3 comments

Comments

@djbusby
Copy link
Member

djbusby commented Dec 27, 2022

The field is documented as both 'VIN #' and 'VIN#' -- notice the space. In the Manifest.csv file it has the space, in the documentation it does NOT have the space.

Also, 'VIN #' is redundant, since VIN means Vehicle Identification Number; suggest changing to just 'VIN' to remove the problem.

@djbusby
Copy link
Member Author

djbusby commented Jan 2, 2023

This field is called 'VIN #' in the upload and 'VIN#' in the download file.

@djbusby
Copy link
Member Author

djbusby commented Jan 2, 2023

Also, it's IR68026 which was closed as 'this is a no-impact observation, not a question.'

@djbusby
Copy link
Member Author

djbusby commented Jan 2, 2023

To add to this one -- in the Error Replies from the LCB system the field has 'VIN#' w/o the space.
So, perhaps we could get some consistency between the documentation, the upload field and the error-response field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant