This document discusses repository architecture and raises several questions about whether a new architecture is needed given existing solutions that work well. It questions if there are truly new problems or if similar issues have been addressed before by content management systems. It also suggests learning from other domains like content management, document management, records management, open data, and open notebook science. Key issues mentioned are the lack of rich metadata capture and whether institutional repositories have developed in a way that supports new research practices.

1. Repository Architecture
#83
Paul Walk
Technical Manager
p.walk@ukoln.ac.uk
UKOLN is supported by:
www.ukoln.ac.uk
A centre of expertise in digital information management

2. questions
• do we need another ‘architecture’?
– perhaps we can make better use of what already exists (and works well)
• is there anything truly new in this problem space?
• haven’t we been here before (or at least somewhere in the vicinity)?
– Content Management Systems (CMS) of the last six years
• can we learn from other domains?
– CMS
– document management
– records management
– open data - addressable data objects
– open notebook science - workflows
2