UKOLN is supported by:

QA for Collection-Level DescriptionAnn Chapman and Bridget Robinson

Collection Description Focus

A centre of expertise in digital information management

www.ukoln.ac.uk

                                                             

Where are we …….

• Morning session focused on:– What is a collection?– Need for collection level descriptions– Format to hold collection level data

• This session focuses on:– Ensuring quality of data – Ensuring quality of application

                                                             

Why collection description?

• Interest in collections as well as items– From collections to items– From items to collections

• Using resources of varying types

• Using resources across sectors

• Using resources across domains

                                                             

Collection description data

• Using a format – RSLP schema ‘de facto’ standard

• Consistent data collected– Users can predict information held– Machine-to-machine exchange

• Support searching– Consistent terms used

                                                             

QA and Format

• RSLP schema

• Variation– Added elements– Unused elements– Modified elements

• Label changes• Sub-divided elements

                                                             

QA and terminology

• Choice of sets of terms– User type (research, study, interest)– User age group (children, teens, adults)– Focus of collection description database

• Subject• Objects• Time or Place

– Format or resource types

                                                             

QA and editorial control

• Can anyone create records?

• Should records be assessed/edited?– Who assesses/edits?

• Guidelines for record creation– Text– Use of chosen term sets– Data for specific elements

                                                             

QA to support the user

• Users may have physical and / or sensory impairment– Speech synthesisers read out labels as

well as data in fields– Consistent order of data will help

• User Eligibility, Charges, Restrictions

• English may not be first language of user

                                                             

QA planning

• QA relates to:– Data– Software

• Build QA into early planning

• Document decisions

• Train record creators

• Create guideline documents

                                                             

Standards in language and terminology

• Use of a standard terminology set e.g. LCSH

• Use of authority control files – Geographic names– Organisation/personal names

• Use of ISO630 language codes

                                                             

Standards in free-text fields

• Clear documentation/guidelines on– Consistent wording e.g. collection strength– Use of neutral language– Length of free-text fields– Ordering of information

                                                             

Accessibility

• Special Educational Needs & Disability Act (SENDA) 2001

• Audience

• Language

• Web Accessibility Initiative (WAI)• vischeck tool - http://www.vischeck.com/