Presented at NISO's "Getting the Most Out of Your Institutional Repository: Gathering Content and Building Use," (03 Dec 2007)... This presentation describes efforts in the DSpace community (ca. 2007-2008) to give researchers more incentive to "live" within their institutional repository, including features designed to motivate them to spend significant time there, manage their content there, and make formal submission of content into the IR an easier and more natural part of their work. We see the user's personal space or "desktop" within DSpace to be an amplifier of their scholarly activities. We believe that users should have basic --- but in this Web2.0 world, expected --- capabilities available to them for relating their current activities and interests to other artifacts in local DSpace collections. The presentation describes experimental DSpace extensions like item bookmarking/tagging within local collections and using the resulting "context" as a basis for recommending related items. We discuss our thoughts on extending DSpace further to facilitate the scholarly workflow, including mechanisms for identifying and retrieving related items within a repository federation and especially for identifying colleagues with related interests. We believe these techniques can be applied to the identification and harvesting of related materials from other, heterogeneous sources such as external blogs, wikis, and web sources <http: />

1. the future of
NISO December 2008
dspace:
dspace:
making it personal
John S. Erickson, Ph.D.
Principal Scientist,
Digital Media Systems Lab
Hewlett-
Hewlett-Packard Labs

2. the future of
NISO December 2008
dspace:
dspace:
making it social
John S. Erickson, Ph.D.
Principal Scientist,
Digital Media Systems Lab
Hewlett-
Hewlett-Packard Labs

3. dspace @ hplabs worldwide
Bristol, UK
Vermont, USA
Beijing, China
Bangalore, India

4. Development is ongoing,
active, vibrant
•A global open source success
•In the footsteps of Apache,
Mozilla, etc…
•Nearly 100 developers, 14
dspace community
committers from around the
More than 270 registered world Adopters from all sectors
live sites and growing • Mostly research and higher
• Leading institutional repository education institutions
platform (ref: CLIR, ARL, others) • Cultural heritage organizations,
• World-wide adoption
World- state libraries/museums
• >>1m digital assets • Even commercial adopters
(Biomed Central, NITLE, CILEA,
CASPUR, ???)
DSpace
community

5. dspace around the world
India
6%
Central America
1%
South America
5% US
26%
Japan
4%
Asia
7%
Af rica
2%
Australia & New Zealand
5%
Canada
7%
UK
11%
Europe
26%

6. •Provide guidance and
guidance support to the DSpace
community
dspace foundation vision
•Provide technical,
strategy strategic roadmaps for
DSpace platform
•Provide infrastructure
infrastructure and governance as
needed
•Develop partnerships
with others who bring
partnerships value to the community
--- commercial and
otherwise
•Work with other
institutions and non-
non-
cooperation
profits with similar
goals of digital
preservation and open
access

7. dspace foundation goals
Organization • Build a “lightweight” organization
• Roll out DSpace 2.0
Technology • Foster new development
• Create technical infrastructure to support the
Infrastructure community
• Highlight an exciting set of open content collections
Exemplars to showcase application of DSpace
• Develop value-added partnerships with commercial,
Partnerships non-commercial entities
Funding • Achieve a sustainable funding model
• Continue to collect feedback from stakeholders
Communication around the world

