Dryad
Cura)on
Prac)ces
August
2012
Dryad
Package/File
Structure
DATA
PACKAGE
METADATA
PUBLICATION/
ARTICLE
DATA
FILE
METADATA
DATA
FILE
METADATA
BITSTREAM
(DATA)
BITSTREAM
(DATA)
BITSTREAM
(README)
Scholarly
publicaHon/arHcle
associated
with
Dryad
data
package,
not
stored
in
Dryad
A
Dryad
data
package
is
a
conceptual
and
metadata
object.
It
contains
a
summary
descripHon
of
all
the
consHtuent
data
files
and
creates
the
link
with
the
associated
publicaHon.
Each
data
file
has
a
metadata
descripHon
and
at
least
one
bitstream
(addiHonal
bitstreams,
such
as
readme
files,
are
opHonal).
Metadata
pertaining
to
the
publicaHon
(citaHon,
publicaHon
date,
arHcle
DOI)
is
stored
in
the
data
package.
Metadata
pertaining
to
each
file
and
its
embargo
period
is
stored
in
each
file
record.
Important
Cura)on
Documents
•  CuraHon
manuals
–  hTp://wiki.datadryad.org/CuraHon
•  [email protected]
–  NoHficaHons
of
new
submissions,
newly
published
arHcles,
other
assignments
–  Correspond
with
authors
using
this
account,
send
as
[email protected]
•  Curator
office
whiteboard
–  Google
doc
shared
with
dryadassistant
google
account
–  Includes
login
informaHon
for
Dryad
user
accounts,
EZID,
etc.
•  Submission
tracking
spreadsheet
–  Google
doc
shared
with
dryadassistant
google
account
•  Integrated
journal
metadata
emails
–  Access
via
[email protected]
•  Templates
for
correspondence
–  hTp://wiki.datadryad.org/Templates_for_Correspondence
Integrated
and
Non‐Integrated
Journals
•  Non‐Integrated
–  No
coordinaHon
between
journal
and
Dryad
(no
metadata
emails,
journal
contact
addresses
for
reporHng,
etc.)
•  Integrated
–  Metadata
emails
send
info
ahead
of
submission
–  May
use
review
workflow
or
only
archive
data
a]er
manuscript
acceptance
–  May
require
‘blackout’
of
Dryad
submission
unHl
arHcle
publicaHon
–  Journal
contacts
are
noHfied
upon
submission
for
review
(if
using
review
workflow),
acceptance
to
blackout
queue,
approval/archiving,
and
weekly
summary
The
original
integrated
workflow
is
represented
to
the
right.
Some
journals
now
also
use
a
review
workflow
with
addiHonal
steps
or
require
the
Dryad
data
package
to
remain
hidden
unHl
a]er
arHcle
publicaHon
(what
we
call
“blackout”).
Further
integraHon
details
are
available
in
the
following
presentaHon:
hTp://wiki.datadryad.org/wg/
dryad/images/c/c6/
DryadIntegraHonOverview.pdf
author
prepare manuscript
and related data files
JOURNAL
submit manuscript
manuscript review
DRYAD
upload data
editor
accepted?
no
accepted?
yes
send article
description
Dryad data
package
send data
identifier (DOI)
curation
data curator
published article
(with data citation)
published data
(with article citation)
Image based on Lowry, R., E. Urban, and P. Pissierssens (2009), A New Approach to Data
Publication in Ocean Sciences, Eos Trans. AGU, 90(50), doi:10.1029/2009EO500004.
Basic
Integrated
Workflow
(no
review)
Author
submits
manuscript
to
journal
Journal
reports
accepted
manuscript
to
Dryad;
Dryad
creates
provisional
record
Journal
invites
author
to
submit
data
to
Dryad
&
provides
link
to
provisional
record
Author
submits
data
to
Dryad
&
receives
DOI Dryad
curator
approves
submission
&
sends
DOI
to
author
&
journal
Dryad
publishes
data
files
with
link
to
ar)cle;
Journal
adds
Dryad
DOI
to
all
forms
of
ar)cle
Review
Workflow
•  Journal
sends
manuscript
informaHon
to
Dryad
before
manuscript
acceptance
and
invites
authors
to
upload
data.
•  Dryad
submission
is
routed
to
private
review
workspace,
not
main
curaHon
and
publicaHon
queue.
Passkey
link
is
sent
to
journal
for
editor/reviewer
access
to
Dryad
submission.
•  Author
may
conHnue
to
add
files
while
submission
is
in
review
workspace.
•  Journal
sends
second
metadata
email
to
Dryad
with
manuscript
acceptance
noHficaHon,
triggering
any
associated
submission
to
move
from
review
to
curaHon.
•  Curator
inspects
and
approves,
queues,
or
rejects
submission,
as
in
basic
workflow.
Review
Workflow
Author
submits
manuscript
to
journal
Journal
reports
manuscript
under
review
to
Dryad;
Dryad
creates
provisional
record
Journal
invites
author
to
submit
data
to
Dryad
&
provides
link
to
provisional
record
Author
submits
data
to
Dryad,
using
link
sent
by
journal
to
provisional
record
Dryad
sends
review
passcode
and
DOI
to
author
&
journal
Upon
ar)cle
acceptance,
journal
no)fies
Dryad
Dryad
publishes
data
files
with
link
to
ar)cle;
Journal
adds
Dryad
DOI
to
all
forms
of
ar)cle
Naviga)on
•  NoHficaHons
of
new
tasks
go
to
[email protected]
•  Log
in
to
Dryad
site
with
[email protected]
and
[email protected],
as
appropriate
–  hTp://datadryad.org/password‐login
•  Dryad
site
le]
sidebar:
–  My
Submissions
are
submissions
you
have
created
–  My
Tasks
are
submissions
you
can
act
on
as
a
curator
–  Workflow
Overview
provides
a
way
to
search
for
items
before
or
a]er
archiving,
and
to
force
changes
in
their
status
that
aren’t
always
available
in
the
interface
Overview
of
New
Submission
Processing
JOURNAL
INTEGRATED
NON‐INTEGRATED
SETTINGS
ARTICLE
STATUS
REVIEW?
BLACKOUT?
METADATA
EMAIL?
SPREADSHEET
ENTRY?
ARTICLE
STATUS
REVIEW
FILES
FILES
APPROPRIATE
APPROPRIATE
NOT
APPROPRIATE
QUEUE
NO
BLACKOUT
QUEUE
FILES
SETTINGS
BLACKOUT
APPROPRIATE
PUBLISHED
ACCEPTED
ERROR
PUBLISHED
NOT
PUBLISHED
REJECT
APPROVE
NOT
APPROPRIATE
APPROVE
REJECT
FILES
NOT
APPROPRIATE
REJECT
NOT
APPROPRIATE
APPROPRIATE
APPROVE
REJECT
Journal
SeQngs
•  See
JournalSubmissionTracking
spreadsheet
shared
in
google
docs.
•  First
tab
(“Notes”)
lists
each
integrated
journal
and
its
review
and
blackout
sekngs.
•  Also
search
for
duplicate
submissions
or
notes
in
appropriate
sheet.
Ar)cle
Status
•  If
integrated
submission,
should
be
indicated
in
metadata
email
(not
stated
=
accepted
manuscript)
•  Look
for
arHcle
DOI
or
volume
informaHon
in
the
submiTed
metadata.
•  Google
search
and/or
visit
publisher
website.
Claiming
Submissions
1.  New
submissions
will
be
listed
on
the
My
Tasks
page
in
the
list
labeled
In
Cura)on:
Unclaimed
2.  Choosing
account
with
which
to
claim
submission
A.  If
item
is
going
to
be
approved/rejected
(publicaHon
blackout
is
not
required
=
integrated
journal
that
does
not
require
blackout
OR
any
journal
if
the
arHcle
has
been
published)

