iiif: discovery of resources

23
@azaroth42 rsanderson @getty.edu IIIF: Interoperabilituy IIIF: Discovery @azaroth42 rsanderson @getty.edu Discovery of IIIF Resources International Image Interoperability Framework

Upload: robert-sanderson

Post on 13-Feb-2017

77 views

Category:

Technology


0 download

TRANSCRIPT

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Discovery  of  IIIF  Resources

InternationalImageInteroperabilityFramework

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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?

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Success?

Scenario:  An  end  user  has  an  information  needSuccess:  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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Scope?

IIIF  Resources:• Content  Resources  (currently  Images)• Description  Resources  (currently  Manifests,  Annotations)

Discovery  requires  Description  resources  to  provide  the  contextof  the  Content  resourcesThe  Image  API  alone  provides  no  description  of  the  Image  content,  just  technical  and  rights  metadata

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Presentation  API

Provide  only  the  informationnecessary  for  an  application  topresent  the  object  to  the  user

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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.

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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)

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Approach  Discussed

Three  Components:1. Central  Registry  of  links2. Crawling  Software  that  crawl  those  links  for  resources3. User  oriented  Search  Engines  over  those  resources

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Approach  Discussed

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Approach  Discussed

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Approach  Discussed

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Central  Registry

Registry  of…• Top  level  Collections• All  Collections?• All  Manifests?

With  APIs  for:• Browse/Search• Submission

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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?

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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!  

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

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??

@azaroth42

[email protected]

IIIF:  Interope

rabilituy

IIIF:  Disc

overy

@[email protected]

Discuss!