Skip to content Skip to navigation

Blog

Posted by Joe Knox on Tuesday, September 22, 2015 - 10:05am

You can do a lot to improve the performance and user experience across your site by making use of your Google Analytics account. In this post, we'll cover five valuable standard reports that you can view for your site right now.

This post aligns with the Google Analytics set up and menu structure as of September 22, 2015.

The "Audience" report

The audience report is one of the most, if not the most, useful reports that you can view for your site. Based on a selected period of time, this report shows the total number of sessions, users, and page views, as well as other valuable information such as the average session duration and the bounce rate percentage.

Demographic, system, and mobile statistics also can be viewed on the same dashboard as the aforementioned numbers. This allows you to see what county and city your site visitors are coming from, what browser and operating system they’re using, as well as what type of mobile device and screen resolution they’re viewing your site on.

How to access the report

  1. Log in to your Google Analytics account.
  2. Click the Reporting tab (if you have more than one site linked with your account, be sure that you’ve selected the site you want to view reports for).
  3. Click Overview from the Audience menu item on the left-hand side of the page.

  4. Select the dates for which you wish to view data for from the calendar in the upper right-hand corner.

The "Acquisition" report

The acquisition report allows you to view how users are getting to your site. For example, you can see the number of users who arrived on your site via organic search, via direct navigation, or via other avenues such as email.

Additionally, each avenue allows you to drill down further for more in-depth information. You can view the keywords users have searched for on search engines that led them to your site, the direct URL they entered, as well as which social network they clicked a link to your site from.

How to access the report

  1. Log in to your Google Analytics account.
  2. Click the Reporting tab (if you have more than one site linked with your account, be sure that you’ve selected the site you want to view reports for).
  3. Click Overview from the Acquisition menu item on the left-hand side of the page.

  4. To drill down even further, click on the item you wish to explore in more depth from the Acquisition column on the lower portion of the page.

The "Site Content" report

The site content report is another handy report, as it shows you which pages are the most visited on your site. You can view the total number of page views for a specific page, as well as other useful stats such as the average amount of time a user spends on a given page.

This report can be incredibly helpful when “cleaning up” your site content, as it aids in painting a picture of what visitors are looking for most on your site.

How to access the report

  1. Log in to your Google Analytics account.
  2. Click the Reporting tab (if you have more than one site linked with your account, be sure that you’ve selected the site you want to view reports for).
  3. Click All Pages from the Site Content menu item under the Behavior menu item on the left-hand side of the page.

The "Real-Time" report

Real-time analytics allows you to monitor activity as it's happening on your site. You can see how many people are on your site right now, top keywords being searched, top active pages, as well as the location(s) of those accessing your site.

How to access the report

  1. Log in to your Google Analytics account.
  2. Click the Reporting tab (if you have more than one site linked with your account, be sure that you’ve selected the site you want to view reports for).
  3. Click Overview from the Real-Time menu item on the left-hand side of the page.

The "In-Page Analytics" report

With the in-page analytics report, you can view extremely specific data on what links your site visitors are clicking on when browsing. The report provides an image of a given page with a visual overlay of where users are clicking. By understanding how visitors interact with your site, you can optimize your site layout to improve the user experience.

How to access the report

  1. Log in to your Google Analytics account.
  2. Click the Reporting tab (if you have more than one site linked with your account, be sure that you’ve selected the site you want to view reports for).
  3. Click In-Page Analytics from the Behavior menu item on the left-hand side of the page.

    view in-page analytics

More in-page analytics coolness

There’s a cool and useful browser extension, Page Analytics (by Google), that allows you to view much of what the in-page analytics report shows you directly on your site.

Caryl Westerberg Posted by Caryl J Westerberg on Wednesday, September 9, 2015 - 9:00am

