55
FUTURE OF THE ARTICLE Linked data, “the dish“ and the value of an interface Chris Mavergames Director of Web Development, The Cochrane Collaboration

Future of the Article

Embed Size (px)

DESCRIPTION

A talk I gave at Oxford University Press' 'Oxford Journals Day' on 22 March 2013 in the afternoon session on future of Medical Publishing

Citation preview

Page 1: Future of the Article

FUTURE OF THE ARTICLELinked data, “the dish“ and the value of an interface

Chris MavergamesDirector of Web Development, The Cochrane Collaboration

Page 2: Future of the Article

Acknowledgements

Thanks and h/t to: Silver Oliver, Ontoba (http://www.ontoba.com) Lorne Becker, Cochrane Innovations

(http://innovations.cochrane.org) Linn Brandt, DECIDE Project (http://www.decide-collaboration.eu) Scott Brinker, (http://chiefmartec.com/) Duncan Bloor, BBC Sophie Hill, Cochrane Consumers and Communication Review

Group Ilkka Kunnamo, (http://www.duodecim.fi) Julian Elliott, Monash University and Cochrane Collaboration Cochrane Linked Data Project colleagues Many others who inspired me

Page 3: Future of the Article
Page 4: Future of the Article
Page 5: Future of the Article

Key concepts

Page 6: Future of the Article

Forgot one – “dish“

Page 7: Future of the Article

Cochrane Reviews

Page 8: Future of the Article

Cochrane Reviews

Have always been electronic Summary of a research project, not really article PICO framework Search, assess and analysis Many of the key components buried in the

document: Forest plots, Risk of Bias assessments, etc.

Continuously updated when new studies are reported

Page 9: Future of the Article

PICO Population Intervention Comparison Outcome

Page 10: Future of the Article
Page 11: Future of the Article

Ilkka Kunnamo

Page 12: Future of the Article

Cochrane has lots of user groups

Clinicians Consumers Guideline writers Policy makers Journalists Authors of other systematic reviews

Different users have different needs...

Page 13: Future of the Article

Getting outside the review/article “container“

Page 14: Future of the Article

Document view

XML <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?><COCHRANE_REVIEW DESCRIPTION="For publication" DOI="10.1002/14651858.CD008440" GROUP_ID="HIV" ID="589309120202025823" MERGED_FROM="" MODIFIED="2011-05-06 12:29:46 +0100" MODIFIED_BY="Rachel Marshall" REVIEW_NO="" REVMAN_SUB_VERSION="5.1.1" REVMAN_VERSION="5" SPLIT_FROM="" STAGE="R" STATUS="A" TYPE="INTERVENTION" VERSION_NO="2.0">........

Page 15: Future of the Article

Key components

Page 16: Future of the Article

linked data

Page 17: Future of the Article

The “age of pointing at things“- h/t Tom Coates, 2005: ttp://www.plasticbag.org/archives/2005/04/the_age_of_pointatthings/

The realization [behind creation of the [Internet] was, "It isn't the cables, it is the computers which are interesting".

[World Wide Web] the realization was "It isn't the computers, but the documents which are interesting". Now you could browse around a sea of documents without having to worry about which computer they were stored on.

Now, people are making another mental move. There is realization now, "It's not the documents, it is the things they are about which are important”.

-Tim Berners-Lee, inventor of the World Wide Web

Page 18: Future of the Article

“The problem is not information overload. It‘s filter failure.“

- Clay Shirky

Page 19: Future of the Article

nimble

Page 20: Future of the Article
Page 21: Future of the Article

Nimble

Structured and linked data can help make content “nimble”

Nimble content can:

• Travel Freely• Retain Context Meaning• Create New Products

- R. Lovinger, Razorfishnimble.razorfish.com

Page 22: Future of the Article

Current web = Web of documents

Page 23: Future of the Article

Docs are linked not data (things) in docs

Page 24: Future of the Article

Machines aren‘t good at reading web pages and documents

Data on the web is meant for human consumption

Machines need the data to be structured Then, information can be more easily shared

within and across datasets and web pages Interfaces and APIs can be built to allow better

(and programmatic) access The article could evolve into an interface onto

a “web of data“

Page 25: Future of the Article

Reviews, studies, references

thing thingthing

thingthing

thing

P

P

P

P

P

P

I

II

I

I

I

C

C

C

C

C

C

O

O

O

O

O

O

Page 26: Future of the Article

Graphs of knowledge

Page 27: Future of the Article

drug

condition

sideEffect CR:ID#

CR:ID#

CR:ID#

study

study

study

study

study

study

studystudy

study

Start anywhere, go anywhere

Page 28: Future of the Article

Page furniture

Page 29: Future of the Article
Page 30: Future of the Article

Chart: Linn Brandt/DECIDE Project

Page 31: Future of the Article

Access points

Page 32: Future of the Article

Access points

Page 33: Future of the Article

LinkedLifeData.com

Page 34: Future of the Article

Linked datasets

Page 35: Future of the Article

Linked Open Data

Page 36: Future of the Article

the “dish“

Page 37: Future of the Article

http://searchinsights.wordpress.com/2011/09/28/the-wheel-of-hunger/

h/t Silver Oliver

Page 38: Future of the Article

Scalable considered linkingh/t Silver Oliver

Page 39: Future of the Article

PICO* = the “dish“

Population InterventionComparisonOutcome

* (some also add another C for condition and/or an S for setting or context)

Page 40: Future of the Article

What‘s your “dish“?

Page 41: Future of the Article

interface

Page 42: Future of the Article

interfacefriendly front endsappssmart searchbetter filters=potential value

Page 43: Future of the Article

Question

Do articles still fulfill their purpose?

Page 44: Future of the Article

Future of article is not about the article at all.

It‘s about:CONTENT & DELIVERY

***NIMBLE***

Page 45: Future of the Article

Think: record company executives once upon a time debating the “future

of the album“...

Page 46: Future of the Article
Page 47: Future of the Article
Page 48: Future of the Article
Page 49: Future of the Article
Page 50: Future of the Article

“Operating system” for science?

“Scientific bundles of knowledge must be structured and accessible by API, with the connections among those bundles and appropriate utility metrics being what connects and prioritizes scientists.”

- Marcio von Muhlen

Source: http://tagteam.harvard.edu/hub_feeds/928/feed_items/41072

Page 51: Future of the Article

CDSR CRS/CENTRAL

DARE

HTAs

CMR

DrugBank

UMLS

Diseasome

SymptomOntology etc.

Evidence-based healthcare OS

Page 52: Future of the Article

Future of the article?

Should really be: Future of content and delivery Interface to web of data Filter API Code Dynamic or “living“ question or series of questions Editors become curators (?) Things we have yet to think of or can‘t imagine

yet...

Page 53: Future of the Article

How did I do?

content knowledge nimble delivery graph PICO question quote

Page 54: Future of the Article
Page 55: Future of the Article

Thank you