MeAggregator
User owned technology
     demonstrator
Initial Aims
• Produce a tool which makes it easier for
  learners to manage their ‘stuff’
• Hence easier to manage their ...
Audience
• People!
• Initially students and staff at our institution
   – But actually, just people
   – Oh, and bears…
Approach
• “Web 3” – using ontologies to support a
  distributed Folksonomical File System (FFS)
• Supporting a trust netw...
Findings & Issues
• Working with 3rd party libraries can cause
  unexpected delays!
• Loosely coupled components can be ve...
More findings & issues…
• There are more services to connect with
  almost every day…
• It is important to build community...
Key take home
Take time to re-evaluate approach & don’t be afraid to change.
                (we should have done it soone...
Upcoming SlideShare
Loading in …5
×

Me Aggregator Project Overview

563 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
563
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Me Aggregator Project Overview

  1. 1. MeAggregator User owned technology demonstrator
  2. 2. Initial Aims • Produce a tool which makes it easier for learners to manage their ‘stuff’ • Hence easier to manage their Digital Identity – And their reputation • Enable users to engage with a Connectivist style of learning
  3. 3. Audience • People! • Initially students and staff at our institution – But actually, just people – Oh, and bears…
  4. 4. Approach • “Web 3” – using ontologies to support a distributed Folksonomical File System (FFS) • Supporting a trust network • Iterative design and refinement • Open Source by license and practice • Loosely coupled software components • Service Oriented Architecture
  5. 5. Findings & Issues • Working with 3rd party libraries can cause unexpected delays! • Loosely coupled components can be very robust, but hard to debug… (no, really?!) • Users have a range of creative uses for the tool (filing system, calendar…) • Some institutional systems are highly politicised
  6. 6. More findings & issues… • There are more services to connect with almost every day… • It is important to build community from day 1 • Building community requires a reasonably high level of resources • Everyone now seems to be interested in Digital Identity
  7. 7. Key take home Take time to re-evaluate approach & don’t be afraid to change. (we should have done it sooner)

×