Stanford Events is Stanford University's central calendar. It's widely used by departments, organizations, and student groups to promote events to the public and members of our campus community, and it provides a valuable resource for planning and scheduling. The challenge is cross-promoting events. In the past, sharing events content across multiple websites required re-typing. Ouch! We'll show you how to use the Stanford Events Importer module to save time and cross-promote events from multiple organizations.

The Stanford Events Importer module was designed to help organizations import their public events from Stanford Events into their Drupal website. Recently Stanford Events was updated with two new types of events feeds

  • unlisted
  • bookmarked

These great new feeds make it easier for organizations to post their own events on the Stanford Events website and share them with via their website, or to hand-select others' events from the calendar to cross-promote on their website.

Next, the Stanford Events Importer module was updated to support the new event feeds, making it even easier to import and display events on a Drupal website.

As an event administrator you can: 

  • post all your events on Stanford Events as either public or unlisted
  • use the planning calendar to identify upcoming events and potentially any events that may interfere with your event
  • import events for your website filtered by type, subject, organization, etc. through your organization's unlisted and bookmarked feeds

Here's how it works:

Adding Events to Stanford Events

To create a feed and add your events to Stanford Events you'll need to request an account at http://events.stanford.edu/. Once you have an account, login and select Add New Event on the Calendar Admin - Main Page.

How to add a new event

Types of events on Stanford Events

When you add an event to Stanford Events you choose the status of an event, and that influences whether the event will be visible on the main calendar and which feeds you use to import them into your website.

Published events

A published event displays on the central event calendar and will belong to the published feeds for your organization and any sponsor organizations.

How to select a published event

Unlisted events

Unlisted events do not display on the central event calendar.  This allows organizations to create events on Stanford Events that are not exposed to the public, but are still available:

  • on the planning calendar
  • to sponsors
  • on the organizations's Unlisted feed

To add your event to your organization's unlisted feed, select Unlisted as the status of your feed.

Bookmarking events

Bookmarks allow you to select any event on Stanford Events and add them to your Bookmarks feed. When you want an event to appear in your bookmarked feed, you would copy the URL and add it to the bookmarks for your organization.

Importing Stanford Events

Stanford Web Services (SWS) developed the Stanford Events Importer module to support importing published, unlisted, and bookmarked events. Special thanks to our colleagues in University Communications, VPGE, and the Department of Classics for their help in implementing and testing this module.

To import Stanford Events into your Drupal website:

  1. Log into your site
     
  2. Enable Events Importer on the Modules page
     
  3. Navigate to the add Stanford Event Importer page at

    Content > Add Content > Stanford Event Importer


     
  4. Give your Importer a title such as "Stanford Toastmasters Published"
     
  5. Select your organization, i.e. "Stanford Toastmasters"


     
  6. Select the Event Type for this feed, i.e. "Published"

    Select published Event Type

  7. Save your new event importer. When first saving your event importer, it will automatically import the events from Stanford Events. 
     
  8. Navigate to the events page, and you should have events!

Look we have events!

 

Embedding a Stanford Event RSS Feed

To embed an RSS Feed onto your site, you can follow this guide from the Stanford Events site.

Tip of the day

If you just added events to your feed, you may need to wait a day for Stanford Events to update.

Our goal is to connect systems in smart ways and make content maintenance just a little easier for website owners. Let us know what you think about the new events calendar and module changes!

Posted in:
Caryl Westerberg Posted by Caryl J Westerberg on Tuesday, September 8, 2015 - 9:30am

Would you like to display courses on your website? How about events or links to people profiles? The Stanford community provides a variety of web feeds which provide data or content that your Drupal website can leverage. 

Frequently the content you need on your website is already published on another website. Rather than adding this content manually to your website, you can use a web feed to import this published content from the source website and display it on your website. 

What is a web feed?

A web feed, such as an RSS or Atom feed, is content that is published on a website in a machine-readable format that can be downloaded by an application such as a feed-reader or another website. These feeds use EXtensible Markup Language (XML) to encode the data. You can identify a page with a web feed when it displays the following icon:

