DSpace Update at Repository Fringe 2014 - Claire Knowles, University of Edinburgh

1. DSpace: Update from
Open Repositories 2014
Claire
Knowles,
University
of
Edinburgh
Repository
Fringe,
July
2014
(CC-­‐BY)

2. Open
Repositories
2014
• June
9-­‐13
Helsinki,
Finland
• 254
Paper
proposals
• Over
460
aNendees
from
38
countries
• Papers
are
available
at:
hNp://www.doria.fi/handle/10024/97524
• hNps://wiki.duraspace.org/display/DSPACE/
OR2014+DSpace+Sessions

3. Open
Repositories
Wordle
Wordle
from
Adam
Field,
University
of
Southampton,
@gobfrey
hNps://twiNer.com/gobfrey/status/478925098125361152/photo/1

4. DSpace
Vision
(2013)
1. DSpace
will
focus
on
the
fundamentals
of
the
modern
"Ins`tu`onal
Repository"
use
case.
We
are
striving
to
meet
the
IR
needs
of
the
next
5-­‐10
years.
2. DSpace
will
be
"lean",
with
agility
and
flexibility
as
primary
goals.
3. DSpace
will
include
a
"core"
set
of
func`onality
that
can
be
"extended"
(think
plugins)
or
have
"hooks"
(integra`on
points)
to
complimentary
services/tools
4. DSpace
will
be
designed
in
such
a
way
that
it
can
be
easily/quickly
configured
to
integrate
with
new
&
future
tools/services
in
the
larger
digital
scholarship
"ecosystem"
5. DSpace
will
support
low-­‐cost,
hosted
solu`ons
and
deployments
(by
featuring
an
easy,
"just
works"
setup)
hNps://wiki.duraspace.org/display/DSPACE/DSpace+2013+Vision+Document

5. Survey
Analysis
and
Planning
• Vision
Survey
2014
• Reviewed
by
6
commiNers
and
DCAT
• Ranked
features
by
importance
– Categorised
by
func`onality
– Created
drag
use
cases
– What
is
the
status
of
popular
features?
hNps://wiki.duraspace.org/display/DSPACE/DSpace+Product+Plan

6. Func`onality
Gaps
• 4
top
ranked,
unmet
requirements:
– Batch
upload
via
UI
– Rela`onships
between
objects
– Configura`on
via
Admin
UI
– Template
driven
UI
for
easy
branding

7. Non
Func`onal
Goals
• DSpace should aim to be:
– Easy to Install
– Easy to Upgrade
– Scalable and have Good Performance
– Attractive to New Developers
– Attractive to New Repo Managers
– Avoid maintaining duplicative codebases

8. Future
Project
Scope
• Crea`on
of
a
single
user
interface
– Reduce
duplica`on
of
code,
`me
and
maintenance
• Refactoring
or
rebuilding
of
codebase
– Clean
up
of
core
codebase
– Decrease
code
duplica`on

9. Group
Recommenda`ons
• Current
development
model
is
not
suited
for
major
development
work
• Funded
full-­‐`me
Technical
Lead
• Funded
Product
Manager
• Governance
Model
which
can
make
decisions
• Planning
process
to
achieve
product
goals

10. DSpace
Planning
Process
hNps://wiki.duraspace.org/display/DSPACE/Product+Planning+Process

11.
DSpace
Governance
Model
hNp://www.dspace.org/governance

12. Why
Membership?
• Increase
community
par`cipa`on
• Membership
is
understood
by
the
community
• Easy
transi`on
for
current
sponsorship
• Recognise
commiNer
ac`vity
• Discounts
for
developing
countries
• Governance
role
for
gold
members
• Consor`um
members

13. Membership
types
• Bronze
($2,500)
$250
for
developing
na`ons
• Silver
($5,000)
• Gold
($10,000)
• Pla`num
($20,000+)
• All
members
can
becoming
involved
in
governance.
hNp://duraspace.org/about_membership

14. Where
are
we
at
currently?
• What
versions
are
we
running
in
the
UK?
– 1.6x
– 1.7x
– 1.8x
– 3x
– 4x
Image
Credit
hNps://flic.kr/p/7vMBN7
CC
BY-­‐NC
2.0
Anssi
Koskinen

15. DSpace
4
• Released
December
2013
• 59
total
contribu`ons
• 4.1
March
2014
• 4.2
July
2014
hNp://`nyurl.com/dspace-­‐4-­‐0
hNp://demo.dspace.org/

16. DSpace
4
func`onality
• ETHOS
Support
(University
of
S`rling)
• New
JSP
user
interface
based
on
Bootstrap
• Lots
of
XMLUI
features
added
to
JSPUI
• Discovery
by
default
• Read-­‐only
REST-­‐API
• Advanced
Embargoes

17. • Google
Scholar
enhancements
• DOI
Support
• Request
a
copy
func`onality
• Enhanced
thumbnails
• Sherpa
Romeo
Integra`on
DSpace
4
func`onality

18. DSpace
5
• Due
late
2014
• October
deadline
for
development
• Main
Features:
– ORCID
support
– Metadata
for
all
objects
– Audio/Visual
Streaming
– Mirage
2
XMLUI
re-­‐design
hNps://atmire.com/preview/

21. Jisc
Repository
Shared
Services
Project
Balviar
Notay,
Jisc
Bringing
together
key
repository
services
to
deliver
a
connected
na4onal
infrastructure
to
support
OA

22. Jisc
Support
for
Integra`on
• Repositories
to
implement
-­‐
patches,
scripts
and
plug-­‐ins
produced
by
repository
shared
services.
Support
is
being
planned
via:
• Repository
Support
Project
(RSP)
• Planning
co-­‐ordina`on
with
plaqorm-­‐specific
support
through
Eprints
Services,
the
DSpace
community
and
Fedora.
Balviar
Notay,
Jisc

23. How
to
get
involved?
• Mailing
Lists
(general,
tech,
dev)
• Join
DCAT
(DSpace
Community
Advisory
Team)
• Join
the
Wednesday
Developer
Mee`ngs
• Answer
or
post
ques`ons
on
stackoverflow.com
• Review
and
create
documenta`on
• Submit
a
patch
or
feature
• Get
your
ins`tu`on
to
join
as
members

24. Credits
• Tim
Donohue:
hNp://www.slideshare.net/DuraSpace/duraspace-­‐plenary-­‐dspace-­‐
overview-­‐at-­‐or14
• Jonathon
Markow:
hNp://www.slideshare.net/DuraSpace/the-­‐new-­‐duraspace-­‐
membership-­‐and-­‐governance-­‐models-­‐webinar
• Jonathon
Markow,
Tim
Donohue,
Lieven
Droogmans,
Debra
Hanken
Kurtz:
hNp://www.slideshare.net/DuraSpace/future-­‐of-­‐dspace-­‐steering-­‐
group-­‐panel-­‐at-­‐or14
• Tim
Donohue,
hNp://www.slideshare.net/tdonohue/d-­‐space-­‐roadmapor14

25. Ques`ons?
If
you
have
any
further
ques`ons:
Claire
Knowles
Library
Digital
Development
Manager
University
of
Edinburgh
Claire.knowles@ed.ac.uk
@cgknowles