You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note:
1)The Current MURs are stored in case_index, the Arch MURs are stored in arch_mur_index
2)Because both MURs are sorted independently when display on the website, the sort order may sometimes be incorrect.
3)So far there are total 7533 MURs(Arch MURs=4448 and Current MURs=3085)
4)Some examples:
ex 1: case_no= 2804(Arch MUR) -- case_no=2804R(Current MUR)
ex 2: case_no= 3620(Arch MUR) -- case_no=3620(Current MUR)
ex 3: some Current MURs with same case_serial , but different case_no (xxxxR)
7894R; 4313R
5)will create new view: fecmur.arch_current_mur_sorting_vw to combine both Current MURs and Arch MURs
with integer column 'case_serial' for sorting.
What we’re after
The sort order for MURs seem to be incorrect. This seems to be the case when current MURs end and archived MURs start. Example website link: https://www.fec.gov/data/legal/search/murs/?search=&case_respondents=&case_min_open_date=&case_max_open_date=&case_min_close_date=&case_max_close_date=&offset=3080&limit=20&sort=#results-murs
Completion criteria
The text was updated successfully, but these errors were encountered: