Elsewhere Online twitter Facebook SLS Blogs YouTube SLS Channel Linked In SLSNavigator SLS on Flickr

Email Tagging

Every email in the Web Team inbox you should assign at least  tags. The first tag is a status one, the second one is the month and year, and the third is a category.

Status Tag: There are four types of statuses for each email. 

Open Issue: a request haven't started. These type of tags are used on faculty  workshops until the Friday when you input them. This is a temporary tag that you will change when you begin or complete a request.

Working Item: This tag is for any request that you are currently working on. These can be ongoing projects or multi-day requests. 

Awaiting Response: This tag is for a request that you're working on, but can't continue with or finish until you receive a response. These requests can include Drupal Accounts (waiting for the user to try to login so we can capture their SUNet or for Chidel to okay them) or just requests that we need more specifics about before we can complete them.

Closed: Once a request has been completed and you have emailed all relevant people back you can mark it as Closed. You don't need to wait for a response from the requester to mark it as closed, though if they request any changes you will temporarily change it back to a Working Item.

Month and Year:

These tags are very straightforward and help us quickly search for the date we completed/received the request. Example: January 2015. 

Category Tag: There are tons of category tags. A request can (and frequently does) have multiple category tags. Developer Projects, Jen Projects, and Jenny Projects usually mean you don't have to complete the request because another team member is working on it. 

Bio Updates: these tags are for biography changes on our site.

Course Notifications: use this tag for import course notifcations/inconsistencies that we receive

Creating Pages: whenever you create a new page on the SLS site use this tag. 

Creating Blogs: use whenever a new blog is created

Developer Projects: use this tag for any bugs/projects that the developer is working on

Documents and Attachments: use this tag any time you're dealing with uploading/editing/deleting any sort of document or attachment for the site/a page. 

Drupal Accounts: use this tag to label any email about drupal accounts, Event or Content Manager permissions, etc. 

Faculty Workshops: use this tag to label the weekly faculty workshops.

Google Analytics: use this tag to label any emails about google analytics for pages.

Highlights: use this tag for the homepage highlight related emails (including those Jenny completes)

Intern Projects: use this tag for large (1 hour or longer) requests you receive. You should also tag with the specific type of request it is.

Law@Stanford: use this tag for any content or emails related to the Law@Stanford publication. This includes any content sent to you or test emails of the newsletter.

Links: use this tag for requests where you have to add/change a link

Meetings: use this tag to label requests to meet 

Page Content: use this request when you're changing general page content (the body of pages). For bio pages please use the Bio Updates tag instead.

Photos and Logos: use this tag for when you add, modify, or create images to the site. 

QA: use this tag for any QA emails. QA is when you make sure the site looks and works as it should and is usually done after a developer changes something. If the QA takes you more than an hour make sure to use the Intern Projects tag as well.

Questions, Comments, Instructions, or Redirects: use this tag when people ask general questions you can answer without modifying any content. Also use this tag when someone sends the Web Team a request that is mean to be handled by someone else (ex: publications). In these cases once you tag it, forward it to the appropriate people.

Roles or Titles: use this tag for dealing with anyone's roles or titles (this includes changing their role type so they appear or don't appear in a directory)

Status Reports: use this tag for the Status Reports that we receive