ER&L 2012: Working For You — NISO Standards and Best Practices

wood, water, and stone
courtyard of the conference hotel

Speaker: Nettie Legace

NISO is more than just the people at the office — it’s the community that comes together to address the problems that we have, and they’re alway soliciting new work items. What are your pain points? Who needs to be involved? How does it relate to existing efforts?

A NISO standard is more formal and goes through a rigorous process to be adopted. A NISO recommended practice is more edgy and discretionary. There are a lot of standards and best practices that have not been adopted, and it depends on the feasibility of implementation.

Get involved if you care about standards and best practices!

Speakers: Jamene Brooks-Kieffer & John Law

They’re talking about the Open Discovery Initiative. Discovery systems have exploded, and there are now opportunities to come together to create some efficiencies through standards. The working group includes librarians, publishers, and discovery service providers.

The project has three main goals: identify stakeholder needs & requirements, create recommendations and tools to streamline process, and provide effective means of assessment. Deliverables include a standard vocabulary, which the group has found they need just to communicate, and a NISO recommended practice. They plan to have the initial draft by January 2013 and finish the final draft by May 2013.

There will be an open teleconference on Monday.

Speaker: Oliver Pesch

SUSHI was one of the first standards initiatives to use the more agile development process which allows for review and revision in 5-7 years. The down side to a fixed standard is that you have to think of every possible outcome in the standard because you may not get a chance to address it again, and with electronic standards, you have to be able to move quickly. So, they focused on the core problem and allowed the standard to evolve through ongoing maintenance.

SUSHI support is now a requirement for COUNTER compliance, and it has been adopted by approximately 40 content providers. MISO client is a free tool you can download and use it to harvest SUSHI reports.

Part of SUSHI’s success comes from being a part of NISO and the integration with COUNTER, but they’re not done. They’re doing a lot of work to promote interoperability, and they have published the SUSHI Server Test Mode recommended practice. They’re also preparing for release 4 of COUNTER, and making adjustments as needed. They’re also publishing a COUNTER SUSHI Implementation Profile to standardize the interpretation of implementation across providers.

Questions/Comments:
Major concern about content providers who also have web-scale discovery solutions that don’t share content with each other — will that ever change? Not in the scope of the work of the ODI. More about how players work together in better ways, not about whether or not content providers participate.

Why is SUSHI not more commonly available? Some really big players aren’t there yet. How fast is this going to happen? A lot of work is in development but not live yet. What drives development is us. [Except we keep asking for it, and nothing happens.] If you allow it to be okay for it to not be there, then it won’t.

JISC created a template letter for member libraries to send to publishers, and that is making a difference.

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.