-
Notifications
You must be signed in to change notification settings - Fork 3
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
Close gaps in fields #53
Comments
I'm suspicious that these are actually two separate fields that aren't being broken up properly. |
Nope, doesn't look like it. From the table map:
Here are a few other RES-REQUESTOR fields that contain spaces:
I think that these are optional, undocumented subfields within this field. The format seems to be a person's name, optionally a state name in parentheses, and then a business name. Check with the SCC on this. |
We're getting this in
But not all of them:
It looks like, if character 51 is an open paren, that we can figure that we're looking at a geographic identifier. We'd strip out the parens, and the last two characters ( I guess we're going to need some kind of optional field type definable in the YAML table maps. That is, we don't know that these two fields (place name and place type) are going to be present, but if they are present, we want to use them as per the mapping. |
In
Note the typos: "FLORDIA," "DELEWARE," and "FORIEGN." My guess is that an SCC admin is adding these notes, and their software is buggy. As with the prior file, the second field starts at character 51. It looks like we should simply remove any whitespace in excess of one character prior to character 51, and then break apart the field based on the parens. Everything prior to the opening paren is the |
In
So we've got up to three fields here. We've got the requestor, we've got the state of the requestor in parentheses, and we've got the requestor's employer. Well, sometimes. See the Norfolk Southern example, where the requestor is an organization, not an individual, and instead of an employer, we have contact information. It's really the inverse of the other examples. Again, the dividing line is character 51. |
Finally, there's
This affects 2,455 records, or 0.5% of all LLCs. I think here, the most sensible thing to do is to replace multiple spaces with a single space. |
We're getting big gaps within text fields, like such:
Figure out what the source of this problem is, and eliminate it.
The text was updated successfully, but these errors were encountered: