Meeting User Needs Metadata and Quality

1
Meeting User Needs Metadata and Quality

• Ben Ryan
• HLSI Software Development Manager

2
What are the user needs?

• Solution to real world problems not
  implementations of specifications
• Help and support in adopting these new
  technologies
• Software that allows and assists them to do their
  job

3
How we developed software

• Implemented specifications
• Tested with users for feedback
• Developed interfaces to hide specifications
• Used technology to satisfy user requirements

4
Human aspects of development

• Communicating metadata debate in understandable
  terms
• Technology and specifications important, but not
  to the end user
• Real, busy people who need a solution that fits

5
Human aspects of development cont.

• We spend 100 of our time on this, they spend
  5-10
• Processes can become a barrier
• Metadata collection must become an everyday
  activity

6
Where we went wrong

• Too much software support default values etc
• Not enough software support not enforcing
  rules,
• Assumed ownership would bring responsibility

7
A new process

• The roles
• Educational practitioner
• Information scientist
• Basic versus advanced metadata
• Responsibilities
• Ownership
• JORUM monitoring and evaluation

8
Staff development

• Answering the question Why should I, Im busy
  enough already
• Selling the benefit of quality metadata
• What else?

9
Improved software support

• Integrated spell checker
• Authority lists
• Separated and control basic and advanced metadata
• On-line thesaurus for advanced metadata entry
• Record/track/report metadata review process