Policy Matters
Blog Home All Blogs
Administered by the Blog Committee, Policy Matters posts are written by members on a variety of topics. From think pieces to how-to's, editorials to news round-ups, there is something for every policy administrator. Interested in contributing a post? Let us know by emailing admin@acupa.org.

 

Search all posts for:   

 

Top tags: policy  policy development  Policy Administration  Jessica Teets  policy process  collaboration  Deborah Bartlett  pandemic  accessibility  COVID-19  Jennifer Gallagher  Gina Kennedy  writing  ACUPA  data  equity  IT  Productivity  remote work  How-to  Lisa Biagas  news  resources  Sara Gigeroff  students  AI  change  compliance  culture  free speech 

Easily Convert Web Pages to PDF Format

Posted By Evelyn Vanderburg, The University of Texas at San Antonio, Monday, May 9, 2022
Updated: Thursday, April 28, 2022

Free Tool Does the Job without Programming or Coding

Have you ever tried to figure out how to convert policy pages into a PDF file and found it to be a tedious experience? Convoluted html coding, such as </p>, <ol>, <li>, <div>, <span>, and &nbsp, confuse you?

There are several software apps and policy management developers who claim to be able to convert web pages into PDF format at minimal cost. Why spend a lot of money trying to find out what to use when you can use this guide for free, thanks to your ACUPA membership!

By following these steps, you will be able to convert HTML code to PDF in no time. The Adobe Acrobat-Create PDF extension tool lets you quickly convert HTML to PDF in your Google Chrome browser. The conversion process happens in seconds without manual deletion of the HTML and CSS codes. Here’s how.

  1. In Google Chrome, check to see if you have the extension. Choose Settings then click Extensions. If you do not see a box with the extension displayed, skip to Step 6 for instructions on downloading the extension.
  2. Enable the Adobe Acrobat-Create PDF extension, by clicking the toggle switch to the right.
  3. Navigate to the page you want to convert.
  4. Use one of the following two options:
    1. Click on the Extensions symbol, and click on Adobe Acrobat PDF edit, convert, sign tools.
    2. In the pop-up box, click on Convert Web page to Adobe PDF.

OR

  1. Right-click on the web page, choose Adobe Acrobat: PDF edit, convert, Convert Web Page to Adobe PDF.
  1. Your browser will save the file according to your browser settings. Note: Design features and images on the page may not convert depending on the page coding. However, all text should convert seamlessly.
  2. If you need to download the extension, go to the following URL in Google Chrome: https://chrome.google.com/webstore/detail/adobe-acrobat-pdf-edit-co/efaidnbmnnnibpcajpcglclefindmkaj
  3. Click the button to Add to Chrome.
  4. In the pop-up window, click Add extension.
  5. The extension is automatically enabled, so you can go back to Step 3 to convert a page.

Tags:  Evelyn Vanderburg  PDF  policy library  policy process  tools 

PermalinkComments (0)
 

Organizing a Policy Catalog

Posted By Jessica Teets CCEP, Purdue University, Monday, October 26, 2020
Updated: Monday, September 27, 2021

How a Numbering Scheme Works Behind the Scenes

The views expressed in this post are solely those of the author and do not represent the views of ACUPA or Purdue University.

Does your institution number its policies? Do you sometimes wonder why? I had the opportunity early on in my policy administrator role to get rid of our policy numbers. Upon further examination, I chose not to. Here’s why.

Purdue University’s catalog contains approximately 120 policies and standards. This number may seem big or small, depending on your perspective. Either way, the number is large enough to me to warrant an effective numbering scheme.

Our policy numbers have three components: volume (Roman numeral), chapter (letter), and number. For example, our policy on policies is number V.C.1. Volume five, chapter C in that volume, and the first policy in that chapter. If you’re curious to know more, visit our policy website for a full description of the numbering scheme. I have heard the criticism that nobody should be expected to remember a policy’s number, and, indeed, I definitely do not know the numbers of individual policies. However, I do use the numbers in two very important ways.

First, I use the number in the name of the page that the policy is posted to on our website. So, the URL for our policy on policies ends with vc1. The URL becomes a static address that can be updated with new versions of the policy whenever it needs to be changed. This means that any other page or website that is linking to that policy will always have a functioning link. If the policy is withdrawn or superseded, we remove the text of the policy and put a note referring visitors to the policy archive and/or to the new policy, so the link is still useful—no 404 error codes.

The second way that I use policy numbers is tracking. On occasion, policy titles change. We add a word, take a word away, or completely rename it for one reason or another. The number of the policy does not change, so I can still find it on my master policy list in the same place, and I can note the previous title for reference. My master policy list tracks the dates of every version of a policy and whether that policy superseded or was superseded by another policy. For this purpose, it is much simpler to refer to policies by their numbers, rather than titles. The second part of policy tracking is finding prior versions of a policy in our archives. I just search by the policy number, and all the incarnations of that policy come back in the search results.

If you are on the fence about numbering your policies, I strongly encourage you to do so. It has made several aspects of my job easier over the years.

Tags:  Jessica Teets  numbering  organizational theory  Policy Administration  policy library 

PermalinkComments (0)