►
From YouTube: NIIIFTY: Data Reliability for the Cultural Heritage Sector using IPFS - Edward Silverton
Description
This talk was given at IPFS Camp 2022 in Lisbon, Portugal.
A
I'm
here
to
talk
to
you
about
a
project
called
Nifty:
it's
data
reliability
for
the
cultural
heritage
sector
using
ipfs,
so
I'm
from
a
company
in
the
UK,
a
creative
agency
called
nemeseen.
A
We
specialize
in
storytelling
with
online
digital
collections.
So
this
is
a
on
the
right.
You
can
see
a
project,
that's
on
recently
for
the
Grace
darling
Museum
in
Northumberland,
where
we
created
a
a
Unity
scene
of
a
using
kind
of
architectural
drawings
of
a
of
her
grace,
darling's
childhood
home,
to
construct
the
lighthouse
in
unity
and
then
look
at
the
camera
kind
of
weaves
its
way
through
the
lighthouse
and
tells
the
story
of
Grace
darling.
A
It
was
a.
It
was
installed
in
the
museum
as
a
as
a
three-screen
kind
of
immersive
video
installation.
A
A
So
it's
basically
a
storytelling
tool
where
you
can
create
scrolly
telling
stories
slideshows,
quizzes
Etc,
so
here's
an
example
of
a
story
about
Jane
Austen.
So
it's
it's
a
scrully
telling
story.
So
as
you
scroll
it,
this
isn't
the
video
I'm
just
going
to
click
through.
So
that's
the
kind
of
Landing
screen
and
as
you
scroll,
it's
loading
up
high
resolution
images
as
you
go.
A
This
is
I
think
from
the
Library
of
Congress,
as
it
tells
you
something
about
the
image
on
the
left-hand
side
and
as
you
keep
scrolling,
it
moves
around
the
image.
It's
telling
you
about
how
a
signature
here
other
facts
about
Jane
Austen
and
it
also
supports
3D.
So
we've
got
a
scan
of
the
of
a
writing
desk
from
the
British
library
in
there,
so
it's
kind
of
as
you
scroll
it's
moving
around
this
object
telling
you
about
it.
A
So
the
standard
it's
using
is
called
triple
if
it
stands
for
international
image.
Interoperability
framework.
This
has
been
around
a
long
time
about
10
years.
I've
been
working
with
it
since
it
sort
of
came
out,
I,
guess,
yeah
and
it's
kind
of
a
family
of
web
standards,
primarily
for
working
with
high
resolution
images,
tiled
images,
so
here's
a
great
example
of
what
you
can
do
with
it.
This
is
a
Japanese
tax
map
with
the
guy
Wayne
who
digitized
it
from
Stanford
to
get
to
show
scale
and
then
overlaid
at
the
top.
A
A
S
of
cultural
heritage
institutions
worldwide,
all
the
big
ones
basically-
and
this
is
the
the
image
API.
So
what
triple
AF
kind
of
innovated
with
in
is
using
URLs
to
Define
tiles
within
images
or
regions
of
images.
A
So
you
can
see
here
it's
second
the
original
image
and
then
it's
addressing
a
region
of
it
and
then
it's
scaling
it
and
you
can
also
optionally
rotate
and
get
a
different
levels
of
quality
as
well.
There's
also
the
presentation
API.
A
So
this
is
a
Json
format
that
allows
you
to
present
your
high
resolution
images
in
kind
of
book
format,
so
kind
of
a
rectober
so
kind
of
layout.
It
also
works
with
manuscripts
and
other
types
of
content,
and
it
relies
on
it's
Json
LD,
so
it
relies
on
URLs
as
identifiers,
and
you
can
see
one
highlighted
there
as
an
example.
A
So
the
problem
with
triple
AF,
though,
is
it,
can
often
change
or
become
unavailable,
and
this
can
cause
tools
like
exhibit
to
break
so
on
the
right
there.
We've
got
a
kind
of
screenshot
of
someone's
error
page
this
as
I
maintain
the
exhibit
website.
I've
had
to
update
the
Showcase
several
times
now,
because
data
has
gone
down
or
changed
and
it's
you
know
the
official
line
on
this
in
the
Community
is
that
this
this
shouldn't
happen,
but
in
practice
it
does
happen
and
it
happens
regularly.
A
So
is
it
possible
to
say
this
can't
happen
so
I've
been
a
big
fan
of
ipfs
pretty
much
since
it
came
out.
You
know
it's
got
really
interesting
properties,
immutability
so
addressing
something
by
its
content.
Hash-
and
it's
kind
of
you
know
verifiable
in
that
regard.
It's
also
just
distributed,
so
content
can
be
pinned
in
multiple
locations.
So
when
you
request
something
you're,
definitely
getting
back
the
thing
you
asked
for
and
if
it's
not
on
the
server
or
you
know
on
a
server,
it
could
be
on
another
server
elsewhere.
A
So
this
is
quite
a
nice
solution,
potentially
for
the
exhibit
problem.
So
I
made
a
prototype
to
test
publishing
triplife
data
on
ipfs
I
think
it's
the
first
time.
Anyone
has
done
this,
so
this
is
a
I
just
use.
A
The
photograph
I
took
in
Barcelona
and
I
could
generate
the
tiles
and
the
Manifest
and
then
I
added
it
to
ipfs
and
then
I
also
minted
an
nft
of
it,
because
you
can
do
that
when
you've
got
a
Content
ID,
you
can
view
the
I
the
example
there,
so
that
was
that
was
the
first
step,
but
then,
as
a
developer,
I
can
do
that.
But
I
want
my
clients
to
be
able
to
do
that.
A
So
I
want
to
make
it
a
drag
and
drop
kind
of
experience,
so
I
applied
for
a
falcoin
Dev
grant
for
what
I
ended
up
calling
Nifty,
and
this
is
going
to
use
web3.
storage
on
the
back
end
to
kind
of
store
the
generated
image,
tiles
Etc
and
you
can
read
about
the
the
grant
there
so
yeah
once
that's
kind
of
complete
I
people
will
be
able
to
kind
of
store
there
triple
F
data
on
ipfs.
A
It
will
be
kind
of
distributed
potentially
by
you
know,
allowing
cultural
heritage
institutions
to
pin
it
on
their
own
nodes
as
well,
but
also
there's
this
kind
of
secondary
aspect
of
it's
kind
of
mintable,
so
I'm
interested
to
kind
of
dive
into
that
a
bit
more
and
you
know,
use
nfts
as
kind
of
canonical
identifiers
for
this
kind
of
cultural
heritage
content,
and
that's
it.