Discussion starter for discovery at the Hague Working Group meetings for IIIF in October 2016

1. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discovery
of
IIIF
Resources
International
Image
Interoperability
Framework

2. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discovery?
Two
main
aspects:
1. How
can
a
user
find
IIIF
resources?
2. How
can
she
then
get
those
resources
into
an
environment
where
she
can
use
them?

3. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Scenarios
Scenario:
An
end
user
has
an
information
need
that
can
be
fulfilled
by
IIIF
resources
Scenario:
An
institution
has
content
in
IIIF
compatible
formats
and
wishes
for
it
to
be
found
and
used
Scenario:
A
developer wants
to
know
how
to
build
software
that
enables
the
above
scenarios

4. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Success?
Scenario:
An
end
user
has
an
information
need
Success:
The
user
finds
the
resources
she
needs
Scenario:
An
institution
has
content
in
IIIF
compatible
formats
Success:
The
user
can
find
the
institution’s
resources
Scenario:
A
developer wants
to
know
how
to
build
software
Success:
There
is
a
clear
specification
for
what
to
build

5. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Scope?
IIIF
Resources:
• Content
Resources
(currently
Images)
• Description
Resources
(currently
Manifests,
Annotations)
Discovery
requires
Description
resources
to
provide
the
context
of
the
Content
resources
The
Image
API
alone
provides
no
description
of
the
Image
content,
just
technical
and
rights
metadata

6. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Presentation
API
Provide
only
the
information
necessary
for
an
application
to
present
the
object
to
the
user

7. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Scope?
IIIF
Resources:
• Content
Resources
(currently
Images)
• Description
Resources
(currently
Manifests,
Annotations)
IIIF
Search
API
covers
the
discovery
of
Annotations,
once
a
Manifest
has
been
found.
It
does
not cover
the
discovery
of
the
Manifest.

8. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Scope:
Discovery
of
Manifests
IIIF
Resources:
• Content
Resources
(currently
Images)
• Description
Resources
(currently
Manifests,
Annotations)
Discovery
is:
How
can
we
discover
Manifests?
(and
Collections
of
them)

9. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Constraints
• Presentation
API
does
not
include
semantic
descriptions
• But
can
reference
them
with
seeAlso
• IIIF
has
a
Resource
Centric
view
of
the
web
• e.g.
Google
Sitemap,
IIIF
Collections
• Not
a
service
oriented
view
• e.g.
OAI-­‐PMH,
SPARQL

10. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Approach
Discussed
Three
Components:
1. Central
Registry
of
links
2. Crawling
Software
that
crawl
those
links
for
resources
3. User
oriented
Search
Engines
over
those
resources

11. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Approach
Discussed

12. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Approach
Discussed

13. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Approach
Discussed

14. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Central
Registry
Registry
of…
• Top
level
Collections
• All
Collections?
• All
Manifests?
With
APIs
for:
• Browse/Search
• Submission

15. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Central
Registry:
Collection
or
Sitemap?
Collections:
• Is
already
specified
in
IIIF,
some
viewers
already
support
them,
can
build
hierarchies
• Need
to
distinguish
audience:
crawler
vs
human
Sitemaps:
• Implemented
by
Google
and
web
community
• But
unknown
what
Google
would
do
with
Manifests?
• ResourceSync extensions
for
metadata

16. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Central
Registry:
APIs?
Browse:
• Can’t
use
Sitemaps
as
only
for
the
domain
• Collections?
Search:
• Likely
to
be
out
of
date,
other
than
submission
date?
• Could
accomplish
by
browse
being
ordered?
Submission:
• Github PR?
Simple
web
form?
What
details
needed?

17. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Crawlers
Crawlers
start
from
the
Registry,
and
follow
links
to
collect
data.
Purpose:
Populate
search
engine(s)
with
data
Needs:
• Implementations
• Community
agreement
on
polite
crawling
• Notification
of
changes
will
help

18. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Search
Engines
Requirements:
• Index
the
crawled
data
• Provide
human
access
to
indexes
• (Not
machine
access)
• Allow
discovered
content
to
be
transferred
to
user’s
preferred
environment
for
use

19. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Search
Engines:
What
Data?
Presentation
API
strings
• Intended
for
humans,
not
machines
• Slightly
better
than
indexing
HTML
• =
No
fielded
search
(can’t
search
by
author,
date,…)
Referenced
semantic
descriptions
• Many,
many
different
standards
in
the
community
• Might
not
be
available

20. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Search
Engines:
Transfer
Need
to
be
able
to
get
IIIF
Resources
from
the
search
engine’s
UI
to
IIIF
client
UI.
Search
engine
could:
• Invoke
a
pre-­‐configured
client
per
result
• Invoke
a
pre-­‐configured
client
per
set
of
results
• Present
results
as
a
draggable Collection
• Present
hits
as
draggable Manifests

21. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Next
Steps?
• Decide
on
initial
format
to
use,
and
implement
if
needed
• Decide
on
APIs
for
registry
submission,
browse,
search?
• Decide
on
scope/size
of
registry
• Implement
simple
registry
and
encourage
submission
• Implement
crawlers
starting
from
the
registry
• Implement
simple
search
engine
over
crawled
data
• Iterate
based
on
experience!

22. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Next
Steps?
• Somehow
bootstrap
from
Aggregators
like
Europeana?
• Don’t
want
to
be
tied
to
region
specific
Cultural
Heritage?
• IIIF-­‐C
/ iiif.io could/should
host
the
registry?
• Working
Groups
to
produce
short
lists
of
standards
to
reference
via
seeAlso,
with
recommended
profiles?
• Other??

23. @azaroth42
rsanderson
@getty.edu
IIIF:
InteroperabilituyIIIF:
Discovery
@azaroth42
rsanderson
@getty.edu
Discuss!