ER&L 2012: Electronic Resources Workflow Analysis & Process Improvement

workflow at the most basic level
illustration by wlef70

Speakers: Ros Raeford & Beverly Dowdy

Users were unhappy with eresource management, due in part to their ad hoc approach, and they relied on users to notify them when there were access issues. A heavy reliance on email and memory means things slip through the cracks. They were not a train wreck waiting to happen, they were train wreck that had already occurred.

Needed to develop a deeper understanding of their workflows and processes to identify areas for improvement. The reason that earlier attempts have failed was due to not having all the right people at the table. Each stage of the lifecycle needs to be there.

Oliver Pesch’s 2009 presentation on “ERMS and the E-Resources Lifecycle” provided the framework they used. They created a staff responsibility matrix to determine exactly what they did, and then did interviews to get at how they did it. The narrative was translated to a workflow diagram for each kind of resource (ebooks, ejournals, etc.).

Even though some of the subject librarians were good about checking for dups before requesting things, acquisitions still had to repeat the process because they don’t know if it was done. This is just one example of a duplication of effort that they discovered in their workflow review.

For the ebook package process, they found it was so unclear they couldn’t even diagram it. It’s very linear, and it could have a number of processes happening in parallel.

Lots of words on screen with great ideas of things to do for quality control and user interface improvements. Presenter does not highlight any. Will have to look at it later.

One thing they mentioned is identifying essential tasks that are done by only one staff. They then did cross-training to make sure that if the one is out for the day, someone else can do it.

Surprisingly, they were not using EDI for firm orders, nor had they implemented tools like PromptCat.

Applications that make things work for them:

JTacq — using this for the acquisition/collections workflow. I’ve never heard of it, but will investigate.

ImageNow — not an ERM — a document management tool. Enterprise content management, and being used by many university departments but not many libraries.

They used SharePoint at a meeting space for the teams.

NASIG 2011: Gateway to Improving ERM System Deliverables – NISO’s ERM Data Standards and Best Practices Review

Speaker: Bob McQuillan

I had notes from this session that were lost to a glitch in the iPad WordPress app. Essentially, it was an overview of why the ERM Data Standards and Best Practices Review working group was created followed by a summary of their findings. The final report will be available soon, and if the grid/groupings of ERM standards and best practices that Bob shared in his presentation are included in the report, I would highly recommend it as a clear and efficient tool to identify the different aspects of ERMS development and needs.

WordCamp Richmond: Starting From Scratch – Introduction to Building Custom Themes

presenter: Wren Lanier

Why use WordPress as a CMS for a small website? It’s flexible enough to build all sorts of kinds of sites. It’s free as in beer and there is a huge support community. It has a beautiful admin (particularly compared to other CMS like Drupal) that clients like to use, which means it is more likely to succeed and make them happy repeat clients.

First things first. Set up a local development server (MAMP or XAMPP) or use a web host. This allows you to develop on a desktop machine as if it were a web server.

Next, download dummy content like posts and comments. There are plugins (WP Dummy Content, Demo Data Creator) or imports in XML form.

Start with a blank theme. You could start from scratch, but nobody needs to reinvent the wheel. Really good ones: Starkers (semantic, thorough, and functional), Naked (created for adding your own XHTML), Blank (now with HTML5), and more.

A blank theme will come with several php files for pages/components and a css file. To create a theme, you really only need an index.php, screenshot.png, and style.css files. Lanier begs you to name your theme (i.e. sign your work).

Now that you have a theme name, start with the header and navigation. Next, take advantage of WPs dynamic tags. Don’t use an absolute path to your style sheet, home page, or anywhere else on your site if possible.

Make things even more awesome with some if/then statements. You can do that in PHP. [I should probably dig out my PHP for Dummies reference type books and read up on this.] This allows you to code elements different depending on what type of page you use.

Once you have your header file, build your footer file, making sure to close any tags you have in your header. Code the copyright year to be dynamic.

It doesn’t have to be a blog!

If you’re going to create a static homepage, make sure you name the custom template. If you don’t do this, the WP admin can’t see it. Go into Reading Settings to select the page you created using the homepage template.

Now that you have all that, what goes into the custom template? Well, you have the header and footer already, so now you put THE LOOP in between a div wrapper. The loop is where WP magic happens. It will display the content depending on the template of the page type. It will limit the number of posts shown on a page, include/exclude categories, list posts by author/category/tag, offset posts, order posts, etc.