Example of an RSS feed icon

What Stanford feeds can I use on my site?

The Stanford community produces numerous feeds. At Stanford Web Services we are supporting the import of data from three feeds in particular:

  • Stanford Event Calendar
  • Explore Courses
  • CAP (Community Academic Profiles)

Stanford Event Calendar

Located at https://events.stanford.edu, Stanford Event Calendar is Stanford University's central source for event information.  

Visit the Events Calendar on Stanford's English Department website to see the Stanford Events Importer in action. Learn all about using Stanford Events feeds at Using Stanford Events on your Drupal Site

Screenshot of the Stanford Events homepage.

Explore Courses

Located at https://explorecourses.stanford.edu, the Explore Courses site displays course information for the current year. These courses are from the Stanford Bulletin, the official statement of degree programs and courses of instruction for Stanford University.

Visit the Current Courses page on Stanford's English Department website to see the Stanford Courses feed importer in action. To learn more about importing Stanford Courses see Importing Courses from ExploreCourses

Screenshot of a search on ExploreCourses website.

CAP (Community Academic Profiles)

The Community Academic Profile (CAP) directory features detailed profiles for faculty, students, postdocs, and staff. Along with education and work experience, these profiles can contain detailed information including publications, presentations, and courses taught.

Learn how link to your CAP profile at Linking to a Profile on StanfordWho.stanford.edu.

Screenshot of the author's profile

Keep your content up-to-date

As you populate your Stanford website, remember that you may be able to import that content and let your feeds keep your data up-to-date.

Photo of John Bickar Posted by John Bickar on Friday, August 28, 2015 - 1:45pm

University IT will perform security updates on all websites on the Stanford Sites Drupal hosting service on the following dates:

These changes include updating Drupal core to the latest release, security-related module upgrades, and bug fixes for both Drupal 6 and 7 sites. See below for a complete list of updated and new modules.

Websites are scheduled to receive upgrades on a rolling basis; there should be no downtime associated with these updates.

If you experience issues with your website hosted on Stanford Sites, please submit a HelpSU request. We will respond as soon as possible. Thanks for using Stanford Sites!

What is included in the upgrade

Drupal 7:

Modules

  • drupal 7.39
  • ctools-7.x-1.9
  • date 7.x-2.9-rc1(bug fix)
  • relation-7.x-1.0

Drupal 6:

  • drupal 6.37
Posted in:
Caryl Westerberg Posted by Caryl J Westerberg on Thursday, August 27, 2015 - 1:00pm

Frequently, at Stanford Web Services we receive requests to build an intranet as part of a website. What exactly do people mean by "intranet?" Each department, lab, and institute might have different requirements an "intranet." Let's look at some different ways you might want to use an intranet and the tools available at Stanford that can help make your intranet possible.

What is an intranet?

According to our old friend Wikipedia, an intranet is:

“...a private network, accessible only to an organization's staff....[and] can constitute an important focal point of internal communication and collaboration, and provide a single starting point to access internal and external resources.”

From our experience we've met with a range of intranet requirements.  An organization may simply need a section of private pages that are protected under a login to keep more sensitive information limited to specific audiences. In other cases we see requirements for collaboration, interaction, and notifications. – a much more complex set of requirements. With such a diversity of needs for an "intranet," we are fortunate that Stanford offers several solutions addressing these intranet needs. Let's look at some intranet requirements and point out some tools that meet those requirements.

Support for communication and collaboration

If your organization needs support for communication and collaboration, Stanford provides a variety of productivity and collaboration tools including Google Talk, Adium, and Pidgin for instant messaging, and Confluence as a collaborative wiki and for update notifications. Here’s a list of productivity and collaboration tools available at Stanford, which include tools such as Wikis, Google Apps, Video Conferencing, and so forth.

Access to resources

Portal

If your organization needs a portal or a “one stop shop” for links and resources, you could be acheive this by using either a wiki such as Confluence, Google Docs, or, yes, by creating a section of private pages on your organization’s website. 

