WIP - Replace a PDF
This process includes steps for uploading a PDF to replace an existing version (updating).
Links and notes for pdf publishing (new process with airtable)
ODI File Tracker (Purple)
- Use this to start and track each PDF that is being published.
- Select tab labeled ODI file tracker.
PDF Historical (Pink)
- Select tab labeled Git history, PDF metadata, and active files.
- Select a view appropriate for what you need (for example, Grouped by Industry category key).
Google Drive Publish folder
- Check that the PDFs have the correct filenames.
- Put the files you are about to publish in the Google Drive Publish folder.
Github Covid-Static PDF folder
- This step will make your file live within minutes of upload. Staging first is not available.
- Make sure you are in the pdf folder: https://github.com/cagov/covid-static/tree/master/pdf
- You may need to download the file onto your device to then upload it to covid-static. Dragging and dropping the PDF from Google Drive Publish folder into covid-static pdf folder has not worked for several of us.
- Once the upload to github is complete, make sure to test that it’s working by clicking on the link that you added in the Airtable tracker for this file.
- Once you’ve confirmed it’s live, change the ODI file status to Publish in the ODI file tracker (purple Airtable). Then check the PDF Historical (pink Airtable) and verify that your newly uploaded file is there, and the green check box is selected.
Old process steps below - need to update
- If you’re uploading an updated version of a PDF, find the current version of your PDF on the live site. Find a difference between the current version and the one you’re uploading so you can confirm the new version uploads later.
a. A date is usually the most convenient reference to use.
- Rename the updated PDF so it’s the same as the existing PDF.
a. The name must be identical.
- Go to https://github.com/cagov/covid-static.
a. Select the pdf folder.
b. In the upper-right corner, select the Add file button.
c. Select Upload files from the dropdown menu.
d. Upload your file by dragging it into the Drag files here to add them to your repository box or selecting choose your files and using the popup window.
e. In the Commit changes section, enter brief details (less than 50 characters) about what you’re doing in the first line that contains the placeholder text Add files via upload. This information will be available in the Github history and #code-movement on Slack to identify what changes happened. Use hyphens in place of spaces. This information will be available in the Github history and #code-movement on Slack to identify what changes happened (e.g., “replacing-translated-guidance-agriculture-12”).
f. Adding additional details in the larger box with the placeholder text Add an optional extended description is only if you have extended information to add.
g. Select the green Commit changes button to submit the PDF for upload.
h. To track the status of the PDF upload, select Actions in the menu at the top of the page. The text added in the Add files via upload line from the Commit changes section will be listed here. When a green check mark appears to the left of this text, the PDF had been uploaded.
- Return to the live page and confirm the updated PDF comes up when the link is selected.
a. It usually takes around 1 minute for PDFs to push to the live site.
b. If it doesn’t come up, confirm in #code-movement that the PDF went through. If it did, confirm the filename of the PDF was the same.
- Open the Translations Tracking Sheet in Google Drive.
- Confirm the PDF is listed in the Guidance Pdfs tab (or the Checklists tab) with the link.
- Select the Metadata tab (for either guidance or checklists). Use this tab to note if there is an issue with the PDF metadata, e.g., Retail Checklist label shows “Schools guidance.”
- Select the Dates tab (either guidance dates or checklist dates), and enter the new date of the PDF.