DigitalNZ presentation to JISC
Upcoming SlideShare
Loading in...5
×
 

DigitalNZ presentation to JISC

on

  • 369 views

Implementing a national vision. DigitalNZ presentation slides for JISC/UKOLN Survive or Thrive conference, Manchester, June 8th & 9th, 2010. Presented by Andy Neale

Implementing a national vision. DigitalNZ presentation slides for JISC/UKOLN Survive or Thrive conference, Manchester, June 8th & 9th, 2010. Presented by Andy Neale

Statistics

Views

Total Views
369
Views on SlideShare
369
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

DigitalNZ presentation to JISC DigitalNZ presentation to JISC Presentation Transcript

  • Implementing a national vision www.digitalnz.org
  • Covering
    • Getting started & getting stuff done
    • Issues & opportunities
    • Ongoing development & iteration
    • Strategic drivers & reflection
    • Things that worked
  • http://www. flickr .com/photos/em1stuk/2424253260/
  • Getting started & getting stuff done
  •  
  • Four initial projects
    • Search widget
    • Mashup
    • Remix experience
    • Tagging demonstration
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  • 2008
    • May – Governance approval for concepts
    • July – Began software development activity
    • November 11 – Launch of coming home projects
    • December 1 – Launch of full aggregation, custom search, and API service
  • Issues & opportunities
  • shotgun vision  team clarity
    • Work on standards development and dissemination and the provision of advisory and support services to organisations working on digital projects
    •  
    • Developing and implementing a robust framework for prioritising digitisation of significant and important publicly held content in order to make strategic use of public funds for digitisation. The framework would establish approaches to digitisation standards, interoperability, preservation issues, online indexing alternatives, and other relevant criteria.
    •  
    • Progressively enable communities around New Zealand to connect with, access and create content for digital content repositories that reflect their rich histories, stories, cultures and environments.
  • Helping people find share and use New Zealand digital content
  • cannibalising other initiatives  finding your niche
  • limited development capability  vendor contracts
  • Multi-vendor arrangement
    • User experience design
    • Front-end development
    • Search infrastructure
  • time & budget constraints  agile development
  •  
  • reputational baggage  inclusive branding
  • too much effort to participate  low barriers to entry
  • bureaucracy  we’re doing it right now
  • Ongoing development & iteration
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  • Strategic drivers & reflection
  • The focus of content to be included in DigitalNZ Search
  • The balance of effort split between central and distributed tools
  • The balance of effort split between maintenance of existing solutions and development of new solutions
  • The availability of resource to fund digitisation consultancy, workshops, and events
  • Things that worked
  • Have the team articulate a clear and simple vision or mission
  • Start with small exciting projects that people can rally around
  • Be clear about your points of difference
  • Lower barriers to participation
  • Use branding and design to inspire commitment
  • Invest time building strong relationships with collaborators
  • Have deadlines that can’t be moved
  • Once you are in the door you can up-sell the initiative
  • Build for reuse and extensibility from the ground up
  • Iterate in small fast cycles
  • Plan for how to maintain energy after launch
  • Have lightweight governance + a team of experts
  • Get on with it + refactoring in response to change
  •