Document management

If your organization needs document management such as providing research papers or resumes for download, Stanford gives you several options including Box for Stanford, Google Drive for Stanford, and AFSHere’s a handy comparison of Stanford’s document management solutions.

Authentication

The typical target audience for an intranet is not the general population. Instead the audience consists of people that are known to the organization and need to login before accessing resources. For a department this may include faculty, students, and staff; for a conference, this may include the organizers, speakers, and attendees. 

If your organization needs to use authentication to manage access to internal resources, Stanford supports this with tools such as WebAuth and Workgroups. These authentication tools integrate with most of the tools listed above.

WebAuth

WebAuth provides a login to access many Stanford web sites with a single sign-on. If your organization needs to limit access to tools and services, you will be able to use WebAuth to provide authentication for accessing Stanford resources such as pages on your website, Box, AFS, and Google Drive,

Workgroups

Workgroups allow you to define groups of Stanford people and grant access privileges based on these groups. If your organization needs to povide access to resources based on groups such as faculty or students, you may find that using workgroups will make it easier for you to manage that access. 

Considerations

So, if you feel that your organization needs an intranet, think through the specific requirements you might need – collaboration? privacy? ... etc. – and before investing your time and resources into building something custom, try out the existing tools. Who knows, maybe you'll find a great fit!

If you have a favorite intranet tool that you use at Stanford, please share. We'd love to hear more about what you use and love!

Linnea Williams profile pic Posted by Linnea Ann Williams on Friday, August 21, 2015 - 10:30am

Card sorting is a powerful, hands-on tool that we at Stanford Web Services use for helping content creators iron out either the information architecture of their site (meaning the big buckets of their navigation) or to develop categories for their content. 

Recently, we used card sorting to develop a secondary sidebar navigation of "Related Content" that crossed the main navigation of a website, and these are my takeaways.

Card sorting is really great for helping people wrap their brains around content using design thinking. By creating cards, each with a single term, category, or page name written on them, we can sort the content of a site, figuring out what things belong together and how best to group the content in logical way.

For a standard card sort to find information architecture (IA), we usually make cards for each known page or chunk of content and then group by subject. For this kind of card sort first instincts work well. But what do we do if already have the primary IA figured out and we're trying to find a secondary way to sort our content? We have to change up our thinking a bit.

Prepping cards for the sort: Include full navigational path

The first thing to do before a card sort is prep the cards. In a standard IA page sort, we include the page title and maybe a little additional information for context. But in our case, where we are trying to determine a secondary way to sort content that is different than the navigation scheme, we needed to know more than just the content itself.

I wanted to be able to see quickly if we were grouping pages that were already grouped by our primary navigation, so I printed the full navigational path with each level on a new line. I did not include cards for the top level navigation pages, since that level of page would not feature our sidebar block of "Related Content."

 For example:

Academics
Undergrad Program
Physics Major
Curriculum
-----------

Where "Curriculum" is the page name and the terms above are the navigation path to get there.

Trick of the trade: cards not stickies

Nothing will hamper a card sort more than the cards sticking to the table! Be sure to use actual cards or pieces of paper not post-its for making your cards.

Getting away from subject sorts

As we started on our card sort exercise, I noticed that we instinctively were grouping content into their navigational structure. Everything in the Connect section got put in a pile with the label Connect.

I thought, "Hmmm, we seem to just be remaking our navigation. How do we break out of that tendency?"

Indeed, card sorting is often used to develop primary navigation: grouping content into the most logical buckets and then building menu structures based on those buckets. We had a natural prediliction for grouping by subject. So we needed a different way of thinking.

User-centered thinking: Grouping by process, circumstance, and role

The deeper we dived into the card sort the more we started to think out of the box. We started grouping based on facets other than subject: things like process, circumstance, and role. The key we found was to consider user roles and the situations that could bring people to our website.

