If information stewards and custodians are to collect, create, appraise, preserve, store, use and access sophisticated, flexible, responsive and future- friendly content at scale, then they will have to think strategically about who's going to use the content, how and where they're going to consume it. COPE – Create Once, Publish Everywhere - is an acronym that describes how content should be conceived once and then disseminated through multiple conduits. The goal of COPE is to capture all content (text, media), context and metadata in a single manner, and then ensure that this content can be accessed and used across a range of publishing platforms.
2. Outline
• It’s about the knowledge, stupid
– Where we’ve been?
• Write once, run anywhere
– What are we learning?
• Content can triumph
– How can you cope?
4. Holy grail of libraries
• “To deliver the right book (and other material)
for the right person at the right time.”
5. Holy grail for e-learning
• Just the right content, to
• Just the right person, at
• Just the right time, on
• Just the right device, in
• Just the right context, in
• Just the right way.
6. Sounds familiar?
• I can’t find the information I need.
• The information I’ve found is out of date
• Content is horribly inconsistent (categories,
structure, and display) .
• I usually go elsewhere to get what I need.
18. Questions
• Do you have content strategy or are you
stuffing communication channels with the
same content?
• Is the content you are distributing truly best of
breed — meaning that it’s as good or better
than anything else available?
• Are you really making an impact on readers
with the information you provide?
19. Content & Container
•We assign value to containers instead of content.
•Content management is a process, not a technology
•We make our content inflexible
20. Controlled & Distributed
Open up and communicate honestly and directly
Allow your users to really play with your content,
You want people engaging with your content, so don’t
make it hard on them to engage.
23. Definitions
• COPE – Create Once, Publish Everywhere.
– “If you are going to build it once, let’s make damn
sure you can take it anywhere”
• Web Service - a way for applications or
systems to talk to each other and does not
usually involve human interaction
– API – Application Programmable Interface
– RSS - Really Simple Syndication
24. Flexible content
• Design Agnostic
• Good design requires flexibility too
• Think about your writing
• Don’t put crap out there
• People are the glue between the tools and the
content
28. API Feeds
• Faculty Info
• Faculties List
• Departments List
• Terms List
• Exam Info
• Exam Schedule
• Vending Machines List
• Professor
• Professor Search
• Academic Programs
• Programs List
• Publications
• Recent Dissertations
• Dissertation Details
• Schedule
• Course Schedule
• Weather
• Wireless Data
• open access to library metadata
• catalog metadata
31. Content strategy
• “Content strategy plans for the creation,
publication, and governance of useful, usable
content”
– Kristina Halvorson
32. Content strategy is an imperative
• “12 billion devices connected to the Internet
by 2014”
– CISCO
• If “Any glass is where we will be?” is true, then
get your content ready to go anywhere
because it’s going to go everywhere.”
33. Know what before how
• Ask - is sufficient quantity of quality content
matter available?
• Can each individual content asset can be
easily located, used, adapted, and stored
again for future use.
• Know what are they doing with the
• Do a content audit
34. Content Management System
• To systematically do that, it’s imperative that
publishers employ what’s (aptly) known as
content management systems (CMSs). The
most common of kind of which is called a
blog.
35. Do’s & Dont’s
• Don’t build one gigantic system
• Distribute information between systems
• Distinguish between content management
and presentation layers
• Understand the building blocks of your
content
• Think “Granularity” and “Re-usibility”
36. Smart Content
• It is likely that, in the near future, academia
will expect “smart content” that is
“presentation agnostic” and will want to
access information and data anywhere on
whatever device they choose. If universities
wish to accede to such expectations then their
data governors need to think about a
comprehensive upfront strategy to bring
content, dissemination, technology and
context together.
37. We won’t cope
• Our content may be stolen
• How do I introduce an API to my boss
• My team does not have capacity
• The benefit feel intangible
• Not enough Time/Money/Resources
• It’s too risky
38. We want to cope
• Content & Containers are inextricably linked
• To Be ‘Findable’ Your Content Should Be Flexible.
• Flexible Content needs to embraces COPE
• Requires investment, processes and structures
• Improves editorial efficiency
• In time, drives relevancy
• Creates opportunities
• Contributes to your tech development
39. COPE has a precedent
Content
has always
been more
important
than its
container
English:ENIAC (Electronic Numerical Integrator And Computer) in Philadelphia, PennsylvaniaGlen Beck (background) and Betty Snyder (foreground) program the ENIAC in BRL building 328
It’s a big computer that is known for being reliable, highly available, secure, and powerful. They are best suited for applications that are more transaction oriented and require a lot of input/output – that is, writing or reading from data storage devices.
http://radar.oreilly.com/2011/10/post-pc-revolution.htmlEach wave of computing not only disrupts, but dwarfs its predecessor. The mainframe was dwarfed by the PC, which in turn has been subordinated by the web. But now, a new kind of device is taking over. It’s mobile, lightweight, simple to use, connected, has a long battery life and is a digital machine for running native apps, web browsing, playing all kinds of media, enabling game playing, taking photos and communicating
The future of design: it wasn’t me, Big Data made me do itI’m getting more and more interested in the intersection between design and Big Data, what it may mean for the future of design, and what are current examples of disruptions in our industry when algorithms get combined with vast amounts of data.When a design is automatically generated and produced, who is responsible for it? While for many of us the obvious answer is whomever wrote the algorithm and published the work, Tim Maly wrote in his very interesting post Algorithmic Rape Jokes in the Library of Babel of how,A t-shirt company called Solid Gold Bomb was caught selling shirts with the slogan “KEEP CALM and RAPE A LOT” on them. They also sold shirts like “KEEP CALM and CHOKE HER” and “KEEP CALM and PUNCH HER”. The Internet—especially the UK Internet—exploded.Amazingly, when people took notice and the complaints came, the company’s apology was that they didn’t know what they were selling, saying in an apology that,Although we did not in any way deliberately create the offensive t-shirts in question and it was the result of a scripted programming process that was compiled by only one member of our staff, we accept the responsibility of the error and our doing our best to correct the issues at hand. We’re sorry for the ill feeling this has caused!Stores sometimes have signs saying “if you break it, you own it.” In this new world, will we need to debate whether “if you(r algorithms) made it, own up to it”?
Using the Universities of Washington's web services, anyone on campus can learn, discover and connect to 29 separate University APIs. Its great to see that a University is trying to create a single directory of all University web services, and even has an API suggestion service where students and faculty can submit and vote on ideas for new, useful campus APIs. With the volatility of school funding, online learning and just overall competition in higher ed, Universities need to start noticing of the transformative powers of APIs, and how it can make University operations more transparent, accessible and nimble, and potentially even save money when it comes to empowering the students themselves to build interfaces for accessing vital University information.