Category Archives: Uncategorized

Photo Specifications

This is meant to become a list of all the photo specifications for various uses.  The goal is t maintain a single, easy to use list where the size of photos for different uses are clear and easy to find.


University Calendar

  • Event Photo : 300 x 225 px

Yearly Updating of RxAmbassadors Web Page

Trigger for Webmaster: Receives finished spreadsheet from Student Services

Yearly, the RxAmbassador web page needs to be updated, taking out any RxAmbassadors who have graduated, adding any new RxAmbassadors, and updating any info as needed.

The webmaster needs two items for this to be done:

  1. A list of which RxAmbassadors are to be removed
  2. A spreadsheet the contains any new ambassadors, as well as any data changes for remaining RxAmbassadors.


This spreadsheet should be used for submitting any new RxAmbassador and any changed data. Note: all columns in the spreadsheet must contain data. There are no named columns that can be left blank.


The webmaster does these steps:

Import spreadsheet into the RxAmbassador Database. (local file)

Sort by last name

Open RxAmbassador web page in Dreamweaver

Cut and past HTML into the page


Monthly Update of Student Addresses

Trigger: On a monthly basis the school registrar will pull a report from the Student DataMart of PharmD student addresses.  This data is then used to update the RxSchool DB.

Historical note:  At one time, we kept three addresses for each student: the home address or “permanent address”, the campus address, and a preferred mailing address.  However, this was abandoned and replaced with the policy as stipulated here, as per the Director of Student Services:

After speaking with Marcia, she informed me that students are told during Orientation that the only address that the School of Pharmacy will recognize is their home address. If their home and mailing address differ in PeopleSoft, it doesn’t matter for our purposes. Therefore, it is conceivable that a student may receive official communication from the university (e.g. semester tuition bill) at their local mailing address and correspondence from us to their home (presumably parents’ home) address. I remind students to update their address(es) each semester, but I will begin framing the request moving forward in a way that reinforces the communication that their home address is the only one we use.



PrimeRx QR Code

Requester (Caylee or Dan) submits a help ticket.  Request type = PrimeRx QR Code
Ticket must be submitted no less than 48 hrs before event, however, for the first few events, more time would be GREAT, as we test out this system.
Ticket contains the following info:
  • Event Name:
  • Event Date:
  • Start Time:
  • End Time:
  • Event Registration Open Time- show long before the event start time should registrations be accepted?
After trigger: Thomas Waters will
  • Create a QR Code
  • Test QR Code
  • Add event to the database
  • Attach PDF of “registration sheet” to the help ticket and mark it as “resolved.”
“Registration sheet” has simple to follow instructions and QR code.
When Requester receives PDF: print out two copies of the PDF to have posted on a table or on the wall at the door of the event.
At some time prior to the event:
  • Requester posts the QR Codes
  • Students can scan QR code, authenticate.
After event: spreadsheet of students who scanned sent to requester as well as archived in the database.


Yearly Changes to Residents

Each year, at the beginning of July, a new class of pharmacy residents begin.  The following steps need to happen regarding this:

  1. Remove leaving residents from email lists (rxschool, rxresident, pharmtherapeutics)
  2. Update residents who are remaining so they are now connected to the correct program.
  3. Delete leaving residents from the RxSchool DB
  4. Add new residents to RxSchool DB
  5. Add new residents to email lists (rxschool, rxresident, pharmtherapeutics)
  6. Revise the residency pages to have correct list of residents


Receive three spreadsheets from Residency coordinator- residents stating, arriving, leaving. Go into RxSchool DB and mark the remaining residents as MGT = “Stay.” Put the new program in the field::Notes.  for those residents who are leaving, set MGT =”Remove”

Take the “new residents” spreadsheet and turn it into a FMP database. Add these fields:

Type = Resident

Degree: PharmD

Title: Pharmacy Resident