I found myself saying, "If I were on this page, what might have brought me here? And what else could I want to know about elsewhere in the site?"

Below are a few hypothetical examples from an academic department website.

Example #1: Considering a Physics Major

I'm a new Undergrad and I'm considering majoring in Physics. I'm looking at the curriculum for the major. I don't really know what I want to study yet and I could probably use some advice. I might want to just Minor in Physics or see what kind of research I could be involved in.

Through the circumstance above, we just identified some pages from throughout the site that are relevant to a category "Considering Major":

  • Academics > Undergrad > Physics Major > Curriculum
  • Academics > Undergrad > Physics Minor > Curriculum
  • Connect > Advising > Undergrad Advisors
  • Research > Centers and Programs > Undergrad Research Centers

 We can then anticipate that there might be a number of other similar categories like "Current Major", "Graduating Major", etc.

Example #2: Graduate Financial Assistance

I'm a graduate student and I'm living with limited means. I'm looking at the financial aid options for my program. I probably also want to know about other financial support that's available, even if it's not directly tied to my degree program. I might also want to reach out to my peers or an advisor.

Through the circumstance above, we just identified some pages from throughout the site that are relevant to a category "Graduate Financial Assistance":

  • Academics > Graduate > PhD > Tuition > Financial Aid
  • Research > Grants > Department Project Grants
  • Research > Grants > Grant Recipients
  • Connect > Advising > Graduate Advisors
  • Connect > Student Groups > Graduate Student Weekly Meetings

Dividing big categories: Aim for 5-6 items in each

The key to developing a related content grouping like this (or any grouping in general) is to limit the number of items in each category to 5-6 for scannability. Readers have a hard time processing more items than that, so you'll serve them better by keeping the number of items in each collection smallBelow are some techniques we used to keep our lists shorter.

Tag the top page for a mini-section, not the details

One way we kept our groupings smaller was to only tag top level items of a section. So rather than tagging a page detailing how to apply to a specific grant, we just focused on the grant's top level page.

Break up large groups into more specific sub-groupings: add facets

If we had large broad groups like "Graduating", we took the opportunity of breaking them out by other facets. Here's an example of "Graduating" which is a process category , divided up by adding roles and circumstances.

  • "Prepping for Graduation (Undergrad)"
  • "Prepping for Graduation (Grad)" 
  • "Post-Graduation (Undergrad Alums)"
  • "Post-Graduation (Grad Alums)"

In conclusion: Know your users

So, there you have it. We found that the key to developing a useful Related Content taxonomy was to know our users and their common motivations. I think that's the key to a lot of things!!

Have you ever made a Related Content taxonomy? How did you go about it?

a face for radio Posted by Zach Chandler on Thursday, July 23, 2015 - 8:00am

Service Design is an emerging practice area that can transform organizations, and create immense value. Stanford Web Services has already begun to introduce Service Design into the way that they develop services for the University. We should all think about more ways to put it into practice.

Design Thinking permeates the air we breathe at Stanford. Innovation is one of our most highly prized values, and creativity is everywhere around us. We have the d.school, and the GSB, STVP, Product Design, and rapid prototyping labs, and we staff members should make good use of that ambient vibrancy. Service Design offers a practical method of doing that.

But what is it? In a nutshell, Service Design is the application of Design Thinking to services, rather than products. It involves making work visible, collaboration and empathizing with stakeholders and service providers alike; and it leverages d.school style methods like prototyping, problem reframing, visualization, and feedback loops. Oh, and stickies. Lots, and lots of stickies. (For a more thorough explanation of what it is, listen to Birgit Mager.) Alternatively we can call this field Service Experience Design, or SXD.

At DrupalCon Los Angeles, our very own Megan Miller introduced Service Design to the Drupal community. I have learned a lot from Megan, and she’s a great storyteller. Megan is at the vanguard of SXD at Stanford (watch this space!), and my hope is that through our new Community of Practice, we can help others see how SXD can create breakthroughs. Look around you. Stanford is a small galaxy of autonomous nodes in a scale-free network of relationships and … services. All of it, all of it, is subject to design, and can be improved to have a greater impact on the mission of the University.

TIP: Megan has also compiled a page of Service Experience Design resources that includes definitions, terms, principles, and links.

Two years ago, Service Design was something that Megan and I were interested in, and had been meaning to learn more about. What made it real for us was attending the Service Experience conference in San Francisco in 2014. We went with a small cohort from University IT and Environmental Health and Safety. This year, we are returning to the SX Conf with an even greater number.

Service Experience Conference 2015

http://service-experience-conf.com/

Where: San Francisco

When: November 16-17

Who: You, hopefully

I think that this is an exciting time to be a part of the reinvention of our work, and just as David Kelley’s new focus is unleashing the creativity of others, I think that Service Design, and its particular vocabulary, mental models, and tools, is an exciting opportunity for all service providers to tap into their creativity, even if you don’t think you are creative … especially if you don’t think you’re creative. Think of SX Conf as innovation school, with highly practical methods you can bring back to your work. COME WITH US!

Photo of John Bickar Posted by John Bickar on Monday, July 20, 2015 - 6:10am

University IT will perform maintenance on all websites on the Stanford Sites Drupal hosting service on the following dates:

  • Friday, July 24th, from 9 a.m. - 5 p.m.: personal sites hosted on people.stanford.edu

  • Saturday, July 25th, from 4 a.m. - 8 a.m.: group and department sites hosted on sites.stanford.edu

  • Sunday, July 26th, from 4 a.m. - 8 a.m.: group and department sites hosted on sites.stanford.edu

These changes are significant and include updating Drupal core to the latest release, security-related module upgrades, new modules, and theme updates for both Drupal 6 and 7 sites. See below for a complete list of updated and new modules.

Websites are scheduled to receive upgrades on a rolling basis. Please note that when the upgrade begins on a website, all logged-in users (if any) will be logged out, and the website will be placed offline temporarily. Visitors will see a message that the website is offline for maintenance. Security patches and database updates will be applied, and the website will be placed back online. We expect the website to be offline for approximately 1 minute during the updates.

If you experience issues with your website hosted on Stanford Sites, please submit a HelpSU request. We will respond as soon as possible. Thanks for using Stanford Sites!

What is included in the upgrade

* = new addition to Stanford Sites

Drupal 7:

Modules

  • drupal 7.38
  • admin_menu 7.x-1.5
  • admin_views-7.x-1.5
  • advanced_help 7.x-1.3
  • backup_migrate 7.x-3.1
  • bean 7.x-1.9
  • better_exposed_filters 7.x-3.2
  • colorbox 7.x-2.9
  • context_list_active 7.x-1.0
  • context_respect 7.x-1.3
  • context_useragent 7.x-1.x-dev
  • css_injector 7.x-1.x-dev
  • date 7.x-2.9-rc1
  • date_ical 7.x-2.14
  • draggableviews 7.x-2.1*
  • ds 7.x-2.10
  • erus 7.x-1.1
  • features 7.x-2.6
  • feeds 7.x-2.0-alpha9
  • feeds_jsonpath_parser 7.x-1.0
  • feeds_tamper 7.x-1.1
  • field_permissions 7.x-1.0-beta2*
  • menu_block 7.x-2.7
  • metatag 7.x-1.6
  • module_filter 7.x-2.0
  • mollom 7.x-2.14
  • pathauto 7.x-1.x-dev
  • print 7.x-2.0*
  • redirect 7.x-1.0-rc3
  • rules 7.x-2.9
  • services 7.x-3.12
  • smart_trim 7.x-1.5
  • stanford (profile) 7.x-2.x
  • stanford_bean_types 7.x-2.5
  • stanford_capx 7.x-1.1-dev+7
  • stanford_carousel 7.x-2.1
  • stanford_courses 7.x-3.6
  • stanford_date_formats 7.x-1.1
  • stanford_date_timepicker 7.x-1.2
  • stanford_easy_wysiwyg_css 7.x-1.1
  • stanford_events_importer 7.x-3.2
  • stanford_image 7.x-3.3
  • stanford_image_styles 7.x-3.2
  • stanford_metatag_nobots 7.x-3.1
  • stanford_page 7.x-2.1
  • stanford_person 7.x-5.0-beta1
  • stanford_sites_helper 7.x-1.5
  • stanford_slides 7.x-3.0
  • stanford_video 7.x-2.1
  • stanford_wysiwyg 7.x-2.4
  • uuid 7.x-1.x-dev
  • views 7.x-3.11
  • views_bulk_operations 7.x-3.3
  • webform 7.x-4.9
  • wysiwyg 7.x-2.x-dev
  • wysiwyg_filter 7.x-1.x-dev

