Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Add command for full-issuance/reissuances #351

Merged
merged 5 commits into from
Jan 24, 2017

Conversation

cmc333333
Copy link
Member

A cleaned up version of navigo#1. Resolves #26 by adding a new command for parsing reissued/initial issuance of a whole CFR part.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 91.97% when pulling 8ebca9f on cmc333333:26-full-issuance into 21c2ed3 on eregs:master.

The pipeline command works by fetching all of the known "version"s of a
regulation (i.e. identifiers), retrieving corresponding annual editions,
and applying diffs based on final rules where annual editions aren't
available.

This approach has (at least) two holes regarding agencies releasing new
CFR parts (or reissuing existing ones):
* If an agency issues a new CFR part and modifies it within the same
year, we will only have the content, in whole once (the annual edition
will correspond to the modification).
* If an agency re-issues a whole CFR part and then modifies it within a
year of re-issuance, we'll run into a similar problem: the notice parser
doesn't know how to understand a reissuance.

This expands on the work started by @eadamsatx to create a command which
will read a full CFR part from a specific notice. This requires a manual
command, but makes it possible to account for the two situations above.
This wasn't a problem until `full_issuance` made these first rules "derived"
We don't need the isolated file system as we're writing to the db.
Using the '//TAG' xpath searches the entire document, regardless of
particular context, while './/TAG' will only search children of the
current el. To check for children of the current el _or_ the current el,
we need to use 'self::TAG|.//TAG'. This also modifies test cases to
account for nested elements.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 91.756% when pulling faf090c on cmc333333:26-full-issuance into c2d8507 on eregs:master.

@cmc333333
Copy link
Member Author

CI failures are due to #347 and #348, which will be addressed shortly, so this should be safe to merge.

@cmc333333 cmc333333 merged commit 45a05d7 into eregs:master Jan 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants