10. Rule 1: The Information rule
All information in the
database is to be
represented in one and
only one way, namely by
values in column positions
within rows of tables.
15. ★ Storage of documents instead of records
★ Relations through hyperlinks
★ Dynamic or non-relational schemas
★ Weak, if any, typing
★ Focus on findability and storagability rather
than on schema adherence
16. ★ Shift from database to data modelling
★ Increasing importance of the domain
model
★ Semi-structured information
★ Content- and information rather than
website or document management
17. Two challenges 1. Domain Modelling
2. ‘External Classification’
19. ★ wireframes
★ navigation hierarchy
★ landing pages
★ lists of things
★ which content will fit where
★ ‘UML’-like domain model
★ content
★ structure
★ which content can be shown where
20. ★ domain model
★ define and name entities, content parts
and characteristics
define and establish relationships
★
think about findability
★
think about unit of manipulation
★
think about access control
★
31. ★ folksonomies
★ tags and optional tag bundles
★ content- rather than
classification-driven
★ user generated micro-content
★ shown as tag clouds
32.
33.
34. ★ user generated micro-content
★ represents a genuine value
★ must be moderated
★ history falsification
★ spam (PR whoring, p0rn)
★ lower the doorstep
★ no authentication required
★ QA burden for content owner
38. impediments
★ when a formal classification is
required
★ expert communities
★ classification ~ structure
★ when full-text searching is a viable
alternative
★ use tags to define weight in ranking
49. Organisation
★ Always make a thorough judgment as to
where to store what
★ RDBMS for relational data
★ Repositories for documents/information
★ Integrate instead of standardization
50. Classification
★ Rich metadata improves findability and (re)
usability
★ Somewhat-typed metadata
★ Tagging, folksonomies r k3wl, but
★ Business case needed
★ Don’t forget menial tasks
61. CCGC
★ Lessons learnt
★ think critically about metadata
★ the system might need adaptation (or the
data)
★ focus on domain model rather than on
the ‘website’