-
Notifications
You must be signed in to change notification settings - Fork 0
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
Multiple Reverse Amendment Dates for Title 46 Volume 3, 4 Year 2017, 2018 #223
Milestone
Comments
barefootford
added
OFR
Need information or decision from OFR
support
Maintenance, bug fixes, upgrades, etc.
labels
Apr 7, 2020
barefootford
added a commit
that referenced
this issue
Apr 7, 2020
barefootford
added a commit
that referenced
this issue
Apr 7, 2020
barefootford
added a commit
that referenced
this issue
Apr 7, 2020
barefootford
added a commit
that referenced
this issue
Apr 7, 2020
barefootford
added a commit
that referenced
this issue
Apr 7, 2020
This is still broken in the latest XML in 2020. We have an ongoing patch from 2017 but we should email OFR about this.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Title 46 Volume 3 amendment date is a reverse amendment date.
It changed changed from October 17, 2016 to July 28, 2016
It should probably be July 28, 2016
It currently affects source xml received on 2017-08-01T01:00:00-0400 to 2017-09-29T01:00:00-0400
Title 46 Volume 3 amendment date is a reverse amendment date.
It changed changed from July 28, 2016 to Oct. 1, 2016
It should probably be Oct. 1, 2017
It currently affects source xml received on 2017-10-04T01:00:00-0400 through the current xml.
This is present in current XML as of 2020-03-26
Title 46 Volume 4 amendment date is a reverse amendment date.
It changed changed from October 25, 2016 to July 27, 2016
It should probably be July 27, 2017
It currently affects source xml received on only 2017-07-29T01:00:00-0400
Title 46 Volume 4 amendment date is a reverse amendment date.
It changed changed from July 27, 2016 to July 28, 2016
It should probably be July 28, 2017
It currently affects source xml received on 2017-08-01T01:00:00-0400 to 2018-01-18T00:00:00-0500
The text was updated successfully, but these errors were encountered: