1 / 12

Enhancing Collection Descriptions for Improved Accessibility and User Experience

Learn how to create high-quality collection descriptions, utilizing standards in language, terminology, and accessibility guidelines. Training provided for record creators.

gcarnes
Download Presentation

Enhancing Collection Descriptions for Improved Accessibility and User Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QA for Collection-Level Description Ann Chapman and Bridget Robinson Collection Description Focus UKOLN is supported by: www.ukoln.ac.uk A centre of expertise in digital information management

  2. 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

  3. 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

  4. 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

  5. QA and Format • RSLP schema • Variation • Added elements • Unused elements • Modified elements • Label changes • Sub-divided elements

  6. 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

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

  8. 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

  9. QA planning • QA relates to: • Data • Software • Build QA into early planning • Document decisions • Train record creators • Create guideline documents

  10. 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

  11. 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

  12. Accessibility • Special Educational Needs & Disability Act (SENDA) 2001 • Audience • Language • Web Accessibility Initiative (WAI) • vischeck tool - http://www.vischeck.com/

More Related