Once you have your home page, you’ll want to build the interior pages. There are several strategies. You could let page.php power them, but if you have different interior page designs, then you’ll want to create custom page templates for each. But, that can become inefficient, so Lanier recommends using if/then statements for things like custom sidebars. A technique of awesomeness is using dynamic body IDs, which allows you to target content to specific pages using the body_class tag depending on any number of variables. Or, once again you can use an if/then statement. Other options for body classes.

Finish off your theme with the power of plugins. Basics: Akismet, All-In-One SEO, Google XML Sitemaps, Fast Secure Contact Form (or other contact form plugin), WPtouch iPhone theme. For blogs, you’ll want plugins like Author Highlight, Comment Timeout, SEO Slugs (shortens the URL to SEO-friendly), Thank Me Later (first-timer comments will get an email thanking them and links to other content), and WordPress Related Posts. For a CMS, these are good: Custom Excerpts, Search Permalink, Search Unleashed (or Better Search, since the default search is  bit lacking), WP-PageNavi (instead of older/newer it creates page numbering), and WP Super Cache (caches content pages as static HTML and reduces server load).

Questions:

What about multi-user installations? She used Daren Hoyt’s Mimbo theme because it was primarily a magazine site.

At what point do you have too many conditional statements in a template? It’s a balancing act between which is more efficient: conditional statements or lots of PHP files.

How do you keep track of new plugins and the reliability of programmers? Daren Hoyt & Elliot J. Stock are two designers she follows and will check out their recommendations.

What is your opinions of premium themes? For most people, that’s all they need. She would rather spend her time developing niche things that can’t be handled by standard themes.

How do you know when plugins don’t mesh well with each other? Hard to keep up with this as patches are released and updates to WP code.

Where can you find out how to do what you want to do? The codex can be confusing. It’s often easier to find a theme that does the element you are wanting to do, and then figure out how they designed the loop to handle it.

Are parent templates still necessary? Lanier hasn’t really used them.

Leave WP auto-P on or off? She turns them off. Essentially, WP automatically wraps paragraphs with a p tag, which can mess with your theme.

CIL 2009: CM Tools: Drupal, Joomla, & Rumba

Speaker: Ryan Deschamps

In the end, you will install and play with several different content management systems until you find the right one for your needs. A good CMS will facilitate the division of labor, support the overall development of the site, and ensure best practices/standards. It’s not about the content, it’s about the cockpit. You need something that will make your staff happy so that it’s easy to build the right site for your users.

Joomla was the #1 in market share with good community support when Halifax went with it. Ultimately, it wasn’t working, so they switched to MODx. Joomla, unfortunately, gets in the way of creative coding.

ModX, unlike Joomla, has fine-grain user access. Templates are plain HTML, so no need to learn code specific to the CMS. The community was smaller, but more engaged.

One feature that Deschamps is excited about is the ability to create a snippet with pre-set options that can be inserted in a page and changed as needed. An example of how this would be used is if you want to put specific CC licenses on pages or have certain images displayed.

The future: "application framework" rather than "content management system"

Speaker: John Blyberg

Drupal has been named open source CMS of the year for the past two years in part due to the community participation. It scales well, so it can go from being a small website to a large and complex one relatively easily. However, it has a steep learning curve. Joomla is kind of like Photoshop Elements, and Drupal is more like the full Photoshop suite.

Everything you put into Drupal is a node, not a page. It associates bits of information with that node to flesh out a full page. Content types can be classified in different ways, with as much diversity as you want. The taxonomies can be used to create the structure of your website.

[Blyberg showed some examples of things that he likes about Drupal, but the detail and significance are beyond me, so I did not record them here. You can probably find out more when/if he posts his presentation.]

wordpress

Jessamyn asks, “Man, is everyone using WordPress nowadays?” Nope. I thought about it briefly when MT 3.0D came out and there was a big to-do over the license pricing tiers, but now that MT allows one author with three blogs under the free license, I’m covered for all I need. I have this blog, my … Continue reading “wordpress”

Jessamyn asks, “Man, is everyone using WordPress nowadays?”

Nope. I thought about it briefly when MT 3.0D came out and there was a big to-do over the license pricing tiers, but now that MT allows one author with three blogs under the free license, I’m covered for all I need. I have this blog, my blog of playlists from when I did college radio, and a test blog that I hardly use as I find that test index pages for this blog works just as well. Though, if I ever need more than one author or a bunch of blogs, I’ll probably switch to WordPress.

css.php