iwmw 2009: hands-on prototyping for (meta)data structures
TRANSCRIPT
![Page 1: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/1.jpg)
A centre of expertise in digital information managementwww.ukoln.ac.uk
UKOLN is supported by:
IWMW 2009Hands-on prototyping for
(meta)data structuresEmma Tonkin
Talat Chaudhri Alexey Strelnikov
![Page 2: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/2.jpg)
Introduction: metadata
What is it, why, and who cares?Actually covers quite a lot of things: Terminologies (taxonomies, controlled
vocabularies) Vocabularies Data structures/models (entity-relationship
models, conceptual models)
![Page 3: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/3.jpg)
Example For example:
'Event Metadata' excerpt
Event Type: WorkshopWorkshop LocationWorkshop TypeWorkshop Date (ISO 8601/W3CDTF)Opinion of Workshop {Boring, Interesting...}
![Page 4: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/4.jpg)
Eliciting information from users People have many different opinions, and
are capable of believing a lot of mutually contradictory ideas! :-)
Classification systems or data structures (hopefully) represent a consensus or at least a compromise
They therefore improve as we learn more about opinion
They also exist (and are useful) within a given context of use – for a given purpose
![Page 5: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/5.jpg)
Organisation...
Needs context! And exists for a purpose! Clean sock drawers are very nice, but
don't necessarily achieve anything unless you wear socks :)
![Page 6: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/6.jpg)
Prototyping techniques
Scope what we're trying to achieve! Learning about data structures Building quick easy models Finding easy ways to test them
![Page 7: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/7.jpg)
Free-listing 'Name all the x's you know'
eg. What types of image can you think of?
Or - What types of book are there? Or - What features might you use to
describe a book? Or – What sort of resources do
researchers create and publish? You might have your own use cases to
look at!
![Page 8: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/8.jpg)
Free-listing on “workshop metadata”
Peer review status
Date
Times
Duration
Event in which it occurs
Venue
Attendee list
Major trends, topics
Organiser(s)
Remote attendees?
Streamed?
Outputs?
Feedback
Presentations
Papers
Slides
Tutorials
Related articles, links, people
Coffee
Breaks
Networking (who met who)
Networking (wifi!!)
Pitches
Endorsements (SIG, etc)
Other events on similar topic
Other events run by same people...
Research area and findings
Related research activities
![Page 9: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/9.jpg)
Consistency
Build a table: (Note: This is a lot like social tagging!)
Compare and contrast your results.Word AppearancesVenue 5
Related research areas 2
Breaktime beverage 1
![Page 10: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/10.jpg)
Card sorting
Once you have some terms, then it's time to figure out how they fit together
This is especially easy to do with taxonomies
supports interface design by grouping functions/menus/etc,
Supports development of conceptual models
![Page 11: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/11.jpg)
Card Sorting: Method1) Make sure you have something to sort (using for
example the approach described earlier)
2) Bribe/trap some 'users' into agreeing to take part (note 'user' means 'the sort of person you are trying to write a system for')
3) After explaining the rules ('we're not testing you... just learning about the area') ask them to sort the cards into logical groupings
May be 'open' (users can create novel groupings or categories) or 'closed' (users must use predefined groupings)
![Page 12: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/12.jpg)
Using the results!
Another table can be built from these results:
Which categories were created? How frequently were they used (how
many users applied them?)Term/Category
Bird Nature Manmade Food Buildings
Seagull | ||
Lighthouse | |
Fish & Chips
||
![Page 13: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/13.jpg)
Evaluating an information structure (eg
classification/taxonomy) Scenario-based evaluation:
1) Get existing classification2) Develop some scenarios for which it
can be used3) See if it is possible to step through the
data structure in order to successfully complete a scenario
Example: Card sorting
![Page 14: IWMW 2009: Hands-on prototyping for (meta)data structures](https://reader035.vdocuments.mx/reader035/viewer/2022070516/587386551a28ab272d8b5dd3/html5/thumbnails/14.jpg)
Final comments
A user level view of things is probably simplified (and so it should be!)
What the user sees does not have to be what you store...
What the developer sees probably does – good documentation helps to encourage uptake of data structures/metadata.
Test early, test often. Card is cheaper than code!