8. Executive Director
dspace foundation structure
Michele Kimpton
Chief Technology
Community Webmaster
Officer
Outreach Mgr (part-
(part-time)
(TBD)
QA/Release
Manager
(part-time)
(part-
Ensure DSpace is a
Help prioritize Extend globally platform that will live
Facilitate and provide
technical through network of on beyond any
guidance
developments lead partners individual institution
or contributor

9. dspace 2.0 technical goals
Scalability: from 100K ->10M++ items
Interoperability: with other repository platforms,
web services and Web2.0-style applications
Web2.0-
Modularity: make independent development of
extensions easier
Work flow: allow customized work flows that better
fit the users’ needs
Data model: allow for versioning, richer metadata
and the management of more complex objects

10. dspace 2.0 development
Funding from
grants and
Four (4) community
international
training
Development & conferences
testing separate, …with full
isolated from core documentation!
6-month core
development
•Four (4) FTEs from
community
18-month project, to
18-
start late Spring ’08
(after 1.6 release…)
Hire CTO
(within the
non-
non-profit) to
guide
development

11. Governance:
HP is a member of…
• DSpace Foundation Board
of Directors
• DSpace Architecture
Review Group
dspace @ hplabs
Research:
Development:
HP moves DSpace
HP contributes
forward…
with…
• Personalization…
• Full-time lead developer,
Full-
• Federation…
DSpace committer
• Policy-based curation…
Policy- curation…
• Interns, contractors,
• Large-scale, distributed
Large- students…
storage…

12. • Context-driven • Peer-based,
dspace research interests
recommendation autonomously-
and collaboration managed federated
services aggregated repositories with
from unlimited intrinsic virtual
sources collection
capabilities
personalization federation
storage curation
• Exploiting
standardized, • Scalable, practical,
distributed, large- policy-based
scale, high- curation and long-
availability storage term preservation of
assets information

13. making dspace personal
Surveys of open repository
adopters confirm the Motivations for and benefits of
"institutional" focus of implementing IRs are those of the
institutional repositories host institution
• enabling greater access to information
• providing managed, long-term preservation
long-
of artifacts
These are not
necessarily the goals
of individual users!

14. Surveys also identify the real threat to the health of
open repositories
making dspace personal
• sustaining a constant stream of contributions from their user
communities
open repository platforms are designed for
self-
self-service ingestion…
• …but the strongest and freshest repositories are those with
professional staffs who are responsible for content management
• This is a luxury few institutions can afford!!!

15. Participation in an IR today represents extra effort for
the busy scholar that adds little value…
value…
making dspace personal
• To their research…
• To their authorship…
• To their collaboration with others in their field
How can we add value for IR users?
• Make DSpace personal !
• Give researchers incentives to “live” within their DSpace
make submission of
add features that
manage their content an easier
motivate them to
content there… and more natural
spend time there…
part of their work

16. making dspace personal Example: DSpace recommendation service
• Automatically relate user’s current activities and interests to
other artifacts, web resources, people
Identify and
Identify
retrieve
Bookmarking Recommend colleagues
related items
and tag items related items with related
within
interests
federation

19. MyTheme1
working
dspace research contexts
context
related
items (local)
related
items
(federated)
related
colleagues
related
blogs
related wikis
my network

20. MyTheme1 MyTheme2 MyTheme3
working working working
dspace research contexts
context 1 context 2 context 3
related related related
items (local) items (local) items (local)
related related related
items items items
(federated) (federated) (federated)
related related related
colleagues colleagues colleagues
related related related
blogs blogs blogs
related wikis related wikis related wikis
my network my network my network

21. dspace research contexts
my research profile
myTheme2
myTheme1
items recommendations
bookmarks
myTheme3 items web
people
feeds
sharing
myTheme4 publishing feeds people

25. The future of “IRs”
will be defined by
how well they
Recommendations integrate with You know the
making dspace personal
are only the scholarly networks examples by now
beginning & workflows (or should!)
Personalization Scholarly
really means profiles will be
“socialization” aggregations of
content and
services

26. building scholarly networks
reputation
relationships groups
presence conversations
scholarly
identity sharing
“profile”

27. Registration:
Registration:
allows claims of
precedence for a
scholarly finding
scholarly value chain
Rewarding:
Rewarding:
rewards actors for Certification:
Certification:
performance in establishes the
communication validity of a
system based on registered
metrics derived scholarly claim
from that system
Awareness:
Awareness:
allows actors in
Archiving:
Archiving:
the scholarly
preserves the
system to remain
scholarly record
aware of new
over time
claims and
findings

28. MIT SIMILE
• Personalization
• Citation Pipeline (w/ CrossRef)
CrossRef)
University of Minho
• Recommender plug-in
plug-
• Commentary plug-in
plug-
• “Web of Comments” plug-in
plug-
University of Rochester
related work
• Researcher Pages plug-in
plug-
Nature Publishing
• Connotea, Nature Network, …
Connotea,
…and the state of the art
• c.f. Programming Collective Intelligence (Toby Segaran)
Segaran)
• Library2.0, “Librarian2.0”

29. John S. Erickson, Ph.D.
john.erickson@hp.com
http://pf-
http://pf-dspace.blogspot.com
http://dspace.org
Thank you!
http://wiki.dspace.org
IRC: #dspace
#dspace