1. SNAC User Interface
2011 May 25 for OCLC Research
Brian Tingle
Digital Special Collections
California Digital Library
University of California, Office of the President
2. SNAC Interface Outline
Intro
Meet the target users
Design Philosophy
Technologies Used
Social Graph Visualization
Linked Data Issues
Site Demo
3. Tingle, Brian Cedric, 1972-
1986 Used Melvyl for the first time
1996 UC San Diego Libraries
2001 CDL
2006 Technical Lead, Digital Special Collections
Usually back end web programmer, SNAC is my first UI/UX Design
http://btingle.bitbucket.org/
5. Meet the target users
Randy: Graduate student working on a PhD that involves biographies and the study of diplomatic families and networks.
Sometimes he comes to the site looking for information on specific people; other times he is looking for information on a
specific subject or event. He also TAs an undergraduate history class and sometimes has to help students find topics for papers.
6. Meet the target users
Randy: Graduate student working on a PhD that involves biographies and the study of diplomatic families and networks.
Sometimes he comes to the site looking for information on specific people; other times he is looking for information on a
specific subject or event. He also TAs an undergraduate history class and sometimes has to help students find topics for papers.
Connie: Works at an institution that contributed records to the project. Is going to be asking themselves how this site
would be useful to their users. Wants to understand how their records were used and what the added value is.
7. Meet the target users
Randy: Graduate student working on a PhD that involves biographies and the study of diplomatic families and networks.
Sometimes he comes to the site looking for information on specific people; other times he is looking for information on a
specific subject or event. He also TAs an undergraduate history class and sometimes has to help students find topics for papers.
Connie: Works at an institution that contributed records to the project. Is going to be asking themselves how this site
would be useful to their users. Wants to understand how their records were used and what the added value is.
Quincy: Library School Student working to QA record matching.
8. Meet the target users
Randy: Graduate student working on a PhD that involves biographies and the study of diplomatic families and networks.
Sometimes he comes to the site looking for information on specific people; other times he is looking for information on a
specific subject or event. He also TAs an undergraduate history class and sometimes has to help students find topics for papers.
Connie: Works at an institution that contributed records to the project. Is going to be asking themselves how this site
would be useful to their users. Wants to understand how their records were used and what the added value is.
Quincy: Library School Student working to QA record matching.
Adele: Person doing authority work during collection processing.
9. Meet the target users
Randy: Graduate student working on a PhD that involves biographies and the study of diplomatic families and networks.
Sometimes he comes to the site looking for information on specific people; other times he is looking for information on a
specific subject or event. He also TAs an undergraduate history class and sometimes has to help students find topics for papers.
Connie: Works at an institution that contributed records to the project. Is going to be asking themselves how this site
would be useful to their users. Wants to understand how their records were used and what the added value is.
Quincy: Library School Student working to QA record matching.
Adele: Person doing authority work during collection processing.
Lenny: Lenny likes linked data, and wants to be able to mine the links that have been established programatically.
13. EAC’s Implicit Information Architecture
Expose Schema’s terminology in user interface
Pick metadata that could get turned to facets
14. EAC’s Implicit Information Architecture
Expose Schema’s terminology in user interface
Pick metadata that could get turned to facets
XTF Section Types / based on hierarchy of EAC
15. Front End Stack
golden grid http://code.google.com/p/the-golden-grid/
form style http://formalize.me/
jquery and jquery ui
hoverIntent for advanced search
google analytics with event tracking
Uservoice forum, google spreadsheets for feedback
16. XTF XSLT Framework
Access system is based on a customized branch of CDL Publishing Group’s XTF
pre filter - do special tokenization to create custom EAC facets
https://docs.google.com/document/d/1wP9x6sdOZTagJNQXoyJfPh0Y6UzQgqLwLI86WSlIPbk/edit?hl=en_US
query parser - CGI params to XTF query XML
result formatter - XTF results to HTML
doc formatter - EAC-CPF to HTML
http://code.google.com/p/xtf-cpf/source/browse/?name=xtf-cpf
18. social graph visualization
EAC to graphML https://code.google.com/p/eac-graph-load/
simple JSON access to tinkerpop graph on backend with javscript
on front end in live prototype [current demo uses Dracula Graph
Library]
graphML file with open license should be viewable in other tools
19. Linked Data / Open Data
RDFa owl:sameAs links to VIAF
httpRange-14 (XTF URL + “#entity” for the car)
HTML5 microdata chronology
Future: RDF Dump with an Open Data License
based on Ed Summer’s “snac hacks” post
links to wikipedia and other sources