Claim
with
Dryad
Assistant
account
B.  If
item
is
going
to
publicaHon
blackout
queue
(integrated
journals
requiring
publicaHon
blackout
OR
non‐
integrated
journals
ahead
of
arHcle
publicaHon)

Claim
with
Dryad
Queue
account
3.  Once
claimed,
submission
will
appear
in
In
Cura)on:
Claimed
list
on
My
Tasks
page
4.  Click
Edit
item(s)
buTon
(lower
right
when
viewing
the
claimed
submission)
and
open
package
and
all
files
in
tabs
to
inspect
files
and
edit
all
metadata
Inspec)ng
Files
•  Check
for
technical
problems,
corrupt
files,
files
that
won’t
open
in
expected
so]ware,
etc.
•  Files
should
contain
something
that
looks
like
data,
with
a
very
broad
definiHon
of
data
(supplementary
figures,
mulHmedia,
etc.,
are
ok,
the
manuscript
itself
is
not).
•  Look
for
copyright
statements
and
licenses
(not
good).
•  Look
for
idenHfiable
human
subject
data
(err
on
the
side
of
cauHon).
•  Look
for
duplicated
files,
data
files
uploaded
in
place
of
readme
files,
etc.,
and
clean
these
up.
Rejec)ng
Submissions
•  The
most
common
reasons
for
rejecHon
are
inappropriate
files,
submissions
associated
with
integrated
journals
for
which
we
have
no
metadata
email,
and
integrated
submissions
that
should
have
been
directed
to
the
review
workspace
but
the
author
did
not
use
the
integrated
process.
A
submission
might
also
be
rejected
because
a
journal
is
out
of
scope,
but
always
consult
a
senior
curator
before
rejecHng
for
this
reason.
•  When
rejecHng
a
submission,
you
must
enter
a
reason.
This
reason
will
be
sent
to
the
submiTer;
it
should
be
courteous
and
should
explain
clearly
to
them
what
the
problem
was
and
how
they
can
fix
it
if
they
wish
to
resubmit.
•  See
Templates
for
Correspondence
wiki
page
for
common
rejecHon
explanaHons.
Edi)ng
Metadata
• 
• 
• 
• 
• 
REMEMBER:
some
metadata,
such
as
author
names,
is
repeated
on
the
package
and
files
and
will
need
to
be
edited
in
both
places.
Scan
over
all
metadata
to
see
if
it
looks
reasonable
and
idenHfy
problems.
Strip
any
formakng
tags
or
mangled
characters.
InternaHonal
or
special
characters
can
o]en
be
copied
and
pasted
from
metadata
email
or
other
source
on
the
web.
Check
the
journal
name,
especially
for
non‐integrated
journals.
It
should
match
exactly
the
name
already
in
use
in
the
repository.
If
it’s
a
new
journal,
ask
a
senior
curator
about
establishing
a
new
name.
Author
names
should
be
formaTed
as
–  LastName,
FirstName
M.
I.
–  remove
any
Htles,
such
as
“PhD”
• 
Data
package
Htle
should
be
formaTed
as
• 
Add
specialized
keywords
(geographic,
temporal,
scienHfic
name),
moving
them
from/to
general
subject
keywords,
as
appropriate.
ScienHfic
names
should
be
LaHn
(common
names
go
in
dc:subject
instead)
and
should
be
recognized
by
hTp://
eol.org/.
Look
for
line
breaks,
especially
in
arHcle
abstract
and
file
descripHons
and
edit
these
fields
as
needed
for
clarity
when
the
content
is
displayed
without
line
breaks.
Check
for
inappropriate
embargoes
(custom
when
we
have
no
info
from
journal,
unHlArHcleAppears
when
arHcle
is
out)
and
adjust
as
needed.
If
custom
embargo,
add
embargo
period
(from
journal)
as
dryad:curatorNote
in
file
metadata.
• 
• 
–  Data
from:
ArHcle
Htle
in
sentence
case
Approving/Archiving
(no
blackout)
1.  Check
for
duplicates
and
notes
in
tracking
spreadsheet,
if
you
haven’t
already
done
so.
2.  Click
Approve
(will
need
to
click
twice
if
item
is
going
through
blackout
first,
based
on
sekngs).
Email
noHficaHon
is
sent
automaHcally.
3.  Visit
Dryad
homepage
and
find
item
in
Recently
Published
list
(if
not
there,
look
for
it
on
My
Tasks
page
or
track
down
any
error).
4.  Check
for
duplicated
package
DOI
and
delete,
if
needed.
If
there
is
a
duplicated
package
DOI
the
link
from
the
homepage
to
the
package
won’t
work,
and
you’ll
need
to
manually
modify
the
link
to
reach
the
package
page.
5.  Check
that
package
DOI
resolves
correctly
(may
be
a
few
minutes
delay).
Log
in
to
EZID
and
check/fix,
if
needed.
6.  Update
submission
tracking
spreadsheet.
Placing
Submission
in
Publica)on
Blackout
Queue
You
should
have
already
claimed
the
item
with
Dryad
Queue
account,
inspected
files,
edited
metadata,
and
checked
for
duplicate
submissions
at
this
point.
1.  Register
package
DOI
in
EZID.
Go
to
Create
IDs
‐>
Advanced
in
order
to
specify
your
DOI.
Use
hTp://
datadryad.org/publicaHonBlackout
as
the
locaHon
and
leave
all
other
descripHon
blank.
2.  Send
acceptance
email
to
submiTer
(and
journal
contacts,
if
integrated
journal).
Template
is
saved
as
a
dra]
in
dryadassistant
gmail
account.
Journal
contact
emails
should
appear
in
package
metadata
and
Dryad
journal
config
file.
3.  Add
entry
to
submission
tracking
spreadsheet.
4.  Leave
task
claimed
in
Dryad
Queue
account.
Upda)ng
Archived
Items
Once
Ar)cle
is
Published
You
have
made
a
match
between
a
published
arHcle
and
a
Dryad
data
package
that
needs
to
be
updated.
1. 
2. 
3. 
4. 
Check
author
names,
arHcle
Htle,
and
arHcle
abstract
against
published
arHcle
and
update
if
needed.
Edit
package
dc:date.issued
to
match
earliest
(online)
publicaHon
date
of
arHcle
(format
as
YYYY‐MM‐DD)
Add
arHcle
DOI
to
package
dc:relaHon.isreferencedby
(format
as
doi:####)
Add
arHcle
citaHon
to
package
dc:idenHfier.citaHon
or
updated
exisHng
citaHon
(if
advance
access
online
arHcle
now
print
citaHon).
Format
as:
or
5. 
6. 
7. 
LastName
F,
LastName
FM
(YYYY)
ArHcle
Htle
in
sentence
case.
Journal
Name
Vol(Num):
page‐page.
LastName
F,
LastName
FM
(YYYY)
ArHcle
Htle
in
sentence
case.
Journal
Name,
online
in
advance
of
print.
Li]
embargoes
or
set
embargo
end
dates
for
each
file,
as
appropriate.
Go
to
the
Item
Embargo
pane
in
Edit
Item
to
work
with
embargoes.
Visit
public
view
of
package
page
(leave
Edit
Item)
and
verify
arHcle
citaHon,
resolvable
arHcle
DOI,
and
updated
embargoes.
Update
submission
tracking
spreadsheet.
Approving
Submission
out
of
Publica)on
Blackout
1.  Update
metadata
as
described
in
Upda)ng
Archived
Items
Once
Ar)cle
is
Published.
Because
this
submission
isn’t
archived
yet,
dates
won’t
have
been
added
to
the
metadata
by
the
system,
so
you
will
add
the
arHcle
publicaHon
date
to
package
as
dc:date.issued,
instead
of
ediHng
an
exisiHng
value.
2.  Click
Approve.
Find
item
in
PublicaHon
Blackout
list
on
My
Tasks
page.
Claim
the
task
and
click
Approve
again.
3.  Visit
Dryad
homepage
and
find
item
in
Recently
Published
list
(if
not
there,
look
for
it
on
My
Tasks
page
or
track
down
any
error).
4.  Check
for
duplicated
package
DOI
and
delete,
if
needed.
If
there
is
a
duplicated
package
DOI
the
link
from
the
homepage
to
the
package
won’t
work,
and
you’ll
need
to
manually
modify
the
link
to
reach
the
package
page.
5.  Update
package
DOI
in
EZID
(use
Lookup
funcHon)
and
change
locaHon
to
point
to
public
item
URL.
6.  Update
file
embargoes
(li]
or
set
end
date,
appropriate).
Go
to
the
Item
Embargo
pane
in
Edit
Item
for
each
file
to
work
with
embargoes.
7.  Update
submission
tracking
spreadsheet.
PACKAGE
METADATA
GUIDE
Authors
dc:contributor.author
repeatable
required
LastName, FirstName M.
Corresponding author
not repeatable
required
LastName, FirstName M.
Spatial coverage
dc:contributor.correspo
ndingAuthor
dc:coverage.spatial
repeatable
optional
place names, geographic coordinates, etc
Temporal coverage
dc:coverage.temporal
repeatable
optional
intended for geologic timespans, but years and other values are accepted
Approval timestamp
dc:date.accessioned
not repeatable
required
system-generated upon submission approval
Approval timestamp
dc:date.available
not repeatable
required
system-generated upon submission approval
Article publication date
dc:date.issued
not repeatable
required
Data package DOI
dc:identifier
not repeatable
required
system-generated to match approval date, later edited by curator to article
publication
doi:10.5061/dryad.####
Article citation
dc:identifier.citation
not repeatable
optional
modified PLoS citation style
Journalʼs manuscript
ID
Data package handle
dc:identifier.manuscript
Number
dc:identifier.uri
not repeatable
optional
only for integrated submissions
not repeatable
required
Abstract
dc:description
not repeatable
optional
http://hdl.handle.net/10255/dryad.####, system-generated upon submission
approval
article abstract
Component data file
DOIs
Article volume, issue,
year
Article DOI
dc:relation.haspart
repeatable
required
doi:10.5061/dryad.####/1, doi:10.5061/dryad.####/2, etc
not repeatable
optional
only present if entered by depositor during submission
not repeatable
optional
doi:####
Keywords
dc:relation.ispartofseri
es
dc:relation.isreference
dby
dc:subject
repeatable
optional
Data package title
dc:title
not repeatable
required
Data from: Article title
Record type
dc:type
not repeatable
required
system-generated, now set to “Article”
Curator note
dryad.curatorNote
repeatable
optional
rarely used
Scientific names
dwc:ScientificName
repeatable
optional
Latin taxon names
Journal name
prism:publicationName
not repeatable
required
use authorized form of name only
FILE
METADATA
GUIDE
Authors
dc:contributor.author
repeatable
required
LastName, FirstName M.
Spatial coverage
dc:coverage.spatial
repeatable
optional
place names, geographic coordinates, etc
Temporal coverage
dc:coverage.temporal
repeatable
optional
intended for geologic timespans, but years and other values are accepted
Approval timestamp
dc:date.accessioned
not repeatable
required
system-generated upon submission approval
Bitstream availability
timestamp
Approval date
dc:date.available
not repeatable
required
dc:date.issued
not repeatable
required
system-generated upon availability of bitstreams for download (will not
appear if file is embargoed)
system-generated upon submission approval
Data file DOI
dc:identifier
not repeatable
required
doi:10.5061/dryad.####/#
Data file handle
dc:identifier.uri
not repeatable
required
File description
dc:description
not repeatable
optional
http://hdl.handle.net/10255/dryad.####, system-generated upon submission
approval
brief file description entered by depositor
Associated data
package DOI
Rights information
dc:relation.ispartof
not repeatable
required
doi:10.5061/dryad.####
dc:rights.uri
not repeatable
required
CC0 URI for all items except a few legacy items under Original License
Keywords
dc:subject
repeatable
optional
Data file title
dc:title
not repeatable
required
Record type
dc:type
not repeatable
required
system-generated, now set to “Dataset”
Curator note
dryad.curatorNote
repeatable
optional
rarely used, mostly to specify custom embargo dates
Scientific names
dwc:ScientificName
repeatable
optional
Latin taxon names
Embargo end date
dc:date.embargoedUntil
not repeatable
optional
Embargo type
dc:type.embargo
not repeatable
required
YYYY-MM-DD, will have value 9999-01-01 for embargoed items when the
article has not yet been published then edited by curator to real date, not
present for items that were never embargoed or after embargo has been
lifted (see dc:date.available for embargo lifting timestamp)
controlled list of values: none, untilArticleAppears, oneyear, custom