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

Port PDF content to new bucket #569

Closed
4 tasks done
Tracked by #60 ...
emileighoutlaw opened this issue Oct 26, 2016 · 6 comments
Closed
4 tasks done
Tracked by #60 ...

Port PDF content to new bucket #569

emileighoutlaw opened this issue Oct 26, 2016 · 6 comments
Milestone

Comments

@emileighoutlaw
Copy link
Contributor

emileighoutlaw commented Oct 26, 2016

@patphongs and I looked at content categorized as "Port" in the content inventory spreadsheet 🔒.

We identified the following as a first round of PDFs that can be ported to a new S3 bucket:

  • IG reports: The new pathway should be /about-fec/ig-reports/
  • Commissioner statements: The new pathway should be /about-fec/commissioners/
  • Audits: The new pathway should be /legal-resources/enforcement/audits/

Notes on progress so far:

IG reports

  • Pat encountered quite a few duplicates in the inventory spreadsheet.
  • These duplicates are likely because content owners accidentally uploaded the file to two locations and referenced it in links in two locations.
  • Pat has already done the hard work of marking which are duplicates.
  • 98 documents were copied over to the S3

Audit reports

  • 1770 files have been copied over to the S3

Commissioner statements

  • Again, many of the PDF documents are duplicates. In this case, the documents were uploaded to the website twice (once in the legal search and a second time in the commissioner section).
  • Our plan is to link the Commissioner pages to the MUR document in the legal-resources section.

Completion criteria

  • Audit PDFs are either moved to a new (public) bucket or are marked as duplicates
  • IG PDFs are either moved to a new (public) bucket or are marked as duplicates
  • We have clarification as to what in Commissioner statements is maintained by the Public Records department and what is not and can be ported over
  • Commissioner statement PDFs are either moved to a new (public) bucket or are marked as duplicates
@patphongs
Copy link
Member

@emileighoutlaw For IG reports, 98 documents were copied over to the S3. This is excluding the duplicates that were flagged in the spreadsheet. This is all complete.

Commissioner statements needs some more clarification as to what is maintained by the Public Records department and what is not and can simply be ported over. Currently, I've flagged SORs that were uploaded to the web server as possible duplicates under this section, since there is a copy of it inside of the legal search system.

@emileighoutlaw
Copy link
Contributor Author

Awesome. IG is checked off as done, and I added the note about clarifying what's under the Public Records Department to the completion criteria. Thanks thanks!

@emileighoutlaw
Copy link
Contributor Author

Also — I marked the "audit" documents as "research," rather than "implement," because we want to do more design thinking around how they're displayed (as opposed to OIG reports, which we're building a template for already).

@emileighoutlaw
Copy link
Contributor Author

After discussion, our plan is to move the duplicative Commissioner PDFs for now (because of time constraints) and maybe do a cleanup in the future. Sound right @patphongs ?

@patphongs
Copy link
Member

@emileighoutlaw you are correct, the PDF files for the Commissioners have been move over. We have one slight issue with some documents from former Commissioners being in HTML format. We need to do a little extra leg work for that. See ticket #616

@noahmanger
Copy link

Now that commissioner PDFs are moved and we have a new issue for HTML pages, I'm going to close this issue.

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

3 participants