Themes

  • open_framework-7.x-2.4
  • stanford_framework-7.x-3.1

Drupal 6:

  • drupal 6.36
  • advanced_help 6.x-1.3
  • cck 6.x-2.10
  • ctools 6.x-1.13
  • mollom 6.x-2.13
Posted in:
Sara Worrell-Berg Posted by Sara Worrell Berg on Monday, July 6, 2015 - 6:08pm

The relatively quiet summer quarter is underway at Stanford, and many folks are in the process of updating their websites for the coming academic year. Stanford is offering excellent new training opportunities to learn about essential tools, including Drupal, for website owners! There are courses to interest everyone, and now's the time to sign up.

Courses include:

  • Drupal for Novices
  • Drupal for Content Editors
  • Drupal for Site Managers
  • Google Analytics
  • CSS3: From the Beginning
  • HTML5: Getting Started
  • MailChimp
  • Git and Github Workshop
  • jQuery: The JavaScript Framework for Anyone
  • node.js: JavaScript Without the Browser
  • Be Agile: Introduction to Scrum
  • and more...

Many of these are part of the seventh annual Techie Festival. For a discounted rate of just $150 per class, learn from the experts on a wide range of topics, including several for web professionals at every level.

How to sign up for courses and webinars

Visit Technology Training's upcoming courses schedule to sign up for regular courses and webinars, or visit the Techie Festival website to see a full schedule of special discounted courses. Use those STAP funds before they expire!

Explore something new through lynda.com

Lynda.com is an Online Video Training Library with over 3,600 courses and nearly 150,000 individual videos (average of 25 courses added weekly). It is available at no charge, anytime, anywhere, and at your own pace to SLAC and University faculty, benefits-eligible staff, and students. Find out more at http://lynda.stanford.edu, or stop by the Tech Briefing led by Laurie Burruss from lynda.com on July 17 from 1-2:30 pm in Turing Auditorium. More details available at https://itservices.stanford.edu/service/techtraining/techbriefings.

Posted in:
Photo of John Bickar Posted by John Bickar on Friday, June 26, 2015 - 9:05am

A simple task: list all the users on a site, optionally filtering by role or by status. Difficulty: using drush.

I had searched around a bit for this functionality and my Google-fu had failed me, so I decided to build off of work that already had been done and write a drush user-list command. (The internal monologue went something like this: "Is this a thing? It doesn't look like this is a thing. This should be a thing. Why is this not a thing? Let's make this a thing.")

Installation

Download user_list from Github or drupal.org and place it where you place the rest of your drush commands (e.g., in ~/.drush/ or /usr/share/drush/commands/)

Use

drush user-list

Returns a table of all users on the site.

drush user-list --status=active

Returns a table of all active users on the site.

drush user-list --roles="administrator,site owner"

Returns a table of all users with the role "administrator" or "site owner" on the site.

That's pretty much it.

Posted in:

Pages

Subscribe to Stanford Web Services Blog